How to Run a Franchise Advisory Council Franchisees Actually Respect

Ask franchisees in almost any network about their advisory council and you'll hear one of three answers. In weak systems: "We have one?" In frustrated systems: "It's where our feedback goes to die." And in a minority of well-run systems: "That's how we got the new POS rollout fixed before it hit everyone."

The gap between those answers is not budget or goodwill. Franchisors that run hollow councils usually want franchisee input. The gap is structural — decision rights, selection, cadence, and follow-through. This guide covers each, drawing on what separates councils that function as genuine operating infrastructure from councils that function as an annual dinner.

What a Franchise Advisory Council Is Actually For

A franchise advisory council (FAC) is a standing body of franchisee representatives that meets regularly with franchisor leadership to review system changes, surface field problems, and advise on decisions that affect unit operations and economics. In most systems it is advisory — the franchisor retains decision authority — which is exactly why the design details below matter so much. An advisory body with no formal power lives entirely on credibility.

Done well, the FAC does three jobs no other mechanism does:

De-risks system changes before network-wide rollout. A new operations procedure, technology platform, or menu change reviewed by eight operators who run real locations will surface failure modes HQ cannot see. This is cheaper than discovering them across 200 locations — the same logic that applies to any technology rollout, applied earlier in the process.

Converts diffuse grievance into structured negotiation. Without a council, franchisee frustration accumulates in Facebook groups and side conversations until it arrives as organized resistance — or litigation. A council gives disagreement a table, an agenda, and a process, which is better for both sides. It's a core piece of the broader franchisor-franchisee relationship architecture.

Gives good ideas a path upstream. Your best operational improvements are already happening in the field, unofficially. The council is one of the few structures that can find them and systematize them.

What an FAC is not: a substitute for franchisee satisfaction measurement (eight people can't tell you what two hundred feel), a marketing fund committee (that's usually a separate body with separate rules), or a place to announce decisions already made while calling it consultation. That last one is the fastest way to destroy the council's credibility — and franchisees can smell it immediately.

Decision Rights: The Design Choice That Decides Everything

Before selecting a single member, write down which category every topic falls into. This single table prevents most council dysfunction:

The specific allocation matters less than its clarity and stability. A council that "shapes" technology decisions and knows it will get a written response to its objections is a real council, even with zero binding votes. A council whose influence depends on the CEO's mood that quarter is theater, and every franchisee on it knows within two meetings.

Two rules make the categories credible. First, never move a topic down a category mid-controversy — reclassifying a contested supplier decision from "shapes" to "informed" because the council disagrees with you costs more trust than losing the argument would have. Second, give the council at least one real "decides" domain, even a small one. A body that decides nothing attracts nobody worth having.

Selection: Composition Beats Fairness

The instinct is to make council selection maximally democratic. Resist it partially. Pure elections in franchise systems reliably select for two traits: tenure and volume. You get the longest-standing franchisees and the loudest ones — which often means a council that over-represents legacy locations and under-represents the operators your system's future depends on.

Design the composition first, then fill it:

• Mix performance tiers deliberately. A council of top performers produces advice calibrated to top performers — staffing models the median location can't afford, local marketing the median owner won't execute. You need your median in the room. One or two struggling-but-serious operators are worth their seats in early-warning value alone.
• Mix formats and geography. Urban and rural, single-unit and multi-unit, old-format and new-format locations. Every operating format that represents more than ~15% of your network should have a voice.
• Set terms and stagger them. Two-year terms, half the council rotating each year. Continuity without permanence. Permanent seats calcify into a shadow leadership team, and the network starts treating the council as an in-group rather than a representative body.
• Hybrid selection works best in practice: franchisees elect from a slate that meets the composition requirements, or elect most seats while the franchisor appoints two or three to fix composition gaps. Disclose the mechanism fully — an opaque process taints every subsequent council position.

Size: five to nine members for networks under ~150 locations; nine to thirteen above that, often with regional sub-councils feeding the national one. Beyond thirteen, meetings become performances.

Cadence and Mechanics: Run It Like an Operating Review

Councils drift into ceremony when they meet rarely and socially. The corrective is boring discipline:

• Quarterly full meetings, minimum. Two in person (one usually attached to your annual conference), two remote. Monthly is better during major rollouts.
• Agenda published two weeks out, with materials. Franchisees reviewing a technology proposal need the actual proposal, not a slide summary presented live. Surprise topics get tabled, not decided.
• Every meeting produces a written record: topics reviewed, council positions (including dissents), franchisor commitments, and deadlines. Published to the entire network, not just attendees. This is the single highest-leverage mechanic on this list — it converts the council from a private conversation into public infrastructure, and it lets the other 190 franchisees see that the thing works.
• Council members carry a communication duty. Each member owns a region or cohort and is expected to collect input before meetings and report back after. Without this, the council represents eight opinions, not the network. Give them the channel and the materials to do it — it slots naturally into your broader communication strategy.

Follow-Through: Where Councils Live or Die

Here is the uncomfortable pattern: most failed councils didn't fail in the meeting room. They failed in the six weeks after, when input vanished into HQ and nothing came back. Franchisees are businesspeople; they invest effort where it returns. A council whose input disappears gets, within a year, exactly the engagement it earns — none.

The fix is a disposition loop. Every substantive council input gets one of four visible statuses:

Track dispositions in the same system your network already uses for operations — visible alongside the SOPs and rollout dashboards, not buried in meeting-minutes PDFs. When a council recommendation becomes a procedure change, the changelog should say so. Nothing builds council credibility faster than a franchisee seeing "updated based on FAC review, March meeting" in the operations manual — and nothing recruits better candidates for the next council term.

A note on declines: a council that never hears "no, and here's why" is being managed, not consulted — and a franchisor that can't write down its reasons for declining probably doesn't have good ones. Honest declines, well-argued, build more trust than soft yeses that die in implementation.

Getting Started (or Restarting) in 90 Days

If you're launching a council — or reviving one that's become furniture — the sequence is:

1. Weeks 1–3: Draft the charter: purpose, decision-rights table, composition requirements, terms, meeting cadence, disposition loop. Keep it under five pages.
2. Weeks 3–6: Socialize the draft with a handful of respected franchisees across performance tiers. Incorporate their edits visibly — the charter process is your first credibility test.
3. Weeks 6–10: Run selection per the charter. Publish the mechanism, the slate, and the results.
4. Weeks 10–13: First meeting. Put one genuinely contested topic on the agenda — a council that opens with softballs teaches everyone it's decorative. Publish the record and the first dispositions within two weeks.

A working advisory council is one of the few mechanisms that makes a franchise network smarter than its headquarters. The operators in the field hold most of your system's undocumented knowledge; the council is how it gets a seat at the table — and how your next rollout ships with its worst bugs already found.