Per-driver daily activity
Driver, date, truck, start and end times and mileage, total stops visited, and detention hours — assembled from the load record rather than transcribed by hand.
USPS & HCR contractors
Contract routes modelled the way they actually run
Trips have parts. Frequencies are codes with irregular rules attached. "Daily except Mondays and days after holidays" is a real schedule, and flattening it into a dropdown is how contractors end up reconciling by hand.
01 · The data model
Where generic TMS platforms lose the detail
HCR work has structure that a generic "trip" record can't hold. When the software can't represent it, the difference gets absorbed by a person and a spreadsheet.
| What HCR work involves | Typical generic handling | In Vektra |
|---|---|---|
| Trip parts | One trip record; parts tracked in notes or a second system | Parts are first-class, each with its own times and assignment state |
| Frequency codes | Flattened to a weekday checkbox, nuance lost | Code plus description plus structured day and holiday rules |
| "Days after holidays" | Simple date match against a holiday list | Offset-aware holiday rules, so the day after resolves correctly |
| Contract expiry | A coloured row a human is expected to notice | Expiry blocks trip generation at the source |
| Contract numbers | Free-text field, inconsistently entered | Structured contract records with real HCR formatting |
| Missing GPS / ELD links | A counter in the header that never reaches zero | A decision item with the consequence attached |
02 · The same pattern, everywhere
An expired contract should stop generating work
It's the identical idea as a maintenance hold blocking a dispatch: a status that has consequences instead of a status that has a colour.
When a contract lapses in Vektra, trip generation against it stops. Nobody has to notice a red swatch in a legend at seven in the morning, and nobody spends the following week unwinding trips that should never have existed.
- Generation gated on contract status, not on human vigilance
- Renewal dates surfaced before they bite, not after
- Anything overridden is explicit and audited
Trip generation, gated
POST /usps/contracts/999X9/trips/generate 409 Conflict { "error": "CONTRACT_EXPIRED", "contract": "999X9", "expiredOn": "2026-06-30", "generated": 0, // nothing was created — renew or extend first }
03 · The paperwork
Reports contractors are still doing on paper
Per-driver daily activity records get hand-written at a surprising number of operations, because the system in place can't produce them. Vektra captures the fields that report needs as part of the normal workflow.
Leg-level detail
Order number, origin and destination, BOL, trailer, depart and arrive times, depart and arrive miles. Captured per leg, not reconstructed afterward.
Trailer spotting & fuel
Trailer in and out with location, fuel gallons and odometer at fueling — the fields that fall off the edge of most equipment records.
Detention is a revenue leak, not a footnote
Detention hours show up twice in almost every contractor's paperwork and rarely once in their software. In Vektra it's a tracked decision item with the underlying time data behind it, so you can bill it or at least know what it cost you.
04 · Straight talk
What's built and what isn't
The contract, trip, part, frequency and holiday-rule model described above is built — it's the schema the product runs on. Expiry gating trip generation works the same way the maintenance hold does, because it's the same underlying pattern.
Direct integrations to USPS systems and third-party visibility platforms are on the near roadmap rather than shipping today. If your operation depends on one of those from day one, tell us on the call and we'll give you a real timeline instead of a maybe.
Bring a contract and a bad week
We'll model your actual frequency codes on the call and show you what generates.