The network reach hero: what the top of Reports measures
The hero panel is the band of numbers at the very top of Reports & Communication, before any of the report or message rows. It lives in the HQ sidebar under **Reports**, at `hq.verinode.ai/reports`…
On this page
The hero panel is the band of numbers at the very top of Reports & Communication, before any of the report or message rows. It lives in the HQ sidebar under Reports, at hq.verinode.ai/reports, and it's the fastest way to answer one question: is HQ's communication actually landing with the network, and how much has HQ produced and sent lately.
Everything in this panel is a network-level rollup. It never names a franchisee, and it never shows which specific member opened, ignored, or responded to anything. That holds even for the headline number, which is built specifically to answer "how much reach did we get" without ever answering "who read it."
The headline: operators reached (30 days)
Under the eyebrow "Comms · Network reach," the large animated number is operators reached in the last 30 days. It's a count of read events across every broadcast HQ sent in the trailing 30 days, added together.
Two things worth understanding about how that number behaves:
- It counts unique reads per broadcast, not raw views. Each broadcast keeps a single running counter. The first time a franchisee opens it, the counter ticks up by one, permanently. Opening the same broadcast again later, or dismissing it after reading, doesn't add anything more. So the counter per broadcast reflects how many distinct members have seen it, not how many times it's been looked at.
- It adds across broadcasts, so it isn't a headcount of people. If you sent three broadcasts this month and one engaged franchisee opened all three, that franchisee contributes three to the 30-day total, once for each message they read. The headline is a reach-and-engagement pulse across everything you sent, not a census of how many distinct members you touched. A very active month with several broadcasts will naturally show a bigger number than a quiet month with one, even at the same membership size.
- Only surveys and broadcasts feed into it, and only broadcasts count toward the headline specifically. Reports on file and surveys sent are their own separate numbers below the headline (see below); the "operators reached" figure is broadcast reads only.
- It only reflects members who've completed onboarding. A broadcast lands in the feed of every active operator in your network, so the reach number tracks your active membership, not every name that might still be sitting in an unreconciled roster.
Why read count, and not a list of who read what
HQ needs to know its messages are landing. It doesn't need, and structurally can't have, a list of which specific franchisee opened which broadcast. Franchisees own their own engagement data the same way they own their business data everywhere else on the platform: HQ sees the aggregate, never the individual record.
That's why "operators reached" is built as a single running counter per broadcast rather than a per-member log. The counter goes up once when a franchisee's device registers a first open. Nothing further is ever attached to that increment, no name, no timestamp tied back to a person, no per-operator read state HQ can query. The hero panel just adds those counters together for every broadcast sent in the last 30 days. That's what makes read count a privacy-safe proxy for reach: it answers "how much did this land" using a number that was never capable of answering "with whom."
Note
This is the same privacy boundary that holds everywhere in HQ: leadership sees the network's shape, not any one member's private detail. See /help/hq-network-privacy-boundary for how that boundary is drawn across every HQ section.
The last-quarterly pill
If your network has ever generated a Quarterly Review, a pill sits next to the headline reading "Last quarterly [date]," the date the most recent quarterly review was generated. It only tracks Quarterly Reviews specifically, not Member Performance, Compliance Audit, or Recruitment Pack reports. If no quarterly review has been generated yet, the pill doesn't appear at all.
The context line under the headline
Directly under the headline and pill, a line of plain-language context sets expectations for what's below:
- Before anything has happened: "Reports + broadcasts surface here once you generate or send them. Quarterly reviews auto-generate on the first day of each quarter."
- Once there's activity: "[N] reports on file · [N] surveys in last 30 days · [N] broadcasts."
That second version is just the three secondary numbers below, written out as a sentence, so you can read the whole panel in one glance without your eyes having to jump between the headline and the smaller figures.
The three secondary numbers
To the side of the headline sit three smaller counters, each animating in with a short stagger:
| Metric | What it counts | Window | |---|---|---| | Reports on file | Every report HQ has generated, across all four types (Quarterly Review, Member Performance, Compliance Audit, Recruitment Pack) | All types, most recent batch | | Surveys (30d) | Surveys HQ has authored | Last 30 days | | Broadcasts | Broadcasts HQ has sent to the network | Most recent batch |
Surveys (30d) is an exact count for the trailing 30-day window, no matter how many surveys the row below is currently displaying. Reports on file and Broadcasts, by contrast, reflect the most recent batch of each that's loaded onto the page rather than an unbounded full history. For most networks that's the same number either way; a network with an especially long run of quarterly reviews or a heavy broadcast cadence over several years may see these two settle at "the recent stretch" rather than "everything ever sent." If that ever looks low against what you remember sending, the Reports and Broadcasts tabs in the detail view hold the fuller list to check against.
Reading it as a weekly pulse
- 1Open Reports from the HQ sidebar. The hero loads before anything else, so it's the first thing you see.
- 2Check the headline against your last check-in. A flat or falling "operators reached" number, especially after a broadcast you expected to matter, is worth a look at what you sent and whether the subject line or timing missed people.
- 3Glance at the last-quarterly pill. If it's more than a quarter old and you expected an auto-generated review by now, open the Quarterly Report deck's Library tab, it may still be compiling, or you may want to generate one on demand.
- 4Use the three secondary numbers to sanity-check activity level: a "Surveys (30d)" of zero next to a "Broadcasts" that just climbed tells you HQ has been pushing information out but hasn't asked the network anything back lately.
Heads up
Don't read "operators reached" as "this many distinct franchisees are engaged." A small, highly engaged network that reads everything you send can post a bigger 30-day number than a larger network that mostly ignores broadcasts. It's a reach total across messages, not a headcount of people.