Franchisee adoption events: who acknowledged, started, completed

What a plan-adoption card is

When you activate a decision plan across your network, each individual franchisee it was rolled out to works through it on their own side of the platform: they acknowledge it, start it, and eventually complete it, or they decline it. Every time one of those individual transitions happens, Verinode drops a card into your Feed marking that one franchisee moved. That card is a plan-adoption card, and like every card describing your network's own activity, it renders as a network_event item with the Network badge.

This is a different lens than the plan-level activation and outcome cards you already see. Those tell you a rollout started or finished network-wide, with an aggregate adoption rate. A plan-adoption card tells you about one franchisee's individual progress on that same plan. Together they answer both "did the network move?" and "who, specifically, moved?"

Where to find it

Open Feed from the HQ sidebar at hq.verinode.ai/feed. Plan-adoption cards appear woven into the same stream as every other network event: network signals, broadcasts you sent, plan activations and outcomes, consent responses, and industry content, all sorted newest first, with critical-severity items (which adoption cards never are) floating to the top regardless of age.

Plan-adoption cards only appear under the All filter tab. They are not decisions, so they do not show under Decisions; they are not industry or vendor content, so they do not show under Content; and they are not calendar events, so they do not show under Events. If you are looking for one and a different filter tab is selected, switch back to All.

Cards resolve within a rolling 30-day window: a franchisee's acknowledgment, start, completion, or decline only shows in the Feed for 30 days after it happened. Older adoption activity still lives on the underlying plan record; it simply ages out of the Feed stream itself.

What the card shows

Title. Reads as <Franchisee> <verb> <plan name>, where the verb is one of acknowledged, started, completed, or declined, for example "Franchisee #4A2F completed Winter Storm Response Protocol." If the plan record cannot be resolved, the title falls back to the generic "a plan" in place of the name.

The franchisee name follows the same privacy rule as the rest of HQ: in the default independent_operators entity model, you see an anonymized label like Franchisee #4A2F, a stable, per-operator label built from the last four characters of the operator's internal ID, not their real name. If your network's entity model has been set to same_entity (a single company operating its own multiple locations, not independent franchisees), the real location name passes through instead. Entity model is a network-wide setting, not something you change per card. See Network health for more on how HQ treats franchisee identity across the platform.

Badge. Network, styled in the steel-blue HQ color, the same badge every network_event card carries (plan activations, plan outcomes, and consent responses all share it too).

Severity. A completed, started, or acknowledged card renders as info severity, routine forward progress. A declined card renders as warning severity, the one case worth a second look: not because a franchisee is obligated to adopt every plan, but because a pattern of declines on the same plan can mean the rollout itself needs rethinking before you re-run it.

Body text. Always blank. Unlike a consent response card, which can carry the rationale HQ gave the franchisee for the original ask, a plan-adoption card carries no body copy, only the title line.

Timestamp. The card sorts by, and its relative time reads off, the moment that specific transition happened: the acknowledgment time for an acknowledged card, the start time for a started card, the completion time for a completed card, or the decline time for a declined card, never the date the plan was first activated.

What you will never see on this card: any detail of what the franchisee actually did while working the plan, or any other private business figure. Only that one franchisee moved to a new stage on one plan, and when.

The four transitions behind the card

1. 1Acknowledged. The franchisee has seen the plan and confirmed they received it. Nothing further has started yet.
2. 2Started (shown as "in progress" in the underlying record, "started" in the card). The franchisee is actively working the plan.
3. 3Completed. The franchisee finished the plan. This is the state that feeds into the plan's network-wide outcome card and adoption-rate math, described in HQ programs.
4. 4Declined. The franchisee opted out of the plan rather than working it. Flagged with warning severity, as above.

A franchisee who has been assigned a plan but has not yet acted on it produces no card at all, cards only mark a transition that actually happened.

What the buttons do

Every plan-adoption card carries the standard three-button row:

• Review: the primary action. Acknowledges the card on your side; Verinode logs that you reviewed it and the card fades from the stream a few seconds later.
• Noted: a lighter acknowledgment for a card you want to register without treating as fully handled.
• Ignore: dismisses the card from the Feed without further action.

None of the three buttons open the underlying plan or the franchisee's workspace, there is no drill-through from this card by design. If a decline (or a pattern of them) is worth following up on, that is a conversation to have through your normal network channels (a broadcast, a call, or however your leadership team communicates), or a look at the plan's own detail under HQ programs, not a link this card provides. Verinode surfaces the signal; leadership decides how to act on it.

Empty states

If no franchisee acknowledged, started, completed, or declined a plan in the last 30 days, no plan-adoption cards appear at all, there is no dedicated empty-state message for this stream specifically. The Feed's general empty state covers it: once every stream is quiet, scrolling to the end of the stream shows "All caught up," with the note "Verinode IQ is continuously analyzing your data and scanning industry sources. New decisions, insights, and updates will appear here as they surface," and "Check back soon. Your next briefing is building." If you have a filter other than All selected and nothing matches it, you will see "No items match this filter."

Best-practice example

Say three cards land in the same morning's feed: "Franchisee #2C91 acknowledged Winter Storm Response Protocol," "Franchisee #7A0D started Winter Storm Response Protocol," and "Franchisee #4A2F declined Winter Storm Response Protocol," the last one flagged warning. Two franchisees are moving through the rollout on schedule, nothing to do there. The decline is the one worth a beat of attention, not to force the issue with that franchisee, but to note it against the plan's outcome card once the rollout closes. If a handful more declines land on the same plan over the following days, that is the actual signal: the plan itself, or the case made for it, may need a second look before the next rollout, exactly the read the plan's own outcome card (see HQ programs) is built to surface at the network level.

Related reading

• HQ feed overview: the full Feed shell, its six sources, filters, and ordering.
• HQ feed consent responses: the sibling network_event card type for consent approvals and declines.
• HQ programs: the decision plans themselves, their activation, and their network-wide outcome cards.
• Network health: how franchisee identity and the entity model work across HQ.
• HQ compliance: compliance-flavored network signals that can surface alongside adoption activity.