Driver compliance belongs on the worker record

You open a worker's file to place them. The name is right. The phone number is right. Everything that decides whether they can actually go out today is somewhere else.

CPC expiry is in a spreadsheet last touched in March. The DVLA check is a PDF in an email thread. Right to Work documents are in a shared drive folder named after last year's temp. Someone on the desk knows where each piece lives. That is not the same as the system knowing.

For UK HGV and industrial agencies, this is ordinary. It is also how renewals get missed and how Mondays turn into scavenger hunts.

Compliance is not a side task. It is the gate.

A candidate is not available because they exist in your database. They are available when the desk can see that the licence categories match the job, CPC and tachograph cards are current, the DVLA check status is known, and Right to Work is valid with a renewal date you can trust.

Those facts belong next to the person — on the worker record — not adjacent to the process in tools that never talk to each other.

When compliance lives in three places, every placement starts with reconstruction. Who checked them last? Where is the document? Is the date on the spreadsheet still true? The consultant doing the placement becomes a filing clerk before they become a placer. Under pressure, people skip a step or trust a memory. That is how risk enters a desk that already works hard at getting it right.

Auditors and clients do not care that your team "knows where everything is". They care that you can show a clean trail without opening three systems and hoping the last update was typed in.

How it drifts out of the record

It rarely starts as a deliberate design. Someone downloads a DVLA check and leaves it in email because that was fastest. Someone builds a CPC tracker in Excel because the CRM only had a generic "document" field. Right to Work renewals end up in a calendar reminder owned by one person.

Each workaround is rational on the day it appears. Together they create a second compliance system that sits beside your recruitment tools instead of inside them.

Generic software makes this worse. Candidate tags are not licence categories. A document folder is not DVLA status on the worker. A notes field is not a renewal date you can sort and act on. You can bolt custom fields onto a CRM until it vaguely looks right — then watch the real status drift back into inboxes the first busy week the process feels awkward.

PAYE and umbrella placements suffer the same split when commercial detail lives in one place and compliance in another. The worker is one person. The desk should not need three sources of truth to say whether they can be put on a shift.

What "on the record" actually means

On the worker record means licence categories in plain view — not tags invented because "candidate type" was too vague. Driver CPC and tachograph card expiry sit beside the licence. DVLA licence check status is recorded against the worker, not buried in a document folder. Right to Work status and renewal dates are visible without hunting through email.

Documents still matter. Status matters more when you are deciding who can go out this afternoon. A PDF without a clear status on the record is just another file to reopen. A status without the document behind it is a claim you cannot defend. Both belong together, on one person.

That is also how the rest of the pipeline stays honest. Registration is where candidates upload licence and Right to Work documents. Worker management is where compliance status lives. Scheduling only makes sense when "available" means compliant and free — not merely listed on a whiteboard.

What we're building at Haulbase

Haulbase is recruitment software for UK HGV and industrial agencies — built so driver compliance sits on the worker from day one, inside the same system as jobs, clients, and placements.

At launch that includes the job board through to scheduling and placement tracking, with manual DVLA and Right to Work status tracking and document upload on the worker. You review status in one place. You do not chase paperwork across inboxes to answer a basic question.

Automated DVLA licence check API integration and automated Right to Work identity verification come later, along with payroll and umbrella integrations. Manual status on the record is not the finished story of automation — it is the honest foundation. We would rather ship a single place for the truth than pretend the APIs are live when they are not.

The point is not prettier folders. It is so a compliant worker becoming available for a placement does not require reconstructing their file from three tools. Built with real agency back-office experience — the kind that knows where compliance actually goes missing on a busy desk.

One record, fewer chases

Drivers will still need checks. Documents will still expire. What you should not need is a separate archaeology project every time someone asks who can cover nights.

If your compliance still lives next to the worker instead of on them, you're the reason we're building Haulbase.