How to replace whiteboard and spreadsheets in a traffic office
A practical guide for UK hauliers moving from whiteboards, paper and spreadsheets to one traffic office system without losing control.
If you want to replace whiteboard and spreadsheets in a traffic office, do it as a controlled records move, not a big-bang software launch. The aim is simple: one place for jobs, vehicles, drivers, maintenance dates, defects, subcontractors and invoice status, so the person running the desk can see what is happening now and prove what happened later.
For a UK operator, the trigger point usually comes somewhere between 5 and 100 vehicles. Below that, a whiteboard and a few spreadsheets can limp along if one experienced person holds it all together. Above that, the gaps start to hurt: missed PMI bookings, unclear trailer allocation, defect reports sitting in a cab, rates held in somebody’s inbox, and no quick way to answer a DVSA question without opening six files and three tabs.
What usually breaks when the traffic office runs on a whiteboard
A whiteboard is good at showing today’s plan. It is poor at showing evidence, history, responsibility and exceptions.
The first thing that breaks is version control. If the traffic planner changes a vehicle, swaps a driver, or tips a job onto a subcontractor, the board may show the latest plan but not who changed it, when, and why. A spreadsheet can add some history if people are disciplined, but in most traffic offices you end up with “final”, “final v2” and “use this one”. That is not an audit trail.
The second problem is that traffic planning and compliance split apart. The board says vehicle 21 is on a trunk tonight. The maintenance spreadsheet says it is due a PMI next week. The defect book in the cab says the marker light is out. The wall planner does not bring those records together, so the wrong vehicle gets sent because the transport office is working from three different truths.
Once you have several vehicles and drivers, paper defect reporting becomes a control problem. A driver writes up a defect in a defect book or on a daily walkaround check sheet. The page stays in the cab until the end of shift, or gets handed to a fitter, or sits in an in-tray. That creates two risks. First, safety-related defects may not be escalated quickly enough. Second, you cannot easily show a clear chain from reported defect to repair decision to rectification to sign-off.
Spreadsheets also struggle with recurring dates. A UK operator needs to keep on top of PMI intervals, MOT test bookings, tachograph calibration, road fund licence, insurance renewal, LOLER where relevant for lifting equipment, and any site-specific accreditations or permit dates. A spreadsheet can store dates, but it does not naturally manage dependencies. If a vehicle is off road, a PMI is moved, and a hire vehicle covers the work, the office needs to see the knock-on effect on jobs and records immediately.
Commercial control usually breaks next. Rates are stored in a rate sheet, customer instructions in emails, proof of delivery in a tray, and invoice status in accounts. That means the traffic office can plan the job, but cannot easily confirm margin, waiting time, redelivery charges, pallet discrepancies or whether the POD has been received in time to bill.
Then there is resilience. If one traffic clerk or transport manager is off sick, a whiteboard system often falls apart because the real knowledge is in that person’s head. A proper office system should let another competent person open the record and understand the live position without ringing around.
For an O-licence holder, the biggest issue is not neatness. It is whether the business can demonstrate continuous and effective management. The Traffic Commissioner is not interested in how tidy the whiteboard looked on a Tuesday. They want to know whether systems are robust enough to keep vehicles fit, drivers managed, and records available.
Which records you need in one place first
Do not start by trying to digitise everything ever created. Start with the records that control today’s operation and the records you are most likely to be asked for.
First, job and allocation records:
- customer name
- collection and delivery points
- booked date and time
- load reference
- vehicle and trailer allocation
- driver allocation
- subcontractor allocation where used
- delivery notes and POD status
- rate, extras and invoice status
If your planners are constantly ringing customers for booking updates or delivery status, it helps to have structured call records. A system with proper customer callover tracking is more useful than a notes column that nobody can search later.
Second, vehicle records:
- registration, fleet number and VIN
- O-licence disc details where recorded internally
- MOT due date
- PMI schedule and completed inspection history
- tachograph calibration date
- servicing and repair history
- tyre records if managed in-house
- insurance details
- hire or lease documents where applicable
For HGV operations, the vehicle file needs to make it easy to retrieve maintenance evidence. For PSV operators, the same principle applies, but the maintenance regime and operating context differ, so make sure the system can separate fleet types if you run both.
Third, trailer records:
- trailer number and VIN
- test dates where applicable
- PMI schedule
- brake test records if held separately
- repair and defect history
- tyre and service records
Fourth, driver records:
- full name and contact details
- driving licence check dates and evidence
- Driver CPC status where applicable
- digital tachograph card details
- right to work documents
- induction and policy sign-off
- disciplinary, accident and training records
- agency or subcontract driver status where relevant
In Great Britain and Northern Ireland, the underlying need is the same: keep complete, current driver files. Where your operation spans both, make sure the software can handle the way your licences, depots and operating arrangements are actually structured rather than forcing one depot logic onto everything.
Fifth, defect reporting records:
- daily walkaround checks
- nil defect submissions
- reported defects
- severity or roadworthiness status
- fitter or workshop action
- parts ordered
- rectification date
- sign-off and return-to-service decision
Sixth, compliance diary items:
- PMI due dates
- MOT bookings
- tachograph calibration
- insurance renewal
- operator licence undertakings and review dates
- training dates
- FORS or customer-specific audit actions if relevant
- DVS permit status if you operate affected vehicles in London
Seventh, commercial records:
- agreed customer rates
- lane or postcode rates
- demurrage or waiting-time rules
- surcharge rules
- subcontractor rates
- invoice batch status
- credit note reasons
- POD received date
This is where proper rate control matters. If your rates are scattered between email chains and old spreadsheets, planners make avoidable mistakes. A structured rate table or rate lookup for traffic planning saves time and reduces disputes.
How to move from paper and spreadsheets without losing control
The safest way to replace whiteboard and spreadsheets in a traffic office is in stages. Keep the current process running while you move one record set at a time.
Stage 1: map the current controls
Write down where each live record currently sits. Not in theory, in practice. For example:
- today’s plan on the whiteboard
- next week’s jobs in spreadsheet A
- vehicle maintenance dates in spreadsheet B
- defects in paper books
- driver licences in HR folders
- subcontractor list in Outlook contacts
- PODs in a tray
- invoicing status in QuickBooks and a traffic sheet
This step shows where the handoffs are. Those handoffs are where things get missed.
Stage 2: move live jobs first
Start with current and forward jobs, not old archives. Enter all open jobs into the system with customer, timing, allocation, job status and commercial status. For one or two weeks, run the board and the system in parallel. At the end of each shift, reconcile them. If the board says trailer T12 is on a load and the system says T14, fix the process before moving on.
Do not migrate years of completed jobs before you can trust tomorrow morning’s plan.
Stage 3: build vehicle and trailer files
Next, load your active fleet only. For each vehicle and trailer, enter the key identifiers and next due dates first. Then attach or reference the current certificates and the last completed PMI records. You can import deeper history later. What matters immediately is that the traffic office can see whether a unit is fit to allocate and what is coming due.
At this point, set clear ownership. Usually:
- traffic office owns allocation status
- workshop or maintenance provider owns maintenance event completion
- transport manager reviews exceptions and overdue items
Stage 4: build driver files
Load all employed drivers, regular agency drivers and any others you routinely allocate. Add licence check dates, CPC status where needed, contact details, and any restrictions. Again, get the current picture right before worrying about older scans.
If your agency use is heavy, create a proper process for temporary drivers. No one should be allocated to a job until the required documents are present and checked.
Stage 5: move the PMI schedule
This is the stage that most directly supports the O-licence holder’s responsibilities. Set each vehicle and trailer to its planned PMI interval and next due date based on your maintenance planner. Then test whether the system can show:
- what is due in the next week and month
- what is overdue
- what has been completed
- what is awaiting documentation
- what was rescheduled and why
Software does not decide the correct maintenance interval for you. That remains an operator decision under your maintenance arrangements. But it should make missed dates and missing paperwork obvious.
Stage 6: switch defect reporting
Move from paper defect books to digital reporting only when the reporting route is simple enough for drivers to use every day. If drivers cannot submit a nil defect or report a fault in under a minute or two, they will work around it.
Before switch-over, agree:
- who monitors incoming defects
- what counts as safety critical
- who can stop a vehicle being allocated
- who records rectification
- how nil defect reports are checked for missing days
Keep a short written procedure. If a driver reports a defect out of hours, the office must know what happens next.
Stage 7: add subcontractors and external hauliers
Subcontracting is often where control disappears. Build a proper approved list with contact details, insurance checks, rates, and document expiry dates. Record who each load was given to, when, and on what rate. If you use owner-drivers or regular partners, treat them as controlled suppliers, not names on a phone.
Stage 8: connect PODs and invoicing
Only after the planning and compliance basics are stable should you tighten the finance flow. Link jobs to POD receipt, query status, extras and invoice release. If accounts runs in QuickBooks, check that the traffic system can pass clean invoice data across without rekeying. Rekeying from traffic to finance is where rates, dates and references get corrupted.
What a digital traffic office should let you prove to DVSA
A digital traffic office should help you retrieve evidence quickly. It does not make you compliant by itself. You still need proper management, proper maintenance arrangements, and people following the process.
For a DVSA visit, desk-based investigation or follow-up under OCRS pressure, you should be able to produce, without delay:
- maintenance planner
- PMI inspection records
- MOT history and bookings
- repair records
- safety inspection sheets
- brake test evidence where relevant
- defect reports and rectification records
- records showing vehicles were not used when prohibited or unsafe
- driver licence check records
- tachograph-related records held as part of your management process
- evidence of management review where you keep it
For an O-licence review or Traffic Commissioner inquiry, the question is often whether the operator had effective systems and used them. That means your records need to show not just that documents exist, but that overdue items, defects and exceptions were noticed and acted on.
If your OCRS is under pressure, retrieval speed matters. When the office can instantly show the last PMI, the defect raised two days later, the repair order, and the return-to-service sign-off, you are in a far better position than when somebody is hunting through workshop folders.
If you operate in London with vehicles caught by the Direct Vision Standard rules, your DVS evidence needs to be easy to locate. That may include permit status and records of the equipment or arrangements supporting the vehicle’s required standard. Do not assume your planner remembers which vehicle has what fitted.
Customer audits often ask for many of the same things as regulators, plus operational proof:
- PODs
- delivery exception notes
- booking compliance
- subcontractor identity
- insurance documents
- claims history
- temperature records for specialist work
- trailer security or seal records where relevant
For operators working towards or within Earned Recognition, disciplined, retrievable data matters even more. The scheme is about demonstrable systems and performance, not a promise that software can replace management judgement.
How to choose software that fits a UK haulage operation
Choose software by walking through your actual day, from first allocation to final invoice. If the supplier only shows dashboards and not the hard bits, keep looking.
Start with planning. Can the office allocate by vehicle, trailer and driver in one view? Can it cope with trunking, multidrop, traction-only work, swap bodies, or trailer changes? Can it separate your own fleet from subcontracted work clearly?
Check compliance handling. Can it store and retrieve PMI records by vehicle and trailer? Can it flag due dates sensibly? Can it hold defect reports and rectification history in a way a transport manager can review? If you run both HGV and PSV work, can it distinguish the records and workflows properly?
Ask about geography and legal structure. If you operate in Great Britain only, that may be straightforward. If you also operate in Northern Ireland, ask how depots, fleets and records are separated or shared, and whether the product fits the way your operation is licensed and managed. Where rules differ from the EU generally, your system should reflect the UK operating reality rather than generic “European transport” settings.
Look at evidence retrieval. Ask the supplier to show you this exact task: “Vehicle AB12 CDE had a roadside issue last month. Show me the last PMI, all defects in the previous six weeks, the repair action, and whether it was allocated to work while awaiting repair.” If they cannot show that quickly, the system may not suit a real traffic office.
Check subcontractor control. Can you record who carried the load, on what terms, with what document checks? Can you search by subcontractor, job, date and customer? If not, you will still end up in spreadsheets.
Review POD and invoice flow. If your accounts package is QuickBooks, ask exactly what passes across:
- customer name
- invoice lines
- references
- VAT treatment
- surcharge lines
- credit notes
- payment status, if relevant
Also ask what does not pass across. That answer matters just as much.
For the traffic desk, little practical details often decide whether the system works:
- can planners see unallocated work clearly
- can they spot trailer clashes
- can they record booking reference numbers
- can they attach customer instructions
- can they search by reg, trailer number, job number or customer PO
- can they export records for an audit without a long support call
Finally, test adoption honestly. Put a planner, a transport manager and someone from accounts in the demo. Ask each of them to do their own tasks. If the planner hates it, the board will come back. If the transport manager cannot review PMIs and defects properly, your compliance risk remains. If accounts still has to retype everything into QuickBooks, you have only moved the bottleneck.
To replace whiteboard and spreadsheets in a traffic office properly, you do not need a grand transformation project. You need a system that matches the real work of a UK haulage operation, and a staged move that keeps control of jobs, maintenance and proof. If you can plan the day, see the risks, and retrieve the evidence when DVSA, a customer or the Traffic Commissioner asks, you are on the right track.