The two-consecutive-refresh miss signal

What this signal is

Process Standards grades every office's stage median against your network's target-days standards on every nightly rollup (see hq-conformance-grading for the full Met / Near / Missed math). A single Missed grade, on its own, doesn't raise anything to your Feed. One slow rollup can happen to any office for any reason: a short-staffed week, a couple of unusually complex jobs, a data-entry lag. Verinode does not escalate on that.

What it does watch for is a pattern: the same office grading Missed on the same standardized transition on two consecutive nightly rollups in a row. That's the trigger for this signal. One bad refresh is noise. Two in a row is a sustained miss worth a conversation, and that's the bar Verinode holds before it puts anything in front of leadership.

This is a distinct mechanism from the cross-network signals covered in hq-network-cross-signals. Those fire when a pattern shows up across a meaningful share of your active members and deliberately withhold which members are affected. This signal is the opposite shape: it always names one specific office and one specific standard, because the whole point is a targeted follow-up with that location, not a network-wide pattern.

Where to find it

This signal surfaces in three places, all reading the same underlying row:

• HQ Feed (hq.verinode.ai/feed, the sidebar's Feed entry): the signal appears in your daily item stream alongside every other network signal, industry content, and plan update.
• Take Action row on Network Health (hq.verinode.ai/network, sidebar Network): the second row on the page, directly under the hero. Every open signal, this one included, renders as a tile there, ordered by severity, most recent first.
• Signals tab, inside the Network Health card slider. Click any Take Action tile to open it, or swipe to the Signals tab directly. This is the full list, not just the top six.

Confirming a miss also drafts a recommendation plan on your Decisions page (hq.verinode.ai/decisions, sidebar Decisions), pre-titled and pre-written, sitting in draft status until you activate it. See "The drafted plan" below.

How a miss gets confirmed

Two things have to line up before this signal can fire at all:

1. A standard has to exist. If your network hasn't set a target-days standard for any transition yet (on the Process Standards page, reached from Compliance in the sidebar), there is nothing for an office to miss, and the detector doesn't run.
2. Two consecutive aggregate snapshots have to exist. The nightly rollup writes one snapshot per day. "Two consecutive refreshes" means the two most recent snapshot dates on file for your network, whatever the actual gap between them happens to be. On a brand-new network with only one snapshot so far, there's no prior snapshot to compare against, so nothing can be confirmed yet.

Given both, the check runs per office, per standardized transition:

• The office's stage median on the latest snapshot has to grade Missed (more than 20% over the standard's target days).
• The office's stage median on the prior snapshot also has to grade Missed against the same standard.
• If either snapshot's median is null, meaning the office hadn't yet cleared the five-case floor on that transition (the "warming up" state described in hq-conformance-grading), that office×transition pair is skipped entirely. A thin or missing sample never counts toward a miss, on either side of the comparison.

Only when both conditions hold does the office×transition pair become a candidate. A single Missed grade, even a bad one, never fires this signal by itself; it takes the same office missing the same standard twice running.

Worst-first ordering

On any given night, more than one office×transition pair can clear the two-consecutive-miss bar at once. Verinode ranks every confirmed candidate across the whole network by overshoot, how far past the target the latest median is, as a percentage of that target, and works down from the worst.

Only the single worst office×transition candidate is written as a signal (and paired with a drafted plan) on a given day. Every other confirmed miss detected in that same run is not dropped, it's recorded internally alongside the top one, but it does not get its own tile, its own row, or its own drafted plan on that day's refresh. If that runner-up office is still missing the same standard on the next rollup too, and it's the worst candidate that night, it surfaces then. The mechanism is designed to put one clear, actionable item in front of you at a time rather than flood the Feed with every office that's currently behind.

In practice this means: when you see this signal, you're looking at whichever office is currently furthest past its standard on a transition it has now missed twice running, not necessarily the only office in that state.

The severity split at 50% overshoot

Every confirmed miss has already cleared the 20% overshoot that makes it grade Missed in the first place. On top of that, this signal splits into two severities based on how far past 20% the latest overshoot runs:

• 50% or more past target: severity Watch (shown in the Hard Hat Yellow accent, the same tone used across the platform for a Watch-level signal).
• Under 50% past target: severity Heads-up (shown in copper, the platform's informational tone).

For example, if a standard is set at 4 days and an office's latest median comes in at 6.4 days, that's 60% over target, past the 50% line, so it fires as Watch. If the same office's median were 5.2 days instead, that's 30% over target, past the 20% Missed floor but under the 50% escalation line, so it fires as Heads-up.

This signal never reaches Critical severity, regardless of how far past target an office runs. That has one practical consequence worth knowing: the Feed's escalation tool (the floating button that lets you hand off the day's critical signals to a regional manager by email) only ever collects Critical-severity items, so a conformance miss never appears in that hand-off list. It stays a Feed and Network Health item you review directly, not something the platform auto-escalates further.

Reading the tile

On the Take Action row and in the Signals tab, this signal reads like every other signal tile: a severity label, a headline, a supporting body sentence, and a detected date. For this signal specifically:

• Headline: "[Office] past the network standard on [Transition]," for example "Franchisee #A1B2 past the network standard on Assigned → Estimate submitted."
• Body: names the transition and office again, states the office's latest median in days against the target in days, notes that both of the last two rollups came back Missed, gives the exact overshoot percentage, states the prior rollup's median for context, and closes with a line about what standards are for and what to do next. For example: "Assigned → Estimate submitted at Franchisee #A1B2 ran 6.4 days at the median against the 4 days network standard on each of the last two rollups (60% past target; prior rollup 6.1 days). Standards keep the network's customer promise consistent: review staffing, handoffs, and workload with the location and agree on a path back inside the standard."
• Meta line: reads "Network Pattern" on this signal's tile, the same fallback text a cross-network coverage signal shows when it doesn't carry an affected-of-total count. Don't read that literally here: this signal always names one specific office, it just doesn't carry the "N of M members" ratio the coverage-signal family uses, so the tile falls back to that generic label. The office name in the headline and body is the real evidence.
• Icon: the process glyph, the same one used for stage-duration drift signals.
• Evidence column: this signal carries no dot-grid or trend sparkline, so the tile shows no visual in its right column, just the icon header.

The drafted plan

Confirming a miss also writes a recommendation-kind plan to your Decisions Inbox, in draft status, titled "Bring [transition] back inside the standard at [office]." Its body restates the miss and proposes a recommended play: confirm the pattern with the location, find the local driver (staffing, handoffs, or workload), and agree on a corrective step with a follow-up date, closing with "Activate this to start the intervention."

The plan won't spawn a duplicate draft every night the same office keeps missing the same standard: Verinode checks for an existing open plan (draft, active, or paused) tied to this signal type, this office, and this transition before writing a new one, and skips the write if one is already sitting open. You'll only see a fresh draft here once the prior one has been resolved or the miss clears and later resurfaces as new.

See hq-playbook-scoreboard-vs-decisions-inbox for how a drafted recommendation moves from draft to active to pushed, and how its adoption is tracked once it's live.

Office naming and the privacy boundary

The office name in this signal's headline and body follows the same identity rule as the rest of Network Health: on an independent-operators network (the default for a franchise or association), the office renders as a stable anonymized label rather than its real name. On a same-entity network (a single-owner, multi-location business), real location names show through.

Whichever form the name takes, this signal, like every other Standards Conformance surface, never carries anything more granular than the office's own stage median and the standard it's being checked against. No individual job, invoice, adjuster name, or customer detail enters this calculation at any point. Franchisees keep ownership of their operational data; this signal exists to give leadership a timely nudge on a sustained miss, not a window into a location's underlying business.

When it doesn't fire

This signal has no bespoke empty-state text of its own. Instead, it simply doesn't write a row, and the surfaces it would have appeared on fall back to their own general empty states:

• No signals of any kind are open. The Take Action row and Signals tab both read: "No open signals. Cross-network warnings appear here when ≥30% of active franchisees hit the same pattern." (That copy describes the cross-network family; this signal can still be the thing that appears there once it fires, the empty-state text just wasn't written with this signal specifically in mind.)
• No standards are set anywhere. There's nothing to miss, so this detector has nothing to check. See the Process Standards empty states in hq-conformance-grading for what that page shows instead.
• Standards exist but there's only one snapshot on file. There's no prior rollup to compare the latest one against, so a miss can't be confirmed yet regardless of how far any office is over target on that single snapshot.
• Offices are missing standards, but never the same one twice in a row. An office can grade Missed one night and Met or Near the next, bouncing around the tolerance band. Because the check requires the identical office×transition pair to miss on both of the two most recent snapshots, that kind of noise never confirms.

None of these are broken states. A quiet Feed on this front means either your standards are being kept, or no office has missed the same one twice running yet.

How to use it

1. 1When this signal appears on Take Action or in the Feed, read the headline and body first: they already name the office, the transition, both medians, and the exact overshoot percentage.
2. 2Check the severity. Watch (50%+ over target) is worth prioritizing over Heads-up (20-50% over) if you're triaging more than one signal at once.
3. 3Open the drafted plan on Decisions. It's already written with a recommended play: confirm the pattern with the location, find the driver, agree on a corrective step and a follow-up date.
4. 4Activate the plan when you're ready to start the intervention, or work the conversation with the location first and activate once you've agreed on next steps.
5. 5If the same office keeps resurfacing on the same transition, treat it as a coaching problem for that location. If several different offices are hitting the same transition's standard hard, that's more likely a sign the standard itself needs a second look. See the Conformance tab in hq-standards-conformance for the full office-by-office breakdown on any transition.

Related articles

• hq-conformance-grading: the Met / Near / Missed / Warming up grading math this signal builds on, including the 20% tolerance band and the five-case floor.
• hq-standards-conformance: the Conformance tab and tile on Network Health, where every office's standing on every standardized transition is browsable directly, not just the single worst confirmed miss.
• hq-standards: setting a target-days standard per transition, and adopting the network's own medians in bulk.
• hq-network-cross-signals: the other signal family on this same Feed and Take Action row, cross-network patterns that withhold which specific members are affected.
• network-health: the full Network Health page this signal's tile and Signals tab live on.
• hq-playbook-scoreboard-vs-decisions-inbox: how the drafted recommendation plan moves from draft to active and gets tracked for adoption.