# Franchise variance referral brief template | SourceX

Canonical: https://refer.sourcex.si/resources/brand-standard-exception-approvals-referral-brief-template
Last updated: 2026-11-04

A company introduction about brand standard exception approvals works best as a one-page form: ten short fields that describe the franchisor's variance history without holding any of it. The fields cover head office size, the business task, record classes, systems, years, rough volumes, the exception pattern, ownership, the contact who can say yes, and the deadline. Fill it from conversation, leave blanks honest, and attach nothing. A completed Illustrative form follows the blank one.

This template is part of the [brand standard exception approvals guide](/guides/workflow-brand-standard-exception-approvals), which explains how the records join across the audit platform and franchise portal. Read the guide to understand the records; copy this page to write them down.

## The blank brief: ten fields

Copy the table, fill the right-hand column, and stop at one page. Every field is metadata: what, how much, how long, which system, who owns it.

| Field | What to write | Where the answer comes from |
|---|---|---|
| 1. Franchisor and size | Sector and head office plus field staff at peak, full-time only | HR or the people team |
| 2. Business task | One sentence on what the variance process decides | Whoever chairs the variance committee |
| 3. Record classes | Plain names: standards, findings, requests, decisions, supplier approvals | Field audit lead |
| 4. Systems | Plain-text tool types or names, including email | IT or the portal administrator |
| 5. Years covered | Start and end per system, and any gap | IT, from go-live dates |
| 6. Rough volumes | Inspections, requests and decisions per year, as ranges | Field audit lead, as a range |
| 7. Exception pattern | The kind of case the records explain | Variance committee |
| 8. Record owner | Which role owns the records and the franchise agreements | Head of franchise operations |
| 9. Authorized contact | The chief executive, who can agree to explore licensing | Confirmed by the chief executive |
| 10. Open questions and deadline | What only a review can answer; the old system's access end date | The vendor contract |

Leave out, always: location names, franchisee names, addresses, photos, permits, lease extracts, exports, logins and any estimate of value.

## How to fill each field without seeing a record

Ask, do not inspect. Each field has one question that gets a usable answer in a sentence.

**Size.** "How many full-time people work at head office and in the field team at peak?" Count only the franchisor's own payroll, not restaurant crews employed by franchisees; see [franchisor employees vs franchisee employees](/questions/franchisor-employees-vs-franchisee-employees). The introduced company needs 50+ full-time employees at peak (contractors excluded).

**Business task.** "What does the variance process decide, and who asks for it?" One sentence is enough.

**Record classes and systems.** "Where does a finding live, where does a request live, and where is the decision recorded?" The answer often names an audit platform, a franchise portal, a document library for the manual and an operations mailbox.

**Years covered.** "When did the portal go live, and where were approvals kept before that?" Earlier approvals by email are common and worth noting.

**Volumes.** "Roughly how many inspections a year, and how many exception requests?" Ranges are fine.

**Exception pattern.** "What kind of request comes up most, and what kind is hardest to decide?" A regional variation forced by a local rule is a typical answer.

**Owner and authorized contact.** "If the company wanted to explore licensing these records, who would need to agree?" The [who can license page](/questions/who-can-license-brand-standard-exception-approvals-records) explains why that is the chief executive, with general counsel advising, not the operations director.

**Deadline.** "When does the old portal stop being accessible under the vendor contract?" The [preservation timeline](/guides/preserve-brand-standard-exception-approvals-records) explains why this date matters more than go-live.

## A completed brief (Illustrative)

Illustrative and invented for this page. A fictional quick-service franchisor; every value is an example, not a real company or a completed deal.

| Field | Illustrative entry |
|---|---|
| 1. Franchisor and size | Quick-service restaurant franchisor; about 230 full-time head office and field staff at peak |
| 2. Business task | Reviewing franchisee requests to vary brand standards, and re-checking approved variances at inspection |
| 3. Record classes | Manual versions, inspection findings, exception requests, decisions with conditions and expiry, supplier approval requests |
| 4. Systems | Audit platform, franchise portal, document library, operations mailbox |
| 5. Years covered | Inspections for about six years; portal requests since go-live four years ago; earlier approvals by email |
| 6. Rough volumes | Several thousand inspections a year; a few hundred exception requests a year |
| 7. Exception pattern | A location needs an approved regional variation because a local rule blocks the standard |
| 8. Record owner | Franchisor's executive team; franchisee-supplied material governed by franchise agreements |
| 9. Authorized contact | Chief executive, with general counsel; operations director as records contact |
| 10. Open questions and deadline | Whether variance IDs were written back to the audit platform; old portal access ends on the date in the vendor contract |

Read it once more and check what it does not say. No location, no franchisee, no photo, no export, no value. That is what makes it safe to send.

## Context that strengthens a brief

Under the completed table, a brief can carry up to four optional context lines. Each one answers a question a reviewer would otherwise send back.

| Optional line | Sample wording for the Illustrative brief | Why a reviewer cares |
|---|---|---|
| Manual editions | "Manual kept in dated editions since 2018; each decision names the edition it waives." | Lets every exception be read against the rule that was in force. U.S. disclosure documents already list the manual's contents under Item 11, so the operations director will know whether editions are kept. |
| Supplier requests | "Alternative-supplier requests go through the same portal as layout and equipment variances." | Item 8 of the disclosure document covers how alternative suppliers are approved and revoked; if those requests share a system, they are a second record class worth one line. |
| Re-inspection link | "Approved variances are re-checked at the next scheduled visit." | Shows the decision has a follow-up record, not just an approval. The FTC's definition of a franchise includes significant control over, or assistance with, the franchisee's method of operation; inspections and re-checks are where that control leaves a trail. |
| Expiry handling | "Most variances carry an expiry date; lapsed ones are flagged to the field team." | Tells the reviewer whether outcomes, not only decisions, are recorded. |

Keep each line to one sentence the operations director has confirmed, and drop any line nobody can confirm. A brief with two solid context lines reads better than one with four guesses.

For wording the introduction itself and disclosing your referral relationship, use the [warm introduction brief](/resources/a-warm-introduction-brief-for-a-business-owner). Franchisors weighing their wider record set can read [franchisor data monetization](/industries/franchisor-data-monetization), and consultants new to the program can start with the [franchise consultant partnership page](/for/franchise-consultant-referral-partnership).

## Before you send it

Check the brief against the qualification basics: 50+ full-time employees at peak, 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.

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, and one partner is credited per company. Whether buyers want variance history, what rights review concludes about franchisee-supplied material, and any price 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.

When the operations director has checked your ten fields and the authorized contact is named, [register as a partner](/register), confirm the franchisor against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you send the brief.

## 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.ecfr.gov/current/title-16/chapter-I/subchapter-D/part-436/subpart-A/section-436.1
