The new franchisee who goes quiet rarely asks for help first
Every franchisor remembers the first franchisee who went silent: the calls that stopped getting returned during build-out, then a visit rescheduled twice, then an agreement quietly heading toward release. What's harder to track is whether you'd know before the calls stop, or only after.
FDD Item 20 turns all of it into a single disclosed line. It doesn't say who's actually at risk, or why.
Where the silence actually starts
None of this starts as a crisis. It starts as a missed callback, a permit delay nobody escalated, a blocker on a checklist milestone that sat unaddressed for a week. Start diagnosing which signed units are furthest into that pattern with the free Backlog Revenue Calculator, no email required for your first run.
Every franchisor who's built a real system has lived through some version of the five below.
The first missed callback looks like a scheduling conflict, not a warning: A franchisee three weeks behind on permits isn't behaving any differently than one who's just busy...yet. By the time the difference is obvious, the file's already cold.
Your best answer to "how's the pipeline" is a guess dressed up as a percentage: When someone in a leadership meeting asks how many signed units are actually on track and the honest answer is "mostly," that's not a status update. That's a blind spot with good posture.
A franchisee's silence reads as busy until it reads as gone: Nobody flags a franchisee who's gone quiet for a week: frandev is busy closing new signings, and ops is helping hand-raisers. By the time three weeks pass and somebody finally calls, the conversation is often about an exit, not a delay.
The checklist changes, but nobody tells the fifteen locations already mid-build: A brand standard update that doesn't reach every open project at once means some franchisees are building last month's version, and won't find out until a site inspection tells them.
Frandev hands off the win, and ops inherits the risk with no record of what was promised: A franchisee's confidence is highest on the day they sign. A rocky handoff into the onboarding and launch is the fastest way to spend that down before the first shovel goes in the ground.
What you don't find out until it's too late to matter
A signed-but-not-opened backlog rarely costs you all at once. Royalty that was contracted for still isn't on the books eight months after signing. A franchisee stops answering by the third unreturned call and asks for a release by the fourth. An area developer's next five units quietly stall because the first one never got the attention it needed, and now the whole territory is behind schedule. None of it looks urgent while it's happening. It looks obvious later, in an exit interview, or in the FDD line item nobody on the leadership team wants to explain.
See your own pipeline before the board does.
Run the two-minute Backlog Revenue Calculator on your own signed-but-not-opened units, or read what changes once you can see a stalling franchisee before the third unreturned call. Both are free. Neither requires a sales conversation.
Every number here traces back to a real FDD line item.
We didn't estimate what a stalled unit costs. This is built around Item 20 disclosures, real royalty timelines, and what franchise development teams actually report when a board asks about the backlog. The dollar figure the calculator gives you isn't hypothetical. It's the same math a franchisor's own finance team would run if they had the visibility to run it today.
Built around real FDD Item 20 disclosure math, not a hypothetical
Reflects royalty timelines pulled from actual franchise development pipelines
Built by the team behind Pacer's opening playbooks, already running across 159,000+ locations
