# Brand standard exceptions across systems | SourceX

Canonical: https://refer.sourcex.si/guides/workflow-brand-standard-exception-approvals
Last updated: 2026-11-04

Five links let someone follow a brand standard exception from start to finish across systems: a location identity that survives resales, a standard reference naming the manual version, a finding ID carried into the exception request, a variance ID shared by the franchise portal and the audit platform, and an expiry date tied to a re-inspection. With those joins, inspection records, exception requests and final decisions read as one case. Without them, each system looks complete and the story is lost.

Many franchisors run inspections in one tool and approvals in another. The audit platform knows what was found; the franchise portal knows what was asked and decided. This guide maps the joins between them, works one Illustrative variance through both systems, and shows what a franchise systems consultant can note without handling any records.

## What links are needed to reconstruct brand standard exception approvals across business systems?

A location identity, a standard reference, a finding-to-request link, a variance ID both systems recognize, and an expiry-to-re-check link. The variance ID is the link most often missing, and its absence has a visible symptom: the same finding reopens at every inspection.

| Join | Audit platform | Franchise portal | Failure if missing |
|---|---|---|---|
| Location over time | Site ID, inspection dates | Franchise agreement ID, owner history | A resale to a new franchisee looks like a new site with no history |
| Standard in question | Checklist item code | Manual section cited in the request | Nobody can say which version of the standard was waived |
| Finding to request | Finding ID and photo | Request referencing that finding | The request cannot be tied to the problem it answered |
| Decision to inspection | Variance ID that suppresses the item | Variance ID, conditions, expiry | Approved variances are flagged again as failures |
| Expiry to re-check | Re-inspection result | Expiry or review date | Variances outlive their conditions unnoticed |

Each join answers a different question. The first says where; the second says against which rule; the third says why the request was made; the fourth says what was allowed; the fifth says whether the allowance was checked.

## Why the manual version and the approval criteria matter

The standard reference is only useful if it names the version of the operations manual that applied on the date of the request. Manuals change, and a variance granted against one edition may be meaningless against the next.

U.S. franchise disclosure rules show why franchisors treat these documents carefully. Under 16 CFR 436.5, Item 11 requires the franchisor to disclose the table of contents of its operating manual, and Item 8 requires it to describe how it grants and revokes approval of alternative suppliers, including whether its criteria are available to franchisees. FTC staff guidance has also warned that a new fee imposed through the operating manual, but not disclosed in the franchise documents, may be an unfair practice. None of that is about data licensing, but it explains why a reviewer needs the manual edition, the stated criteria and the decision side by side: they are what make an exception decision interpretable later.

## A worked exception: a regional sign variation

**Illustrative**, not a real case or a completed deal. A fictional franchisor of a quick-service brand employs 260 people at its head office and field team. One franchised location sits in a historic district where the local ordinance bars internally illuminated signs, so the standard illuminated fascia sign cannot be installed.

| Step | Record | System | What it shows |
|---|---|---|---|
| 1 | Inspection finding: fascia sign is non-standard, photo attached | Audit platform | The initial problem and when it was found |
| 2 | Exception request citing the ordinance, with the permit refusal | Franchise portal | The franchisee's grounds and evidence |
| 3 | Review against three tests: legal requirement, brand recognition, cost of cure | Portal comments, committee notes | The criteria actually applied |
| 4 | Approval: externally lit sign in brand colors, valid until the lease renewal | Franchise portal | The authorized action, its conditions and expiry |
| 5 | Variance ID added to the audit checklist for that site | Audit platform | The link that stops the finding reopening |
| 6 | Re-inspection passes the sign under the variance | Audit platform | The checked result |

Remove step 5 and the record set still looks complete in each system, but the next inspection fails the location for a sign the franchisor approved. Remove the finding ID from step 2 and the request floats free of the problem it answered. That cross-system context is what makes an exception history useful for training AI systems to handle exceptions rather than only rules; see [exception handling data for AI agents](/guides/exception-handling-ai-agents-data). For the general pattern of exception records in approval workflows, see [procurement approvals and exception workflows](/guides/how-to-assess-procurement-approvals-and-exception-workflows).

## What a partner can note about the joins

Describe which joins exist, not what the records say. Ask the franchise operations director five yes-or-no questions, one per join, and write down the answers with rough years and volumes.

- Does the site ID survive a resale, or does a new franchisee get a new record?
- Do exception requests cite a manual section and edition?
- Do requests carry the finding ID, or only a free-text description?
- Is the variance ID written back to the audit checklist, and since when?
- Are expiry dates tracked and tied to a re-inspection?

Note too where decisions were made outside the portal, such as by email or in committee minutes. Do not collect inspection photos, portal exports or franchisee correspondence. If the franchisor is restructuring, the [franchisor bankruptcy](/industries/franchisor-bankruptcy) page covers what changes about timing, and [franchisor data monetization](/industries/franchisor-data-monetization) covers the wider record set.

## Does the franchisor qualify, and what stays unknown?

The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, 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. See [who qualifies](/who-qualifies) and the [industries hub](/industries).

The franchise operations director usually knows which joins exist and for how many years. Rights sit with the franchisor's counsel, because inspection photos and exception requests include material supplied by independent franchisees, and the franchise agreement decides who may reuse it. The person who can authorize a licensing discussion is the CEO, or the owner in an owner-run franchisor.

Until SourceX reviews it, nobody knows whether buyers want variance histories, what rights review concludes about franchisee-supplied material, how much de-identification is needed, or whether an offer follows. Partners sign the Channel Partner Agreement before submitting introductions; the first valid introduction within the 90-day window is credited when the company submits a verified application.

## Go deeper on brand standard exception approvals

- [Who can license brand standard exception approvals records](/questions/who-can-license-brand-standard-exception-approvals-records) answers which franchisor decision-maker a partner should introduce.
- [Preserve brand standard exception approvals records](/guides/preserve-brand-standard-exception-approvals-records) is an inventory checklist for the months before a franchise system transition.
- [Brand standard exception approvals referral brief template](/resources/brand-standard-exception-approvals-referral-brief-template) gives a fill-in introduction note.

## 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's variances can still be followed from finding to re-inspection across its audit platform and portal, [register as a partner](/register), check the franchisor against [who qualifies](/who-qualifies), and read the [program terms](/terms) before you introduce the executive who can authorize the discussion.

## Sources

- https://refer.sourcex.si/terms
- https://www.ecfr.gov/current/title-16/chapter-I/subchapter-D/part-436/subpart-C/section-436.5
- https://www.ftc.gov/system/files/ftc_gov/pdf/Franchise-Issue-Spotlight.pdf
- https://www.ftc.gov/system/files/ftc_gov/pdf/Franchise-Staff-Guidance.pdf
