Cross-network signals in Take Action

What a cross-network signal is

Every membership running Verinode IQ generates its own signals: margin drift, a stalled job, a certification about to lapse, a slow-paying carrier. Those are private to that franchisee. HQ never sees them one by one, and it never sees which specific member tripped which specific alert.

What HQ does see is the pattern that emerges once the same kind of signal starts showing up across a meaningful slice of the network at once. When enough members hit the same issue in the same window, Verinode rolls it up into a single network-level row: a cross-network signal. Instead of "Acme Restoration's margin is drifting," HQ reads "12 of 40 locations · Margin Drift." The individual franchisee is never named in that rollup. The pattern is the finding, not the franchisee.

This is the mechanism behind the Take Action row on the Network page and the Signals tab in the slider beneath it. This article covers what triggers a cross-network signal, how the severity ladder works, what the affected-of-total evidence means, and how to read and act on every part of a signal tile.

Where to find it

Cross-network signals live in two places on the Network page (sidebar → Network group → the top item, which reads Network, Franchisees, or Locations depending on how your organization is set up):

• Take Action row. The second row on the page, directly under the hero gauge. Every open signal renders as a tile here, in severity order, newest first, up to six at a time.
• Signals tab. Click any Take Action tile, or open the slider and select the Signals tab, to see the full list, not just the top six.

Both surfaces read from the same underlying rows. Take Action is the headline view; Signals is the complete list.

How a pattern becomes a network signal

A cross-network signal starts life as an ordinary signal inside one member's IQ account. Verinode's aggregator watches every open signal of Watch or Critical severity across all active members in the network, groups them by signal type, and counts how many distinct members currently have one open.

That count only turns into something HQ sees once it clears a coverage bar. Verinode surfaces here are built to keep leadership out of the daily noise of a single franchisee's week and into the pattern that affects the network as a whole, so a signal needs to show up across roughly a third of active members before it appears at all. Below that share, it stays exactly where it started: inside that member's own IQ account, invisible to HQ.

Once it clears the bar, the rollup carries the severity of the underlying signals that fed it. A pattern built from Watch-level member signals surfaces as a Watch-level network signal; one built from Critical-level member signals surfaces as Critical. The coverage bar itself rises with severity too: a Critical-level pattern needs to show up across a distinctly larger share of active members before HQ sees it flagged Critical than a Watch-level pattern does. The idea is the same either way: the more alarming the label, the more of the network has to actually be affected to earn it. Verinode never surfaces a single outlying franchisee's problem as a network-wide critical.

A second, separate family of cross-network signals covers reporting coverage rather than a shared operational pattern: for example, a signal reading that a meaningful number of locations have not reported a P&L, or have no certifications on file. These fire on a simpler bar (a material share of the network not reporting) and typically carry a lower, informational severity, since the point is to nudge coverage up, not to flag a crisis.

The severity ladder

Every signal, whichever family it comes from, carries one of three severity labels:

| What you see | What it means | |---|---| | Critical | The pattern has cleared the higher coverage bar. Read this first. | | Watch | The pattern has cleared the lower coverage bar. Worth a look, not yet urgent. | | Heads-up | Informational. Typically a reporting-coverage nudge (a share of the network hasn't reported financials or certifications), not an operational risk. |

Take Action always orders tiles Critical first, then Watch, then Heads-up, and within a severity, most recently detected first. The Signals tab lists every open signal in the same order.

Reading a Take Action tile

Each tile on the Take Action row is built from one network signal row and carries the same six pieces, every time:

• Icon. A small glyph in the header keyed off what kind of pattern this is (margin, cash, cert, safety, process, and so on). It's a visual sort, not a control.
• Severity label. Critical, Watch, or Heads-up, colored to match (Ember Red for Critical, Hard Hat Yellow for Watch).
• Headline. The network-rollup title, in the shape "N of M locations · [Pattern]," for example "12 of 40 locations · Cert Expired." If literally every active member is affected, it reads "All M locations · [Pattern]" instead of repeating the same number twice.
• Supporting line. A sentence naming the pattern, how many members it hit this week, and what share of the network that represents.
• Evidence column. A small dot grid: one dot per active member, with the affected share filled in the signal's severity color, and a caption underneath reading "N of M · X%." This is the affected-of-total evidence in visual form, at a glance you can see roughly what fraction of the network is lit up without reading a number first.
• Detected date. In the tile's corner, the date this network row was last written.

Click any tile and it opens the Signals tab in the slider, scrolled to and highlighting that exact signal.

The Signals tab

Inside the slider, the Signals tab lists every open network signal as a row, most severe and most recent first. Each row shows:

• The severity label, in the same color as Take Action.
• The affected-of-total line: "N of M members" when the signal carries that evidence, or "Network pattern" when it doesn't.
• The title and the body sentence explaining the pattern in plain language.
• The date it was detected.

There's no per-member drill-in from here. A network signal is a rollup by design, and the Signals tab keeps it that way: you get the pattern, the share of the network it touches, and when it was first seen, never a link to the specific franchisee behind it.

Empty state. When there are no open signals, the tab reads: "No open signals. Cross-network warnings appear here when roughly a third of active franchisees hit the same pattern." (The Take Action row phrases the same idea slightly differently: "No open signals. Cross-network warnings appear here when ≥30% of active franchisees hit the same pattern.") Either way, an empty Signals tab is a genuinely quiet network, not a broken feed. A signal that clears the bar for even one member's individual pattern will appear here on the next refresh; it simply hasn't yet.

What to do with a cross-network signal

A cross-network signal is a prompt to look at process, training, or a shared vendor or carrier relationship, not to chase down one franchisee. Because the rollup deliberately withholds which members are affected, the right next step is usually one of:

• Check Best Practices to propagate, the row just above Network Flow on the Network page, for a related recommendation drawn from what your top-performing locations do differently.
• Push a network-wide resource, a program update, an SOP revision, a broadcast, if the pattern points at something shared rather than something one member is doing wrong.
• Watch the trend. If a signal keeps reappearing week over week, it's a standards or training gap worth a Discovery Day agenda item, not a one-off nudge.

Verinode surfaces the pattern; it never tells leadership what to decide. The signal names what's happening across the network and how widely. What you do about it, a program change, a broadcast, a standards update, is your call.

Related help articles

• Network Health overview for the full Network page: hero gauge, Explore tiles, Network Flow, and the member directory this signal row sits inside.
• HQ overview for how the HQ platform is structured and the privacy boundary that governs every surface, including this one.
• HQ Standards for how stage-time standards feed the Conformance tab that sits beside Signals in the same slider.
• HQ Compliance for the certification and audit rollups that the reporting-coverage signal family points back to.
• Broadcasting to your network for pushing a network-wide message once a pattern points at something shared.
• Discovery Day for turning a recurring cross-network signal into an agenda item with your members.

Data sources