Fleeta Limited: fleet technology with a real workshop foundation
+44 (0) 1284 844114
← Back to all articles

Brake test records that stand up at a DVSA visit

A practical guide to keeping rolling brake test records for an O-licence fleet, with DVSA-ready filing, links to PMI, and common mistakes to avoid.

Brake test records that stand up at a DVSA visit

If DVSA call in, the question is not whether you do brake testing. It is whether you can prove control. A pile of printed roller sheets in a drawer is not control. Nor is a workshop system that stores results nobody can match to a vehicle, a PMI, a repair, or a decision to return the unit to service.

For an O-licence fleet, managing rolling brake test records properly means each result can be found quickly, understood without guesswork, and tied back to the maintenance history. That is what shows roadworthiness is being managed, not assumed. It also matters long before a visit. Good records help you catch declining performance, justify repair decisions, and avoid arguments after a fail at MOT or a roadside encounter.

What records does a DVSA examiner expect to see?

A DVSA examiner will usually want to see the maintenance story, not one isolated document. For brakes, that means evidence of testing, evidence of review, and evidence of action where the result showed a problem.

At a minimum, we expect an O-licence fleet to be able to produce:

  • Rolling brake test reports for the vehicle or trailer
  • The related PMI record
  • Any driver defect reports that mention braking performance, warning lights, pulling, noise, imbalance, or parking brake concerns
  • Job cards or workshop repair records for brake work
  • Evidence of any re-test after adjustment or repair
  • MOT history where that helps explain timing or findings

If you use laden roller brake testing as part of your maintenance regime, those records should be there too. If you only have unladen tests, the paperwork still needs to show they were reviewed in context. A pass printout on its own is weak if the brake efforts are marginal, imbalance is high, or previous records showed a drop that nobody followed up.

The examiner is looking for whether your maintenance system is effective. That is the word behind a lot of DVSA conversations. Not tidy. Effective. Can you show that brake performance is being checked at suitable intervals, that poor results trigger action, and that the vehicle was not left in service with a known issue?

For UK operators, this sits inside the wider O-licence duty to keep vehicles fit and serviceable. The EU may use different regulatory structures and inspection language, but for a UK operator the practical test is simple. Could you put the records on a desk and show a clear chain from test, to judgement, to repair, to return to service?

That is also why brake records affect OCRS. Poor roadworthiness outcomes, prohibitions, and weak maintenance control all feed the picture of how your fleet is seen. Good paperwork will not rescue a bad vehicle at the roadside, but poor paperwork can make a manageable issue look like a system failure.

Where fleets come unstuck is treating brake testing as a separate workshop event. It is not separate. It is part of the roadworthiness record. We cover the same point on the workshop side in our guide to brake roller testing and what customers should expect. The result only becomes useful when it is anchored to the rest of the maintenance file.

What to capture on every rolling brake test record?

A usable brake record needs more than the printed figures from the machine. The machine output matters, but so does the context around it. If that context is missing, you end up with a sheet that proves a test happened but not much else.

On every rolling brake test record, we recommend capturing these fields as standard:

  • Vehicle registration
  • Fleet number, if you use one
  • Trailer registration or trailer number where relevant
  • VIN or chassis number if there is any risk of duplicate or misread identity
  • Test date
  • Odometer reading, or hubodometer reading for trailers where you record one
  • Test location
  • Name of technician who carried out the test
  • Whether the test was laden or unladen
  • Axle by axle service brake results
  • Parking brake result
  • Brake imbalance figures where shown
  • Brake efficiency figure, if the machine provides it
  • Any advisory notes from the tester
  • A clear pass, fail, or pass with repair required before release status
  • Link or reference to the related PMI or workshop job

That last point is where many fleets are weak. The roller printout often sits in one system and the PMI sheet in another. Then, six months later, nobody can prove which inspection the test belonged to.

You also need to record enough detail to explain odd results. For example:

  • Vehicle presented unladen
  • Trailer tested without load simulator
  • ABS warning lamp on at presentation
  • Nearside rear brake binding before test
  • Re-test carried out after slack adjuster set
  • Parking brake tested after chamber replacement

Those notes matter because raw numbers can mislead when read cold at audit time. A weak first result followed by a satisfactory re-test is fine, if the records show what happened in between. A weak first result with no explanation looks like a vehicle may have gone back out without proper control.

Be careful with handwritten additions to printed roller sheets. They are often necessary, but they need to be legible and attributable. We prefer a typed digital record attached to the machine output, with the technician and reviewer both identified. If you are handwriting, use the same format every time and make sure the person adding the note can be identified.

Dates and times matter too. If the brake test was done during a preventative maintenance inspection, the record should line up with the PMI date. If the vehicle failed in the morning and was repaired in the afternoon, the repair record and re-test should reflect that sequence. When dates do not line up, DVSA start asking whether the paperwork was built after the event.

If you are working out how to manage rolling brake test records for an O-licence fleet, the practical answer is consistency first. Decide your required fields. Make them mandatory. Do not let a test be closed without them.

How to link brake tests to PMI, defects and repairs

This is where a decent maintenance process earns its keep. A brake test record should not live on its own. It should sit inside a chain that starts with routine inspection or reported concern, moves through diagnosis and repair, and ends with a documented decision that the vehicle is fit for service.

The cleanest link is between the brake test and the PMI. If a roller brake test is part of the inspection, the PMI sheet should carry the brake test reference number, and the brake record should carry the PMI number. One clicks to the other, or one paper file contains both in order. Either works. What does not work is saying, "It will be somewhere in the system."

Where a driver defect report has triggered the work, that needs linking too. If a driver reported poor braking, pulling to one side, excessive pedal travel, a warning lamp, or a parking brake concern, the defect report should show:

  • Date and time reported
  • Vehicle or trailer identity
  • Exact wording of the defect
  • Decision taken, including whether the vehicle was stopped
  • Job reference for investigation and repair

Then the workshop job should show what was found and what was done. "Checked brakes" is not enough. Better entries are specific:

  • NSR brake chamber leaking, replaced
  • Offside front pads below limit, renewed both sides
  • Trailer axle 3 service brake imbalance traced to seized caliper slides, freed and lubricated, pads replaced
  • Parking brake travel excessive, adjusted and re-tested

After that, the re-test record completes the chain. Without the re-test, you have evidence of repair but not evidence of restored performance.

This matters just as much for recurring issues. If the same trailer shows marginal or uneven results over several inspections, you want that pattern visible. Otherwise each event gets treated as isolated, and the underlying problem keeps coming back. Good records let you spot the repeat offender, whether that is a particular trailer, axle type, component brand, or maintenance gap.

The same principle applies around MOT. If a vehicle fails on brake performance at annual test, your records should help you answer two uncomfortable questions. Was there warning in the previous PMI and brake test history? And what changed between the last satisfactory inspection and the MOT failure? If your paperwork can answer that honestly, you are in a much safer position.

We have written separately about keeping driver defect reports under control on an O-licence and recording HGV repairs without risking your O-licence. The point in both is the same. Records need joining up. Brake testing is one part of that bigger maintenance picture.

Do not forget trailers. In many fleets, trailer brake records are the first to go adrift because trailers move around, odometer readings are less consistent, and responsibility gets blurred between yard, workshop and transport office. That is exactly why the trailer identity and inspection link need to be watertight.

How to file records so they are usable at audit time

Audit time is when bad filing habits become expensive. Not because the records never existed, but because nobody can retrieve them quickly enough to show control.

For a small or mid-sized fleet, we recommend filing brake test records by asset, then by date, with a fixed naming convention. Whether you keep them digitally or on paper, the structure should let anyone sensible find the last inspection history for a given unit without asking the person who set the system up.

A practical digital naming format is:

VehicleReg_or_TrailerNumber_YYYY-MM-DD_BrakeTest_PMIRef

For example:

AB12CDE_2026-03-14_BrakeTest_PMI2478

That gives you identity, date and cross-reference in one line. Avoid filenames like scan001 or brake test March. Those are useless once the folder gets busy.

Our preference is one master vehicle file per unit, with sections for:

  • Vehicle details
  • PMI records
  • Brake test records
  • Defect reports
  • Repair history
  • MOT and test history
  • tachograph calibration and related compliance documents, where you keep the full vehicle record together

You can keep separate document types in the system, but the retrieval view should still be by vehicle or trailer. When DVSA ask for six months of maintenance history on one unit, they do not want a lecture about your folder structure.

If you are paper based, the same principle applies. One binder or file per asset, documents in date order, oldest to newest or newest to oldest, but choose one and stick to it. Loose thermal printouts from brake rollers should be copied or scanned. They fade. We see this regularly. A faded brake ticket six months later is as good as missing.

Access control matters as well. Too many people editing records creates its own mess. We normally advise that technicians can create and attach records, but sign-off or closure sits with a workshop controller, fleet engineer, or transport manager. Someone needs to own the final check that the brake test, PMI and repair trail all match.

Retention needs some discipline too. Keep records long enough to show maintenance history and support any question that lands later. Different document types may have different practical retention needs, but for O-licence maintenance records the real point is not to purge anything that explains roadworthiness decisions while the vehicle is in fleet and for a sensible period afterwards.

Searchability is the difference between storage and control. If you cannot pull all brake tests for one trailer, or all brake failures across the fleet, you are not really managing the records. You are archiving them. That is one reason many operators move away from shared drives and spreadsheets once the fleet grows. We covered the wider issue in our piece on choosing maintenance records software for your O-licence.

Common brake test record mistakes that cause trouble

The first common mistake is treating a brake test as complete because the machine printed something. A printout is not a reviewed record. If nobody has checked whether the result was acceptable in context, the process is only half done.

The second is missing identity. We still see roller sheets with no clear registration, trailer number, or PMI reference. Once that sheet is separated from the job, it becomes almost worthless.

The third is no evidence of action after a poor result. If the test shows imbalance, low effort, or a parking brake issue, there should be a repair record and usually a re-test. If there is not, DVSA are entitled to ask whether the vehicle went back into service unchecked.

The fourth is mismatch between documents. Typical examples are:

  • Brake test dated after the PMI it is supposed to support
  • Repair dated before the defect was reported
  • MOT fail for brakes with no corresponding workshop activity
  • Trailer number on the brake test not matching the trailer inspection sheet

Some mismatches are innocent admin errors. The problem is that repeated errors make the whole maintenance system look unreliable.

Another common issue is keeping only the latest result. That loses trend history. A single pass can hide a slow decline over several inspections. Trend matters. If axle efficiency has been dropping for three PMIs, we want to see that somebody noticed.

Watch out as well for vague workshop language. "Brakes adjusted" is weak. Which axle? What was adjusted? Why was it needed? Was there wear, seizure, contamination, air leak, or poor balance? The record does not need to be a novel, but it does need to mean something six months later.

Unclear release decisions cause trouble too. If a vehicle failed the first test and passed the second, the file should make clear that it was not returned to service in between unless that was justified and documented. This is where timestamps and job status matter.

Then there is the problem of split responsibility. The workshop has the roller tickets. The transport office has the PMI planner. Drivers send defects by text message. Nobody owns the complete file. That setup almost guarantees gaps. One person, or one controlled system, needs to hold the joined-up record.

Finally, do not ignore presentation. We are not talking about pretty reports. We mean records that can be followed by another human being. If a DVSA examiner or a Traffic Commissioner has to work hard to understand your brake history, you have already made life harder for yourself.

The fleets that handle this well are not necessarily the biggest. They are the ones that make the record part of the job, not an afterthought. Every brake test has an owner. Every poor result has a next step. Every document can be found. That is how to manage rolling brake test records for an O-licence fleet in a way that stands up when somebody asks to see them.

Do I need a rolling brake test result at every PMI?

Use current DVSA guidance and your maintenance arrangements. What matters is that brake performance is assessed properly, recorded clearly and supported by a system you can justify for the fleet.

How long should I keep brake test records?

Keep them in line with current DVSA expectations for maintenance records under the operator licensing regime. Do not guess. Your system should make older records easy to retrieve if asked.

Can I keep brake test records digitally?

Yes, if they are complete, legible, secure and easy to produce. A digital record is only as good as the filing behind it. If you cannot find it quickly, it may as well not exist.

Should brake test records be attached to the PMI sheet?

They should at least be clearly linked. That can be by attachment, reference number or shared vehicle history. The point is to show one joined-up maintenance story, not separate piles of paper.

What if a brake test shows a poor result?

Record the result, the diagnosis, the repair and the retest. A bad result is not the main problem. Failing to show what you did about it is usually what causes concern.