Skip to content
NAVYAX

Questions

Answered here, so nobody has to ask on the call

What it costs, whether drivers will use it, what happens with no signal, where the data lives, and which parts are not built yet.

Northlake CarriersSample data

Thursday, September 17

Morning, Marcus

Report an incidentTakes about a minute
Request time offAsk about pay

Recent

INC-2026-0142Under review
INC-2026-0137Closed
HomeReportRequestsHistory

The ones people actually ask

Does NAVYAX actually collect money from drivers or customers?

No. There is no payroll deduction, no invoicing and no insurer integration, and NAVYAX is not connected to your payroll system. Your office decides who carries a cost; NAVYAX records that decision — the amount, the written reason, and the photographs and timestamps behind it — audited and unrewritable. What you do about it afterwards is your call and happens outside this software: invoice the customer, claim on the insurer, absorb it, or take it up with the driver. Whether a cost can be charged to a driver at all is a question of federal and state law and of your own agreements; take your counsel's advice on that, not ours. The reason recovery usually fails is that the decision and the evidence never existed, and that is the part this fixes.

Is DOT compliance tracking working today?

Yes. You set the requirements your operation carries, against drivers and against units, and each one decides whether letting it lapse takes that driver or unit out of service. The board sorts worst first, so what is missing sits above what is merely expiring. The office is emailed at 60, 30, 14, 7 and 1 days, judged against each depot's local date. Drivers photograph a renewal on their phone and the office approves or rejects it, and every record keeps its chain — what replaced what, who voided it and why. Two honest limits: the FMCSA set is not seeded, so defining your requirements takes an afternoon, and existing credentials are entered rather than bulk imported, so moving a long spreadsheet across is real work. Both are on the list and we will say so on the call.

Will my drivers actually use it?

That is the right question, and it is why the driver side is seven short screens rather than one long form — each asks a single thing, which is how it still takes about a minute. The targets are sized for gloves, the camera opens on the rear lens, and a driver cannot be asked a question the category does not need. The honest risk is not the interface — it is that nobody told the drivers why. We set up one terminal for a week first for exactly that reason.

Does it notify anyone?

Expirations do. Nothing else does yet. The office is emailed before a credential lapses — at 60, 30, 14, 7 and 1 days, judged against the depot's local date. There is still no push and no SMS, and nothing is sent about an incident, a request or a decision: a driver sees a decision by opening the app, and the office sees a new request by looking at the queue. The only other mail the system sends is a driver's sign-in link. That remaining gap is real and it is on the list. What you get today is that none of it is in a text thread on a dispatcher's personal phone, where it cannot be searched or handed over and leaves when they do.

What does it cost?

Per truck per month, with a floor for small fleets. We quote on the call because the number depends on your fleet size and how many terminals you run, and we would rather fit it to your operation than publish a tier that fits nobody. Ask on the call and you will get a figure, not a brochure.

Does the driver have to install anything?

No. They open a link and sign in. It is built for a phone — 48px targets you can hit with gloves on, the rear camera for photos, and text large enough to read in a cab — but there is nothing to download and nothing to update.

What happens if the driver has no signal?

The form fills in fine, but sending it needs a connection. What the signal cannot break is the report identity: it is minted when the form opens, so if the send drops and they try again you get one report, not two. Saved offline drafts are on the roadmap and not here yet — we would rather say so than have you find out at a weigh station.

Where does our data live, and who can see it?

In the United States, in a private network with no public address on the part of the system that holds it. Separation between companies is enforced by the database itself rather than by application code, and it fails closed — a query that forgets its filter returns nothing at all. Inside your account, what each person can see is decided by the groups you put them in.

Can NAVYAX staff see our incidents?

Only by entering your account, which requires a typed reason, shows a black banner across the interface the whole time they are in, and writes their name onto everything they touch. There is a log of who entered, when, and why. Support can read driver requests but cannot decide them — that is your staff's call, and the system refuses it.

Can we get our data back out?

The driver and vehicle roster exports to a spreadsheet, with the dropdowns intact, whenever you want it. A full incident export is on the roadmap and not built yet. If you leave, we will hand you the data.

Do you integrate with our ELD or TMS?

Not yet, and the honest answer is that it depends entirely on the vendor — a documented API and a nightly file drop are weeks apart in effort. Tell us what you run and we will tell you which it is.

How long does it take to get started?

A week, most of which is you deciding your incident categories. We set the account up, import the roster from the spreadsheet you already keep, and create the logins. Run one terminal for a week before anyone else touches it.

Do your drivers get it in Spanish?

Not yet — the driver side is English only today. It is on the list, and it matters more than most of what is on there, because a form a driver half-understands produces a report you cannot rely on. If a large share of your drivers would use Spanish, say so on the call: it moves up the order, and the fleets running it now are the ones setting that order.

Who is behind this?

A small, independent company. You will deal with the person who built the thing. At this size that means the roadmap is genuinely shaped by the first few fleets on it — which is the reason to be one of them.

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.