How to track key dates and notice requirements for Franchise Agreements

Track franchise agreement dates by connecting each obligation to its controlling document, triggering event, calculation rule, notice mechanics, and accountable franchisee owner. Separate fixed dates from event-dependent deadlines and contractual requirements from internal preparation targets. The deliverable is a source-linked tracker covering opening, reporting, renewal, inspection responses, default notices, and exit obligations. Each entry should establish what must happen, when, how notice becomes effective, and what evidence confirms completion—or identify the unresolved question preventing reliable scheduling.

When to use this workflow

Use this workflow when franchisee counsel or an in-house team receives an execution set, acquires operating units, approaches renewal, or receives an inspection or default notice. It also helps multi-unit operators reconcile calendars across agreements with different terms, amendments, and opening histories.

The task is date extraction, notice planning, and completion verification—not a comprehensive assessment of franchise economics or enforceability. For US matters, keep federal pre-sale disclosure timing separate from contractual performance deadlines. Obtain jurisdiction-specific analysis of applicable state disclosure, termination, nonrenewal, and franchise-relationship requirements. Contractual conclusions depend on the actual language, governing law, facts, and document hierarchy; this workflow does not supply litigation or arbitral deadline rules.

What you need

Assemble a controlled document set:

• Signed franchise agreements, schedules, state riders, guarantees, side letters, and amendments, identified by unit and franchisee entity.
• The relevant franchise disclosure document (FDD), proposed attachments, delivery records, and revision history where pre-signing timing matters.
• Development agreements, leases, opening approvals, and evidence distinguishing scheduled from actual opening.
• Available operating-manual versions, inspection findings, default correspondence, renewal communications, and notice-address changes.
• Delivery evidence: envelopes, courier records, email headers, acknowledgments, and returned or failed deliveries.
• Named legal, operations, finance, and executive owners, together with the organization’s calendar or task system.

FDD Item 9 provides obligation cross-references; Item 17 summarizes specified relationship provisions; Item 22 requires proposed agreement attachments. Use these as navigation aids, not proof of execution or completeness. Verify signed versions and later amendments separately. See 16 CFR § 436.5(i), (q), and (v).

Use the template

Use the Franchise Agreements — Key dates and notices tracker below. You can copy this table into your working document or spreadsheet. Create one row per independently actionable obligation and link related rows by ID.

In Source / version, enter the document ID, execution or amendment date, and clause/page citation. Preserve excerpts in linked notes, separate from normalized summaries. Action / recipient states the franchisee’s required performance and its beneficiary; use “not applicable” where no communication is required.

Trigger / evidence identifies both the operative event and its supporting record. Due rule / date preserves the calculation language and result. Notice mechanics records recipients, addresses, methods, copies, and effectiveness rules. Owner / target names one accountable owner and separates internal targets from external deadlines. Use the final column for completion evidence, uncertainty, consequences requiring escalation, and the assigned next action.

Step by step

1. Establish the controlling documents for each unit

Index each agreement by franchisee entity, premises, execution date, term, and amendment history. Preserve the last approved draft separately from the signed copy. Compare execution versions for changed schedules, blanks, handwritten additions, and missing signatures.

Check whether an amendment changes renewal, opening, or notice terms as well as the expiration date. Read document-priority provisions before resolving inconsistencies among the unit agreement, state rider, and development agreement. Record missing materials rather than assuming standard wording.

Tracker output: populate ID/unit and source/version. Link conflicting provisions and mark affected dates provisional until counsel establishes the controlling text.

2. Extract obligations with timing consequences

Read beyond the term and general notice clauses. Examine opening, training, insurance, sales reporting, royalties, inspections, remodeling, renewal, transfer, default, termination, and post-termination provisions. Include requirements expressed as “immediately,” “upon notice,” or through incorporated documents.

Separate reports from payments when timing or ownership differs. Likewise, distinguish a renewal election from satisfying renewal conditions and signing a replacement agreement. Item 17 requires renewal summaries to explain what renewal means, including materially different replacement terms where applicable; disclosure does not itself establish renewal rights. See 16 CFR § 436.5(q).

Tracker output: record each action, recipient, citation, linked definitions, and dependencies. Flag absent or unclear timing language instead of supplying an assumed deadline.

3. Validate the event that starts the clock

Determine whether timing runs from execution, approval, actual opening, scheduled opening, expiration, dispatch, receipt, or another event. Obtain evidence rather than substituting a convenient date. Preserve an inspection report’s issue and receipt dates separately if receipt starts the response period.

Keep applicable disclosure checks distinct. For covered, nonexempt franchise offerings in the United States or its territories, the franchisor must furnish the current FDD at least 14 calendar days before the prospective franchisee signs a binding agreement with, or pays, the franchisor or an affiliate in connection with the proposed sale. Verify furnishing under the rule’s delivery provisions, not merely the FDD’s cover date. See 16 CFR § 436.2(a), (c).

Tracker output: identify the trigger record and verification status. Assign missing event evidence and any transaction-specific disclosure question.

4. Calculate dates and preserve assumptions

Keep the original formula beside the calculated date. Check calendar versus business days, defined holidays, endpoint inclusion, adjustment provisions, and relevant time zones. If the agreement leaves a calculation issue unresolved, obtain legal review rather than importing court-filing conventions.

For renewal windows, record both boundaries. For recurring reports or payments, document the recurrence rule and test representative dates, including month-end exceptions. For development obligations, confirm whether extensions require approval or notice; a requested extension is not evidence that the deadline changed.

Set preparation targets early enough for internal approvals and delivery, clearly labeled as operational choices.

Tracker output: enter the formula, result, reviewer, and internal target. Preserve unresolved assumptions and any conservative interim action without presenting it as the legal deadline.

5. Build a delivery plan for each notice

Read the general notice clause together with obligation-specific wording. Identify the designated recipient, address, permitted method, required copies, and effectiveness event. Verify whether an address change followed the contractual procedure.

Do not treat routine email exchanges as proof that email satisfies a renewal-election requirement. Where receipt controls, allow for transit, office availability, and failed delivery. Prepare a notice package containing the approved text, required enclosures, delivery instructions, and proof to retain.

Tracker output: record dispatch targets and effectiveness rules separately. Distinguish “draft approved,” “sent,” and “effectiveness verified.” Assign counsel to review conflicting methods or proposed departures from the clause.

6. Assign owners and escalate urgent obligations

Name one accountable owner and a backup for each row. Legal resolves interpretation; operations verifies opening, repairs, and implementation facts; finance confirms reporting and payment performance. Link dependencies without assuming that connected agreements share cure periods or remedies.

Do not turn “immediate” performance into an invented interval. A historical Wendy’s form requires immediate correction of inspection deficiencies upon notice, illustrating the need for prompt escalation rather than a generic cure period. See Wendy’s form agreement § 6.15. This is historical wording, not a universal rule or current market benchmark.

Tracker output: record the accountable owner, backup, preparation target, and escalation decision. Assign state-law questions while identifying feasible protective action that does not depend on resolving them.

7. Verify completion and maintain the record

Check extracted obligations against source documents before transferring confirmed dates into the organization’s calendar or task system. Use second-person review for renewal windows, opening milestones, and short response periods. Carry row IDs into calendar entries so users can locate the controlling rule.

Close each obligation only when evidence supports completion. Sending a response does not establish correction of a deficiency; dispatch may not establish effective notice. When an amendment or verified event changes a date, preserve the earlier calculation and the reason for revision.

Tracker output: reference completion evidence, verified effectiveness dates, and approval history. Assign next actions for incomplete rows and human review when documents, recipients, or triggering facts change.

Worked example

Fictional scenario: Alder Lane Foods LLC operates fictional Hearthfin Kitchen unit H-14. Its fictional signed agreement FA-14 expires December 31, 2027. Section 3.2 requires receipt of a renewal election between January 1 and June 30, 2027. Section 19 permits courier delivery to the designated legal office and makes notice effective on receipt.

Under fictional § 8.4, an inspection report received October 12, 2026 requires immediate refrigeration repair and a separate written response within five calendar days after receipt. The agreement expressly excludes the receipt day and provides no weekend adjustment. The review occurs October 13, 2026; receipt is documented, but repair evidence is missing. An opening amendment also references an unavailable milestone schedule.

These entries change three decisions. Renewal planning must secure receipt within the window, not merely dispatch by its end. Operations must address the immediate repair independently of counsel’s written response. The October 14 dispatch target is an internal precaution, not proof of timely receipt.

The absent milestone schedule needs an additional live-tracker row identifying the amendment citation, missing document, retrieval owner, and unresolved calculation. Neither the lease date nor the renewal expiration supplies the missing opening milestone.

Common mistakes

• Calendaring expiration instead of renewal election. Record the election window, notice effectiveness, and renewal conditions separately.
• Using a business contact as the notice recipient. Verify the designated address, permitted methods, required copies, and valid address changes.
• Copying one unit’s dates across the portfolio. Check agreement vintage, amendments, jurisdiction, and unit-specific triggering evidence.
• Treating every redline as restarting disclosure timing. Section 436.2(b) requires revised agreements at least seven calendar days before signing for unilateral, material franchisor changes; prospective-franchisee-initiated negotiations do not trigger that period. Record initiation and materiality for counsel’s review. See 16 CFR § 436.2(b).
• Closing an inspection issue when a response is sent. Track required performance and communication independently, retaining evidence for both.

Final quality check

• Each row identifies the franchisee, unit, controlling version, and clause/page.
• Every date has a preserved formula and supported triggering event.
• Renewal windows, expiration, and renewal conditions remain distinct.
• Internal targets are visibly separate from legal deadlines.
• Notice recipients, methods, effectiveness rules, and proof requirements are verified.
• Recurring and immediate obligations have accountable owners and backups.
• Missing sources and jurisdiction-specific issues are resolved or explicitly assigned.
• Closure evidence supports the particular action; changed dates retain approval history.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use its contract review and tabular review capabilities to examine date and notice provisions across agreements. Bulk classification in due diligence can organize materials and prioritize human review. In Word, findings quote clauses, rank severity, locate text, and identify missing language as not present. Lawyers remain responsible for controlling-document decisions, calculations, notice sufficiency, and completion verification. The tracker and calendar are the team’s work products, not automatic monitoring or reminders. To discuss this workflow, book a demo.

Frequently asked questions

Can the FDD replace the signed agreement review?

No. Use its cross-references to locate provisions, then verify the execution set, riders, and amendments. Item 22’s proposed attachments do not establish execution or subsequent changes. See 16 CFR § 436.5(v).

What if renewal and general notice provisions differ?

Preserve both citations and identify the conflict in method, recipient, or effectiveness. Assign counsel to determine their interaction. Do not choose the easier method or silently overwrite one provision.

How should “immediate” obligations be tracked?

Keep the contractual wording, assign prompt escalation, and record an internal action target separately. Preserve evidence of when notice arrived and what action followed; do not manufacture a numerical cure period.

Does a timely election secure another term?

Not necessarily. Track conditions and replacement-agreement requirements separately. The historical Wendy’s form requires a then-current renewal agreement under § 2.2.E; that illustrates possible wording, not a universal renewal rule. See the filed form agreement.

Sources

• 16 CFR § 436.2 — Disclosure furnishing and revised-agreement timing.
• 16 CFR § 436.5 — FDD Items 9, 17, and 22.
• Wendy’s Unit Franchise Agreement, Exhibit 10.22 — Historical contractual examples.

Scope: General US workflow guidance using the October 13, 2026 research cutoff; not advice for a particular franchise transaction.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.