Where drivers apply should feed the desk

A driver finds your vacancy on your website, fills in a form, and hits send. Somewhere on the desk a CV lands. Then the real work starts: chase the licence scan, ask for Right to Work again, dig for CPC, and hope someone files the DVLA check where the next person will find it.

The application worked. The pipeline did not.

For UK HGV and industrial agencies, that gap is ordinary. A job board that only collects interest is still an inbox with better branding.

Interest is not a worker record

Drivers already look for work on agency sites. An embeddable board on the website you already run is the right front door. The failure is what happens after the click.

If the form only captures a name, a number, and a CV, you have a lead — not someone you can place. Licence categories, CPC and tachograph dates, DVLA check status, and Right to Work still live somewhere else. Someone has to re-ask for documents that should have landed with the application. Someone else has to type the same facts into a CRM, a spreadsheet, or both.

That is not recruitment. That is transcription with a deadline.

Generic boards and website plugins make this easy to accept. They are good at listings and applications. They are poor at becoming the first stage of a desk that needs compliance on the worker before anyone asks "who's free". So the board stays pretty, and the paperwork stays in email.

Registration is the stage most tools skip

On a real desk, registration is where a candidate becomes usable. It is where licence and Right to Work documents are uploaded, reviewed, and tied to a person — not left hanging in a thread titled "docs as discussed".

Without that stage inside the same system as the board, every new applicant creates a second project: chase, download, rename, file, update a tracker. Under pressure the chase gets abbreviated. Status gets guessed. The worker record stays thin while the shared drive grows fat.

Consultant-configured CRM rarely fixes this either. Someone can add an "application" object and a document folder. The board still sits outside. Staff still copy fields by hand. Six months later the process note says "upload licence at registration" and the habit says "we'll sort documents when we place them". By then you have candidates without compliance, and compliance without a clean link back to how they arrived.

What a connected front door looks like

The front of the pipeline should do one useful thing: turn an application into a record the rest of the desk can trust.

That means the board feeds registration, not a separate inbox. Candidates apply where they already look for work, and upload licence and Right to Work documents as part of that flow. Your team reviews DVLA and RTW status in one place — no scavenger hunt to answer whether the paperwork even arrived. Worker management then carries licence categories, CPC and tachograph expiry, and check status on the same person, ready for a client's job.

Clients and jobs stay on their own side of the ledger. Scheduling only starts to mean something once the person coming off registration is more than a CV. PAYE and umbrella still matter at placement time. None of that helps if the first stage never captured the documents that decide whether someone can go out.

One system is not six logins. It is so nothing useful gets typed in twice between "applied on the site" and "on the worker record".

What we're building at Haulbase

Haulbase is recruitment software for UK HGV and industrial agencies — pre-configured from job board to placement, so the place drivers apply is the same system that holds compliance, clients, jobs, and scheduling.

At launch that includes an embeddable job board, registration, worker, client, and job management, plus scheduling and placement tracking. DVLA and Right to Work status are tracked manually on the worker, with documents uploaded and reviewed in one place. Automated DVLA licence check API integration, automated Right to Work identity verification, and payroll or umbrella company integrations come later.

We would rather ship a front door that feeds the desk honestly than pretend the automations are finished when they are not. Manual status on one record, fed by registration instead of email, is still a cleaner Monday than a pretty board and a paperwork chase.

Built with real agency back-office experience — ten years of watching good applicants stall because the CV arrived and the documents did not, or arrived somewhere only one person could find. Still pre-launch. If you're on the waitlist, thanks — more soon.

The vacancy was never the hard part

You will still need drivers to find you. You will still need to check them. What you should not need is a human bridge between your website and the worker file every time someone applies.

If applications still land as CVs while licence and Right to Work chase follows by email, you're the reason we're building Haulbase.