Plan activation and outcome cards: did the network move?

What these two cards are

Every decision plan you push through Verinode HQ, whether it is a canonical Playbook, a one-shot Directive, a soft Recommendation, or a network-level Experiment, surfaces back in your Feed twice. The moment you activate it, a lean announcement card appears: "Plan activated", plus the plan's title. Then, once the rollout finishes, a second card appears in its place on the timeline: an Outcome card, built from the same cron-decorated numbers that power the Playbook Scoreboard, answering the one question the announcement card cannot: did the network actually move?

These two cards are one thread of the Feed's "Decision plan activity" source, covered at a high level in The HQ feed: your network's home screen. This article is the deep-dive on that one thread: exactly what each card says, where every number comes from, and how to read the outcome line without over- or under-reading it.

Verinode does not decide whether a rollout succeeded. It reads your plan's activation and completion timestamps, your franchisees' adoption records, and the network signal the plan was built to address (when there is one), and lays the result out plainly. You decide what a given adoption rate means for your next move.

Where to find it

Open Feed from the HQ sidebar, or go straight to hq.verinode.ai/feed. Both card types live in the main stream, mixed in with your other network activity:

• The All filter shows them alongside everything else.
• The Decisions filter pill narrows the stream to your network's own activity, including these two card types.
• A deep link such as hq.verinode.ai/feed?filter=decisions&tb=30d opens straight into that filtered, 30-day view.

Both cards carry a Network pill in the top-right corner (the same steel-blue badge every network-activity card in the Feed uses) and, in the top-left, a source line reading Hq initiative for the activation card or Hq outcome for the outcome card, followed by how long ago the card fired, for example "Hq outcome · 3d."

Where a plan actually gets built and pushed to your network is a separate surface. For that, see Programs: how HQ codifies what the network adopts, the Playbook Scoreboard, and Playbook Kinds for the full authoring and portfolio-management story. This article covers only how the two Feed moments read.

The window: which plans show up

Both cards look back 60 days from today. A plan you activated 61 days ago and completed yesterday shows only its Outcome card; the activation announcement has aged out. A plan that both activated and completed within the last 60 days shows both cards as two separate entries in your stream, sorted to their own place by when each moment actually happened, not grouped together. Up to the 20 most recently updated plans in your group are eligible each time the feed loads.

The Plan Activated card

What it says. The headline reads "Plan activated," a dash, then your plan's title exactly as you authored it. The line beneath it reads the plan's kind, capitalized, followed by "now in flight across the network," for example:

• Playbook now in flight across the network.
• Directive now in flight across the network.
• Recommendation now in flight across the network.
• Experiment now in flight across the network.

That is the entire card. It carries no franchisee count, no percentage, and no severity color beyond the default informational tone, because at the moment of activation nothing has happened yet to measure. It exists to tell you the rollout is live, not how it is going.

What it links to. Nothing. There is no source URL behind this card, so it never opens a new tab. It is a pure announcement.

The Outcome card

What it says. The headline reads "Outcome," a dash, then the plan's title. The body line beneath it is built from the same fields the adoption metrics glossary defines in full detail for the Playbook Scoreboard and the plan detail view: the affected-of-total franchisee count, the adoption completion percentage, and whichever median-days figure is available. The Feed assembles them into one compact line, joined with a middle dot, choosing the richest combination the data supports:

| What has decorated so far | What the card reads | |---|---| | Affected/total present, percentage present, median-to-acknowledge present | "Adopted by 18 of 24 franchisees · 75% · median 2d to acknowledge" | | Affected/total present, percentage present, no median yet | "Adopted by 18 of 24 franchisees · 75%" | | Affected/total present, no percentage yet, median present | "18 of 24 franchisees adopted · median 2d to acknowledge" | | Affected/total present only | "18 of 24 franchisees adopted" | | No affected/total, median-to-acknowledge present | "median 2d to acknowledge" | | No affected/total, no median-to-acknowledge, median-to-start present | "median 5d to in-progress" | | Nothing has decorated yet | "Network-wide rollout wrapped." |

That last line is the card's own empty state for a brand-new completion: the cron that writes these numbers runs once overnight, so a plan that finished minutes or hours ago can genuinely have nothing to report yet. It resolves itself on the next nightly pass; there is nothing to configure or refresh manually.

A consequence of that split worth knowing: the percentage only ever prints on this card alongside the franchisee count, and the count only exists for plans authored against a specific network signal. A plan you built as a general initiative, with no signal binding, will never show a percentage on its Outcome card even once its completion rate is fully calculated, it falls to the median-days row instead, or to the plain wrap-up line if no median is available either. If you need that plan's percentage regardless of signal binding, it is always on the Playbook Scoreboard and the plan's own detail view, which read the percentage on its own, unbundled from the franchisee count.

What it links to. Nothing, same as the activation card. It is a read-only summary; the per-franchisee breakdown behind it lives on the plan's own record, reached from Playbooks or Decisions, not from this card.

Reading the numbers together

Say you activated a Directive titled "Winter Storm Prep Protocol" across a network of 24 memberships twelve days ago, and it completed two days ago. Overnight, the cron decorates the plan: current_affected_count 18, current_total_count 24, adoption_completion_rate_pct 75, median_days_to_acknowledge 2. Your Feed shows two cards for this plan within the same 60-day window:

• Plan activated, Winter Storm Prep Protocol, twelve days ago: "Directive now in flight across the network."
• Outcome, Winter Storm Prep Protocol, two days ago: "Adopted by 18 of 24 franchisees · 75% · median 2d to acknowledge."

Read that outcome line as two separate facts riding together, not one: three-quarters of the memberships you pushed the directive to finished it (the response side), and the underlying storm-prep signal still shows 18 of 24 franchisees affected today (the problem side, which may or may not track completion tightly depending on how the signal itself is defined). A fast median-to-acknowledge (2 days) tells you the network noticed the push quickly; it says nothing about whether they finished the work, which is what the percentage is for.

Interacting with the cards

Both card types carry the same three buttons along the bottom: Review, Noted, and Ignore. None of the three navigates anywhere, since neither card carries a link to open, they only change how the card behaves in your stream:

• Review marks the card read. It briefly shows a checkmark and the word "Done," then clears from your session.
• Noted briefly confirms with the word "Noted" and a few seconds to tap Undo before it clears the same way.
• Ignore dismisses the card immediately, with the same brief Undo window, after which it is gone for good.

For the full per-franchisee detail behind either card (exactly which memberships acknowledged, started, declined, or completed, and when), open the plan from Playbooks or from Decisions. These two Feed cards are the headline; the plan's own record is where you drill in.

Empty states

There is no dedicated empty-state message for this feature on its own; it simply contributes fewer, or zero, cards to the merged stream when nothing qualifies. Two feed-level empty states cover the cases that matter:

• If you filter to Decisions and nothing at all is currently pending in your network, whether that is signals, broadcasts, plan activity, consent responses, or adoptions, the panel reads: "No items match this filter."
• If you scroll to the end of any filter, you reach the shared closing card: "All caught up. Verinode IQ is continuously analyzing your data and scanning industry sources. New decisions, insights, and updates will appear here as they surface. Check back soon. Your next briefing is building."

A quiet network with no plans activated or completed in the last 60 days will simply show neither card type; nothing on screen calls that out specifically.

The privacy boundary

Both the activation and outcome cards are pure aggregate: a plan title, a kind, a franchisee count, a percentage, and a median-days figure. Neither card ever names a specific franchisee, and neither reads any franchisee's underlying job files, invoices, or margin numbers to build its numbers. The affected-of-total count and the adoption percentage are both rollups across your network, not a per-membership scorecard.

This is different from the Feed's separate plan adoptions cards (covered in the Feed overview), which do name the specific membership as it acknowledges, starts, completes, or declines a plan, subject to your network's entity-model configuration: an anonymized, stable label like "Franchisee #4F2A" for networks of legally separate, franchisee-owned locations, or a real location name for a network of your own company's own locations. The activation and outcome cards covered in this article never carry that per-membership detail at all; they only ever roll the whole network up into one line.

Best-practice example

You open Feed on a Monday morning and, filtering to Decisions, see an Outcome card near the top: "Outcome, Estimating Software Rollout," reading "Adopted by 9 of 30 franchisees · 30%." Thirty percent after the rollout has run its course is a program-health flag, not a franchisee-health flag, so instead of reacting to the headline number alone, you click into the plan from Playbooks, where the Need Diagnosis row already has it flagged. There you see the acknowledgment rate was actually fast, most memberships opened the push within a day or two, but few carried it through to completion, pointing at a substance or difficulty problem with the rollout itself rather than a visibility problem. That is a different next step (revise the plan, or follow up directly with the memberships that stalled) than if the acknowledgment rate itself had been slow.

Related reading

• The HQ feed: your network's home screen: where these two cards sit inside the full six-source stream.
• Reading Adoption Metrics: Rates, Median Days, and the Nightly Cron: the field-by-field definition of every number this article's outcome card summarizes.
• Playbook Scoreboard: The Network-Wide Adoption View: the full ranked, portfolio-level view these same numbers feed.
• Playbook Kinds: Playbook, Initiative, Intervention, Pattern, Subtask: what a plan's kind label means and which kinds you can actually author today.
• Scoreboard vs Decisions Inbox: Two Different Questions: where a plan gets pushed and managed day to day, upstream of both cards in this article.
• Programs: how HQ codifies what the network adopts: the broader standards and requirements catalog a decision plan often reinforces.
• Network health: the wider aggregate rollup these plan metrics are one slice of.
• HQ compliance: compliance-flavored plans and signals that can surface through this same Feed thread.