Most franchisors trying to hold locations accountable are solving the wrong problem.
They design reporting systems. They schedule field visits. They write corrective action plans. They build dashboards that aggregate location data every thirty days. Then, when a location underperforms for a quarter before anyone notices, they add another layer of oversight.
The problem is not that they need more management. The problem is that they cannot see what is happening until it is too late to fix cheaply.
According to FranConnectGO, by the time financial results reveal a problem at a franchise unit, "months of revenue opportunity have been lost" and operators are "always playing catch-up." That phrase stuck with me because it precisely describes what accountability systems built on lagged data always produce. You are not micromanaging your franchisees. You are managing the past.
Franchising has concentrated: 19.3% of franchisees now control 58.8% of all locations, according to FRANdata and the IFA. The operators at that scale are not running out of management capacity. They are running out of visibility. Every unit you add is another set of decisions you cannot see in real time. At some point, the accountability gap is not a willpower problem or a culture problem. It is a data architecture problem.
Here is the decision tree I would use to diagnose which problem you actually have.
Branch 1: Do you know, right now, which locations are underperforming?
If your honest answer is "I would know by next month's call" or "I have to pull a report to find out," you have a visibility problem. Stop there. Nothing downstream matters until you solve this.
Visibility problems do not respond to tighter management. They respond to live data. What you need is a view where every location's KPIs update on a cadence short enough to catch a slide before it becomes a trend. That cadence is days, not months.
At Sneeze It, we track performance across client locations using our own agents running on a unified scorecard. Dash, our analytics agent, reads cross-location data daily and flags anomalies before a human would notice them. Tally, our scorecard agent, pushes KPI values from source systems into the org chart so nothing depends on someone remembering to update a spreadsheet. The agents do not decide anything. They surface what is happening so the humans who need to decide have current information.
The portfolio feature in OTP (available now in early access) addresses this directly at the system level. A portfolio groups member orgs (each location is its own OTP org, running its own hybrid chart) and rolls their KPIs up into super-metrics at the portfolio level. You get one view across all locations. Corporate can see which units are above baseline, which are at baseline, and which have dropped, without asking franchisees to self-report.
If you solve the visibility problem, you will often discover the underlying performance problem is smaller than you thought. You were just seeing it late.
Branch 2: You can see the gap. Is it execution or standards?
Once you have visibility, every underperforming location falls into one of two buckets. Either the location is not executing against a standard that everyone agrees on, or the standard itself is the wrong one for this unit.
These are completely different problems with completely different fixes. Applying a management solution to a standards problem is how you burn franchisee relationships.
Execution gaps mean the franchisee knows what the standard is, has agreed to it, and is not hitting it. The conversation is specific: here is the KPI, here is where you are, here is where the comparable locations in the system are. What changed? What is the plan?
That conversation is much easier when the benchmarking is built into the system. Location-to-location benchmarking is a named requirement in franchise operations for exactly this reason. The most effective accountability tool I have seen in this space is not a corrective action plan. It is a ranked view of the same metric across all your locations, visible to everyone in the system. When a franchisee can see where they rank among their peers, the conversation about execution shifts from "corporate says you're underperforming" to "here is where you are in the system."
OTP's portfolio super-metrics produce exactly this view. The franchisor sees the roll-up. Each location can see how its contribution sits relative to peers. No one is hiding from a number, because the number is shared.
Standards gaps mean the standard is either wrong, unclear, or inconsistently applied. You cannot hold someone accountable to a standard they do not understand or cannot practically meet. This is the consistency problem that scales with every unit you add.
The franchise consistency problem has a structural fix: set the operating standard once, and lock it. In OTP, portfolio presets are how this works. A portfolio defines default settings and sidebar configurations for its member orgs. Member orgs inherit those presets. Corporate can lock them so locations cannot drift. Every new location joining the portfolio inherits the same setup at day one.
This is not micromanagement. It is the structural equivalent of how franchise brand standards work. You do not ask each franchisee to guess your logo colors. You publish a brand guide and you enforce it. Presets are the operating-system version of that guide.
Branch 3: Execution gap confirmed. Is it a human problem or a process problem?
Assuming you have visibility and the standard is clear, execution gaps usually have two causes.
The first is that the person responsible for a function at the location does not have the information they need to act. The second is that they have the information and are choosing not to act.
Most of the time, it is the first one. Most of the execution gaps I see in multi-location operations are not willpower failures. They are information routing failures. The right person does not know what they need to know, when they need to know it.
This is where per-location agent teams change the math.
A location running its own Radar (chief of staff agent) gets a daily briefing on what is happening across its operations. Arin, the call center agent, monitors speed-to-lead and dial volume without anyone having to pull a report. Crystal, the project manager agent, tracks delivery timelines. Pulse, the retention agent, monitors client health signals. The agents carry the operational work so the human at the location can focus on the decisions that require judgment.
The franchisor's portfolio view then shows whether each location has the agents running. The combination of per-location agents feeding a portfolio rollup is the structural answer to "how do I hold them accountable without micromanaging?" You are not in their daily meeting. The agents are. The outputs flow to a shared view you can see from the portfolio level.
Branch 4: Human problem confirmed. Narrow the decision point.
If visibility is live, standards are clear, process is instrumented, and a location is still underperforming, you have a narrower conversation to have. And now you can have it from an informed position.
The informed position matters because the most common failure mode in franchise accountability is escalating too fast with too little data. A franchisor who calls a franchisee about underperformance with a month-old report and a vague concern is going to have a defensive conversation. A franchisor who calls with a current benchmark showing where the location sits relative to its peers, the specific KPI that moved, and the date the slide started is going to have a different conversation.
The data does not make the decision for you. But it makes the decision conversation honest.
And that is the actual goal. Not micromanagement. Honest conversations between people with the same information, fast enough to fix things before they compound.
What this looks like in practice
At Sneeze It, each client location we support has agents carrying specific operational functions. Arin handles call center performance. Dash tracks ad performance across all locations. Dirk manages the pipeline. Pepper handles email triage. Nick runs prospecting. Bogdan, our COO, carries the decisions that require judgment. Janine carries the financial accountability. The agents run the scorecards. The humans run the organization.
That structure is what I would replicate at the location level inside a franchise portfolio. Each location runs a hybrid chart. The hybrid chart feeds the portfolio. The portfolio shows the franchisor what is happening across the system in real time.
The mission is what it has always been: let agents carry the operational work, so people are free for the work that matters.
Accountability without micromanagement is what you get when visibility is fast, standards are structural, and the agents carry the data so the humans can carry the conversation.
See the live chart
You can query OTP's portfolio structure directly, including how member orgs connect to portfolio super-metrics, using the OTP MCP.
In Claude Desktop or Cursor or any MCP client, add this block:
"otp": {
"command": "npx",
"args": ["-y", "@orgtp/mcp-server"]
}
Restart the client. Then ask: "Use OTP to show me the Sneeze It org chart and explain how each agent seat would map to a franchise location's operational functions."
You will see how each seat maps to a specific accountability function, which is exactly the model a per-location team would replicate inside a portfolio.
Series: Franchise. Post 30. Previous posts in this series cover how a franchise is a portfolio, why presets are the consistency lever, and what per-location agent teams look like in practice.