01
Everything that needs you, in one list.
Hours, credentials, inspections, faults, deviations, safety, charge, ETAs and trailer tags — nine kinds of problem, one order, and every row opens the screen that fixes it.
Flotta · Fleet operations
One list. In order. Every morning.
Hours, credentials, inspections, fault codes, safety events, trailers, charge, fuel cards — everything that needs a decision today, in one queue, worst first. You clear it. The map proves it.
9kinds of problem in one queue
6rules you can retune yourself
2hours clocks on every truck card
4DOT registers on one screen
3telematics providers it reads
12modules on one platform
These are things Flotta does — not results a customer measured.
01
The queue
Everything that needs you, in one order.
Hours, expired credentials, overdue inspections, fault codes, route deviations, safety events, low charge, late ETAs, dying trailer tags — nine different kinds of problem, one list, worst first. Each row says what it is, which unit, and what happens if you ignore it.
Every row deep-links into the stage that resolves it. You never go hunting for the screen that fixes the thing you just read.
HOS · OUT OF HOURS — EF-104, Ty Nguyenboth clocks exhausted — driver cannot legally moveOpen fleet
COMPLIANCE · EXPIRED — Medical Certexpired 32d ago — driver blocked until renewedRenew
ENGINE · FAULT — EF-104aftertreatment NOx sensor, implausible signalOpen map
ROUTE · DEVIATION — EF-101, Dallas → Houston175.3 km off the assigned corridorOpen map
TRACKER · BATTERY — TRL-203gateway at 5%, riding with EF-107Open assets
02
The rules
You decide what earns a row.
Every row in that queue was written by a rule, and every rule is on one screen with its number showing. Tracker battery under a percentage. Reefer more than so many degrees off setpoint. A drive clock under so many minutes. Change the number; the next pass uses it.
Each rule names the row it writes, in plain words. And each row carries the rule that wrote it back the other way — so nothing appears on your list without an answer to "why am I looking at this?"
03
The trucks
Both clocks, on the face of the card.
Drive left and duty left, side by side on every truck — not two clicks into a log. Alongside them: live speed or state, the driver, the year and model, fuel or charge, and any fault code the engine is currently throwing.
Diesel and electric sit on the same roster. On an electric tractor the fuel figure becomes state of charge and the range it actually buys you.
04
Trailers and equipment
The trailer knows which truck it's under.
Dry vans, flatbeds, reefers, chassis, gensets, excavators, light towers, skid steers — all on the same roster as the tractors. Each one reads with EF-101, in yard, or on site, with the job site named, when it last spoke, and how much battery its tag has left.
Reefers carry the temperature they're actually holding against the one you set, with twelve hours of history behind it.
05
Compliance
The audit folder, already assembled.
Driver logs, inspections, fuel tax and credentials on one screen. A violation doesn't say "violation" — it prints the regulation it broke, against the day it happened, with the log still marked open or certified.
Logs from different ELD vendors land in the same table, each row stamped with where it came from. Running Samsara on half the fleet and Motive on the other half stops being two audits.
Why this instead of what you have
A map tells you where. It won't tell you what to do.
Twenty trucks on a screen is the easy half, and every vendor has it. The morning goes somewhere else — to the seven places you check before you know which driver can't legally turn a wheel today.
The ELD knows the clock. Nothing else does.
So a load gets planned onto a driver with forty minutes left, and you find out from the driver.
The credential expired in a spreadsheet.
A medical card lapsed thirty-two days ago. Nothing was watching the date, so nothing said anything until a scale house did.
The alerts stopped meaning anything.
Same driver, one km/h over, twelve identical emails. By week two nobody opens them, including the ones that mattered.
One queue, in one order, built by rules you set and can change in ten seconds. When it's empty, you're actually done — and you know what "done" covered.
06
Safety
It tells you who hasn't been talked to.
Drivers ranked worst first, each with a score, the mix of events behind it, and the one thing most systems leave out — whether anyone has ever coached them, and how long ago.
Every event ends in a decision: coached, or dismissed. Nothing sits in a list forever quietly training people to ignore the list.
07
Fuel and the numbers
Every swipe, checked against where the truck was.
A fuel card gets used at a pump in Amarillo. Flotta looks at where that unit actually was at that minute and returns one of three answers: verified, flagged — or unverifiable, when there was no position to check against.
That third answer is the point. Absence is stated, never guessed. Utilization comes from your own position history, and where the data can't support a number, it says so instead of printing one.
08
Five reasons it wins
Plenty of tools do one of these. This does all five.
02
Every row came from a rule you can change.
The thresholds are on a screen, in the condition's own units, with the row each one writes named beside it. Too noisy, too quiet — you fix it yourself, and the next pass obeys.
03
The fuel card gets checked against the truck.
Every swipe against the unit's own position at that minute. Verified, flagged, or unverifiable — and it says which, rather than quietly rounding the third into one of the others.
04
The trailer knows which truck it's under.
Not two dots that happen to be near each other — a state. Reefers, flatbeds, gensets and job-site equipment all sit on the roster with the tractors, each one paired, parked or on site by name.
05
It runs on the telematics you already bought.
Samsara, Motive or Zonar. Connect one and every screen switches to the live feed with nothing else changing — and it shows you what each connection actually buys before you make it.
09
What's in it
Six areas, one module.
The queue
6- One list across the whole fleet, worst first
- Nine kinds of problem in one grammar
- Every row opens the screen that resolves it
- Plain language, not status codes
- Need you, watched, in motion, positioned
- Clear it and the map proves it
The rules
5- Every condition has a rule you can see
- Thresholds in the condition's own units
- Each rule names the row it writes
- Warning or critical, set per rule
- One row per unit per day, with the count
Trucks and trailers
6- Drive left and duty left on every card
- Fault codes on the roster, not buried
- Diesel and electric on one list
- Charge with the range it actually buys
- Trailers paired to a named tractor
- Reefer temperature against setpoint
Compliance
5- Logs, inspections, fuel tax, credentials
- Violations cite the regulation by number
- Certified or open, per driver per day
- Mixed ELD vendors in one table
- Expiries walk themselves onto the queue
Safety
5- Drivers ranked worst first, with a score
- Whether they've ever been coached
- Seven event types, counted per driver
- Speed against the posted limit, and the road
- Coached or dismissed — nothing lingers
Numbers and the floor
6- Fuel swipes checked against position
- Verified, flagged, or honestly unverifiable
- Utilization from your own position history
- No number printed without ground to stand on
- Scheduled email digest with the CSV attached
- Samsara, Motive or Zonar underneath
Thirty-three of them. There are more, but these are the ones that change how a morning goes.
Next step
See it on your fleet.
Ninety minutes on your operation: your units, your telematics provider, the credentials you track, and which six rules you'd set first. You keep the configuration.
Flotta is the ELYON fleet module. Every capability here is live in the product today. No figure on this page is a customer outcome.