VARO · The first AI employee for trucking carriersPrivate beta · a few fleets at a time

VARO reads your inspection violations and prepares evidence-backed DataQs challenges.

Press two keys. VARO reads what is on your screen, runs every finding through seven checks, and files through your own DataQs account with one keystroke. Drivers feed it from the roadside. Brokers read its passport. It starts with the safety record; the rest of a carrier's paperwork follows, one job at a time.

Start with your DOT number Request a beta seat

No waitlist. Your record is read today, the way insurers read it. Beta seats go to fleets whose record we have already reviewed.

Where it stands

What is live today, and what the beta adds.

The boards below are the destination. This is the ground we stand on today, stated plainly, because that is what makes the rest worth reading.

Live today

Free record check for any USDOT number
VARO chat, reading your real FMCSA record
Nightly watch on the record, with alerts
Challenges drafted and cited to 49 CFR
Done-for-you filing by our team, followed to a decision

In the private beta, in this order

Roadside intake: report photo in, signed statement out
The ⌥V overlay and the seven checks, one key to file
The vault, the filing policy and the morning queue
Watch and email: new violations become drafted cases
The Record Passport

After the beta

Scoped keys for outside filers and brokers
Live session watch and take-over
Roles, SSO and API for enterprise fleets

How it works, board by board

One inspection, start to finish.

Six boards from the product plan. The fleet, the units, the numbers and the people on them are made up; the rules and the checks are real.

01 · The overlay

Press two keys. VARO reads what is on your screen.

An inspection report PDF, the DataQs portal, an ELD dashboard, a broker's email. Press ⌥V and VARO reads it where it is: no upload, no copy-paste, no new tab.

It checks the rule before the wording

The report says the trailer is a 1992 build. 49 CFR 393.13 reaches only trailers made on or after 1 December 1993. The rule does not apply, and that is a stronger finding than any argument about how the officer wrote it.

Seven checks on every finding

The regulation text, quoted. Does it apply to this unit and this day. The fact that decides it, checked, not guessed. Does it count in your scores. Repeated codes on the same inspection. Points at stake. What that argument has done before in that state.

One key to file

A 138-word request, filed through your own DataQs account as your authorized representative. The exact text you approve is logged.

The rest of the report, already sorted

The other violations are tiered as they are read: strong files first, standard next, slim last. A tire at 42 of 110 PSI is slim because CVSA counts 50% or less as flat.

VARO never argues what it cannot show. If a check is missing, the finding is unverified and it waits.

The VARO overlay over an inspection report: a dark pill reading the report and a finding card with seven gate rows — Illustration with sample data. Northstar Reefer Lines, its units, numbers and people are made up.

02 · Roadside intake

The report arrives in the first hour, from the driver holding it.

Every filing needs the inspection report and, for most of them, the driver's account. Today fleets hunt for both weeks later. VARO collects them at the scale house, before the truck rolls.

Text the report

The driver texts a photo of the report to the fleet's safety line. VARO reads the state, the report number, the level and the violations, tells him which one looks like it does not apply, and asks for four photos.

Evidence in 60 seconds

Four photos with time and place: the trailer's lower rear where the tape should be, the tire with a gauge in the groove, the lamp switched on, the report's signature line. Taken now, they are proof. Taken next week, they are a story.

His statement, his words

He talks; VARO transcribes in English, Punjabi or Spanish. Five facts, none added by VARO. He hears it read back and signs. A driver statement is the driver's own account, never a fact we gave him.

No app on day one: SMS and a web link. Every violation also sits on the driver's own PSP, so drivers carry VARO from fleet to fleet.

Three phone screens: texting a report photo to VARO, the evidence camera with GPS locked, and a signed driver statement — Illustration with sample data. Northstar Reefer Lines, its units, numbers and people are made up.

03 · Autopilot

Eleven minutes a morning. The rest of the day VARO works.

The safety manager does not open VARO to read. She opens it to approve. Six cases waiting, strong first, slim last, each with its seven checks visible.

The vault

Her DataQs login lives in an encrypted vault, the way a password manager holds it. Under her written policy, strong findings file before she sits down. Standard and slim wait for her.

Watch

The FMCSA snapshot brought three new violations on two units overnight. Two are drafted. One is waiting on a report VARO requested from the state at 06:02.

The points clock

Which points leave the record on which date, and what that does to each BASIC if nothing new lands. This is the number her boss asks about.

A hold is a hold

A speeding citation still in court files nothing until the court decides. Four amber checks means unverified, and unverified sorts last with no override.

VARO cannot file an unverified finding. Every submission is the exact text she approved or her policy allowed, and every one is logged.

The morning queue: six cases with gate dots, a vault chip, four stat tiles and a Watch rail — Illustration with sample data. Northstar Reefer Lines, its units, numbers and people are made up.

04 · The Record Passport

What brokers and insurers see, with the fix next to the risk score.

A broker's vetting tool shows a percentile. It cannot say that half the violations are being challenged. A shareable page, verified against FMCSA data that morning, can.

Risk score versus record

Left, the hiring-risk tier the broker already sees. Right, the record: challenges filed, granted, pending, and the points that leave next.

The after-pending number

Each BASIC today and if the pending challenges are granted. Shown as "after pending", never as a promise.

Every challenge, including the denied ones

Inspection number, regulation, state, status. The denied ones stay on the page. A passport that only shows wins is a brochure.

A pending challenge is a request, not an outcome. No success rate is implied. That sentence sits in the footer of every passport.

The Record Passport page: verified chip, risk score beside the record, five BASIC tiles, a points clock and the challenges table — Illustration with sample data. Northstar Reefer Lines, its units, numbers and people are made up.

05 · Three teams, one product

The same gate, the same vault, the same passport. Only who does the work changes.

Small fleets need one cleanup. Bigger fleets pick up new violations every month, so they need a system they keep using. Half of all violations on the 24-month record sit on fleets of 11 trucks or more.

1 to 10 trucks: done for you

Our filers clean the record once, then VARO watches it for a small monthly fee.

11 to 100 trucks: VARO, with our filers behind it

Your safety team runs the queue. Our filers work the backlog inside your VARO, with a scoped key.

101 trucks and up: your team in VARO

Named account, roles, SSO and API. Two-week white-glove onboarding, then self-serve.

Pricing follows the shape: quoted per record for a cleanup, per truck per month for the platform, annual for enterprise. Numbers are published with the mid-market launch.

Three tier cards for small, mid-market and enterprise fleets, and the five-step build order — Illustration with sample data. Northstar Reefer Lines, its units, numbers and people are made up.

06 · Remote monitoring and access

Watch VARO work, take over mid-form, and see who did what.

Eight systems that can touch your record, each on its own clock. And when VARO is inside a portal, you can watch the screen, pause it, or take over the same session.

Three kinds of key

VARO's autopilot acts under a written policy. The owner approves and can revoke anyone. A filer holds a scoped key: draft and request reports, never submit, and the key expires. ELD connections are read-only.

The live session

Nothing is retyped. Every keystroke in a portal session is recorded and hashed into the consent log.

The access log

Who logged in, what was filed, which report was requested, who approved. An auditor can replay exactly what was filed, by whom, under which approval.

This is how our own filers will work for mid-market fleets: inside the client's VARO, with a scoped key, every action visible.

The Monitor page: eight watched systems, a live DataQs session with Watch, Take over and Pause, and the access log — Illustration with sample data. Northstar Reefer Lines, its units, numbers and people are made up.

The seven checks

Nothing files until every check is shown.

A finding that fails any check is marked unverified and sorts below everything complete. There is no override, not for VARO, not for our filers. That is why a safety director can trust what it files under her name.

7 of 7 · complete

4 of 7 · unverified, waits

Regulation text

The 49 CFR paragraph, quoted from the regulation, never from a summary of it.

Applicability

Does the rule reach this unit, this driver, this day. Model year gates, class exemptions.

The deciding fact

Named, checked against a document, result shown. Never guessed.

Counts in your scores

Is the violation in the Safety Measurement System at all.

Repeated codes

The same code twice on one inspection: all instances, or nothing moves.

Points at stake

Severity weight times time weight, so the biggest move files first.

What happened before

That argument, in that state, from our own decided filings. Rates only at five decided filings.

A day at a fleet

Four people, one inspection, nothing emailed around.

VARO works before anyone is awake and after everyone has gone home. People appear only where a human decision or a human fact is needed.

06:00VARO
Reads the FMCSA snapshot, DataQs, the ELD and the state portals. Requests a missing report. Files the strong findings under the fleet's policy.
08:40Safety manager
Opens the queue, approves four cases, holds the court case. Eleven minutes.
09:30Filer
With a scoped key, drafts the slim cases, asks a driver for evidence, requests two state reports. Cannot submit, and does not need to.
14:32Driver
Inspected at the scale. Texts the report photo, takes the four photos, signs his statement. Fifteen minutes, before he drives off.
14:45VARO
Reads the photo, opens the case, attaches the evidence and the statement, runs the seven checks. The safety manager gets the alert.
16:40Safety manager
Watches VARO inside DataQs, takes over one session for two minutes, approves.
17:30VARO
The Watch digest: what was filed, what is pending, what leaves the record next.

The private beta

How to get in.

Start with your USDOT number. You get your record today. If VARO fits your fleet, we call you about a seat.

Start with your DOT number Book 15 minutes

What is the private beta?: A few fleets at a time, onboarded by hand, using each part of VARO as it ships in the order above. Beta fleets get the done-for-you team behind every filing while the software catches up.
Is there a waitlist?: No. Start with your USDOT number and you get your record read today: inspections, violations, points, what leaves when. Beta seats go to fleets whose record we have already reviewed.
Does VARO file without me?: Only what your written policy allows, and only findings that pass all seven checks. Everything else waits for your approval, and every submission is logged with the exact text.
Do you guarantee a violation comes off?: No. The state that wrote the inspection decides every DataQs request. We promise the work, the evidence and a straight answer on what will not hold.

Keep your record clean. Keep rolling.

Run your real FMCSA record free. No signup to start.

Run my record free Book a 15-minute call