Skip to content

Systems and records

Franchise operations exception data: mapping brand and local approvals

By SourceX Editorial · Reviewed by Noah Loul ·

10 sections

Short answer

Represent a franchise exception as one case with two approval tracks. The brand track records the standard deviated from, the clause or manual section that lets the franchisor allow it, and who approved on the franchisor's behalf. The local track records the franchisee owner's decision and any regulator, landlord or permit sign-off. Link each approval to its authority document and order, so the record shows why the deviation was allowed.

Provenance trail

Franchise operations

This page covers franchise operations exception data: mapping brand and local approvals.Illustrative

Key takeaways

  • A franchise exception often needs the brand's permission and a local one; a single approved status hides which authority decided.
  • The franchise disclosure document points to the brand's authority: Item 8 for suppliers, Item 11 for system data access, Item 12 for location approval.
  • Record each approval as its own event with the deciding agent, the party they acted for and the manual version in force.
  • Local regulators can be the deciding authority; under the Food Code model a variance is issued by the regulatory authority, not the brand.
  • Mark approvals documented, reported or unknown, and keep refused requests, because they show where the standard's boundary sits.

What makes a franchise exception different from an ordinary operating exception?

A franchise exception answers to more than one authority. An ordinary exception, such as a late shipment or a refund outside policy, is approved inside one company. A franchise exception, such as a unit using a supplier that is not on the approved list or changing a process the operations manual fixes, needs the brand's permission because the franchisor sets standards, and often a local permission as well, because the franchisee runs the unit and local regulators, landlords and permit offices have their own say.

The federal Franchise Rule builds that split into the definition of a franchise. One of its elements is that the franchisor has significant control over, or gives significant assistance in, the franchisee's method of operation. That control is what generates the exception requests in the first place; the franchisee's local responsibility is what makes a brand approval alone insufficient.

For anyone turning these cases into training or evaluation data, the consequence is simple. A record that says only "exception approved" teaches nothing about the most important part of the decision, which is who had the authority to allow the deviation, under which document, and whether a second authority also had to agree.

Where the brand's authority over an exception is written down

The brand's authority sits in three places: the franchise agreement, the operations manual it incorporates, and the franchise disclosure document that summarizes both for prospective franchisees. The disclosure document is the easiest to read and the most standardized, because the Franchise Rule fixes its items.

Item 8 is the core of most supply exceptions. It requires the franchisor to disclose what the franchisee must buy from the franchisor, its designee, approved suppliers or to its specifications, and how the franchisor grants and revokes approval of alternative suppliers, including whether its criteria are available to franchisees. Item 11 covers required computer systems and whether the franchisor has independent access to the data they generate, which tells you where exception records are likely to live. Item 12 covers whether the franchise is for a specific location or one the franchisor approves, which governs relocation and site exceptions.

Where the brand's authority over an exception is written down
Exception typeBrand authority to look forLocal authority that may also applyWhere the record usually lives
Supplier or ingredient substitutionItem 8 approved-supplier terms and the manual's specificationsFranchisee owner; health regulator if the change affects a food safety processSupplier approval requests, purchasing system, email
Equipment or fixture deviationManual equipment standards; Item 8 for required purchasesBuilding or fire permit office; landlord under the leaseRemodel tickets, permit files, vendor quotes
Process change requiring a varianceManual procedure and brand food safety standardRegulatory authority that issues the varianceVariance application, HACCP plan, brand quality file
Relocation or site changeItem 12 location approval termsLandlord, zoning or permit officeReal estate file, franchise development tracker
Local menu, service or promotionAgreement terms on what may be sold and marketing standardsFranchisee owner; state or local rules on the offerMarketing approval tool, field consultant notes
Hours, staffing or service-area deviationManual operating standards; territory termsLease hours clause; local ordinancesField audit reports, POS settings history

The franchise agreement and authority mapping worksheet

The worksheet turns one exception into one case record with both approval tracks side by side. Fill one row set per case. A team can keep it as a spreadsheet tab or as a table in whatever system already logs exception requests; the field names matter less than the rule that every approval points to the document that gave the approver authority.

Example values in the third column are illustrative. Leave a field blank and mark it unknown rather than inferring it from the outcome; an approval that was assumed because the change went ahead is exactly the error the worksheet exists to catch.

The franchise agreement and authority mapping worksheet
FieldWhat to recordExample value (illustrative)Why it matters for a model
Case and unitCase ID, unit ID, operating legal entity, date openedEXC-0412, unit 118, franchisee LLC, opened in MarchSeparates the unit's decision from the brand's and keeps cases joinable
Exception typeOne value from a fixed list such as supplier, equipment, process, site, offer, hoursSupplier substitutionLets a model learn which authority each type usually needs
Standard deviated fromManual section and its version or effective date at the time of the requestManual 4.2 produce specifications, revision in force that quarterA decision is only right relative to the standard then in force
Brand authorityAgreement clause, disclosure item or manual section that lets the franchisor approve or refuseItem 8 alternative-supplier approval processShows where the approver's power comes from
Brand decisionApprover role, acting on behalf of whom, decision, conditions, expiryField consultant for the franchisor, approved for 90 days, supplier must pass auditCaptures delegated and conditional approvals
Local decisionFranchisee owner or operator decision and dateOwner approved the cost and the trialThe franchisee carries local responsibility and cost
External authorityRegulator, landlord or permit office, document ID, statusNot required for this caseSome deviations are lawful only with a local permission
Order and conflictsWhich approval came first, whether one was conditional on the other, how disagreement was settledBrand approval conditional on local supplier auditSequence carries most of the reasoning
OutcomeWhat happened, any follow-up audit result, whether the exception was renewed, ended or became the standardRenewed once, then supplier added to approved listLets a model connect decisions to results
Record authorityWho holds each document, any confidentiality term, whether it may leave the systemBrand file held by franchisor; owner email held by franchiseeDecides what can be shared and by whom

How do you assemble a case when its pieces sit in different systems?

Start from the brand's request log and pull the local evidence toward it, not the other way round. The franchisor's approval tool, quality file or field audit system usually gives each request an identifier and a date; the franchisee's side of the story sits in email, the owner's files, the permit folder and sometimes the POS settings history. Use the brand's case ID as the key and attach local documents to it by unit and date window.

Expect three kinds of gap. Some requests were made and settled by phone, so only the outcome exists. Some local documents, such as a landlord consent, were never shared with the brand. And some field consultant notes describe several requests at once. Record each gap in the worksheet instead of guessing a match, and split combined notes into one case per decision.

Pull a small pilot first, around a few dozen cases from one region and one quarter, and fill the worksheet by hand. The pilot shows which fields the systems can supply automatically, which need a person to read documents, and how often the local track is missing. That share, more than the total case count, tells you whether the set is useful.

How should the two approval tracks be linked in the data?

Model each approval as its own event attached to the case, with the agent who decided, the role they acted in, and the party they acted for. Do not collapse two approvals into one status field. A flat field cannot say that a field consultant approved on the franchisor's behalf, that the owner approved for the franchisee, and that the health regulator's variance was a separate condition.

The W3C PROV ontology offers a ready vocabulary. In PROV-O an activity is associated with an agent through wasAssociatedWith, optionally with a plan, and delegation is expressed with actedOnBehalfOf, where the delegating agent also bears responsibility. Mapped to franchising, the approval is the activity, the operations manual section is the plan, the field consultant is the agent, and the franchisor is the party on whose behalf the consultant acted.

Conditions deserve their own field rather than a note. A brand approval that holds only until a supplier audit, for a fixed number of days, or only if the regulator agrees is a different decision from an unconditional one, and a model trained on the outcome alone cannot tell them apart. Record the condition, who had to satisfy it, and whether and when it was satisfied.

Keep requests that were refused or withdrawn. A dataset of approved exceptions alone shows a model only where the line was crossed with permission. Refusals, and the reasons given, show where the line is.

Which constraint would a generic training example miss?

The local regulatory layer is the one generic examples drop. In food service, the FDA Food Code is a model code that state, local, tribal and territorial agencies adopt, and FDA describes it as widely adopted by the agencies regulating more than one million food establishments. Under the Food Code, a variance is a written document issued by the regulatory authority that modifies or waives a requirement, and the 2022 edition says a variance based on a federal performance standard must be supported by a validated HACCP plan with records and documented verification available to the regulator. FDA's summary of changes for the 2026 edition lists only a cross-reference update to that variance section.

That means a brand's food safety team can approve a process change for the system while a particular unit still cannot run it until its own regulator issues a variance. A training example that shows the brand approval and the outcome, without the local variance, teaches the wrong rule: that the franchisor's approval was sufficient.

Two quieter constraints matter as well. Manual versions change, so a deviation approved under one revision can be standard practice, or forbidden, under the next. And adopted codes differ by jurisdiction and edition, so the same request can need a variance in one city and not in another. Both belong in the record, not in the reader's head.

Worked scenario (illustrative): one quarter of exception requests in a restaurant system

This scenario is illustrative; the system, counts and percentages are invented to show how the worksheet reads. A franchisor exports one quarter of exception requests from its approval tool and the field consultants' notes for a regional group of units, 40 cases in all.

Mapped through the worksheet, 26 cases needed only brand approval, 9 needed brand and local approval, and 5 were local matters the brand only had to be told about. Of the 9 dual-approval cases, 3 had no recorded brand decision at all: the change went ahead after a phone call, so the brand-decision field is marked unknown, not approved.

One case shows why order matters. A unit asked to change a cooking and holding process for a seasonal item. The brand's quality team approved it on the condition that the unit obtained a variance from its local regulator. The unit's file holds the variance application and the regulator's approval about six weeks later; the item launched only after that date. Recorded as two linked events with the condition, the case teaches the right lesson. Recorded as one approved status, it teaches that the brand's approval was enough.

The 3 unknown cases are kept but flagged, and the 9 dual-approval cases make up about 23% of the quarter, a share worth reporting so that a buyer or model team knows how much of the set depends on local authority.

Which assumption changes the decision, and how should uncertainty be recorded?

The assumption that most often flips a case is that an approval existed because the change happened. Treat every approval field as having a status: documented, with the document ID; reported, where someone says it was given but no record exists; or unknown. Report the share of cases in each status for the whole set.

At a glance

Which assumption changes the decision, and how should uncertainty be recorded

  • Manual version: if the revision in force at the time is unknown, mark the standard field unknown instead of using today's manual.
  • Delegation: if it is unclear whether a consultant could approve without head office, record the consultant's decision and leave on-behalf-of as unverified.
  • Local requirement: if nobody checked whether a variance or permit applied, record that the local track was not assessed, which is different from not required.
  • Data access: Item 11 tells you whether the franchisor can independently access POS or system data and under what contractual limits; access does not settle who may share the record.
  • Outcome: if the follow-up audit never happened, keep the case but do not label it a success.

Whose exception records are these to share?

Usually both parties hold part of each case, so both may need to agree before the records leave the system. The franchisor typically holds the brand approval file and the manual; the franchisee typically holds its own correspondence, costs, staff notes and customer details. The franchise agreement's clauses on data, confidentiality and required software decide who may use which part, and the operations manual itself is usually confidential to the franchisor.

A franchisor assembling cases across many units should expect the answer to differ by unit. Agreements signed in different years often carry different data clauses, conversion franchisees may have negotiated their own terms, and a unit that has left the system may be bound by post-termination provisions. Add the agreement version to the record authority field, and treat a case whose local documents came from a former franchisee as needing its own review before use.

Exception records also carry personal data: owner and employee names, customer complaints that triggered a request, and inspection details. Plan to remove or replace names and identifiers, and to strip customer details, before any external use, and have counsel read the agreement for the specific system rather than relying on a general rule.

Licensing dual-approval exception cases as AI training data

Exception cases with both approval tracks recorded are the kind of operational evidence that is hard to synthesize, because the reasoning lives in the authority chain rather than in the outcome. A franchisor or a large multi-unit franchisee that has kept these files may hold a set worth assessing, provided the agreement allows it and both sides' records are handled correctly.

A franchisor or multi-unit franchisee can license selected operating records as AI datasets through SourceX, which handles rights review, contracting, preparation and delivery. The first step is a short company assessment with no upload, and delivery happens only after the company approves scope and terms and signs the agreement.

Frequently asked questions

Does a franchisor's approval replace a local health department variance?

No. Under the FDA Food Code model, a variance is a written document issued by the regulatory authority, not by the brand. A franchisor can approve a process change for its system, but a unit may still need its own regulator's variance before running it, depending on the code its jurisdiction adopted.

What is Item 8 in a franchise disclosure document?

Item 8 covers restrictions on the sources of products and services. The franchisor must disclose what franchisees must buy from it, its designee, approved suppliers or to its specifications, and how it grants and revokes approval of alternative suppliers. It is the first place to look when mapping supplier exceptions.

Can a field consultant's approval count as the franchisor's approval?

It depends on the agreement and the franchisor's internal delegation. Record the consultant as the deciding agent and the franchisor as the party they acted for, and mark the delegation unverified until a document confirms the consultant's authority for that type of exception.

Should refused exception requests be kept in the dataset?

Yes. Refusals and their reasons show where the boundary of the standard sits, which approved cases alone cannot show. Keep them with the same fields and mark the outcome as refused or withdrawn.

Does franchisor access to POS data mean the franchisor owns it?

Not necessarily. Item 11 requires disclosure of whether the franchisor has independent access to data in required systems and any contractual limits on that access. Ownership and the right to share are set by other clauses in the franchise agreement.

Sources

  • The Franchise Rule's disclosure items require franchisors to describe required sources of products and services and how alternative suppliers are approved (Item 8), whether they have independent access to data in required computer systems (Item 11), and whether the franchise is for a specific or franchisor-approved location (Item 12). Source
  • The Franchise Rule defines a franchise to include the franchisor's significant control over, or significant assistance in, the franchisee's method of operation. Source
  • The 2022 FDA Food Code defines a variance as a written document issued by the regulatory authority that modifies or waives a Code requirement, and says a variance based on a federal performance standard must be supported by a validated HACCP plan with records and documented verification. Source
  • FDA says the Food Code is a model code, not a requirement, widely adopted by state, local, tribal and territorial agencies that regulate more than one million food establishments. Source
  • The W3C PROV ontology links activities to responsible agents with wasAssociatedWith, optionally with a plan, and expresses delegation with actedOnBehalfOf. Source
  • FDA's summary of changes in the 2026 Food Code lists only a cross-reference update to section 8-103.12 on variances. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies