Network Follow-Through: incident corrective-action speed

Incident Follow-Through is the network's median speed at closing the loop on a safety incident: the number of days from an incident occurring to its corrective action being marked closed. It is one…

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

What this tile shows

Incident Follow-Through is the network's median speed at closing the loop on a safety incident: the number of days from an incident occurring to its corrective action being marked closed. It is one metric, one tile, and it sits in the Network Follow-Through row on the Safety page. Where the rest of the Safety page counts things (how many certs, how many open incidents, how many OSHA-recordable events), this tile is the one place on that page that measures a duration: not whether the network responds to incidents, but how fast it actually closes them out once it does.

The number is mined from lifecycle dates your memberships already log in their own IQ accounts, specifically the incident date and the date a corrective action is marked closed, pooled across the whole network. Verinode does not log an incident, set a corrective action, or close one out. A membership's own safety workflow does that; this tile just reads the two dates once they exist and reports how long the gap between them has been running across the network.

Note

This tile is the Safety page's own read of one specific process transition: Occurred → Action Closed under the "safety" process. It is mined by the same engine that powers the network's broader Network Flow surface (job lifecycle, supplement turnaround, recruiting pipeline, and this one), and it is covered at a summary level inside Safety: network safety posture at a glance. This article is the deep dive on that one tile: what exactly it measures, what the industry comparison means, and what it deliberately does not show you.

Where to find it

Open Safety from the HQ sidebar, in the Compliance band alongside Programs, Compliance, and Certifications, at hq.verinode.ai/safety. Scroll past the Network Safety hero and the Compliance Frameworks row. The next row down is Network Follow-Through, holding this one tile, before the Safety Cert Coverage Gaps and Safety Incidents rows further down the page.

Unlike most tiles on the Safety page, this one is not a click-through into a membership's record. It carries no drill-in on this page. If you want the per-office breakdown behind this exact transition, fastest office to slowest, that view lives on Network Flow instead (Network Health in the sidebar, at hq.verinode.ai/network-health), covered in full in that article.

Reading the tile

The tile carries three things:

  • Label: "Incident Follow-Through." This is a fixed name for the Occurred → Action Closed transition under the "safety" process; it does not change based on your network's configuration.
  • The headline number, the network's median days to close a corrective action, shown as a whole number of days with a trailing "d" (for example, "9d"). This is a pooled median across every membership's closed corrective actions, not an average of each membership's own median, so a membership with more closed incidents on record weighs into the figure more than one with fewer. Read it as "across every corrective action the network has closed, half closed within this many days and half took longer," not as "the typical membership's own number."
  • A comparison line underneath, when an industry figure exists for this transition (see below). When there is no industry figure yet, no comparison line appears at all, only the day count and its "Median days to close a corrective action" subtext.

That is the whole tile. It does not carry a chart, a trend line, or a per-office spread; those live on the fuller Network Flow surface, not here.

The industry comparison

Where Verinode's anonymous industry cohort for this specific transition has published a median, the tile's comparison line reads one of two ways:

  • "On Pace With Industry," in neutral gray, when the network's median and the industry median are within half a day of each other.
  • "Xd vs Industry," where X is the day gap rounded to a whole number, colored green when the network is faster than the industry figure and red when it is slower.

The industry figure behind this line is never a named competitor and never a single peer's number. It is drawn from the wider industry cohort that Verinode's process-mining layer has anonymized and published for this exact stage transition, snapshotted onto your network's row the last time the aggregate refresh ran. Verinode does not disclose how many peers sit behind that published figure, only that it cleared the anonymity floor required before a cohort figure is allowed to publish at all. Below that floor, no industry figure exists for this transition yet, and the comparison line is simply omitted rather than showing an unreliable number.

Why the tile can be missing entirely

This row does not always show a tile. Two separate thresholds control it, and both exist to stop a thin sample from wearing a real metric's label:

  • The network-level figure itself needs enough closed corrective actions, pooled across every membership, before Verinode will render a median at all. Below that floor, the tile does not appear, and no placeholder or dashed number takes its place.
  • The industry comparison line is gated independently, by the anonymous peer cohort's own floor for this transition. A network can clear its own floor and still see a bare day count with no comparison line, if the industry cohort for this specific stage has not yet published.

Neither threshold is disclosed as a specific count anywhere on this page or in this article. Verinode's approach across every aggregate figure on HQ is the same: publish the number once there is enough data behind it to be meaningful, and simply stay quiet until then, rather than showing a technically-real number built on too thin a sample to trust.

Empty state. Until the network has closed enough corrective actions for a network median to be statistically meaningful, the Network Follow-Through row is empty. No tile, no zero, no "not enough data yet" placeholder appears in its place, the row simply does not render, exactly as it disappears rather than showing a misleading figure.

The privacy boundary on this tile

Everything this tile shows is a network-wide rollup:

  • No membership's individual incident record, corrective action, or safety documentation ever surfaces here. The underlying incident stays inside that membership's own IQ account; only the two dates that bound the "how long did closing it take" measurement ever feed the pooled figure.
  • No per-membership figure appears on the Safety page for this metric at all. The tile is a single network number. A per-office breakdown of this same transition exists, but only inside the Network Flow tab reached from the Network Health page, where office identity follows your network's standard data-sharing model (real location names for a single legal entity operating multiple locations, an anonymized stable label for an independent-operator franchise or association network).
  • The industry comparison is a published cohort figure, never a named competitor's number. It only appears once enough peers sit behind it that no single contributor could be identified from the published median.

How to use it

  1. 1Read the day count first. A network with a fast, well-understood incident process should see a low number here; a rising number over time (compare against what you remember from prior visits, Verinode does not chart the trend on this tile) is worth a closer look even without an industry comparison.
  2. 2Check the comparison line. "Xd vs Industry" in red means the network is taking longer to close corrective actions than the wider industry cohort; that is a signal worth raising in your next safety or compliance review, not an automatic verdict, Verinode surfaces the gap and leadership decides what to do about it.
  3. 3If the tile isn't showing at all, that's a data-maturity state, not a problem to fix directly. Encourage memberships to log both the incident date and the corrective-action-closed date consistently in their own IQ accounts; the tile appears on its own once the network clears the floor.
  4. 4For the office-by-office view behind this same transition, faster and slower offices side by side, open Network Flow from Network Health. That is the surface for "which offices are driving this number," not the Safety page.

Tip

A membership that also shows up in Safety Cert Coverage Gaps or Safety Incidents on the same visit is worth prioritizing in a review alongside a slow network-wide follow-through number: a gap in certification or an open incident sitting next to slow corrective-action closure across the network is a stronger combined signal than any one of the three read alone.

Data sources

  1. 1.Membership incident and corrective-action lifecycle dates. the network data, process-mining aggregate refresh.
  2. 2.Anonymous industry peer cohort, restoration process benchmarks. Verinode network intelligence.
Was this helpful?