What HQ Sees on the Scoreboard: Aggregates and Adoption Only

Why this article exists

The Playbook Scoreboard ranks plans by how well your network adopted them. That word, adoption, can sound like HQ is watching a franchisee's operations. It is not. Every number on this page describes whether a location acknowledged, started, or finished the plan you pushed to them, never what their business actually did as a result. This article documents exactly what the Scoreboard shows, where per-franchisee detail lives, and why it never crosses into a franchisee's private data.

If you administer a franchise network, a multi-location enterprise, or a PE-backed platform of independently reporting locations, this is the article to read before you present adoption numbers to a franchisee advisory council, or before a franchisee asks "what exactly can you see about my location on this page."

Where to find it

Open Playbooks from the HQ sidebar, in the top group of links alongside Feed, Decisions, and Action Plans, at hq.verinode.ai/playbooks. See hq-playbook-scoreboard for a full walkthrough of the page's layout and rows; this article is scoped to the privacy question specifically.

What "adoption" actually measures

Every decision plan (playbook, initiative, intervention, pattern, or subtask) you push to your network carries a per-franchisee adoption record with one of five statuses: Pushed, Acknowledged, In progress, Declined, or Completed. A nightly job reads those statuses across every franchisee assigned to a plan and calculates two things: the adoption completion rate (the share of assigned franchisees who reached Completed) and the median number of days it took franchisees to move from Pushed to Acknowledged.

That is the entirety of what "adoption" means on this page. It is a status a franchisee (or HQ, pushing on their behalf) sets on a plan, not a reading of their jobs, their financials, their client roster, or their margin. A location can decline or sit on Pushed for weeks and every number on the Scoreboard still reflects only that lifecycle status, nothing about why, and nothing about what else is happening in their business.

The Scoreboard itself: pure aggregate, no franchisee identity

Nothing on the Playbook Scoreboard page names a franchisee. Walk through what actually renders:

The hero row shows four counts: Active playbooks (plans currently in active status), Completed (90d) (plans completed in the last 90 days), In draft (plans authored but not yet activated), and Distinct kinds (how many plan kinds appear across your portfolio). These are headcounts of your own plan library. None of them touch a franchisee record.

The three tile rows (Top performers, Need diagnosis, All active playbooks) each render a plan, not a franchisee, as a tile. Every tile follows the same shape:

• Label: the adoption percentage, read as "N% adopted," or "Awaiting cron" if the nightly job has not decorated the plan yet.
• Headline: the plan's title, as you authored it.
• Sub-line: the plan's kind (Playbook, Initiative, Intervention, Pattern, or Subtask) followed by a ratio, for example "8 of 12 franchisees," meaning 8 of the 12 franchisees assigned to this plan have completed it.
• Meta line: timing context, either the median days franchisees took to acknowledge the plan, or how long the plan has been live.

"8 of 12 franchisees" is a count, not a list. The Scoreboard never tells you which 8, or which 4 are lagging, by name. That detail lives one click away, on the Decisions page, described below.

Tile color follows the same logic across the two ranked rows and the full list: adoption at 75% or higher renders in Expand green, 40% up to 75% in Maintain yellow, under 40% in Analyse red, and a plan awaiting its first cron decoration renders in neutral copper. The Need diagnosis row's own heading states its rule plainly: adoption under 40%. None of this coloring or thresholding is about hiding franchisee identity, it is a plan-level performance read, the same as a headline metric on any other HQ page.

Where per-franchisee status actually appears: the plan's detail, not the Scoreboard

Clicking any tile takes you to that plan's detail, where HQ admins see the fuller per-membership breakdown. This is the one place on the Playbooks surface where individual franchisees appear at all, and it is still limited to adoption lifecycle, never business data:

• Adoption summary: a five-way count, pushed, acknowledged, in progress, completed, declined, across every franchisee the plan was pushed to.
• Slow movers: up to five franchisees still sitting in Pushed or Acknowledged more than a week after the push, each shown with a name, its current status, and days since pushed. A Compose nudge button opens a pre-filled email you can send directly, or, if no contact email is on file for that location, a line reading "Add an email in Locations."
• Sponsorship: if you attached IU sponsorship to the push, a rollup of budget, used, and remaining IUs across sponsored franchisees.

That is the complete list of what a per-franchisee row can show anywhere in Playbooks: a name, an adoption status, a date, and, where you sponsored it, an IU figure. There is no column, no drill-in, and no hover state anywhere in this flow that surfaces a franchisee's jobs, revenue, margin, cash position, client list, or vendor spend.

Named or anonymized, depending on how your network is set up

Whether that franchisee name reads as a real location name or as an anonymized label depends on how your group is configured, not on anything you choose per plan:

• Independent operators (the default posture for franchise and association networks): each location is a separately owned business. Franchisee names in the per-plan breakdown display as an anonymized label built from the franchisee's account, for example "Franchisee #4F2A," rather than the location's real name.
• Same entity (company-owned multi-location networks): there is no separately owned business to protect, so the real location name passes through unchanged.

Unlike some other HQ surfaces, Playbooks does not additionally suppress a franchisee's row below a minimum cohort size. That distinction matters and is deliberate: on pages like Vendors, hiding a whole row below a cohort floor exists because the underlying number, a vendor's monthly spend or satisfaction rating, is the franchisee's private business data, and even an anonymized name would still identify that one operator by elimination. Adoption status is different in kind. Whether a location acknowledged a plan you pushed to them is not private commercial information about how their business runs, it is a record of their response to something HQ initiated. That is why the row itself is safe to show (anonymized where the network model calls for it), while the business results that might explain a slow adoption stay completely out of view.

Contact email: a way to reach someone, not a way to see their business

The Compose nudge action reads a contact email from your member directory to build a pre-filled message. That email address is encrypted at rest under your group's own key and is treated strictly as contact information, how to reach a location, never as a channel into what that location's business is doing. It answers "who do I email to follow up," nothing more.

What never appears on Playbooks, full stop

Regardless of network model, adoption percentage, or how a plan is performing, the Playbooks surface and everything it links to:

• Never reads a franchisee's jobs, invoices, cash position, margin, or financials. The queries behind this page are scoped entirely to your own network-level tables (the network data) and are documented in code as HQ-side only, with no reads against the the private layer schema that holds franchisee business data.
• Never shows a franchisee's client roster, vendor relationships, or any other operational detail unrelated to whether they acted on a plan you pushed.
• Never explains why a location is slow or has declined. A plan reading "Declined" or stuck at 20% adoption is a prompt to reach out, not a diagnosis of what is wrong with that franchisee's operations.

Empty states, read correctly

Two empty states you will run into are also part of this same discipline:

• "Adoption rates appear after the next nightly cron decorates recently-activated plans." (Top performers, when nothing yet has a percentage.) This is a timing statement about the calculation job, not a data restriction.
• "No active playbooks. Author one in Broadcast or activate a draft." (All active playbooks, when your network has nothing live.) A live link into Broadcast lets you push a new plan from there.

Neither of these is a franchisee-privacy message. They describe your own plan library's state, the same way the hero counts do.

Why the boundary sits here

Verinode HQ measures whether your network is acting on what you have shipped, not what any single location's business looks like. Franchisees own their data. The Scoreboard's job is to tell you, at a portfolio level, which playbooks are landing and which need a nudge or a rethink, so you can act on the network as a whole, not to hand you a window into any one franchisee's books.

1. 1Use the Scoreboard's counts and percentages to judge your playbook portfolio, this is the aggregate, franchisee-blind view.
2. 2Click into a plan when you need to act on a specific location, that is the only place names (real or anonymized, per your network model) appear, and only alongside a lifecycle status.
3. 3Use Compose nudge to follow up directly. It is a contact tool, not a lookup into that franchisee's operations.
4. 4If you need to understand why a location is slow, that conversation happens off-platform, HQ's own tools stop at "here is their status," by design.

Related reading

• hq-playbook-scoreboard: the full layout and rows of the Playbook Scoreboard page.
• hq-playbook-hero-metrics: what the four hero tiles mean and how they are counted.
• hq-playbook-top-performers: how the highest-adoption row is built and ranked.
• hq-playbook-need-diagnosis: how the under-40% row is built and why it has no empty-state message.
• hq-playbook-scoreboard-vs-decisions-inbox: how the Scoreboard's portfolio view differs from the Decisions inbox queue.
• broadcasting-to-your-network: how a plan gets pushed to franchisees in the first place, upstream of every adoption number described here.
• hq-vendors-privacy-boundary: the same discipline applied where the underlying data (vendor spend) is a franchisee's private business result, and why that surface suppresses whole rows where Playbooks does not.
• network-health: the broader network rollup that adoption and program-effectiveness signals feed into.
• hq-overview: what HQ is built to show across the network, and what it is not.

Data sources