DOT compliance
Know before it lapses, not on the morning it matters
Every requirement your operation actually carries, against drivers and against units, judged in each depot's own local date — and an email at sixty days rather than a phone call at six in the morning.
R. Whitfield
Medical certificate
T-4108
Annual inspection
M. Okonkwo
CDL
P. Alvarez
MVR review
T-4471
Annual inspection
Two out of service. Dates judged against each depot’s own local day.
A lapsed medical card is a driver you cannot legally dispatch
And you usually find out on the day, from the driver, at six in the morning. The cost is not the violation — it is the load that did not move, the reshuffle, and a number on your record that takes two years to come off.
Most carriers run this on a spreadsheet somebody maintains by hand, and it works until that person is on vacation. The failure is never dramatic. It is one certificate nobody re-checked, found during an audit that was going fine until then.
This keeps the same record for every driver and every unit, judges each date in the depot’s own local time, and emails you at sixty days rather than on the morning it matters — then again at thirty, fourteen, seven and one, and only within the window you set for that requirement.
Straight answer
This is running now, with two limits worth knowing before the call. The FMCSA set is not seeded — you define the requirements you actually carry, which takes an afternoon. And existing credentials are entered rather than bulk imported, so moving a long spreadsheet across is work. Both are on the list.
- Requirements per driver and per unit — licenses, medical cards, MVR reviews, annual inspections, whatever else you carry
- A board that sorts worst first, so what is missing sits above what is merely expiring
- Email reminders at 60, 30, 14, 7 and 1 days, judged against each depot's local date
- Drivers photograph a renewal on their phone; the office approves or rejects it
- Every record keeps its whole chain — what replaced what, who voided it and why
- What a driver and unit held is written onto an incident as it stood that day
Where it joins the rest
An incident remembers what was current that day
Filing a report writes down what the driver and the unit held at that moment, as it stood. Six months later nobody has to reconstruct whether a medical card was in date — the answer was recorded when it was still true, and it survives the card being renewed and the requirement being retired.
Dates are judged where the driver is
Each depot carries a validated IANA time zone, and a reminder is measured against that local date rather than the server's. Expiry dates judged centrally are wrong twice a year, and wrong in the direction that puts somebody on the road who should not be.
A lapse does not always mean parked
Each requirement decides for itself whether letting it slip takes the driver or unit out of service. Expired and still in service is a real state that the system keeps as a real state, rather than flattening everything into one alarm nobody can act on.
The chain cannot be rewritten
Every record keeps what replaced what, who voided it and the reason they gave. Update and delete are revoked from the application at the database level, so the history an auditor asks for is the history that exists, not the one left after somebody tidied up.
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.