"HQ Decisions: the franchisor inbox"

What HQ Decisions is

Every network has four separate places where a franchisor makes a call: playbook plans you've drafted for the network, at-risk locations someone flagged for follow-up, benchmark consent requests waiting on your response, and program audits or violations sitting in your judgment queue. Left as four tables, that's four places to check every morning. Decisions is Verinode's answer: one inbox that projects all four sources into a single board, so leadership works one queue instead of four.

The board itself is not a new surface built for HQ. It's the same Decision Log component Verinode IQ uses on the operator side (gallery view, search, status and sort controls, a workspace slider that opens on click), reused here so the read is identical no matter which side of the platform you're on. What changes is what feeds it: four core.* source tables instead of an operator's own signals.

Per Verinode's privacy boundary, HQ never reaches into a franchisee's own business systems to build this board. Interventions and consent requests carry a franchisee identity, but everything else behind this page, the row data, the status, the timing, comes from the network-level tables HQ's own admins and Verinode's aggregator already maintain. Franchisees own their data; this inbox is HQ's own workflow, not a window into anyone's private books.

Where to find it

Click Decisions in the HQ sidebar. The page lives at hq.verinode.ai/decisions. The header reads Decisions, with the subtitle describing it as network-level decisions across plans, interventions, consent requests, and program audits, the franchisor inbox.

A sibling page, Actions, sits at /franchise/actions and reads the exact same four sources. Decisions is the full log, a flat gallery organized by status. Actions is the execution view: only the plans currently in flight, laid out on a Gantt timeline by when their next step is due. This article covers Decisions; think of Actions as "what am I actively running" versus Decisions' "what's in my inbox, in total."

The four sources, in plain terms

Every row on the board traces back to one of four places:

• Decision plans are the playbooks you've drafted for the network, the kind of coordinated initiative you'd roll out across multiple locations (a new program, a process change, a directive). A plan's status moves through draft, active, paused, completed, or archived.
• Interventions are locations flagged for follow-up, the same queue described in full in The interventions queue for at-risk locations. A flag starts Queued, moves to Contacted, then In Progress, and ends Resolved or closed without action.
• Consent requests are HQ's own asks of a franchisee, most often a request to unlock a benchmark comparison or share a data point. A request sits Pending until the franchisee answers Approved, Declined, Withdrawn, or it simply Expires.
• Program audits and violations are the judgment queue behind vendor, carrier, and TPA programs: an audit submitted for your review (or disputed by the franchisee running it), and an open or escalated violation against a program's rules.

Each source keeps its own lifecycle underneath the hood. What this page does is translate all four into the same shape, so you never have to remember which table uses which words for "still open."

The board

Search and filters

Along the top of the gallery:

• Search decisions…, a plain text box matching against the row's title and, where the row names one, the franchisee or program it's about.
• Status dropdown, six options, each showing its live count in parentheses: All, Pending (new or seen, not yet acted on), Acted (you've moved it forward), Parked (you've paused it), Ignored (you've dismissed or archived it), Resolved (closed out). These are the same five working states IQ's Decision Log uses on the operator side; HQ's four sources each map their own status values into this shared set so the counts stay coherent across all of them.
• Business-area dropdown ("All areas"), appears once your open rows span two or more business areas. HQ's four sources land in Operations (decision plans), Risk (interventions), Governance (consent requests), and Compliance (program audits and violations). Counts reflect only what's left after the status filter, so picking Pending first and then Compliance tells you how many of those pending rows are audit or violation related.
• Sort dropdown, Newest first (the default) or Biggest impact. HQ rows on this board don't currently carry a calculated dollar estimate, so in practice sort defaults to date order regardless of which option is selected.

Unlike the operator-side Decisions log, this board does not organize itself into "Decide this week / Coming up / Handled" lanes, and it doesn't offer a Gantt or Calendar toggle, both of those are reserved for the Actions page. Decisions here is always a flat gallery.

Reading a tile

Each row renders as a tile with a colored accent that carries the same meaning it does everywhere else on the platform: red for an urgent pending item, amber for a non-urgent pending one, green for something acted on or resolved, teal for parked, grey for ignored. A tile shows:

• A small icon: the entity's logo where the row names a vendor, client, carrier, or TPA, or a domain glyph otherwise.
• The title, the plan's name, the flag reason, the consent request's rationale, or the audit type paired with the program name (for example, "Compliance audit · Fire Restoration Standard").
• The entity name, when the row is about one: an anonymized franchisee label for interventions and consent requests (see below), or the program name for audits and violations.
• The status label and a date, when the row was first detected, flagged, requested, or conducted.

Buttons on a tile

The tile's action buttons are wired to the same underlying source table the row came from, and which buttons appear depends on both the source and its current status:

• Decision plans: Act moves a draft or paused plan to active, or an active plan to completed. Park is available on an active plan and pauses it. Ignore archives the plan from any state.
• Interventions: Act advances the lifecycle, queued to contacted, contacted to in progress, in progress to resolved. Ignore closes the intervention with no action taken. There's no Park button here, an intervention has no paused state.
• Consent requests: HQ can only Ignore, which withdraws the request. Approving or declining is the franchisee's call, not HQ's, so those buttons don't appear here.
• Program audits: Act approves a submitted or disputed audit. Ignore disputes a submitted audit.
• Program violations: Act resolves the violation. Park escalates an open violation. Ignore waives it.
• Discuss appears on every row regardless of status. It opens the AI agent panel with this row's context loaded, so you can talk through the situation before deciding what to do with it.

Rows already in a resolved or dismissed state show Discuss only, there's nothing left to act on.

Clicking anywhere on the tile body (not a button) opens the same row in the workspace slider for a closer read, without triggering any status change.

Domains and severity

Every row carries a business-area domain and a severity. Decision plans read as Operations, a directive-kind plan carries Warning severity while a standard plan reads Info. Interventions are always Risk / Warning. Consent requests are Governance / Info. Program audits are Compliance, Info normally and Warning once disputed. Violations are Compliance, and their severity mirrors what was recorded on the underlying violation record, Critical, Warning (for a high-severity violation), or Info.

Empty states

If nothing matches the current filter, the gallery shows a plain message instead of an empty grid. With the status dropdown on All, it reads that there are no decisions yet and that they'll appear as Verinode spots cost savings, risk, and growth opportunities in your data. With any other status selected, it reads that nothing is in that state right now, for example nothing acted, nothing parked.

The privacy boundary on this board

Two of the four sources, interventions and consent requests, name a specific franchisee. That name is anonymized by default: unless your network's entity model is configured as a single legal entity (one operator running every location), the location's real name is replaced with a stable anonymized label everywhere it would otherwise appear on this board, in search, and inside the workspace slider. Decision plans, program audits, and violations don't carry a franchisee identity at all, they're about the network or a program, not about any one member's private data.

This board never pulls a franchisee's job files, invoices, or claims. Interventions and consent requests read from the network data and the network data, tables HQ's own admins populate directly; decision plans read from the network data; audits and violations read from the network data and the network data, joined to your network's own program records. None of the four touch a franchisee's pii.* business data.

How to use it

1. 1Open Decisions from the sidebar and start with the status filter on Pending, that's everything waiting on a call from you.
2. 2If your board spans several business areas, narrow with the area dropdown, Governance for consent requests waiting on a response, Risk for open interventions, Compliance for audits and violations.
3. 3Click Discuss on a row before acting if you want to talk it through with the agent first, especially on a disputed audit or an escalated violation.
4. 4Use the row's Act, Park, or Ignore button to move it forward. The change applies immediately and the tile updates without a page reload.
5. 5Check Actions at hq.verinode.ai/actions for the Gantt-style execution view once a decision plan is active, so you can see its timeline against everything else in flight.

Related reading

• The interventions queue for at-risk locations, the full detail on flagging, statuses, and the franchisee drill-in behind an intervention row.
• Compliance: brand health across your network, where certification, safety, and reputation data behind program audits and violations rolls up.
• Network Health: your HQ command home, the network's front page and where interventions first get flagged.
• Programs, where the vendor, carrier, and TPA programs behind audits and violations are set up and managed.
• Standards, the process standards and forms audits that feed some of the audit rows on this board.
• Report library, where broadcasts and one-off exports related to network decisions are archived.
• Broadcasting to your network, for pushing a decision plan's outcome out to every location once it's complete.
• What HQ sees, the platform shell this page lives inside.
• Item 19 basics, background on the disclosure rules that shape how program compliance data gets used.
• Discovery Day, the in-person step some program and consent decisions eventually feed into.

Data sources