Foi Parcurs Online

Romanian transport companies are legally required to keep route sheets for every vehicle, every day. In practice this meant a printed form per driver, filled in by hand, collected at the end of the week, and re-typed into a spreadsheet by an office administrator who had no way to check whether the numbers were right.

The client ran a fleet of ninety vehicles. Two people spent most of their week on transcription, and the fuel-consumption figures that management used for pricing decisions were four to six weeks old by the time anyone saw them.

Discovery started in the dispatch office rather than in a document. We watched the process for three days, timed each step, and found that the expensive part was not the data entry itself but the correction loop afterwards — chasing drivers about illegible odometer readings.

So the first thing we built was not a dashboard. It was a driver-facing form that validates the odometer reading against the previous entry at the moment it is typed, on a phone, in a truck cab, offline if necessary.

Six months, two-week sprints, a staging release at the end of each. The platform covers vehicle and driver records, route sheet generation, fuel and consumption tracking, cost centres, and the export formats the accountants already used — because the fastest way to kill adoption is to make the finance team change their process too.

Rollout was one depot at a time. The paper process ran in parallel for three weeks so nobody had to trust us before the numbers matched.

React and TypeScript on the front end, Laravel and MySQL behind it, hosted on AWS with Docker images and a CI pipeline that deploys on merge. Nothing exotic: the client has an internal developer who needed to be able to maintain it after we stepped back, and he does.