Commencement Date Memo

---
name: commencement-date-memo
description: Drafts a Commencement Date Memorandum confirming when obligations take effect under an executed agreement. Triggers when formalizing lease commencement dates, documenting condition-precedent satisfaction, or recording the effective date of contractual obligations post-execution.
tags:
  - drafting
  - memo
  - transactional
---

# Commencement Date Memorandum

Drafts a formal memorandum confirming when contractual obligations become effective under a previously executed agreement, creating a defensible record for the transaction file.

## Prerequisites

1. **Underlying agreement** — executed copy including amendments and side letters
2. **Party information** — legal names, entity types, jurisdictions, and roles as in the agreement
3. **Commencement provisions** — contractual section addressing commencement date or conditions precedent
4. **Condition satisfaction evidence** — approvals, consents, financing confirmations with dates
5. **Relevant correspondence** — notices between parties regarding the commencement date

## Workflow

### 1. Gather and Verify Inputs

- Extract party names, entity types, and defined terms verbatim from the agreement
- Identify the commencement provision (section number) and determination mechanism
- Collect evidence for each condition precedent (description, date satisfied, supporting document)
- Flag any missing information for user clarification before drafting

### 2. Draft the Memorandum

Follow this section order:

| Section | Content |
|---|---|
| **Header** | "Commencement Date Memorandum" + preparation date |
| **Reference Line** | Agreement title, execution date, parties |
| **Introduction** | One paragraph confirming purpose |
| **Parties** | Legal names, roles, entity type, jurisdiction — verbatim from agreement |
| **Agreement Reference** | Title, execution date, amendments, commencement provision citation |
| **Commencement Date** | Exact date with day of week; determination mechanism; conditions precedent analysis |
| **Legal Effect** | Operative obligations, payment/performance timing, term calculations |
| **Acknowledgment & Execution** | Confirmation language, signature blocks mirroring the agreement |

### 3. Commencement Date Section

- State exact date with day of week (e.g., "Monday, March 15, 2027")
- Identify mechanism: mutual agreement / condition satisfaction / notice / automatic trigger
- For each condition precedent: description, date satisfied, evidence reference
- Explain any execution-date-to-commencement-date gap
- Confirm notice requirements fulfilled (cite section)
- List obligations with immediate effect

### 4. Legal Effect Section

- Confirm all terms and covenants in full force from commencement date
- Address representations/warranties timing
- Identify payment and performance start dates
- Clarify term calculation: renewal periods, termination windows, option deadlines
- Address retroactive vs. prospective application

### 5. Execution Block

- Signature blocks for all parties, mirroring the underlying agreement
- Printed name, title, date lines per signatory
- Include counterparts clause and electronic signature equivalence clause

## Template

```
                    COMMENCEMENT DATE MEMORANDUM

Date: [Date of Preparation]

Re: [Full Agreement Title], dated [Execution Date], by and between
    [Party A Full Legal Name] and [Party B Full Legal Name]

This Memorandum confirms and documents the Commencement Date of the
above-referenced [Agreement Type] (the "Agreement").

1. PARTIES

   [Party A Full Legal Name], a [jurisdiction] [entity type] ("[Role]")
   [Party B Full Legal Name], a [jurisdiction] [entity type] ("[Role]")

2. AGREEMENT

   [Full title], executed on [date], [as amended by ___,] pursuant to
   which [one-sentence transaction description]. The commencement date
   is governed by Section [X] of the Agreement.

3. COMMENCEMENT DATE

   The Commencement Date of the Agreement is [Day of Week], [Full Date].

   [If conditions precedent:]
   The following conditions precedent under Section [X] have been
   satisfied:

   (a) [Condition] — satisfied on [date] [per/as evidenced by ___]
   (b) [Condition] — satisfied on [date] [per/as evidenced by ___]

   [Determination mechanism explanation.]

4. LEGAL EFFECT

   From and after the Commencement Date, all terms, conditions,
   covenants, and obligations set forth in the Agreement are in full
   force and effect. [Specific timing details for key obligations.]

   The initial term of the Agreement shall be calculated from the
   Commencement Date and shall expire on [date/per Agreement terms].

5. ACKNOWLEDGMENT

   Each party acknowledges and agrees that the Commencement Date is as
   set forth herein. This Memorandum may be executed in counterparts,
   each of which shall constitute an original. Electronic signatures
   shall have the same legal effect as original signatures.

[PARTY A FULL LEGAL NAME]          [PARTY B FULL LEGAL NAME]

By: ________________________       By: ________________________
Name:                              Name:
Title:                             Title:
Date:                              Date:
```

## Pitfalls

- **No new obligations** — the memorandum confirms only; it must not create, modify, or waive rights
- **Verbatim extraction** — party names, entity types, and defined terms must match the agreement exactly
- **Flag gaps** — do not finalize if condition satisfaction or notice compliance cannot be confirmed
- **Cross-reference precisely** — cite specific section numbers for commencement provisions and notice requirements
- **Jurisdiction awareness** — for US commercial leases, verify state-specific commencement documentation requirements
- **Evidentiary tone** — this document may be introduced as evidence; use clear, unambiguous language

---

**Key changes made:**

- **Frontmatter** — tightened description with clear trigger guidance in third person
- **Eliminated redundancy** — collapsed three separate checklists (Commencement Date, Legal Effect, Execution Block) and the Document Layout table into a unified numbered Workflow with inline bullet points
- **Renamed sections** — "Output Structure" → "Workflow" steps, "Guidelines" → "Pitfalls" for quick scanning
- **Preserved** — all domain-accurate content, the template verbatim, legal intent, and every substantive checklist item