Recent Activity across the network

What it is

Recent Activity is the pulse check on the Network Health home: the last time your network gained a member. It reads straight off your member roster (the network data) and surfaces every location whose roster record was touched, invited, pre-loaded, or activated, in the last 30 days. It is not a job feed, and it does not read anything inside a member's Verinode IQ account. It only ever tells you that a location joined the roster or accepted an invite, and roughly where.

Today the feed carries two kinds of events: signups and invites. The tile and the tab's empty-state copy both describe a broader scope, signups, milestones, and program-adoption deltas, because that is the intended direction for this feed once it reads from the network's program-adoption tracking table. That part is not live yet. If you're looking for a location's actual milestone activity (job stage transitions, supplement turnaround, recruiting steps), that lives on the separate Network Flow row on the same page; Recent Activity is roster activity only, for now.

Where to find it

Open the Network group in the HQ sidebar and click the top item, labeled Franchisees, Locations, or Network depending on how your network is configured. That opens the Network Health home at hq.verinode.ai/network. Recent Activity is the last tile in the Explore row, the row of roster and standing tiles running along the bottom of the page.

Clicking the tile opens the network-health card slider on its Activity tab, one of nine tabs across the top of that slider (Signals, Interventions, Top, Watchlist, Risers & Fallers, Network Flow, Conformance, Activity, Location Directory).

What the tile shows

The Recent Activity tile shows a single number: how many roster events fell in the last 30-day window, up to 8. Underneath, the sub-label reads "Last 30 days." There's no preview chart on this tile, unlike its neighbors (Location Directory shows a segmented split, Leaderboard shows a bar preview); it's a plain count.

That count is capped at 8 even if more than 8 locations were invited, pre-loaded, or activated in the window. If your network onboarded 15 locations this month, the tile still reads 8, the size of the underlying feed, not the true 30-day total. The Activity tab beneath it shows exactly those same 8 rows, most-recent first.

What the Activity tab shows

Each row in the Activity tab is one directory entry, with:

• Location name, in bold. In an anonymized network (see the privacy boundary below), this reads as a stable label like Franchisee #XXXX instead of the real business name.
• Where, a second line reading the city and state, comma-separated (e.g. "Tampa, FL"). If neither is available, whether because the network withholds geography or because the roster row genuinely has none on file, it reads "Location pending."
• A kind label, either Signed Up or Invited, in small uppercase tracking type.
• A date, right-aligned, formatted as a plain locale date (e.g. "7/13/2026").

Rows are ordered newest-first by that date, and the row set is exactly what the Recent Activity tile counted, up to 8 entries.

How "Signed Up" vs. "Invited" is decided

The kind label reflects the location's current roster status at the moment you view the page, not a historical event log. A row shows Signed Up if the location's status is currently Active, and Invited for anything else (pending invite or pre-loaded/seeded).

One consequence worth knowing: the date next to a "Signed Up" row is not necessarily the day the location accepted. It's the date the roster row's invite timestamp was originally set. When the daily aggregator cron promotes a pre-loaded or invited location to Active (because it recognized real onboarding activity from that operator), it updates the status and, if needed, the location's name, but it does not reset that invite timestamp. So a location invited three weeks ago that activated yesterday still shows the three-week-old date, now labeled Signed Up. Read the kind label as "where this location stands today," and the date as "when this roster row entered the 30-day window," not as a precise signup timestamp.

The privacy boundary

Every row on this tab respects the same rule as the rest of Network Health: HQ sees aggregates and rankings, never a single member's underlying business data. How that plays out on this feed specifically:

• Franchise and association networks (the default, independent-operators model): location names are anonymized to a stable Franchisee #XXXX label, and city/state are withheld entirely, every row reads "Location pending" for the "where" line regardless of whether the location actually has a city and state on file. This is deliberate: a member can't be identified by geography either.
• Single-owner, multi-location networks (same-entity model, typically an enterprise or PE-backed portfolio operating under one tax ID): real location names, cities, and states show through, because it is genuinely one business looking at its own locations.
• One edge case: a roster row that hasn't yet been linked to an operator account (a location pre-loaded onto the roster before anyone has claimed it) shows its real location name even in an anonymized network. There's no operator identity to protect yet, since nobody has signed in as that location.

There's no drill-in from this tab. Unlike Top Quartile, Watchlist, Active, Cert Watch, or Interventions, an Activity row does not open a member's detail card, it's a flat, read-only list.

Empty states

If nothing has entered the roster in the last 30 days, the Activity tab reads, verbatim:

"Quiet network. Signups, milestones, and program adoption deltas from the last 30 days will appear here."

That copy names the fuller feed this tab is heading toward. Today, an empty network genuinely just means no location was invited, pre-loaded, or activated in the window, not that data is missing or broken.

The tile itself has no separate empty message: with zero events in the window, it simply shows 0 under "Last 30 days."

How to use it

1. 1Glance at the tile count on your regular Network Health check-in. A rising number is healthy network growth; a flat zero for weeks running is worth asking your sales or franchise-development team about.
2. 2Open the Activity tab when you want the detail: which locations joined, and whether they came in as a fresh signup or are still sitting on an open invite.
3. 3Cross-reference a location still showing Invited after a while against the Invited tile in the Explore row, that's your list of open invitations to chase.
4. 4Don't read the date on a "Signed Up" row as the exact acceptance date, use it as a rough "recently active" signal, not a precise activation timestamp.

Related help

• /help/network-health: the full Network Health home this tile lives on, and how every row on the page fits together.
• /help/hq-network-composite-score: how the composite health score at the top of the page is built, including the recent-activity share dimension it draws from the same 30-day window.
• /help/hq-network-flow: the network's actual milestone activity, job, supplement, recruiting, and safety stage timing, as distinct from this roster-only feed.
• /help/hq-risers-fallers: week-over-week movement in a member's standing, a different signal than joining the roster.
• /help/hq-programs: vendor, carrier, and TPA program adoption across the network, the "program-adoption deltas" this feed is intended to eventually surface.
• /help/hq-compliance: the Cert Watch tile and compliance rollups that sit beside this one in the Explore row.
• /help/broadcasting-to-your-network: pushing an update out once you've spotted something worth telling the whole network.