Case study — Corporate consignment
Compliance was the qualification,
not the paperwork.
Sharma Transport Corporation goes after corporate consignment work. That freight is not awarded on rate alone — it is awarded to the operator who can show, trip by trip, that the driver was trained, the load met the client’s standard, and the checklist was completed before the vehicle started.
Before
Evidence assembled after the fact.
The obligations were never in doubt. Every enterprise client publishes its loading standard, every one of them expects the driver on that consignment to have been trained against it, and every one of them expects a pre-start check on the vehicle and the load.
What was missing was the trail. Training records sat in a folder, the loading standard sat in the client’s document, and the checklist happened — but it happened in a supervisor’s head, or on a sheet that stayed at the yard. When an audit or a tender asked which driver ran which consignment against which check, the answer had to be reassembled from memory. That is a slow answer, and a slow answer reads like a no.
After
The checklist is the ignition.
The enterprise client’s checklist is configured once and then stands between the vehicle and the trip. It runs on the driver’s phone before the trip opens: vehicle condition, load securing, documentation, whatever that client’s standard specifies. Nothing starts until it is complete, so it cannot be done later or done from memory.
Driver training data sits on the driver record, against the standard it was training for, so the roster itself knows who is qualified for which client’s freight. The completed checklist, its timestamps and its photographs stay attached to the trip they belong to. Producing the evidence stops being a project and becomes a filter.
Compliance recorded at the moment it happens is a sales asset. Compliance reconstructed a month later is an expense.
The operating principle behind this deployment
What the app is actually doing
Three things, automated from the start.
01
The pre-trip checklist, baked in
Per enterprise client, per vehicle type. It is not a form filed alongside the trip; it is the condition on which the trip opens. A check that can be skipped is a check that eventually is.
02
Training data on the driver
Which loading standard each driver has been trained against, and when. Dispatch can see it while there is still time to change the roster, rather than the client discovering it at the gate.
03
Evidence as a by-product
Every consignment carries its own compliance record because that record is how it started. Answering an audit, or a tender’s compliance annexure, becomes a query rather than a search.
The same principle applied to spending: driver expenses against the trip →
Your fleet, your standards
Bring one client’s checklist. We’ll wire it in.
More customers
All case studies →The fleet was profitable. Nobody could say which trips were.
Margin known once a month, at fleet level, after the fact — an average with the interesting parts cancelled out. Per trip, per vehicle and per driver, the arithmetic had simply never been done.
Two fleets →Receipts arrived a week late, attached to nothing.
Driver spend that was never mapped to a trip or a delivery, approved from a recollection of a date. Inaccurate in a way that quietly moved money, and impossible to audit after the fact.
Two fleets →