Skip to content
OperatorCompliance
Free trial
← All articles

· 11 min read

How to check London DVS status before a PCN lands

A practical guide to checking London DVS status, finding your star rating, and keeping the records operators need before entering Greater London.

How to check London DVS status before a PCN lands

If you send HGVs into Greater London, checking DVS status before the journey is not optional admin. It is part of route planning, vehicle allocation and permit control. A quick London DVS check tells you whether a vehicle meets the required safety standard for the scheme, or whether you need to apply for the right permit before the vehicle enters the area. If you leave it until after the job is booked, you risk a Penalty Charge Notice, a failed delivery plan and a compliance trail that does not stand up well when someone asks who checked what, and when.

For most operators, the real issue is not how to do one check. It is how to do it consistently across a fleet, keep evidence of the result, and make sure permit dates, vehicle changes and route changes do not catch you out. That is where a proper process matters more than a last minute search for a London DVS checker.

What the London DVS check is for

A London DVS check is used to confirm whether a heavy goods vehicle meets the Direct Vision Standard requirements for driving in Greater London, and whether a permit is needed. The scheme applies to most HGVs over 12 tonnes gross vehicle weight that enter or operate in the Greater London area.

The purpose of the check is straightforward. Transport for London uses the Direct Vision Standard to assess how much a driver can see directly through cab windows, rather than indirectly through mirrors or camera systems. Vehicles are given a star rating. Depending on the current scheme requirement, a vehicle may either meet the standard outright or need a permit linked to additional safety equipment.

Operators usually look this up before a vehicle enters London for one of four reasons:

  1. To decide whether the planned vehicle can lawfully do the job.
  2. To confirm whether a permit is already in place and still valid.
  3. To avoid a PCN for a vehicle that should not have entered without the correct approval.
  4. To keep a record showing the transport office checked the vehicle before dispatch.

This is a London specific requirement. It is not an EU wide operator licensing rule, and there is no direct equivalent that applies in the same way across all EU member states. If you run internationally, that matters. Your operator-licence systems may already track MOT, annual-test, inspections, Driver CPC, DQC and tachograph evidence across the UK fleet, but DVS is a separate London access control issue that needs its own checks and records.

In practice, the DVS check tends to sit alongside other pre-entry checks such as LEZ, ULEZ, insurance status, and whether the vehicle is correctly taxed and specified for the job. Some operators also cross-check policy and cover details through askMID data or records sourced from the Motor Insurers' Bureau, depending on how their internal systems are set up. The point is the same, a London run should not rely on memory.

How to check a vehicle’s DVS status

The practical steps are simple, but they need to be followed in the right order.

First, identify the exact vehicle that will enter Greater London. Use the registration mark and confirm you are checking the correct unit, not a similar plate or a trailer record. DVS applies to the vehicle, not the traffic office assumption about what usually goes on that contract.

Second, confirm the vehicle’s weight category. The scheme is generally relevant to HGVs over 12 tonnes gross vehicle weight. If the vehicle is below that threshold, record that fact and move on. If it is above, continue with the DVS check.

Third, verify the vehicle’s DVS star rating or permit status. In many fleets, this information is already held against the vehicle record because it was obtained when the vehicle joined the fleet or when the permit was first applied for. If you do not already hold it, you need to check the current status using the relevant official process and match the result to the registration and vehicle details on file.

Fourth, confirm whether the vehicle meets the current London requirement as it stands, or whether it needs a safety permit. A vehicle may be compliant because its star rating is high enough, or compliant because it has the required permit in place based on its specification and fitted equipment. Those are not the same thing, and your records should show which applies.

Fifth, check dates. A permit that existed last year is not enough information on its own. Before dispatch, confirm whether the permit is active for the relevant date of travel and whether any supporting equipment or conditions attached to that permit are still in place on the vehicle.

Sixth, record the result internally. At minimum, note the date checked, who checked it, the source used, the outcome, and any expiry or review date. If the vehicle is not compliant, add the action taken, such as vehicle reallocation or permit application.

If you want to tighten the process, build the DVS check into the same workflow as route planning and dispatch sign-off. A London booking should not be released until the vehicle record shows a satisfactory result. We cover the route planning side in our guide to using the DVS map for safer London route planning, and the dispatch side in our article on checking DVS status before a London delivery.

What documents and details you should have ready

A DVS check is quicker when the vehicle file is complete. The transport office should have the following details ready before checking status or applying for any permit.

Start with the core vehicle identifiers:

  • registration mark
  • make and model
  • gross vehicle weight
  • VIN or chassis number
  • fleet number, if you use one internally
  • operator licence disc details or internal allocation reference

You should also have the vehicle’s current compliance record to hand, including:

  • whether the vehicle is active, off road, sold, hired in or hired out
  • whether the vehicle is currently VOR
  • the depot or operating centre it is allocated to
  • the usual traffic area or contract allocation
  • any previous DVS permit reference and expiry date
  • evidence of any additional safety equipment fitted to the vehicle

For audit purposes, keep copies or references to the documents that support the DVS position. Depending on the vehicle and its status, that might include permit confirmations, manufacturer information, internal fitment records, workshop sign-off for safety equipment, and dated photographs if you use them as part of your evidence trail.

If you are running a mixed fleet, it also helps to record vehicle type and body type clearly. A rigid on multidrop work, an artic on trunking, and a specialist vehicle entering London only occasionally may need different planning rules even if all are over 12 tonnes. The DVS result alone is not the whole operational picture.

Internally, we recommend keeping a standard record for each check. A good entry should capture:

  • vehicle registration
  • date and time checked
  • name of the person who checked it
  • source of the information
  • compliance result
  • permit number or reference if relevant
  • expiry or review date
  • follow-up action, if any

That record matters if there is later a dispute about a PCN, or if the Traffic Commissioner ever wants to see whether your systems are controlled or ad hoc. It also helps when the transport manager is off and someone else has to pick up the desk without relying on memory or email trails.

Where possible, keep DVS records in the same system as the rest of your operator-licence evidence. If MOT bookings, annual-test dates, inspection sheets, defect reporting, driver licence checks, Driver CPC dates and DQC records all sit in one place, DVS should not be buried in a separate spreadsheet on one planner’s desktop.

What to do if a vehicle does not meet the requirement

If a vehicle does not meet the London DVS requirement, the first step is not to send it and hope for the best. Stop the allocation and decide which operational option is actually available.

The main options are usually these.

Reallocate the job to a compliant vehicle. This is often the cleanest answer if you have another unit with the required star rating or a valid permit. Record the change against the booking and note why the original vehicle was removed from the job.

Apply for the appropriate permit if the vehicle is eligible. This needs planning. Do not assume a permit can be sorted at the point the vehicle is due through the gate. Check what supporting evidence is needed, make sure the vehicle specification matches the application, and keep the approval on file once issued.

Reschedule the work if neither of the first two options is available. That may mean changing delivery dates, splitting loads, or arranging a compliant subcontractor for the London leg. If you subcontract, keep evidence of the subcontractor’s DVS position as part of the job file.

Restrict the vehicle from London work until the record is corrected. In practice, many operators flag the vehicle in the fleet system so it cannot be selected for Greater London jobs without management override.

This is also the point to review whether the problem is one vehicle or a process failure. If a non-compliant vehicle reached the dispatch stage, ask:

  • was the DVS status missing from the vehicle record?
  • was the permit expired?
  • was the wrong vehicle allocated at short notice?
  • did a planner assume the vehicle was covered because a similar unit was?
  • was the supporting equipment removed, changed or not evidenced?

Those questions matter because a one-off error can become a pattern very quickly in busy traffic offices.

Keep a record of the decision taken. If the vehicle was stood down, note the date and reason. If the job moved to another unit, record the replacement registration. If a permit application is in progress, set a follow-up date and hold the vehicle out of London allocation until the result is confirmed. This is the same discipline operators already apply to VOR control, inspection intervals and annual-test bookings. DVS should be managed with the same level of care.

How to manage DVS checks across a fleet

The difficulty with DVS is not the individual check. It is controlling hundreds of moving parts across vehicles, depots, contracts and planners. A spreadsheet can work for a very small fleet, but it becomes fragile as soon as vehicles are replaced, permits expire, work is subcontracted, or someone is away from the office.

A better approach is to manage DVS status as part of the live fleet record.

For each vehicle, keep a single record that includes its weight category, London DVS status, permit reference, issue date, expiry or review date, and any evidence attached to that status. If the vehicle changes ownership, body, operating centre or contract type, the DVS record should be reviewed as part of the same change process.

You should also be able to filter the fleet by status. For example:

  • vehicles compliant for London use
  • vehicles requiring permit renewal
  • vehicles not to be allocated to Greater London work
  • vehicles awaiting evidence or application outcome
  • vehicles currently VOR but normally used for London runs

That makes daily planning easier and reduces the risk of the wrong unit being selected under pressure.

Alerts matter as well. Permit dates should not sit silently in the background until a PCN arrives. Set reminders in advance, in the same way you would for MOT, annual-test, inspections, insurance and Driver CPC deadlines. If your fleet system can trigger tasks, assign responsibility to a named person and make completion visible.

At Operator Compliance, this is exactly why we keep vehicle compliance in one place rather than scattering it across email folders, spreadsheets and paper files. A transport manager needs to see the vehicle record, the document trail and the deadline position together. That is especially important where the same system is already being used for DVSA aligned maintenance records, defect evidence, tachograph analysis and Traffic Commissioner file preparation.

For larger fleets, integration also matters. If you are feeding vehicle data from another system, or pushing compliance status into planning or telematics tools, structured data is more reliable than manual rekeying. That is where tools such as a REST API and webhooks become useful, because they let systems pass changes automatically rather than relying on someone to update multiple records by hand. Some operators also bring in related fleet data from platforms such as Fleetalyse or Logivo.AI, but the key point is that DVS status needs a clear owner and a controlled source of truth.

We built OperatorCompliance through Fleeta Limited around real operator needs, including the kind of record keeping expected under the DVSA Guide to Maintaining Roadworthiness. DVS is not a maintenance interval, but the management principle is the same. If a requirement affects whether a vehicle can legally do the work, the status, evidence and dates should be visible, auditable and easy to act on.

If you are still managing London access checks manually, start with a simple rule. No vehicle goes into Greater London until its DVS position is confirmed and recorded. Once that rule is embedded, the next step is to make the process repeatable across the whole fleet, so the answer is already in the vehicle record before the traffic desk needs it.

What does a London DVS checker do?

It helps an operator confirm whether an HGV meets the London Direct Vision Standard requirement or needs a permit before entering the area.

Does DVS apply to every commercial vehicle?

No. Operators should check the current London rules carefully, because DVS is aimed at specific vehicle types rather than every van, car or minibus.

Can I rely on a driver to check DVS status?

The transport office should control it. Drivers may report issues, but operators need a clear record showing the vehicle was checked and allocated correctly.

What records should I keep after a DVS check?

Keep the vehicle identity, the result, any permit details, relevant dates and who checked it. Store it with the rest of the vehicle compliance file.

Is a DVS check the same as MOT or annual-test compliance?

No. DVS is separate from MOT or annual-test obligations. Operators need to manage all of them together so a road-legal vehicle is also scheme-compliant.

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