How to extract obligations with source references for Franchise Agreements

Extract franchise agreement obligations by assembling the applicable documents, separating each required action, and linking it to exact clause and page references. Capture payment formulas, operating standards, event-driven duties, and conditions for renewal or transfer without stripping out exceptions. Verify definitions, amendments, notice mechanics, and missing incorporated materials before assigning implementation owners. The deliverable is a franchisee-focused obligations register showing what must happen, when, who is responsible, and the source supporting each conclusion—including unresolved questions that prevent reliable implementation.

When to use this workflow

Use this workflow when franchisee counsel or an in-house legal team receives an execution set, acquires an operating unit, or reconciles obligations across existing locations. It also supports pre-signing review, provided proposed obligations remain distinct from executed commitments.

The task is extraction and operational handoff, not a complete assessment of franchise economics or enforceability. Start with one unit and its related agreements before extending the register across a portfolio.

This guide uses a US orientation and an October 13, 2026 research cutoff. The federal disclosure provisions cited below concern covered, nonexempt offerings involving US franchises; they do not supply comprehensive franchise-relationship protections. Obtain jurisdiction-specific analysis where state disclosure, termination, nonrenewal, restrictive-covenant, or enforceability questions affect a row. Contract rights also depend on the actual language, facts, and deal context. See 16 CFR § 436.2.

What you need

Collect the franchise disclosure document (FDD), franchise agreement, state riders, schedules, guarantees, development agreement, lease, side letters, amendments, and available operating-manual versions. Include inspection reports, notices, opening-date evidence, and renewal or transfer correspondence relevant to current duties.

Item 22 requires attaching proposed agreements regarding the offering to the FDD. These attachments are collection leads, not proof of execution. Verify signed versions separately. See 16 CFR § 436.5(v).

Before extraction, establish:

• A document index identifying unit, version, execution status, and missing attachments.
• Searchable files checked against page images, particularly fee tables and handwritten changes.
• The franchisee entities, guarantors, locations, and internal operating owners.
• A date reference sheet distinguishing execution, scheduled opening, actual opening, and expiration.
• A status convention separating verified duties, conditional requirements, and unresolved questions.

Do not silently substitute a current manual for the referenced version. Record the supplied version and investigate which provisions apply, including any contractual authority to change standards.

Use the template

Use the Franchise Agreements — Obligations register below. You can copy this table into your working document or spreadsheet. Keep one independently actionable obligation per row and connect related rows through their IDs.

In Source / version, record the document ID, section, printed page, and PDF page when different. Cite relevant definitions, riders, and amendments alongside the operative clause. Preserve exact excerpts in source notes keyed to the row ID; the action column contains your normalized instruction, not purported contract text.

Use Basis / qualifications for calculation inputs, exceptions, dependencies, and remedy cross-references. Use Owner / evidence for the accountable internal person and expected proof of performance. Assigning a controller does not change the entity contractually responsible for payment.

State gaps explicitly. “Opening date unverified—minimum applicability unresolved” is more useful than a blank cell. Mark document-collection rows as review issues, so they are not mistaken for contractual duties. The recommendations below describe a working method, not a legally prescribed register format.

Step by step

1. Establish the document set for each unit

Assign stable document IDs and preserve proposed, approved, and executed versions separately. Compare the execution copy against the approved draft, including signatures, schedules, blanks, riders, and handwritten changes. Read amendment and priority provisions before deciding which conflicting term controls; file chronology alone is insufficient.

Group portfolio documents by brand, jurisdiction, vintage, unit type, and amendment status. Do not apply one location’s fee schedule to another without supporting language.

Register output: populate unit and source fields. Add a clearly labeled review issue for each missing document that prevents extraction, with a collection owner.

2. Use disclosure cross-references as a map

Read FDD Item 9 alongside the agreements. It requires a table of principal franchisee obligations with contractual and disclosure cross-references. It is neither counsel’s prescribed format nor a completeness guarantee. See 16 CFR § 436.5(i).

Follow relevant cross-references, then read the full agreement for training, approved suppliers, staffing, insurance, reporting, technology, confidentiality, transfers, and post-termination conduct. Compare disclosure summaries with operative wording and preserve discrepancies as questions.

Distinguish affirmative duties from conditions for exercising rights. Renewal prerequisites belong in the register but are not an unconditional duty to renew.

Register output: create recurring, event-driven, and conditional rows, supported by agreement citations rather than FDD references alone.

3. Split clauses into actionable duties

A clause requiring record retention, monthly reporting, and inspection access usually needs separate rows because owners, timing, and evidence differ. Capture the actor, beneficiary, conduct, trigger, exceptions, and any linked remedy for each.

Preserve qualifications when normalizing language. “Provide access on the notice specified in § 12” must not become “provide unrestricted access.” Trace definitions and cross-references before marking the row verified. Separate guarantor obligations from franchisee obligations even where one executive coordinates both.

Check extracted text against page images, especially negatives, percentages, dates, and subsection lettering. Do not reconstruct uncertain OCR from expected wording.

Register output: add precise action statements and source excerpts; flag incomplete reference chains for legal review.

4. Extract payment mechanics, not just rates

For royalties, advertising contributions, technology charges, and audit costs, capture the calculation base, exclusions, minimums, escalation, payment frequency, reporting dependencies, and debit authorization. Cite the applicable sales definition and payment provision together.

The historical Wendy’s form illustrates why: §§ 4.2 and 4.5 combine a royalty minimum and escalation mechanism with a gross-sales definition addressing business-interruption proceeds and uncollected credit sales. This is historical wording, not current pricing or a market benchmark. See the SEC-filed form agreement.

Ask finance to test the actual formula against refunds, discounts, delivery-platform receipts, and insurance proceeds. Separate contractual inputs from accounting assumptions and retain supporting calculations outside the concise register row.

Register output: record formula components, finance ownership, and unresolved treatment questions without assuming exclusions.

5. Connect operating standards to changes and inspections

Read manual-incorporation, system-change, capital-expenditure, and inspection clauses together. Separate the agreement’s compliance obligation from specifications contained in a manual or notice. If those specifications are unavailable, identify what cannot yet be implemented or costed.

The historical Wendy’s form allocates costs for prescribed system changes in § 6.17 and addresses inspection cooperation and immediate correction upon notice in § 6.15. These illustrate contractual requirements, not a universal statutory correction period. See the filed agreement, §§ 6.15–6.17.

Distinguish correction deadlines from any separate default notice or cure mechanism. Do not treat a remedy provision as extending the performance deadline without supporting language.

Register output: link operating rows, manual versions, notices, spending dependencies, and remedy references. Assign missing specifications and unclear implementation periods for resolution.

6. Resolve triggers, notices, and conditional rights

Distinguish fixed dates from periods measured after opening, notice receipt, inspection, transfer requests, or expiration. Record the trigger and evidence before calculating a date. Capture recipients, delivery methods, receipt provisions, and the clause’s treatment of calendar or business days.

For renewal, extract election timing and prerequisites separately. Item 17 requires specified relationship summaries and cross-references, including an explanation of renewal and materially different replacement terms where applicable. Disclosure does not itself create a renewal entitlement. See 16 CFR § 436.5(q).

Register output: mark each date verified, provisional, or not yet calculable. Link renewal prerequisites without presenting their satisfaction as guaranteed renewal.

7. Verify and hand off the register

Conduct a source-to-register pass for omitted duties and a register-to-source pass for unsupported summaries. Recheck rows affected by amendments. Have finance validate economic inputs and operations confirm that actions and completion evidence are understandable.

Keep pre-signing disclosure checks separate from operating obligations. For covered transactions, § 436.2(a) requires the current FDD at least 14 calendar days before signing a binding agreement with, or paying, the franchisor or an affiliate in connection with the sale. Section 436.2(b) requires revised agreements at least seven calendar days before signing following unilateral material franchisor changes; franchisee-initiated negotiated changes do not trigger that period. Record initiation and materiality rather than treating every redline as restarting a waiting period. See 16 CFR § 436.2.

Register output: assign verification status, implementation owner, and completion evidence. Give every unresolved issue a decision owner and next action.

Worked example

Fictional scenario: Cedar Lantern Foods LLC operates Unit A under an agreement with Hearthway Kitchens Inc. Counsel receives signed FA-01, signed rider R-01, and inspection notice N-01. All parties, documents, provisions, and amounts below are invented.

FA-01 § 5.2 requires monthly royalties of 3% of defined sales, subject to a $600 minimum, by the tenth of the following month. R-01 § 2 expressly overrides that minimum for the first three operating months. FA-01 § 9.4 requires equipment specified in bulletin B-01 within 60 days after opening. Section 11.2 requires correcting listed inspection deficiencies within ten calendar days after receipt, determined under § 15.3. Opening confirmation, B-01, and evidence of notice receipt are missing.

The rider prevents finance from applying the minimum merely because it appears in the base agreement. Its applicability still requires opening evidence. The equipment row cannot support procurement or a final deadline without the bulletin and opening date. The inspection scope is known, so operations can begin corrections while counsel verifies receipt; an unresolved calendar date is not a reason to postpone known work.

Common mistakes

• Treating Item 9 as exhaustive. Read operative agreements and incorporated materials; use disclosure references for navigation.
• Recording only a royalty percentage. Preserve definitions, minimums, escalation, and reporting dependencies.
• Using execution as every timing anchor. Verify whether opening, expiration, or receipt controls instead.
• Marking missing manual specifications verified. Identify the unavailable material and affected duties.
• Combining franchisee and guarantor duties. Separate actors and performance requirements, even with a shared internal owner.

Final quality check

• Each verified row identifies its unit, contractual actor, and applicable version.
• Clause and page references match source images and retained excerpts.
• Definitions, riders, amendments, and exceptions accompany affected duties.
• Payment formulas preserve calculation bases and qualifications.
• Dates identify their triggers, receipt rules, and supporting evidence.
• Conditional rights remain distinct from unconditional duties.
• Every duty has an implementation owner and expected completion evidence.
• Open issues are resolved or explicitly assigned, not obscured by a general “reviewed” status.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review supports selecting the represented party in Word and giving deal-specific instructions; findings quote clauses, locate text, rank severity, and identify missing language as not present. Tabular review supports work across documents, while due diligence classification can organize materials and prioritize human review. The register remains your work product: lawyers verify sources and operational owners confirm implementation. Book a demo to discuss this workflow.

Frequently asked questions

Should the FDD or signed agreement supply the obligation?

Use the FDD to locate and compare disclosures. Verify operative duties against signed agreements, riders, and amendments. Preserve discrepancies for legal review rather than silently selecting one account.

Can one register cover multiple locations?

Yes, if each row identifies applicable units and source versions. Separate exceptions for opening dates, riders, fee schedules, and renewal terms. A shared brand does not justify copying another unit’s assumptions.

What if a deadline depends on an unavailable notice?

Record the timing rule and relevant notice clause, mark the date unresolved, and assign collection of the notice and receipt evidence. Do not substitute an email timestamp unless the contractual provisions support that trigger.

Should termination consequences be included?

Link remedies and cross-default provisions to affected duties. Extract post-termination actions separately. Assign jurisdiction-specific termination and enforceability questions for legal analysis rather than resolving them through an operational summary.

Sources

• 16 CFR § 436.2 — Obligation to furnish documents.
• 16 CFR § 436.5 — Disclosure items.
• Wendy’s International, Inc., Unit Franchise Agreement, Exhibit 10.22, historical wording illustration only.

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.