Scoreboard vs Decisions Inbox: Two Different Questions

What it is

The Playbook Scoreboard is a network-wide performance view of every decision plan your organization has shipped to its membership, ranked by adoption. It answers one question: which playbooks are landing, and which need diagnosis?

It reads the same underlying table as your Decisions inbox, the network data, but it is not the inbox. The Scoreboard is a leaderboard for the FOM (Field Operations Manager) or program lead: a ranked view built for performance management, not a queue of things to act on today. Decisions Inbox (/franchise/decisions) is the workload queue: individual plans, interventions, consent requests, and program audits waiting on a decision from you. The Scoreboard is where you step back and ask how the portfolio as a whole is performing.

Where to find it

Open Playbooks from the HQ sidebar, at hq.verinode.ai/playbooks. The page loads immediately with your network's current adoption standing; there is no date picker or filter bar to configure first.

The page header reads:

Network-wide view of every decision plan you've shipped, ranked by adoption. Distinct from Decisions (the inbox queue), this answers "which playbooks are landing and which need diagnosis?"

"Decisions" in that sentence links directly to /franchise/decisions.

Why two different views

It is tempting to think Playbooks and Decisions are the same list shown twice. They are not, and the distinction matters for how you use each one:

• Decisions Inbox is time-ordered and action-oriented. It surfaces the plans, interventions, and consent requests that need a decision from you right now: push, pause, escalate, resolve. It is the shell you already know from IQ's own /decisions view, reused for the franchisor's inbox.
• Playbook Scoreboard is outcome-ordered and portfolio-oriented. It does not ask "what needs my attention today"; it asks "of everything I've shipped, what's working and what isn't." Nothing on the Scoreboard requires an action from you directly on the page. Instead, every tile is a door into the plan's detail, which opens in the Decisions view.

Think of the Scoreboard as the standings table and the Decisions Inbox as the referee's whistle. You check the standings to understand the season; you go to the inbox when a specific call needs to be made.

The hero band

At the top of the page, four tiles summarize your current playbook posture:

• Active playbooks. A count of every plan currently in active status across your network. The subtitle shows "Last created [month day]" if you have created at least one plan, or "Currently shipping" if there is no creation date to show.
• Completed (90d). How many plans reached completed status in the last 90 days, with the sub-label "Rollouts wrapped this quarter."
• In draft. Plans that exist but have not been activated yet, sub-labeled "Authored, not yet activated." These are plans your team is still writing in Broadcast; they carry no adoption data because they have never been pushed to a membership.
• Distinct kinds. The number of different plan kinds currently in your portfolio (for example, playbooks alongside directives or experiments), sub-labeled "Plan-kind variety across portfolio." This is a mix indicator, not a quality signal: a network running only one kind of plan isn't necessarily behind, but a portfolio limited to a single kind for a long stretch is worth a look if you intended to diversify your intervention types.

None of these four tiles are clickable; they are read-only context for the rows below.

Row 1: Top performers

This row ranks your highest-adopting plans, drawing from both completed and active plans and sorting by adoption rate, descending. Only plans that already have an adoption percentage are eligible; the row shows up to six tiles.

Each tile shows:

• Label (top): the adoption percentage, formatted as "N% adopted."
• Headline: the plan's title, exactly as your team wrote it.
• Sub-line: the plan kind followed by a fraction, for example "Playbook · 14 of 18 memberships." The fraction is the count of memberships the plan currently affects over the total it was pushed to.
• Meta line: either the median days to acknowledge ("median 6d to acknowledge") if the cron has calculated one, or, if not, how long the plan has been live ("live since Mar 3").

These tiles render wider than standard tiles so the title and stats have room to breathe.

Empty state. If no plan yet has an adoption percentage, the row collapses to a plain text block instead of an empty tile row:

Adoption rates appear after the next nightly cron decorates recently-activated plans.

This is expected the first day or two after a plan goes live. Adoption math is calculated by a nightly job, not in real time, so a freshly-activated plan will not show a percentage until the next overnight refresh.

Row 2: Need diagnosis

This row is the inverse of Row 1: plans with adoption under 40%, sorted lowest-first, so the plan struggling the most sits at the front. Like Row 1, it draws from completed and active plans and caps at six tiles.

There is one additional filter here that Row 1 doesn't apply: a plan only appears in Need Diagnosis once the cron has actually decorated it at least once (it has a "decoration refreshed" timestamp). This keeps a plan that was activated an hour ago, and simply hasn't had a chance to accumulate any adoption yet, from being flagged as an underperformer by default. A brand-new plan isn't struggling; it just hasn't been measured yet.

Tiles in this row use the same label/headline/sub-line layout as Row 1, but the meta line differs when a median-acknowledge figure exists: instead of just reporting the number, it adds "review friction," for example "11d median ack, review friction," as a nudge that a slow acknowledgment time is itself a diagnostic clue. If no median exists yet, the meta line reads "Awaiting acknowledgment."

Visually, these tiles carry a heavier, high-intensity accent in the Analyse signal color so they read as attention-needed at a glance.

Empty state. Unlike every other row on this page, Row 2 has no fallback text. If no plan currently qualifies (nothing is both under 40% adopted and already decorated), the entire row is omitted from the page. A network with no Need Diagnosis row is a network with nothing currently flagged as struggling; it is not a rendering gap.

Row 3: All active playbooks

This is the full list, every plan currently in active status, sorted by adoption percentage descending, with plans that have no adoption data yet pushed to the bottom rather than the top (so an unmeasured plan doesn't crowd out a plan you already know is struggling). The row caps at 18 tiles.

Each tile here is standard width (not the wider double-size used in Rows 1 and 2) and color-codes by adoption tier using the platform's signal palette:

• 75% or higher adoption: Expand green
• 40% to 74% adoption: Maintain yellow
• Under 40% adoption: Analyse red
• No adoption percentage yet: neutral copper

The sub-line drops the "median ack" framing seen in Rows 1 and 2 and instead shows just the kind and the raw fraction, for example "Directive · 9/12." The meta line shows "live since [date]" when the plan has an activation date, or is blank if it doesn't.

Empty state. If your network has no active plans at all, the row shows:

No active playbooks. Author one in Broadcast or activate a draft.

"Broadcast" links directly to /franchise/broadcast, where new plans originate (see below).

Clicking a tile: how the deep link works

Every tile on this page, in all three rows, is clickable. Clicking any plan tile does not open a modal or drawer on the Playbooks page itself; it navigates you to /franchise/decisions?plan=<plan-id>, opening that specific plan's detail view inside the Decisions Inbox.

This is the structural reason the Scoreboard and the Decisions Inbox are two separate pages rather than one page with two tabs: the Scoreboard is a ranked entry point, and the actual plan detail, the per-membership adoption roster, the Act / Park / Ignore controls, the Discuss-with-agent button, all of that machinery lives once, in the Decisions Inbox. The Scoreboard never duplicates that logic; it only ranks and routes to it.

Inside the plan detail you land on after clicking a tile, you'll see the full per-membership adoption breakdown: which memberships the plan was pushed to, and where each one sits in its lifecycle (pushed, acknowledged, in progress, declined, or completed). If your network operates on an independent-operator model, individual membership names in that breakdown are shown anonymized, consistent with the trust boundary described in HQ overview; on a same-entity (company-owned locations) network, real location names show through. Either way, you will never see the underlying business data behind a membership's adoption status, only that it has or hasn't engaged with the plan.

How playbooks originate: Broadcast

The Scoreboard is a read-only ranking. It has no compose button, no "new playbook" action anywhere on the page. Every plan that appears here was authored somewhere else first: Broadcast.

Open Broadcast from the sidebar (/franchise/broadcast) and select the Initiatives tab, one of five tabs in the capsule control at the top of the page (Announcements, Initiatives, Surveys, Polls, Consent). Initiatives is the umbrella label for outbound decision pushes: the plan kinds you'll see referenced across both Broadcast and the Scoreboard are Playbook, Directive, Recommendation, and Experiment.

1. 1From Broadcast, select the Initiatives tab.
2. 2Click + New initiative to author a new plan: give it a title, a body, and a kind.
3. 3The plan saves as a draft. It will not show adoption data and will not appear in either Scoreboard performer row until it is activated.
4. 4Activate the plan and push it to the memberships you choose. This is also where you can attach an IU sponsorship budget per membership, if your program covers some or all of the Intelligence Units a membership spends acting on the plan.
5. 5Once pushed, the plan enters active status. It shows up immediately in the Scoreboard's All active playbooks row (with no adoption percentage yet), and will pick up an adoption percentage after the next nightly cron run.

You can also track and manage everything you've pushed from the Initiatives tab itself without ever visiting the Scoreboard; the Scoreboard is a different lens on the same underlying plans, built for ranking rather than authoring or pushing.

What the numbers mean, in one place

A few figures recur across all three rows and are easy to misread if you're skimming:

• "N% adopted" is the adoption completion rate: the share of memberships the plan was pushed to that have reached completed status on that plan, not merely acknowledged it.
• "Awaiting cron" appears instead of a percentage when the nightly aggregation job hasn't run against this plan yet. This is normal for a plan activated within the last day.
• "X of Y memberships" (or "X/Y" in the All active row) is the current affected count over the current total count: how many memberships the plan is reaching, out of how many it was pushed to.
• "median Nd to acknowledge" is the median number of days it took memberships to move from pushed to acknowledged. A high number here, even on a plan with decent eventual adoption, is worth a look: it means memberships are getting there, just slowly.

Empty network state

If your organization hasn't shipped any decision plans at all yet, the hero band shows zero counts across the board, and every row below falls back to its own empty-state text as described above, guiding you to Broadcast to author your first plan.

Related articles

• HQ overview
• Broadcasting to your network
• Network health
• HQ benchmarks
• HQ programs
• HQ compliance

Data sources