Your haulage company is growing, but so is the admin. How do you break the cycle?

Administration in transport grows in step with volume, because every journey requires the same manual steps

Twenty lorries each making four journeys a day produce eighty journeys. Every journey goes through the same steps: entering the order, scheduling, sending it to the onboard computer, printing the CMR, receiving the proof of delivery, processing hours, invoicing. Thirty lorries produce a hundred and twenty journeys, and so one and a half times as much of every step.

As long as a person performs those steps, the office time required grows exactly as fast as the number of journeys. That is why the rule of thumb "one administrative member of staff per so many vehicles" is so persistent in many businesses: it holds, as long as the work per journey stays the same. The only way to break that line is to reduce the work per journey. An integration between the TMS and the on-board computer costs money once and then processes every journey, whether there are eighty or two hundred.

That distinction is the core of the scaling question. An extra employee solves today's problem and shifts it to the next stage of growth. Less work per journey solves it for every growth stage after that. Our article on why transport administration takes so much time sets out the seven causes one by one; here the question is in what order you tackle them.

The problem rarely lies with people; it usually lies in the handovers between systems

A journey passes through at least four pairs of hands and four systems: from the planner to the driver, from the driver to administration, from administration to accounting, and from accounting to the client. At each handover, something is retyped, chased up by phone or checked again.

The handovers are where the time goes. The planner enters the trip in the TMS and retypes it into the on-board computer, because the two aren't integrated. The driver hands in a paper trip sheet, because the app can't capture proof of delivery. Administration checks the charter invoice against the trip list, because nothing does that automatically. And accounts asks on the fifth of the month whether all proofs of delivery are in, because otherwise the invoice can't go out.

A growing business feels this more than a small one, for a simple reason: with ten vehicles, the planner knows every driver and every customer and catches handover errors from memory. At forty vehicles that no longer works, and the handovers become more formal, slower and more error-prone. The business then adds checks, and those checks are manual work again.

The order determines whether it works: first the process, then integration, then automation, then custom development

Businesses that start automating before the process is settled end up automating the errors too. Businesses that start custom development before they know which steps really deviate end up building too much. The sequence below avoids both.

1. The process: one order number from intake to invoice

   Agree that every order gets one number that appears on the planning, the CMR, the trip sheet, the proof of delivery and the invoice. Record who enters which data and who owns addresses, time windows and rates. Set a fixed cut-off time for changes. This costs no software, but without this step no integration can know which trip belongs to which document.

2. Integrations: getting your TMS, on-board computer and accounts software working together

   The trip passes automatically from the TMS to the on-board computer, the status and hours flow back automatically, and the completed trip goes to the accounting package as an invoice line. That removes the retyping between systems, the biggest source of duplicate work. For which integrations a TMS needs, see our page on building a TMS; for how an integration with the on-board computer works, see the page on a transport planning API.

3. Automating recurring steps

   Now that the systems know each other, you can automate the steps that recur for every trip: document recognition reads the CMR and the weighbridge ticket, the POD arrives through a driver app, and the charter invoice is automatically checked against the trips driven. Staff review the exceptions, not every document.

4. Custom development where standard software falls short

   Only at this stage does it become clear which parts of your process a standard package can't handle: a custom customer portal, planning with industry-specific rules, or a module your TMS lacks. You then build those specifically, around the integrations from step two. See developing transport software and, more broadly, custom software development.

Why this order? Integrate before automating, because document recognition without an integration still needs a member of staff to get the result into the TMS. Automate before custom development, because most recurring steps can be solved with existing building blocks, so custom work is only needed for what remains. Reverse the order and you build at greater cost and still keep manual work. Our page on automating logistics processes describes the building blocks we use for this.

You can tell whether it works from the administrative hours per trip

Hours per month naturally rise with growth and so say nothing about the approach. Hours per trip do: if those fall while the number of vehicles rises, the line has been broken.

The measurement is simple. Each week, add up the hours that planners and administration spend on data entry, document processing, checks and follow-up calls, then divide that by the number of trips that week. Do this before you start and after each step. A company with twenty vehicles that goes from three quarters of an hour per trip to half an hour could, on paper, run thirty vehicles without any extra office staff. You can work out what the current manual handling costs per year with our manual administration calculator.

Does the pressure start with the planning itself, for example because two planners work in a single Excel file? Then transport planning in Excel: when does it stop working? is the better starting point. And if you operate internationally, the eFTI regulation from 2027 gives you an extra reason to process documents digitally; you can read more in eFTI 2027: why invest in digitising transport documents now?.