Section 172 Notices: The Legal Duty to Name the Driver - and the Offence of Not Answering

Every speeding ticket, red-light allegation and camera-detected offence aimed at a fleet vehicle arrives with a legal question attached: who was driving? The mechanism that forces the answer is section 172 of the Road Traffic Act 1988, and it is one of the most consequential pieces of routine law a transport office handles. Get it right and it is admin. Get it wrong - ignore it, answer it late, answer it vaguely - and the company or its officers can end up convicted of an offence more damaging than the original speeding allegation.

What section 172 requires

Where the driver of a vehicle is alleged to be guilty of an offence to which the section applies, the person keeping the vehicle shall give such information as to the identity of the driver as they may be required to give by or on behalf of a chief officer of police. Failing to comply with that requirement is itself an offence.

Two features do the heavy lifting. First, the duty falls on the keeper - for fleet vehicles, that is the company, not whichever individual opens the post. Second, the obligation is to give the information, not to try fairly hard. The law places the burden of knowing who drove your vehicle on the keeper, and it enforces that burden by making non-compliance a separate offence, commonly punished more harshly than the underlying traffic offence - typically carrying its own penalty points and a fine, and for companies, fines and the reputational cascade that follows a conviction for obstruction-flavoured offending.

Why fleets fail at it

The failure modes are drearily consistent:

• The unrecorded pool. Several drivers could have had the van that day, nobody’s allocation was written down, and the honest answer “we don’t know” is not a defence the courts accept from an organisation expected to keep records.
• The late letter. The notice goes to a registered office that forwards post weekly, or to a keeper address that is out of date, and the response deadline - notices run on tight statutory timescales - expires before anyone reads it.
• The half-answer. A reply naming “probably Dave” without the required particulars, or a nomination sent without the nominated driver’s details, treated as non-compliance.
• The hopeful silence. Hoping it goes away. It does not go away; it goes to court.

Each failure converts a 3-point speeding matter for one driver into a section 172 conviction for the company - and, where the company’s systems are shown to be casual, into a pattern that prosecutors and courts treat as deliberate.

The duty also reaches further than the keeper alone - the section extends to requiring information from others where the law provides, and company officers can find themselves answerable where a corporate keeper’s failure reflects their own neglect. ## The systems answer

Section 172 compliance is entirely a records-and-process question:

1. Driver allocation as a daily record. Every vehicle movement has a named driver, recorded contemporaneously - telematics logins, allocation sheets, key-control registers. The standard is: for any vehicle, any date, any time, you can answer “who was driving” from records, not memory.
2. Keeper details current. The registered office and correspondence address on the V5C must be where post is read daily. A notice that arrives late because the address was wrong is not late in law’s eyes.
3. A named owner of the process. One role opens camera-related post, logs the notice, pulls the allocation record, completes the nomination accurately, and diarises the deadline. The reply goes back with the driver’s full correct details, on time, every time.
4. Honesty in the hard cases. If records genuinely fail to identify the driver, the right response is to demonstrate the records system and its diligence - not to nominate someone convenient. A false nomination is perverting the course of justice territory, a different universe of trouble from a traffic offence.
5. Agency and subcontract cover. The allocation record must extend to agency drivers and any subcontract use; “it was the agency’s driver” is the beginning of the answer, not the end, and your records should hold the name.

The compliance-culture point

Courts see section 172 failures from two kinds of keepers: the disorganised and the evasive. Neither plays well, and for O-licence holders both feed the wider picture of how the business is run. A transport operation that cannot say who was driving its vehicles has a deeper problem than any single notice - and the authorities reading the file know it. The fix is boring and total: allocation records, current addresses, a named responder, honest answers.

Sources

• Road Traffic Act 1988, section 172 - legislation.gov.uk