Skip to content
NAVYAX

Incidents

A record that outlives everyone who touched it

What the driver files, what the system keeps, and how your roster gets in. The part the rest of the product rests on, because a decision about cost is worth nothing without the evidence underneath it.

Northlake CarriersSample data
Check and send7/7
CategoryBacking incident
WhenSep 17, 8:12 AM
WhereI-80 W, mile 132
UnitT-4471
SeverityModerate
Photos3 attached
Send report

You cannot change it after sending.

HomeReportRequestsHistory

On the phone

Seven screens, at the roadside, with gloves on

Seven for a backing incident; six when no vehicle is involved, because the category decides which questions get asked at all and nobody answers a form about a vehicle after a slip in the yard. Each screen asks one thing, which is how seven of them take about a minute. Every target is at least 48px, and the text is sized to be read in a cab.

Northlake CarriersSample data
What happened2/7

Safety

Collision with another vehicleBacking incidentStruck a fixed objectNear missRoadside inspection
HomeReportRequestsHistory
Your categories, not ours. A fleet that cares about backing incidents gets a category for backing incidents.
Northlake CarriersSample data
When and where3/7

When it happened

Sep 17, 2026, 8:12 AM
Location found

41.52519, −88.08173

Accurate to about 8 m

Where, in your words

I-80 westbound, mile 132
HomeReportRequestsHistory
A GPS fix with its accuracy in metres, so you know whether that is ±8 m or ±400 m. If the driver denies location, the form asks them to type where instead of blocking.

The part that matters at 2 a.m.

The report ID is minted when the form opens, not when it sends.

So when the signal drops halfway through and the driver presses send again — and they will — you get one report, not two. The office is never reconciling duplicates of the same collision, and the driver is never told their report failed when it did not.

What the record holds

Three timestamps, because they disagree

When it happened, when the device says it was reported, and when the server received it. A claim can turn on that gap, and a system that stores one number has already thrown the answer away.

What was reported cannot be rewritten. Not the driver’s account of it, not the category, not when or where. What the office decides afterwards — the status, the cost, who carries it, which customer it was about — can be revised, and every revision is written to a trail with a name on it that nobody can erase.

Evidence can still arrive late, because it does. A driver adds photographs from the phone; the office attaches the police report, the adjuster’s letter, the cost breakdown — even after the report is closed. Every file records who attached it and from which side, and a driver is never shown the office’s paperwork.

Internal notes stay internal. The office can write notes the driver never sees; the two threads are separate at the API, not merely hidden in the interface.

Cost is shown to the driver only once responsibility has actually been decided — not while it is still an open question with their name near it.

Incident · INC-2026-0142Sample data
OccurredSep 17, 2026, 8:12 AM CDT
Reported by deviceSep 17, 2026, 8:19 AM CDT
Received by serverSep 17, 2026, 8:54 AM CDT
Location41.52519, −88.08173 · ±8 m
Stated placeI-80 westbound, mile 132
DriverMarcus Okonkwo · D-1042
UnitT-4471
Anyone hurtNo
Unit driveableYes
Photos5, captured on device

Thirty-five minutes between the device recording the report and the server receiving it. That is a driver in a dead spot on I-80, and it is a fact worth keeping rather than rounding away.

Getting started

Your roster arrives as the spreadsheet you already keep

Upload it and you get a preview, not a result. Every row is classified before anything is written, and nothing is applied until you say so.

Import preview · nothing applied yetSample data

1

Add

1

Update

1

Retire

1

No change

1

Cannot apply

Sheet rowNameEmployee refWhat will happen
4Okonkwo, MarcusD-1042No change
5Alvarez, PriyaD-1043Update
6Santos, ElenaD-1147Add
7Kowalski, TomasD-0884Retire
8—D-1043Cannot apply

Row 8 — employee ref D-1043 appears twice in this file.

Errors are reported against your row numbers. Row 8 of your file is called row 8, so you can fix it in the spreadsheet still open on the other monitor.

Duplicates are caught both ways — against what is already in the system, and against the other rows of the same file, which is where they usually come from.

A round trip with no edits changes nothing. Export it, open it, close it, upload it: every row comes back marked “no change”. An import tool that cannot do that is one nobody trusts twice.

It goes back out, too. The roster exports as a real spreadsheet, dropdowns intact, whenever you want it.

Book a demo

Twenty minutes, on your own data if you want

Send a roster beforehand and we will import it first, so what you are looking at is your fleet rather than a made-up one.

You will get a reply from a person, usually the same day. There is no sequence, no sales team and no follow-up drip — there is one of us.

If you would rather not use the form, hello@navyax.com and (227) 268-4898 both reach the same place.

We use this to reply to you and nothing else. No newsletter, no list, and no advertising or cross-site tracking — we count page views, and that is all.