Brand standard exception records retention timeline: what to keep before a franchise system transition

Short answer

Before a franchise portal or audit platform is replaced, inventory the variance register and the records that explain it: superseded manual versions, closed inspection findings, approved, denied and expired exception requests, and the conditions and expiry dates on each decision. Migrations load active locations, current standards and open items, so these drop first. Note each record class's system, years covered, owner and the old system's access end date, and leave the decision to keep any of it to the franchisor's executives and counsel.

Visual briefFull-size diagram
A horizontal timeline running from six months before a franchise portal switch to the old portal's access end, with five record types; denied requests, expired variances, closed findings and superseded manual versions fade out at their drop points unless preserved, while active variances carry over.
Illustrative transition timeline for a fictional franchisor. Real drop points depend on the migration scope and the vendor contract.

This retention timeline is part of the brand standard exception approvals guide, which maps how inspection records and decisions join across systems. This page answers a time question: in the months before a transition, what disappears, in what order, and who has to approve keeping it.

Why a transition drops variance history

A migration is scoped around what the new system needs on day one: active locations, the current manual, open findings and pending requests. History has no balance and no open status, so it is usually out of scope by default.

Approved variances that are still running are the most dangerous to lose. If the new audit platform does not know a location has an approved variance, it flags that location as non-compliant at the next inspection. Expired and denied requests are the least likely to move, yet they hold the reasoning: why one location got an exception and another did not.

Retention rules do not help here by default. The FTC Franchise Rule requires franchisors to keep a copy of each signed disclosure receipt for at least three years, and sample copies of each materially different disclosure document for three years after the fiscal year it was last used. It sets no comparable period for inspection findings or variance decisions. Those follow the franchisor's own retention schedule, which is why they are easy to leave behind.

The retention timeline (Illustrative)

Illustrative and invented for this page. A fictional franchisor with a 240-person head office and field team is moving from an older franchise portal to a new operations platform. Months are counted from the go-live date.

WhenMilestoneWhat happens to variance historyDecision needed from
Month -6Migration scope agreedActive variances included as a flag; history marked out of scopeFranchise operations director, with IT
Month -4Data mappingConditions and expiry dates do not map to the new flag fieldOperations director
Month -2Test loadDenied and withdrawn requests excluded from the loadOperations director
Month 0Go-liveNew platform holds current manual and open items onlyExecutive sponsor
Month +3Old portal read-onlyStaff stop adding notes; email approvals stay in mailboxesIT and operations
Month +6Old portal access ends under vendor contractAnything not exported is goneChief executive and general counsel, before this date

The last row sets the real deadline. Go-live dates move; access end dates are usually written into the vendor contract. Ask for that date first.

What disappears first, and roughly how long each record lasts

Each record class has its own exposure. The order below is the usual order of loss in a transition, earliest first. Retention periods vary by franchisor and are set by its schedule and counsel, so the middle column describes typical patterns, not rules.

Record classTypical life in practiceWhen it is usually lostWhy it matters
Denied and withdrawn exception requestsKept only as long as the old portal runsExcluded at test loadShows where the franchisor held the line
Expired variances with conditionsKept only as long as the old portal runsOut of scope at mappingShows what was allowed, for how long, and whether it was rechecked
Closed inspection findings and photosOften a rolling window of past audit cyclesOld audit platform switch-offTies each request to the problem it answered
Superseded operations manual versionsOften overwritten when the intranet is updatedAny document library migrationShows which version of a standard was waived
Email approvalsAs long as mailboxes are retainedMailbox clean-up after departuresOften hold the reasoning the portal lacks
Active variancesCarried over, often reduced to a flagRarely lost, but conditions arePrevent false non-compliance findings

Manual versions deserve a separate note. U.S. franchisors disclose the operations manual's table of contents under Item 11, with the pages per subject, unless the prospective franchisee may view the manual. Every exception is an exception to a particular section of a particular edition. FTC staff guidance has also said that a new fee imposed through the operating manual, if not disclosed and included in the franchise agreement, may be an unfair practice. A franchisor that keeps manual versions can show what any location was held to on any date. Supplier approval requests are a related class worth counting: Item 8 asks how approvals of alternative suppliers are granted and revoked, and a disclosed process usually leaves a record.

Who must approve keeping each record

A consultant inventories; the franchisor decides. Do not recommend keeping anything the franchisor has no authority or reason to keep.

  • Franchise operations director. Confirms what exists, which years and regions used email, and where the variance register lives. Can propose a scope change.
  • Chief executive. Approves any decision to export and retain history beyond the migration scope, and any later licensing discussion.
  • General counsel. Checks the retention policy, franchise agreements and confidentiality terms, especially for franchisee-supplied photos, permits and lease extracts. Ownership questions are covered in franchise data ownership.
  • IT or the platform vendor. Confirms export formats and the access end date. Never assume an export exists until they say what the old portal can produce.

The who can license page sets out the same roles as a decision tree for the licensing question.

The inventory a partner can take away

One row per record class: system, years covered, rough volume, owner, access end date. Metadata only. Never ask for portal exports, photos or franchisee correspondence. The referral brief template turns that inventory into a one-page note for the introduction.

Transitions often follow a change of control. The private equity franchise platform guide and the franchisor bankruptcy page cover how those events change timing and authority, and the franchise consultant partnership page covers the partner side.

The franchisor needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Whether buyers want variance history, what rights review concludes about franchisee material, and any price all stay unknown until SourceX reviews it.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a franchisor has a written access end date for its old portal and variance history outside the migration scope, register as a partner, check it against who qualifies and read the program terms before you brief the franchise operations director.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is there a legal rule for how long a franchisor must keep variance records?

The FTC Franchise Rule sets retention periods for signed disclosure receipts and disclosure document versions, not for inspection or variance files. Those follow the franchisor's own retention schedule and legal advice, which is why they are easy to drop in a migration.

Should a consultant recommend keeping everything just in case?

No. Recommend an inventory, not a retention decision. Whether to keep a record class, and for how long, belongs to the franchisor's executives and counsel, under its retention policy and franchise agreements.

What is the single most urgent date to ask for?

The date the old portal or audit platform becomes inaccessible under the vendor contract. Go-live dates move; access end dates are usually fixed in writing.

Sources

  1. ecfr.gov/current/title-16/chapter-I/subchapter-D/part…
  2. ecfr.gov/current/title-16/chapter-I/subchapter-D/part…
  3. ftc.gov/system/files/ftc_gov/pdf/Franchise-Staff-Gui…
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment