Clean Records, Lower Risk: Franchise Litigation Documentation as Defence

Franchise litigation documentation is the record a system can produce once a dispute arrives: support delivered and dated, policies published with acknowledgements, standards enforced consistently, decisions traceable to a person and a reason. Better records usually narrow a dispute. They also cut both ways, which is why retention belongs with counsel.

None of this is legal advice. I am a founder describing what the operations side of a system can hand to counsel when a matter starts, and what it costs when the answer is a shared drive and three people's memories.

Almost none of that work is legal work. It is filing, cadence and naming conventions, done in ordinary months by somebody whose job title has nothing to do with disputes.

What a matter actually asks a franchisor to produce

Disputes in franchising are rarely arguments about the agreement. What gets contested is everything that happened after it was signed.

A termination turns on notice, cure periods and whether the standard was applied the same way elsewhere. A failure-to-support claim is a question about what was delivered, to whom and when. An encroachment argument turns on what a candidate was told before signing, against a disclosure document whose contents the FTC's Franchise Rule compliance guide already prescribes. In each of those, the record gets assembled from systems nobody built as evidence: a field-visit app, a learning platform, a portal, an email account, and the phone of a coach who left last year.

Two properties decide whether that assembly goes well: whether the record is contemporaneous, and whether the records agree with each other. The second is where franchising has a known weakness. A brand that scores itself keeps two accounts of the same location: self-reported scores pulled 33% further from actual audit results during 2020, on FranConnect's operations index. In an ordinary quarter that is a management problem. In a dispute it is a pair of exhibits saying different things about the same store, produced by the same brand.

The four record classes franchise litigation documentation turns on

Ask counsel what they wish existed at the start of a matter. The list is short and dull.

1. Support delivered, dated, per location. Visits, calls, escalations, what was asked and what was sent back. Capacity is why it is thin: the field span FranConnect measured in 2020 was 34 units to a consultant, after a pandemic-era rise it puts at more than 21%. A coach carrying that load logs the exceptional visit, not the ordinary one — which inverts the file's value.
2. Policies published, dated and acknowledged. Not the fact that a policy exists. The version that was in force in the month at issue, and evidence the operator received it.
3. Standards applied consistently. Findings, notices and outcomes across the network, in a form that can be compared operator to operator.
4. Decisions traceable to a person and a reason. Who approved the exception, on what basis, on what date.

None of that list requires a lawyer. All of it requires somebody to have decided, in advance, where each class of record lives and who is accountable for it being complete.

Consistency is the record that decides more of these than founders expect

The commonest defect I see is an enforcement pattern the brand cannot explain.

A standard is enforced at three locations and quietly waived at a fourth, because the fourth is a fifteen-unit operator mid-way through a development commitment and nobody wanted the conversation. Each decision was commercially sensible. Assembled into a table by somebody with an interest in assembling it, they read as something else.

Ruthless enforcement is not the fix. Make the exception a documented decision rather than an absence: who granted it, why, for how long, and what the operator agreed to in return. An exception with a rationale and an end date is a judgement. The same exception with no record is a pattern.

A buyer reads that table too, and there it is priced. Diligence treats termination and dispute history as a signal about how a system selects and supports operators — one of the mechanisms behind a franchise business valuation multiple, and why the private equity franchise investment risks that survive every deal are so often about evidence quality.

Records cut both ways, and pretending otherwise is the naive version

Everything you keep is also discoverable. The field note speculating about an operator's divorce, the thread where somebody calls the standard unreasonable, the message where a director agrees the territory was oversold — all of it is the record too, produced alongside the helpful material. More documentation buys you a bigger production, read in full by somebody hostile.

Three consequences worth putting to counsel rather than deciding in an operations meeting.

Retention is a policy decision, not a storage default. How long field notes, interaction logs and internal messages are kept should be set deliberately, applied uniformly, and suspended properly when a matter is anticipated. A vendor's default period is not a policy, and selective deletion once a dispute is live is a worse problem than having kept the material.

Write field notes for the reader you will eventually have. Observations, not diagnoses: what was seen, said and agreed. Not speculation about an operator's finances, health or marriage, none of which a coach can substantiate and all of which gets read aloud.

A written policy nobody follows is worse than none. It creates a standard the brand is then measured against by its own document — the one place where more paper reliably makes things worse.

So record quality narrows the range of outcomes rather than guaranteeing a good one. A brand with a clean, contemporaneous file usually finds disputes narrow earlier, because the facts stop being arguable. A brand without one is negotiating about what happened.

The version that takes a quarter and no budget

Three moves, cheapest first.

Name the four record classes and give each an owner. Most brands already hold three, in systems nobody has queried together.

Pull one location's whole file as a rehearsal. Everything the brand holds about a single store for three years, assembled by someone who was not involved. What takes a fortnight now takes a fortnight when it matters, at a much worse moment.

Get one retention schedule drafted by counsel and applied to every system, including the messaging tool nobody thinks of as one. While counsel is looking: anything used to judge an operator should be observed rather than self-reported, or it will contradict a record you also hold.

None of that survives as a project. It survives as somebody's routine — the same routine that turns a documented operating system into a number at exit, which is the argument in sell franchise business premium valuation.

The file gets built in the quiet years or not at all. By the time a matter has a number, you are finding out what your records say, not deciding it.

A buyer eventually reads the same file an adversary would: sell franchise business premium valuation.