By Domain: grouping open signals

The Signals page is where every open cross-network signal lives, not just the handful surfaced on Feed. Signals are rollups: when a meaningful share of active memberships hit the same operational p…

7 min read·Updated July 14, 2026
On this page

What the By Domain row is

The Signals page is where every open cross-network signal lives, not just the handful surfaced on Feed. Signals are rollups: when a meaningful share of active memberships hit the same operational pattern in their own IQ accounts, Verinode's aggregator groups those individual signals into one network-level row. No single membership's business data ever reaches this page; HQ sees the pattern, never the franchisee behind it.

By Domain is the third row on that page. Every open signal on the network carries a domain, the operational area it belongs to (Margin, Safety, Carrier, and so on), inherited from the same domain taxonomy your memberships' IQ accounts use day to day. This row takes every open signal, groups it by that domain, and gives you one tile per domain: how many open signals sit in it, and how severe the worst of them is. It's the fastest way to answer "which part of the network needs attention right now" without reading every signal title individually.

Where to find it

Open the Signals page at hq.verinode.ai/signals. The page header reads Feed (it shares the same sticky-title shell as the rest of the platform), and the rows stack top to bottom:

  1. Hero. Total open signal count, with a breakdown of critical, high, medium, and low, plus how many resolved in the last 30 days.
  2. Critical & High Severity. Wide tiles for every open signal at critical or high severity.
  3. By Domain. One tile per domain with at least one open signal. This is the row this article covers.
  4. Recent. Every signal (open or resolved) detected in the last 7 days.
  5. Resolved. Signals closed in the last 30 days.

The same underlying network signals also drive the card-based Feed view in your sidebar. Signals is the fuller, row-by-row breakdown of that same dataset, useful when you want the whole shape of what's open at a glance rather than scrolling a chronological feed.

What a domain tile shows

Each tile in the By Domain row carries exactly three pieces of information, no more:

  • A severity-colored eyebrow label, reading Critical, High, Medium, or Low. This is the top severity among the open signals in that domain, not an average or a count-weighted score. One critical signal in a domain with five low-severity ones still earns that domain a Critical label.
  • The domain name as the tile's headline, in HQ-facing wording (see relabeling below).
  • A small caption underneath, reading "N open signal" or "N open signals" (singular/plural handled automatically), the total count of open signals in that domain regardless of their individual severities.

There is no icon, no evidence visual, and no footer meta line on these tiles, unlike the wider Critical & High Severity tiles above them. A domain tile is deliberately plain: label, name, count. It's a triage index, not a detail view.

Note

Critical and High both render in the same accent color (Ember Red). The two severities are distinguished by the label text itself, "Critical" versus "High", not by tile color. Medium renders in Hard Hat Yellow, and Low in copper. If you're scanning quickly, read the label word, not just the color.

How domains are ranked and sorted

The row only includes domains that currently have at least one open signal (status "new" or "seen"); a domain with zero open signals doesn't get a tile at all, it simply drops off the row until something opens in it again.

Domains are sorted by their top severity first (Critical domains sort ahead of High, High ahead of Medium, Medium ahead of Low), and within the same top severity, by open signal count, most open signals first. This means the first tile in the row is always the domain that most needs a look: either the only one with a critical signal open, or, if several domains share the same top severity, the one carrying the most open signals at that severity.

A signal without a domain recorded is grouped under Uncategorized rather than dropped from the row.

HQ domain relabeling

Operator domains come from the same taxonomy your memberships' IQ accounts use for their own signals and decisions: Margin, Clients, Vendors, Team, Process, Safety, Equipment, Jobs, Costs, Cert, Compliance, Recruiting, Reputation, Carrier, Growth, and Forecasting. Most of those read fine unchanged, just Title Cased, on an HQ tile.

One doesn't: Growth. On an operator's own IQ account, "Growth" means their Sales & Marketing domain, lead generation, close rate, marketing spend. On HQ surfaces, "Growth" already has a different, established meaning: the Recruit & Grow area of the franchise network itself, recruiting new franchisees and expanding territory. Showing a network signal about member sales pipelines under a tile labeled "Growth" would put two unrelated concepts under the same word on the same page.

So HQ relabels it. A signal whose domain is the operator's growth reads Sales & Marketing on this row and everywhere else on HQ surfaces that display operator domains. Every other domain falls through unchanged (Title Cased) to whatever the underlying value is, so a new operator domain added later never accidentally collides with an HQ term, it just shows up Title Cased until someone decides it needs its own relabel.

Tip

If you ever see a domain tile labeled Growth on an HQ surface, it refers to franchise-network growth (recruiting, territory), never a member's sales and marketing signals. Member sales and marketing signals always surface as Sales & Marketing instead, specifically so the two never get confused on the same page.

Why domain tiles are currently non-drill

Clicking a domain tile does nothing right now. That's deliberate, not a bug: the By Domain row already shows you the full set of domains with open signals in one place, so there is nothing further to drill into yet, no per-domain filtered signal list exists behind the tile today.

The Critical & High Severity, Recent, and Resolved rows above and below already give you the individual signal tiles, each of which opens a detail slider when clicked. If you want to see every open signal in, say, Safety, today's path is to scan those rows (or the Feed) for Safety-domain tiles rather than clicking the Safety domain tile itself. A per-domain filtered list, so clicking Safety would show every open Safety signal in one place, is planned for a future signal-deck expansion but has not shipped.

Heads up

The domain tiles are informational only for now. Use them to see which domains carry the most severe or the most numerous open signals; use the other rows, or Feed, to actually open and act on an individual signal.

Empty state

When there are no open signals on the network at all, the By Domain row (along with the rest of the page) has nothing to group, and it reads:

No open signals to group by domain.

This is a genuinely quiet network, not a broken row. The moment any signal clears the network-wide coverage bar and opens, a domain tile appears for it on the next refresh.

How to use it

  1. 1Scan the By Domain row first when you open Signals. The leftmost tile is always the domain that most needs attention, by severity first, then by volume.
  2. 2Read the label word, not just the tile color, to tell Critical from High at a glance, since both use the same accent.
  3. 3Note the domain name and open count, then go find the individual signals behind it in the Critical & High Severity or Recent rows (or Feed), since the domain tile itself won't filter or drill in yet.
  4. 4If a domain keeps reappearing with a Critical or High label week over week, treat it as a standards or training conversation for Discovery Day rather than a one-off nudge, the same way a persistent cross-network pattern is meant to be read.
  • Cross-network signals in Take Action for the Network page's Take Action row and Signals tab, a different presentation of network-level signals with its own severity ladder and evidence tiles.
  • Network Health overview for the hero gauge, Explore tiles, and member directory that sit alongside network signals.
  • HQ overview for how the HQ platform is structured and the privacy boundary that governs every network surface, including this one.
  • HQ Standards for the process standards that many Process- and Compliance-domain signals point back to.
  • Broadcasting to your network for pushing a network-wide resource once a domain's signals point at something shared.
  • Discovery Day for turning a recurring domain pattern into an agenda item with your members.

Data sources

Data sources

  1. 1.Open network signals (the network data), aggregated from member IQ accounts. Your network's members.
  2. 2.Operator domain taxonomy (COO_DOMAINS), relabeled for HQ where terms would collide. Verinode platform.
Was this helpful?