The interventions queue for at-risk locations

What the interventions queue is

The interventions queue is where HQ tracks franchise locations that a human has flagged for follow-up. It is deliberately separate from the network's automated pattern detection: the Take Action row on the Network home surfaces signals Verinode's aggregator detects on its own (a compliance gap spreading across the cohort, a margin pattern repeating across offices), while an intervention is something an HQ admin decided to raise about one specific location, with a reason attached. A flagged location does not need to have tripped any automated signal at all, and an automated signal does not create an intervention by itself.

It is also worth separating from the Watchlist tile on the Network home, which is the bottom quarter of the composite office leaderboard, an automatic ranking based on the network's benchmark scores. Watchlist tells you who is ranking low. Interventions tells you who someone has actually decided to reach out to, and why. A location can be on the Watchlist without an open intervention, and vice versa.

Per Verinode's privacy boundary, HQ never queries a franchisee's own business systems directly. Everything behind the interventions queue, from the directory row to the financial and operational detail on a franchisee's card, is read from the network-level rollup tables the aggregator cron maintains in core.*. Franchisees own their data; HQ sees the aggregates that roll up into these summaries and rankings, and in networks of independent operators, the location's real name never enters the picture.

Where to find it

Open Network from the HQ sidebar (hq.verinode.ai/network). The Explore row near the bottom of the page has an Interventions tile: its number is the count of currently open interventions, with the subtext reading Open flags when the count is above zero or All clear when it is zero. Clicking it opens the Franchisees slider directly on the Interventions tab.

The same slider also opens from the Active, Invited, Seeded, and Cert Watch tiles on the Explore row, each landing on its matching tab. The Location Directory tile is a separate surface: it opens a different slider tab that carries the admin tools for adding, editing, or removing member rows, rather than the browse-and-drill-in view described below.

Flagging a franchisee for follow-up

Flagging is only available to HQ admins, from a franchisee's own detail card, not from the Interventions tab itself (rows only appear there once they are already flagged). Open any franchisee through the Active, Invited, Seeded, or Cert Watch tab and click into their row.

1. 1On the franchisee's detail card, look at the stat strip under the name. If there is no open intervention already, a Flag button appears next to it.
2. 2Click Flag. A dialog titled "Flag [location name]" opens.
3. 3Choose a Reason from the dropdown: "Engagement dropped, no recent data," "Margin trending below network," "Compliance gap, cert expiring or expired," "Brand-protection concern (reputation / safety)," or "Other (note inline)."
4. 4Optionally add an Intervention type, a free-text label such as "coaching call," "on-site visit," or "broker check-in." This is what shows on the intervention's tile alongside the reason.
5. 5Click Flag franchisee. The dialog confirms "Flagged [location name]. The intervention queue updates next refresh," then closes and refreshes the page.

Verinode blocks a duplicate: if the location already has an open intervention, the Flag button does not appear at all, and the underlying action would refuse a second one with "An open intervention already exists for this franchisee."

When a flag goes in, every other HQ admin on the account gets an in-app notification (the bell icon) under the Interventions category, titled "Franchisee flagged for intervention" with the reason as its body. The admin who created the flag does not get their own notification, since they just saw it happen.

Flag reason and status

Every intervention row carries two things: the reason it was raised, and its status.

The reason is either the preset dropdown text chosen at flag time, or the free-text "Other" note. It is what shows as the row's main line in the Interventions tab and on the franchisee's own card. If a row somehow has neither a reason nor notes on file (only possible on legacy data), it falls back to reading "Owner needs follow-up."

Status is one of five values:

• Queued, a new flag, not yet acted on.
• Contacted, someone reached out.
• In Progress, an intervention is actively underway.
• Resolved, the situation is closed out.
• Closed, the intervention was closed without further action.

The interventions queue only ever shows open interventions, meaning Queued, Contacted, or In Progress. The moment a row moves to Resolved or Closed, it drops out of the Interventions tab and out of the Explore tile's count, but it does not disappear from the network: it still shows on the franchisee's own detail card, in the full history described below.

The Interventions tab

Inside the Franchisees slider, the Interventions tab lists every open flag, most recently flagged first. Each row shows:

• The franchisee's name (or its anonymized label, see below)
• The flag reason or notes, as the body text
• The current status label
• The date it was flagged, in the top-right corner

Clicking a row opens that franchisee's full detail card, the same drill-in described in the next section. On the rare occasion a flagged operator has since dropped out of the directory entirely, the row still displays but is not clickable.

Empty state. When nothing is flagged, the tab reads: "No franchisees flagged for intervention. Use the directory to flag at-risk operators."

The franchisee detail drill-in

Clicking any franchisee row, from Interventions or any other tab, flips to a full detail card. This is the richer view referenced across HQ whenever a specific location comes up: it batches every rollup the aggregator maintains for that one operator into a single read, still without ever touching the franchisee's own systems.

At the top, a hero panel shows the location name, its city and state (or "Location pending"), and up to five stat pills: Cert health (the worst certification status on file), Programs (how many vendor, carrier, or TPA programs the location has adopted), Intervention (Open or None, in red or green), and, once the aggregator has computed them, Margin (a position band, not a raw figure: Top Quarter, Middle Half, Bottom Quarter, or Pending), Headcount (active against target), and Reputation (a composite score). The Flag button lives in this same header when there is no open intervention yet.

Below the hero, sections appear only when there is data behind them:

• Overview: location, city/state, status, and how long the location has been in the network.
• Financials: margin position, gross margin, cash runway, and days to pay. Until financial periods flow in, this reads "data will appear as the operator's financial periods flow in."
• Operations: SOP coverage, average cycle time, capacity utilization, equipment item count.
• Certifications (per-cert breakdown) and Certifications posture (the aggregate roll-up: total certs, active, expiring in 90 days, expired, CEC completion, last cert issued).
• Reputation: Google and Yelp ratings with review counts, BBB rating, composite score, and trend.
• Team: active headcount against target, FTEs, contractors, technicians, leadership, admin/office staff, average tenure, last hire, open safety incidents, OSHA recordables.
• Facilities: facility count, owned versus leased, square footage, monthly rent, leases expiring soon.
• Fleet: vehicle count, ownership mix, average vehicle age, overdue services, expiring registrations and DOT inspections, policy and driver detail, accident history.
• Forms & audits: form and audit counts, response rate, average audit score, open findings, last activity.
• Adopted programs: the vendor, carrier, and TPA programs this location has taken up.
• Interventions: the location's full history, every flag ever raised, not just the open one, each with its reason, notes, status, and flagged date. This is where the Edit notes (or Add notes) button lives, letting an admin record what happened, what a broker said, or what the next step is. Notes are encrypted at rest under the group's admin-only key; only HQ admins with an active session can read them.

Any of these sections is simply omitted from the card when there is no data behind it yet, rather than showing a row of dashes.

How the flag notification deep-links back to the queue

Two query parameters carry a franchisee or an intervention across HQ: ?member=<operator id> opens the Franchisees slider on the Active tab, pre-focused on that location's detail card, and ?intervention= opens it straight to the Interventions tab. Both work on /franchise/network and on the legacy /franchise/franchisees alias.

This is the same mechanism behind the notification a flag creates: the bell notification records a link back into the platform, so opening it from the notification list lands directly on the queue instead of the general Network home. Other HQ surfaces, wherever a specific franchisee's name shows up (Margin & Cash, Operations, Brand & Compliance, Facilities, Fleet, Safety, Team, Certifications, Reputation, Forms, saved items), carry the same ?member= link back to that location's card, so you never have to search the directory by hand once you've spotted a name elsewhere.

Whether a flag reaches you as an in-app bell notification or in your inbox depends on your own notification settings. Under Settings → Notifications, the Interventions category ("When a member is flagged for follow-up") can be toggled independently of the other categories, and the Email channel toggle controls whether flagged-for-follow-up notifications also land in your account email, on top of the in-app bell. Either way, the link inside carries you to the same deep-linked queue.

Who sees what

Every HQ user on the account, admin or not, sees the same directory and the same interventions queue: the list of flagged locations, their reasons, and their status is shared visibility across the account. Flagging a new location, and adding or editing notes on an existing flag, is restricted to admins. Viewers can open every card and read every section; they simply won't see the Flag or Edit notes controls.

Related articles

• Network Health, the home page these tiles and the franchisee directory live on
• HQ Compliance, for the certification detail behind the Cert Watch tab and a franchisee's Certifications sections
• HQ Benchmarks, for how the composite score behind Top Quartile and Watchlist is built
• HQ Overview, for how the Network page fits into the rest of the HQ shell