Signals on mobile

What Signals on mobile shows

Signals on the mobile HQ app reads the same underlying data as the web Signals page: cross-network patterns the aggregator has detected because a meaningful share of active memberships hit the same operational pattern in their own IQ accounts at the same time. A single membership having a rough month is normal. A pattern showing up across a real slice of the network at once is not, and this is the page where you see that it's happening, how severe it is, and whether it's clearing or building.

Mobile does not run a separate, lighter calculation. The mobile view calls the exact same rollup function the web Signals page calls (getSignalsRollupForGroup), so the open count, the severity breakdown, the domain groupings, and the resolved-in-30-days figure are guaranteed to match whatever the web page shows at the same moment. What differs is presentation: mobile condenses the web page's hero panel and five rows into four hero tiles plus three flat list sections, sized for a phone screen and a fast scan between meetings rather than a working session.

Verinode does not decide what a signal means or what to do about it. It surfaces that a pattern crossed the network-wide bar, how many memberships and domains it touches, and whether it has cleared. Reading the pattern and deciding on a network memo, a program change, or a direct call to the affected memberships stays a leadership decision.

Where to find it

Open the Sections button in the mobile HQ tab bar. In the sheet that opens, titled HQ Sections, scroll to the NETWORK group, alongside Network and Team, and tap Signals. Its hint line in that sheet reads "Open network alerts by severity & domain." The route is /mhq/signals.

The page is a single scrolling view: a hero row titled Signals at the top, followed by three flat list sections, top to bottom: Critical & high, By domain, and Recently resolved. Nothing on this page opens a drill-in screen today; every tile and row is read-only, built to be scanned rather than tapped into.

The four hero tiles

At the top of the page, a horizontal scrolling row titled Signals carries four tiles. Each has a kicker label, a large value, a caption underneath, and, where the data supports it, a support line beneath that:

• Open. The total count of currently open signals, network-wide, across every severity and domain, captioned "Open network signals." The support line reads "across N domains," the number of distinct domains that currently have at least one open signal. This tile is neutral-toned when the count is above zero and turns green only when it reads zero.
• Critical. The count of open critical-severity signals, captioned "Critical-severity signals." Red when above zero, green at zero.
• High. The count of open high-severity signals, captioned "High-severity signals." The support line reads "N medium · N low," so the two lower severities are folded into this tile's support text rather than getting tiles of their own. Red when above zero, green at zero.
• Resolved 30d. The count of signals resolved in the last 30 days, captioned "Resolved in the last 30 days." Always a calm, neutral-to-good tone regardless of the number, since a high resolved count is progress, not a warning.

Two things worth knowing if you've read the web Signals page first. First, mobile has no separate "All clear" pill and no domain-count pill sitting beside a headline; the Open tile's number and support line together do that job. Second, mobile has no combined "High + Medium" stat the way the web hero does. Medium and Low counts only appear here as the High tile's support text, "N medium · N low," never as their own tile.

Critical & high

The first list section. Every currently open signal at critical or high severity, most severe and most recently detected first, up to 10 rows. Each row shows:

• Title: the signal's plain-language title, for example the kind of sentence that would read "Carrier X paying slower than usual across the network."
• Meta line: the signal's domain (Margin, Cash, Carrier, Team, and so on, in HQ-facing wording), with " · X/Y offices" appended when the aggregator captured both an affected count and a total count for the pattern. A signal with no domain on file shows "Network" here instead of a domain name. If no affected/total counts were captured, the meta line is just the domain (or "Network") on its own.
• Value: the severity label, Critical or High, right-aligned, tinted red.

The severity scale in use today is info / warning / critical; you may still see a signal labeled High, Medium, or Low if it was written before that scale settled, since the older labels are kept as a fallback rather than dropped. Either way, this row groups anything at the critical or high end of the scale together.

Empty state, verbatim: "No critical or high-severity signals open."

By domain

The second list section. Every domain that currently has at least one open signal (Margin, Cash, Carrier, Team, Safety, and so on), one row per domain, worst-severity-first, up to 10 rows. Each row shows:

• Title: the domain name. A signal with no domain recorded groups here under Uncategorized. The operator "growth" domain reads Sales & Marketing here, the same relabeling the web page uses, so it can't be confused with the franchise network's own Recruit & Grow activity.
• Meta line: "Top severity X," the single worst open severity among the signals grouped into that domain. One critical signal in an otherwise-quiet domain still earns that domain a Critical label here.
• Value: the domain's open signal count, with "open" underneath as the value's sub-label.

This row groups every open signal by domain, not just the critical-and-high ones above it, so a domain can appear here with only Medium- or Low-severity signals behind it even when it's absent from Critical & high.

Empty state, verbatim: "No open signals across the network."

Recently resolved

The third list section. Every signal resolved in the last 30 days, most recently resolved first, up to 8 rows. Each row shows:

• Title: the signal's title.
• Meta line: the signal's domain, or "Network" if it had none on file.
• Value: the literal word "Resolved," tinted green.

This is where you confirm a pattern actually cleared, useful after a network-level change, a new vendor rate card, an updated process template, a carrier escalation, to see it reflected as a signal closing out rather than piling up.

Empty state, verbatim: "Nothing resolved recently."

What never appears here

No row on this page, in any of the three sections, shows a membership's identity. There is no franchisee or office name, real or anonymized, anywhere on the mobile Signals page, unlike some other HQ mobile rollups that list per-office rows behind an entity-model anonymization setting. Signals only ever surfaces the pattern (a title, a domain, a severity, an "X/Y offices" ratio) and never the roster of which specific memberships tripped it. That roster does exist, on the web page's detail panel, gated behind the same anonymization rules as the rest of HQ, but the mobile rollup doesn't carry that drill-in at all (see the next section).

How mobile differs from the web page

The mobile rollup reads the same source data as the web Signals page, but presents and caps it differently, and drops two pieces the web page has:

• No tap-through detail panel. Tapping any row on mobile does nothing today. The web page's click-through opens a right-side panel with a four-figure reach grid (Affected, Network reach, Fire threshold, Detected), the list of affected memberships (with an "Open profile →" link into each), a sample of the underlying pattern, and the raw signal type code. None of that exists on mobile yet; the three list sections are as deep as the mobile page goes.
• No Recent row. The web page's fourth row, every signal (open or resolved) detected in the last 7 days regardless of severity, isn't on the mobile rollup. Mobile keeps Critical & high, By domain, and Recently resolved.
• Different row caps. Critical & high and By domain cap at 10 rows each on mobile; Recently resolved caps at 8. The web page's Critical & High Severity row caps at 8 tiles, and its Recent and Resolved rows cap at 8 as well.
• Compact affected-count phrasing. Where the web page's tile subtitle reads the full sentence "X of Y franchisees affected," the mobile row's meta line appends a compact "X/Y offices" instead, to fit a phone-width row.
• No fire-threshold explanation. The web hero panel's empty state spells out that a signal only fires once a meaningful share of active memberships hit the same pattern. Mobile's empty states are shorter and don't restate that mechanic; see Signals: your network's early-warning feed for the fuller explanation if you need it.

How to use it

1. 1Open Signals from the Sections sheet under NETWORK, and read the four hero tiles first: Open and its domain count, Critical, High (with its Medium/Low support line), and Resolved 30d.
2. 2Scan Critical & high for anything needing same-day attention. The meta line's "X/Y offices" ratio tells you how far a pattern has spread without needing the full web detail panel.
3. 3Check By domain to see whether this week's pressure is concentrated in one area (Margin, Carrier, Safety, and so on) or spread across several.
4. 4Check Recently resolved after you've made a network-level change, a program update, a carrier escalation, to confirm the pattern actually cleared rather than just going quiet.
5. 5If you need to open a specific membership's profile or see the full fire-threshold math behind a signal, switch to the web Signals page; mobile doesn't carry that drill-in yet.

What HQ never shows here

Signals follows the same enforcement as every other HQ surface. Every number on this page comes from a pattern the aggregator wrote to your network's signal table because a share of active memberships' own IQ accounts hit the same thing, not from a live read of any membership's private data. HQ's database role has no path to query a membership's own PII database directly, and nothing on this mobile page, or its web counterpart's detail panel, hands you the numbers behind why a membership is affected, only that it is.

Related reading

• Signals: your network's early-warning feed, the full web page this rollup mirrors, including the detail panel mobile does not carry
• Reading the network-signals hero, a deeper look at the web hero panel's headline, pill, and secondary-stat logic this mobile hero condenses
• The Critical & High Severity row, the web equivalent of this rollup's Critical & high section, including the coverage dot-grid mobile doesn't carry
• By Domain: grouping open signals, the web equivalent of this rollup's By domain section
• HQ overview, orientation to the full HQ sidebar and mobile Sections sheet
• Network health, the aggregate-only privacy boundary every number on this page depends on
• Broadcasting to your network, turning a signal into a message to affected memberships
• Equipment on HQ mobile, a sibling mobile rollup with the same "no drill-in yet" pattern
• Certifications on HQ mobile, another sibling mobile rollup for comparison

Data sources