Routes → Pay
Routes become pay. Nobody types.
Route files land, hours sync to the allocated crew, the log writes itself — before breakfast.
Retyping routes is a job nobody was hired for.
An evening of retyping every week costs more than the Drivetrain does all year — and every typo is a pay dispute.
Point the route emails at us. Done.
One forwarding rule on the depot inbox. Every route file after that reads itself.
Your carrier’s own files are the input — no new process for the depot.
Inbound · depot email
Route file Parsed
BAR-Mon-14.pdf
Landed
05:58 · read on arrival
Auto-ingest
It reads the routes, so you don’t.
- Emails parse themselves. Route files are read the moment they land.
- Hours follow the crew. The allocated crew gets the hours — attribution is automatic.
- Logs exist by morning. Route logs are ready before anyone’s first coffee.
- Never invents hours. A route that doesn’t match queues for a human — guessing is not an option.
Routes → Pay
1 route needs a human
No crew matched — queued for review
Route to log to live invoice, on every phone.
Made for whoever retypes the routes today.
Crews see their hours the same morning. Operators never touch a keyboard.
£5 per crew, per month.
One retyped week costs more than a crew’s whole year of Drivetrain. Runs inside Runmark, or bolts onto your stack through its ingest API. Switch off just as cleanly.