"Accidents: at-fault incidents across the network in the last 36 months"

What the Accidents row shows

Accidents is one of four content rows on the HQ Fleet page. It lists every franchisee in your network that has recorded at least one at-fault vehicle accident in the trailing 36 months, ranked so the franchisee with the most at-fault accidents sits first. Each tile shows two numbers side by side: how many at-fault accidents that franchisee has on record, and how many total accidents (at-fault plus not-at-fault) sit behind that count.

The distinction matters. A fleet that gets hit by other drivers has an exposure problem worth understanding, but it is not a coaching or liability problem in the same way a fleet that keeps causing accidents is. Splitting total from at-fault is what lets leadership tell the two apart at a glance instead of reading "accidents" as one undifferentiated risk number.

Verinode does not investigate accidents, assign fault, or file anything with an insurer. It reads the accident records each franchisee has logged in their own Verinode IQ fleet module, where at-fault determination is already recorded against each incident, and rolls those counts up into this row. What to do about a high count, whether that is a coaching conversation, a route change, a policy review, or nothing at all, is a leadership decision, not something Verinode recommends or acts on.

Where to find it

Open Assets from the HQ sidebar. Assets is a single sidebar entry covering three sibling views, switched with a pill tab strip at the top of the page: Facilities · Fleet · Equipment. Click the Fleet pill, or go directly to hq.verinode.ai/fleet.

The page's sticky title reads "Assets" (the cluster label), with the Fleet pill highlighted active in the tab strip just underneath. Below that, the page runs in this order:

1. The network fleet hero (active vehicles, total mileage, annual premium, policies expiring in 90 days). See /help/hq-fleet-hero-network-metrics.
2. Insurance Risk, franchisees with a commercial-auto policy expiring inside 90 days.
3. Compliance & Driver Risk, franchisees with an overdue service, an expiring registration or DOT inspection, an expired driver license, or a stale MVR pull.
4. Accidents, this row.
5. Fleet by Franchisee, every franchisee with at least one vehicle, regardless of risk status.

Each row scrolls horizontally as its own strip of tiles; drag it or use the arrow controls at either edge if there are more franchisees than fit on screen. A Download board slide button sits in the top-right corner of the page and exports the whole Fleet view, hero and every row including Accidents, as a PDF for a board deck.

Reading a tile

Each tile in the Accidents row represents one franchisee and shows:

• Label, in the tile's top corner: the at-fault count, formatted as "N at-fault" (for example, "3 at-fault"). This is the number the row is sorted by.
• Headline: the franchisee's name. If your network is set up as same-entity (one company, multiple locations, configured in Settings → Group → Data posture), this is the location's real name. If your network is set up as independent-operator (each franchisee its own legal business, the default), this is a stable anonymized label like "Franchisee #A1B2" instead, so no franchisee identity leaks through this row.
• A small segmented bar underneath the headline: a two-color strip showing the at-fault count against the rest of that franchisee's total accidents. The at-fault portion renders in Ember Red; the remaining, not-at-fault portion renders in the tile's neutral accent. A franchisee whose entire accident history is at-fault shows a solid red bar; one where at-fault accidents are a minority of a larger total shows red as a smaller slice of the bar.
• Subline: the total accident count for that franchisee across the same 36-month window, formatted as "N total accident" or "N total accidents" (for example, "5 total accidents"). This is always greater than or equal to the at-fault count in the label above it.

There's no third line of metadata under these tiles (no dollar figure, no date, no "vs peer" delta) the way some of the other Fleet rows show. The row keeps to the two numbers and the visual split that matter for accident exposure: how many, and how many were this franchisee's fault.

The whole row uses the Ember Red / Analyse accent, the same signal color used across the platform to flag something that needs a look. That's a visual cue that this row is a watchlist, not a neutral status list, even before you read a single number.

Sorting and ranking

The row is always sorted by at-fault count, highest first. A franchisee with 4 at-fault accidents and 4 total sits above a franchisee with 6 total accidents but only 2 at-fault, because the ranking is built around at-fault exposure, not raw accident volume. Up to six franchisees show at once in the row; if your network has more than six with at-fault accidents on record, scroll or drag the row to see the rest.

Franchisees with zero at-fault accidents in the trailing 36 months, including franchisees with only not-at-fault accidents on record, do not appear in this row at all. A franchisee who was rear-ended twice but caused nothing themselves has a clean Accidents row entry: they simply aren't listed here.

Opening a tile: the franchisee detail

Clicking any tile in the Accidents row opens that franchisee's full Fleet detail as a centered overlay. It is the same detail view you'd reach by clicking a tile in any other Fleet row, not an accidents-only popup, so once it's open you're looking at everything HQ tracks about that franchisee's fleet, not just the accident history that got you there.

The overlay header shows the franchisee's name (real or anonymized, following the same rule as the tile), city and state when on file, an active/inactive status pill, and a pill showing active vehicle count (plus total vehicle count when some are inactive).

Below the header, a scope switcher lets you choose what the franchisee's numbers are compared against: Group (other franchisees in your own network), Regional (peers in the same state), or National (peers across other networks). Each tab's label includes roughly how large that comparison group is. A scope that doesn't yet have enough peers to compare against without risking identifying an individual franchisee is grayed out with an explanation, rather than silently showing a comparison that could be traced back to one operator. As of this build, Regional and National scopes for fleet metrics are not yet seeded with live industry data; the scope footer at the bottom of the overlay says so plainly rather than showing a comparison that doesn't exist yet. Group scope, comparing within your own network, is live today.

Three sections follow the scope switcher:

• Fleet shape, vehicle count, average vehicle age, annual commercial-auto premium, and owned-vs-leased mix, each against the selected peer scope.
• Safety, the two metrics behind this row:

- Accidents (36mo), the franchisee's total accident count, compared to the selected scope's median, with a percentile and a colored delta ("On par with peers," or a percentage above/below median). - At-fault (36mo), the same treatment for at-fault accidents specifically.

For both metrics, fewer is better: a franchisee running below the peer median is shown in green (Expand), one running noticeably above it in red (Analyse) or amber (Maintain) depending on how far above, and one close to the median reads "On par with peers" in neutral gray. If a group-wide safety target has been set through an active HQ program, a ✓ Meets target or ✗ Below target tag appears under the metric with the target value and the program it comes from.

• Compliance watch, overdue services, expiring registrations and DOT inspections, expired driver licenses, and stale MVR pulls for that franchisee, the same data that drives the Compliance & Driver Risk row.

If either safety metric's peer comparison isn't available at the selected scope, the tile reads "Cohort too small" (not enough peers in that scope to compare against) or "Pending benchmark seed" (that scope's benchmark data hasn't been populated yet) instead of a blank space.

The privacy boundary

Verinode HQ never opens a franchisee's individual accident report, police report, insurance claim, or incident narrative. What flows up from each franchisee's Verinode IQ account into this row is a count: how many accidents were logged in the trailing 36 months, and how many of those were recorded as at-fault. The underlying incident detail, whatever a franchisee typed into their own accident log, stays in that franchisee's own account. HQ sees the tally, not the file.

In an independent-operator network, the franchisee identity behind each tile is also masked with a stable anonymized label rather than shown by name, everywhere this row and its drill-in appear. Same-entity networks, where every location belongs to one company, see real location names throughout instead, since there's no separate business to protect.

Small networks: aggregate-only view

Even an anonymized tile can identify a franchisee by elimination if a network only has a small handful of active operators; there's nowhere else the numbers could belong to. When your network is independent-operator and doesn't yet have enough active franchisees for that protection to hold, a disclosure banner appears above the row stack (shared across Facilities, Fleet, and Equipment) explaining that per-franchisee tiles are suppressed on privacy grounds for now, and that they return automatically once the network grows past that floor, or you can change the network's data posture in Settings → Group → Data posture. While that banner shows, the Accidents row, along with Insurance Risk, Compliance & Driver Risk, and Fleet by Franchisee, are all empty by design; the network fleet hero above them keeps reporting real totals the whole time. Same-entity networks never see this banner.

Empty states

If no franchisee in your network has an at-fault accident recorded in the last 36 months, the row reads, verbatim:

"No at-fault accidents recorded across the network in the last 36 months."

This is a clean bill of health, not a loading state or an error. It also appears (as part of the shared small-network disclosure described above) when your network is independent-operator and hasn't yet reached the active-franchisee floor needed to show per-franchisee tiles safely, even if at-fault accidents exist somewhere in the network; in that case the hero's aggregate totals still surface, only the per-franchisee tiles are withheld.

Best-practice example

Say the Accidents row shows three franchisees. The top tile reads "4 at-fault" under a franchisee headline, with a mostly-red segmented bar and a subline of "5 total accidents," meaning four of that franchisee's five logged accidents were their fault. The second tile reads "1 at-fault" with a subline of "6 total accidents," a mostly neutral-colored bar with a thin red sliver, meaning five of six were not this franchisee's fault. Read together, these are two different conversations: the first franchisee's pattern points toward driver behavior or route risk worth a direct conversation, the second franchisee's pattern points toward exposure (being hit by others) that a coaching conversation won't fix. Click into the top tile, switch to whatever scope is available, and check the At-fault (36mo) metric against the peer median before deciding whether this franchisee is an outlier worth flagging or simply running a larger fleet than its peers. Verinode surfaces the pattern; what you do with the top franchisee is a leadership call.

Related reading

• /help/hq-overview: what the HQ product is and how the sidebar sections relate to each other.
• /help/hq-fleet-hero-network-metrics: the network-wide fleet hero above this row, including how the small-network disclosure banner works in full.
• /help/network-health: the network-wide health rollup Fleet's aggregates feed into.
• /help/hq-compliance: how compliance events (registrations, DOT inspections, license and MVR pulls) are tracked network-wide, the data behind the Compliance watch section of this same franchisee detail overlay.
• /help/hq-benchmarks: how HQ compares network figures against outside reference data more broadly.

Data sources