Skip to content
OperatorCompliance
Free trial
← All articles

· 12 min read

Agency driver records and CPC tracking in one system

A practical comparison of agency driver records and Driver CPC tracking, including checks, evidence, deadlines and operator-licence risk.

Agency driver records and CPC tracking in one system

Using agency drivers does not move operator-licence responsibility away from us. The agency may recruit, vet and supply the driver, but we still need to know that the person driving our vehicle has the right entitlement, valid Driver CPC where it applies, and a record trail we can show to DVSA or a Traffic Commissioner. If those checks sit in email chains, agency portals and spreadsheets, gaps appear quickly.

That is why many operators want driver agency licence and CPC tracking in one place. The practical need is simple. We should be able to see who drove for us, what was checked, when it was checked, what evidence was held, and when each item is due again, alongside the rest of our compliance records for vehicles, trailers and tachographs.

What operators need to control when using agency drivers

When we use temporary labour, there is a tendency to assume the agency has “done the compliance”. In practice, some checks may be carried out by the agency, but the operator still needs its own control process. That matters whether we run HGVs, PSVs, vans, or a mixed fleet.

For agency drivers, we need to control at least five things.

First, identity and right to drive the vehicle we are assigning. That means confirming the driver is the person they claim to be and that their licence entitlement matches the class of vehicle and use. For goods vehicles, that may mean checking the relevant LGV categories. For bus and coach work, the PSV entitlement must be correct for the duty. If the role involves towing, we also need to consider trailer entitlement.

Second, Driver CPC status where the work requires it. A valid vocational entitlement on its own is not enough if the driver also needs current Driver CPC. We need to know whether the driver holds a valid DQC, when it expires, and whether any booking creates a risk of the card expiring mid-assignment.

Third, working time and tachograph readiness. If the driver will be using a tachograph, we need their driver card details, any declarations needed for missing mileage or other work, and a process for obtaining downloads and infringement analysis. Agency status does not remove our duty to manage drivers’ hours risks in our operation.

Fourth, induction and local controls. Agency drivers still need site rules, defect reporting instructions, load security expectations, accident reporting, walkaround check procedures and any route or customer-specific requirements. A signed induction record matters. We cover this in more detail in our guidance on using agency drivers compliantly and on driver induction and handbook records.

Fifth, recheck dates and exceptions. One clean licence check at the start does not solve the whole issue. Endorsements can appear later. A DQC can expire. A medical issue can affect entitlement. If we use the same temporary driver repeatedly, we need the same discipline we would apply to a permanent employee.

For UK operators, this sits within the wider operator-licence duty to run safely and compliantly. That includes keeping our driver records organised and available. If a DVSA visit happens, “the agency has that” is not a strong answer if we cannot promptly show what we checked before putting the driver on the road.

How agency licence checks differ from Driver CPC tracking

Licence checks and Driver CPC tracking are related, but they are not the same task.

A licence check is about legal entitlement to drive. In the UK, that usually means checking the driver’s details against the DVLA record, reviewing the categories held, expiry dates, endorsements, disqualifications and any restrictions relevant to the work. For vocational drivers, we also need to consider whether the licence itself remains valid in light of age and medical requirements. If we rely on agency labour, we should be clear whether we are accepting the agency’s report, running our own DVLA check, or doing both. Our article on driver licence checks for operators sets out the operator side of that process.

Driver CPC tracking is different. Driver CPC is a professional qualification requirement for many vocational drivers, and the evidence is the DQC. A driver can hold the correct vocational entitlement on the licence but still be unable to carry out in-scope work if their Driver CPC has lapsed. Equally, a valid DQC does not tell us anything about endorsements, disqualification or entitlement categories on the licence.

That is why the records need separate fields and separate review dates.

For licence checks, the recheck schedule is usually risk-based. A driver with points or recent changes may need checking more often than a driver with a stable record. Many operators set a standard recheck cycle, then shorten it for higher-risk cases. Agency drivers who work only once may need a check before each booking. Agency drivers who work every week may fit into a scheduled review cycle, but only if we can evidence that process.

For Driver CPC, the key control is the DQC expiry date and any evidence of periodic training completion if the replacement card is pending. In day-to-day operation, we want a record of the card number if held, the expiry date, and who verified it. We also need alerts well in advance. If a card expires tomorrow, the booking team needs to know before the shift is assigned, not after the vehicle has left the yard.

There is also a practical difference in evidence. A licence check may produce a DVLA result, a check code record, or a report from a connected checking service. Driver CPC tracking may rely on a scanned DQC, a verified expiry date, or another documented proof route accepted in our process. These should not be stored as one generic “driver document”. They should be categorised so anyone reviewing the file can see exactly what was checked.

Where rules differ between the UK and the EU generally, operators need to be especially careful with cross-border assumptions. The UK regime uses DVLA records and UK Driver CPC processes. EU operators may be dealing with different national databases, card formats and renewal arrangements. If we operate in Great Britain under a UK operator-licence framework, our system should reflect UK checks first, then allow for additional evidence where an overseas driver is lawfully engaged.

Separate tools or one compliance system?

Many fleets start with a spreadsheet, a shared drive and whatever the agency emails over. That can work at very small scale, but only while the number of drivers, vehicles and deadlines remains low. Once we have regular agency cover, multiple depots, mixed vehicle types or frequent tachograph activity, separate tools create blind spots.

A spreadsheet can list names, licence dates and DQC expiry dates. What it cannot do well is prove who checked what, retain signed records in context, or show the link between a driver, a vehicle, a shift and a follow-up action. It also depends heavily on one person keeping it current. If that person is off, the process stalls.

Agency portals have a different weakness. They may show what the agency has on file, but they rarely form our full operator compliance record. They do not usually hold our induction sign-off, our tachograph exceptions, our defect reporting evidence, our internal notes on restrictions, or our reminders for rechecks across permanent and temporary labour together. They are also fragmented if we use more than one agency.

Standalone driver-check tools improve the licence-checking part, but they still leave us moving between systems. If the driver record is in one place, the vehicle inspection schedule in another, the trailer records elsewhere, and tachograph analysis in another platform again, the transport office spends time reconciling data instead of acting on it.

A single compliance system is stronger because it reflects how operators actually work. Drivers, vehicles, trailers and jobs are connected. If a temporary driver is assigned to a vehicle that is due inspection, has an unresolved defect, or sits within a tachograph process requiring downloads and analysis, we want those issues visible in one operational view.

That is the point of Operator Compliance. We built it around the record-keeping and planning that operators need under the DVSA Guide to Maintaining Roadworthiness, not as a standalone HR file. Because Fleeta Limited runs trucks under an operator licence itself, we designed the software around the way transport offices actually gather evidence, chase dates and prepare for scrutiny.

For mixed operations, that matters. A courier fleet may need van records, grey fleet controls and driver checks. A haulier may need MOT and annual-test dates, PMI records, trailer planning, VOR status and tachograph workflows. A bus and coach operator may need the same discipline across PSVs and relief drivers. If agency-driver records sit outside that structure, they are harder to use when a real compliance question arises.

Integration also matters. If we need data to move between systems, a REST API and webhooks are useful, particularly for larger operators or agencies with existing back-office tools. But integration should not be a substitute for a coherent compliance record. The core question is whether the system lets us manage the actual operator duty in one place.

What evidence should be ready for a DVSA visit or Traffic Commissioner file?

If DVSA visits, or if we need to produce a file for a Traffic Commissioner, we should be able to provide agency-driver evidence quickly and in order. That means more than a screenshot of a portal.

At minimum, we should be ready to show:

  • The driver’s full identity details as held on our system.
  • The date the driver first worked for us.
  • The licence-check result, including the date checked, who checked it, and the source of the check.
  • The entitlement categories relevant to the work assigned.
  • Any endorsements, restrictions or notes, and the decision taken about suitability.
  • The Driver CPC record, including DQC evidence and expiry date.
  • Recheck dates for both licence and Driver CPC.
  • Signed induction records, handbook issue if used, and local policy acknowledgements.
  • Tachograph-related records where relevant, including card details, downloads, declarations and infringement follow-up.
  • Any accident, damage, defect or complaint records linked to that driver.
  • Evidence of action where a check failed, expired or raised concern.

Dates matter. Signatures matter. Version history matters. If a document was replaced, we should still be able to see what was held before and when it changed. If a recheck was missed, there should be a note showing what happened next. A proper audit trail is often the difference between a controlled process with one exception and a process that appears not to exist.

For vehicle-linked evidence, we should also be able to show which vehicle or trailer the driver used, whether the vehicle was compliant at the time, and whether any VOR period affected the booking. That is one reason a driver file on its own is not enough.

Some operators also want supporting fleet records close at hand, such as insurance verification through askMID, which is the public-facing service connected to the Motor Insurers' Bureau, also referred to as MIB. That is not a substitute for our own insurance records, but it can support quick checks in operational use. The same applies to records exported to VOL or management reports built for internal review.

Good evidence is easy to retrieve. If we need half a day to find the DQC copy, the induction form and the last licence check, the process is too fragile.

How to compare systems for mixed fleets and temporary labour

When comparing systems, start with the real operating model, not the software demo.

If we are a haulier, we should ask whether the system handles HGV drivers, trailers, MOT and annual-test planning, inspection schedules, tachograph workflows and agency-driver records in the same environment. If agency-driver data sits as an add-on with no link to the rest of the fleet, it will not help much during an audit.

If we run vans or courier fleets, we should look for strong driver controls as well as vehicle records. Van operations often use temporary labour heavily and move fast. The system should make repeat checks easy, flag expiring records clearly and cope with drivers moving between vehicles and depots.

If we are in bus and coach, we should test PSV entitlement and Driver CPC handling carefully. Relief drivers, school contracts, private hires and seasonal peaks all create pressure on rostering. We need a system that shows at a glance whether the driver is cleared for the duty.

If we are an agency managing permanent and agency drivers together, we should avoid tools that create two separate populations. The transport team needs one record standard, one audit trail and one reminder structure, even if the source of the labour differs.

Practical buying criteria are straightforward.

First, can the system store licence checks, Driver CPC evidence and DQC expiry dates as separate controlled records?

Second, can it schedule rechecks by risk, not just by one fixed interval?

Third, can it hold signed documents and show who uploaded or approved them?

Fourth, does it link drivers to vehicles, trailers and tachograph activity?

Fifth, can it produce a clear history for DVSA or a Traffic Commissioner without manual reconstruction?

Sixth, does it support mixed fleets and operational exceptions such as VOR vehicles, depot differences and temporary assignments?

Seventh, if we need integration, does it offer a proper REST API and webhooks?

Eighth, can it fit into the wider compliance stack if we also use tools such as Fleetalyse or Logivo.AI, without losing the core record inside the operator system?

Finally, look at how the software is built. OperatorCompliance is not a generic HR database with a transport label added later. We built Operator Compliance around UK operator-licence work, using the same logic transport managers use every day. That matters when the task is not just to “store documents”, but to prove that our process for driver agency licence and CPC tracking is current, consistent and tied to the rest of our fleet compliance.

The best system is the one that lets us answer simple questions immediately. Can this driver legally do this duty today? When did we last check the licence? Is the Driver CPC current? Where is the DQC evidence? What vehicle did they drive? What tachograph records follow from that? If we can answer those questions from one place, we are in control.

Does an operator need to track Driver CPC for agency drivers?

Yes. If the driver is working in your operation, you need to know they are entitled to drive and that Driver CPC requirements are being met where they apply.

Is a driving licence check the same as Driver CPC tracking?

No. A licence check confirms entitlement and endorsements. Driver CPC tracking covers periodic training status and the DQC record. Both should be checked and recorded.

Can an agency's own records be enough for compliance?

They may help, but operators should still keep their own accessible evidence, recheck dates and audit trail for the drivers they use.

What should be stored as proof of a CPC check?

Keep the check date, result, who carried it out, any supporting evidence seen, and the next review date. A clear audit trail matters as much as the status itself.

Why is one system better than spreadsheets for agency drivers?

A single system can link driver checks, expiry alerts, tachograph records and vehicle use. Spreadsheets often depend on manual updates and are harder to evidence.

Ready to stop chasing dates?

Set up in an afternoon. Keep your operator licence clean for good.

14-day free trial · no card · cancel anytime