Status and domain facets

What this article covers

The Decisions board has two dropdown filters sitting above the gallery: a status filter and a business-area (domain) filter. Both carry a live count next to every option, and both counts are computed straight from your current row set every time the board renders, not cached, not stale. This article is the deep dive on how those two counts actually work, why the status numbers never move when you touch the domain filter but the domain numbers do move when you touch the status filter, how the readable labels (Governance, Compliance, Operations, Risk) get built from the underlying data instead of showing raw tokens, and what happens at the edges: when a filter combination would leave nothing on screen, when the domain dropdown disappears entirely, and how search and sort layer on top.

For the walkthrough of the board itself, tiles, buttons, the slider, start with HQ Decisions: the franchisor inbox. For where every row actually comes from and how its status, domain, and severity get assigned, see The four HQ decision sources and how they map into one log. This article assumes both and goes one layer deeper, into the filter bar's own logic.

Where to find it

Open Decisions from the HQ sidebar, at hq.verinode.ai/decisions. The filter bar sits directly under the page header, above the gallery of decision tiles. Reading left to right: a Search decisions… text box, the status dropdown, and, when it qualifies (see below), the business-area dropdown, followed by a Newest first / Biggest impact sort dropdown. There is no Gantt or Calendar toggle on this page, and no "From a scan" chip either, those belong to other surfaces; Decisions is always a flat gallery here. The sibling page, Action Plans at hq.verinode.ai/actions, uses its own separate filter (bucketed by plan-step urgency, not by status or domain) and doesn't carry either of the two facets this article covers.

The status dropdown: six counts computed from every row on the board

The status dropdown lists six options, each with its live count in parentheses:

• All, every row currently on the board, regardless of any other filter.
• Pending, rows that haven't been acted on, parked, ignored, or resolved yet.
• Acted, rows you've moved forward.
• Parked, rows you've paused.
• Ignored, rows you've dismissed or archived.
• Resolved, rows closed out.

Two things are worth being precise about, because they explain the numbers you'll see:

The count is a straight tally of the whole board, not a filtered subset. Whichever business area or search term you currently have active, the status dropdown's numbers stay exactly the same. If your board has 40 total rows and 12 of them are Pending, the dropdown reads "Pending (12)" whether you're looking at all business areas, only Compliance, or you've typed a search term into the box above it. The status count answers one question only: across everything HQ has surfaced to you, how many rows are in this state. It's the stable reference number for the whole inbox.

Pending is a merge of two underlying states. Internally, a fresh row starts in one of two raw states before anyone has acted, parked, ignored, or resolved it. The dropdown collapses both of those into the single Pending bucket rather than splitting them, since the distinction (has HQ opened the tile yet, or not) isn't a decision HQ needs to make, only whether it's still waiting on a call.

The business-area dropdown: counts scoped to whichever status you're already viewing

This is where the mechanics diverge from the status dropdown, and it's the detail worth understanding if the numbers ever look inconsistent at first glance.

The domain count only looks at rows matching your current status selection. If you've set the status dropdown to Pending, the business-area dropdown's counts describe only the Pending rows, not the whole board. So "Compliance (5)" next to Pending means 5 of your current Pending rows are Compliance rows, not that there are 5 Compliance rows total across every status. Switch the status dropdown to Resolved and the same Compliance option might read "Compliance (1)" or disappear altogether, because it's now counting a completely different slice: resolved rows only.

This is deliberate, and it reads naturally once you notice it: the business-area filter exists to help you break down whatever you're already looking at, not to give you a second, independent view of the whole inbox. "Pending (12)" followed by narrowing to "Compliance (5)" tells you, in one glance, that 5 of those 12 outstanding items are compliance-related, which is exactly the number you'd want before deciding where to spend the next ten minutes.

The dropdown only appears once your current status view spans two or more business areas. If everything under your current status selection happens to fall into a single business area, say every Resolved row on your board today is Operations, the business-area dropdown doesn't render at all for that status. There's nothing to break down. Switch back to All or to a status where the rows span multiple areas, and the dropdown reappears with its own fresh set of options and counts.

Options are listed alphabetically by their readable label, not by raw code order or row count. Whatever areas qualify under the current status render as Compliance, Governance, Operations, Risk (in that alphabetical order, once all four are present), each followed by its count. An All areas option sits first, showing the total for whatever status is active.

Choosing a business area filters the gallery down further, on top of the status filter. Picking a status and a business area together narrows to rows that satisfy both, exactly as you'd expect from two stacked filters.

What happens when a filter combination empties out

The two dropdowns are wired to protect you from a dead end: a business-area selection that quietly filters everything off the board because the status you just switched to doesn't have any rows in that area.

If you have a business area selected and then change the status dropdown to a status where that area currently has zero rows, Verinode automatically resets the business-area dropdown back to All areas the moment that happens. You land on the full set of rows for your new status instead of an empty grid with an invisible, phantom filter still applied. You'll need to re-pick the business area if you still want it narrowed, but you won't be stuck staring at a blank gallery wondering why nothing is showing up.

If the combination of status, business area, and your search term together still leaves nothing to show, the gallery shows a plain message instead of an empty grid. With the status dropdown on All, it reads:

No decisions for you yet. They'll land here as Verinode spots cost savings, risk, and growth opportunities in your data.

With any other status selected, for example Acted, it reads:

Nothing acted for you right now.

(Substituting the label of whichever status you've chosen, lowercased: pending, acted, parked, ignored, resolved.) This message reflects the status filter's wording specifically; a business-area filter that also happens to be narrowing the view doesn't get its own separate empty-state sentence, the status-level message is what you'll see either way.

Why the labels read as words, not database tokens

Every row on the Decisions board is tagged, underneath, with one of the domain values HQ's decision mapper produces: rows from your own decision plans land in the operations area, at-risk-location interventions in risk, benchmark consent requests in governance, and program audits or violations in compliance. A fifth value, growth, exists in the same underlying vocabulary, reserved for future network-growth decision types (expansion or territory-level initiatives), but none of today's four sources produce it, so you won't see a Growth option on this board yet.

Rather than showing those raw lowercase tokens in the dropdown, a small label map turns each one into the word you'd actually want to read: compliance becomes "Compliance," and the remaining values, since they're already plain English words underneath, get automatically capitalized into "Governance," "Operations," "Risk," and (once it's ever produced) "Growth." The same readability rule extends to the domain chip printed on each individual tile in the gallery, so the word you filter by and the word stamped on the tile always match.

This is the same general mechanism the operator side of the platform uses for its own, much larger domain vocabulary (Vendors, Equipment, Carriers, Clients, Billing, and so on, for IQ's own Decisions log), just applied to HQ's smaller, network-level set of five. Whichever side of the platform you're on, the rule is the same: nothing that reaches this filter bar is ever left as a raw database token, and any new area added to the underlying vocabulary automatically renders as Title Case even before anyone gets around to giving it a bespoke label.

Search and sort on top of the facets

Search narrows whatever the two dropdowns have already selected. It matches against a row's title and, for rows that name one (interventions and consent requests name the affected membership; audits and violations name the program), that name. Search doesn't touch either dropdown's counts, those are always computed before your search term is applied, so a status count like "Pending (12)" stays "12" even while your search box is actively hiding rows that don't match your text.

Sort offers Newest first (the default) or Biggest impact. On this board, sort doesn't change which rows are showing, only their order. In practice, Biggest impact and Newest first currently produce the same order here: none of the four HQ decision sources carries a calculated dollar-impact estimate the way an operator-side signal can, so there's nothing for the impact sort to rank by yet. Newest first orders by when each row was first detected, flagged, requested, or conducted.

How to use it

1. 1Start with the status dropdown on Pending, since its count is a stable read of everything currently waiting on a call from you, independent of any other filter you add.
2. 2If a business-area dropdown appears, use it to see the makeup of that Pending count, for example how many of your outstanding items are Compliance versus Risk versus Governance.
3. 3Switch statuses to check other buckets. Watch the business-area dropdown's options and counts change (or disappear) as they reflect the new status, that's expected, not a bug.
4. 4Add a search term only once you've narrowed with the dropdowns, since search stacks on top of whatever they've already filtered down to.
5. 5Leave sort on Newest first unless you specifically want to check whether Biggest impact would reorder anything, on this board today it won't.

Related reading

• HQ Decisions: the franchisor inbox, the full walkthrough of the board: tiles, buttons, the slider, and the privacy boundary.
• The four HQ decision sources and how they map into one log, where each row's status, domain, and severity actually come from, and how far back each source reads.
• Network playbooks and directives as decision rows, the Operations-domain rows in detail.
• The interventions queue for at-risk locations, the Risk-domain rows in detail.
• Audits and violations: enforcing a program, the Compliance-domain rows in detail.
• Compliance: brand health across your network, where the certification, safety, and reputation data behind program audits and violations rolls up.
• What HQ sees, the platform shell this page lives inside.

Data sources