How to check DVS status before a London delivery

If you are sending a vehicle into Greater London, check its Direct Vision Standard status before the job is dispatched, not when the driver is already on the way. In practice, that means confirming the vehicle’s star rating, checking whether a valid HGV Safety Permit is already in place, and making sure any Progressive Safe System equipment required by the permit has actually been fitted and recorded.

Most operators looking for a DVS checker are trying to answer one operational question. Can this vehicle legally enter the London DVS area for this delivery on this date? The safest way to answer that is to treat DVS as part of pre-allocation control, alongside MOT, annual-test, insurance, driver licence, Driver CPC, DQC and any route-specific restrictions.

What a DVS check is and when operators need one

A DVS check is a compliance check against Transport for London’s Direct Vision Standard rules for heavy goods vehicles operating in Greater London. Operators usually search for a DVS checker when they need to confirm whether a vehicle can be sent into the zone without risking a contravention, a refused job, or a last-minute vehicle swap.

For UK operators, this matters mainly for HGVs over 12 tonnes gross vehicle weight that enter or operate in the Greater London area. It is not a general UK-wide scheme. It is a London requirement, so a vehicle that is fully compliant for national operator-licence purposes can still be non-compliant for a London delivery if its DVS position has not been checked.

The point of the check is straightforward. DVS rules are based on the vehicle’s direct vision star rating and, where applicable, whether the vehicle has the required permit and safety equipment. A vehicle may be compliant because it has a sufficient star rating for the current rules, or because it holds a valid permit subject to conditions. If neither applies, it should not be allocated to the job.

This is why transport managers tend to check DVS status before:

• accepting a London delivery or collection
• assigning a vehicle to a route that enters Greater London
• using subcontracted or hired-in vehicles
• reactivating a spare vehicle after a period as VOR
• changing a registration mark, body type, or fleet record
• planning overnight trunking that crosses into the zone

For mixed fleets, DVS checks are especially important because the rule only catches certain vehicle classes and weights. Vans, buses and coaches have their own compliance considerations, but the London DVS regime is specifically relevant to qualifying HGVs. That means planners need a clear fleet list showing which units need DVS controls and which do not.

Where operators work across borders, it helps to keep the distinction clear. This is not an EU-wide direct vision rule applied in the same way across member states. In the UK, the practical issue is whether the vehicle falls within the London scheme and whether it meets the current permit conditions for that journey.

What information you need before you start

Before checking DVS status, have the right vehicle and permit information in front of you. Most wasted time comes from trying to verify compliance with incomplete records, especially where a unit has changed operator, had bodywork altered, or been added to the fleet recently.

At minimum, we would want the following ready:

• vehicle registration mark
• make and model
• gross vehicle weight
• vehicle category and body type
• VIN or chassis number
• fleet number, if used internally
• current operator details
• expected date of the London journey
• evidence of any existing HGV Safety Permit
• details of any Progressive Safe System equipment fitted

The registration mark is the obvious starting point, but it is not always enough on its own. If a vehicle has been acquired second-hand, transferred between entities, or has had registration changes, cross-check the core identity details against the V5C and your own asset register.

You should also have the permit record itself, if one exists. That means the permit reference, issue date, expiry details if relevant, and any conditions attached to it. Keep a copy in the vehicle file and in the central compliance record, not just in a planner’s inbox.

Supporting documents may include:

• V5C registration certificate
• manufacturer information or evidence of star rating
• permit confirmation from the issuing authority
• installation records for cameras, sensors, audible warnings and signage where required
• workshop job sheets or fitter certificates
• internal vehicle compliance checklist
• route or customer instructions confirming the vehicle will enter Greater London

If you are checking vehicles operated by agency drivers, subcontractors, or owner-drivers working under your control, ask for the same standard of evidence. A hired or subcontracted vehicle entering London on your work still needs proper checking before dispatch. Do not rely on verbal assurance that a permit is “sorted”.

This is also where a central compliance system helps. In Operator Compliance, we structure vehicle records so transport managers can see deadlines, documents and status in one place, rather than checking separate folders, emails and spreadsheets. The same discipline you apply to MOT, annual-test and inspection records should be applied to DVS evidence.

If your fleet data is already digitised, it is worth making DVS a defined field in the vehicle master record, alongside taxation class, test dates, insurer details and any route restrictions. That avoids repeated manual checking and gives planners a simple compliant or hold status at the point of allocation. If you want to see how we organise these records, our vehicle and driver compliance features show the sort of controls we use for operator-licence management.

How to check whether a vehicle meets the DVS rules

In practical terms, there are three parts to the check. First, confirm whether the vehicle is in scope. Second, confirm the vehicle’s star rating or permit status. Third, confirm any required safety equipment is fitted and evidenced.

Start with scope. Ask:

• is this an HGV over 12 tonnes gross vehicle weight?
• will it enter or operate in Greater London?
• is the journey date within the current DVS enforcement period?

If the answer is yes, move to compliance confirmation.

The next step is the vehicle’s DVS star rating. For many operators, this is the key piece of information because it determines whether a permit is needed and on what basis. The star rating is not something to guess from age or appearance. Use the manufacturer’s information and the official permit route, and keep the supporting evidence on file.

Then check whether a valid HGV Safety Permit is already in place for that registration. If it is, make sure the permit applies to the exact vehicle being dispatched and that there has been no change which could affect validity. A permit record against the wrong registration, or against a previous fleet identity, is not good enough.

If the vehicle only qualifies to operate because additional safety equipment has been fitted, verify that the equipment is actually present and recorded. Depending on the applicable DVS requirements, that may include items such as:

• camera monitoring systems
• blind spot information systems
• moving off information systems
• audible left-turn warning systems
• warning signage

Do not stop at “ordered” or “booked in”. If the equipment is required for compliance, the vehicle should not be treated as available until fitting is complete and evidenced.

A sound workshop and compliance process would include:

1. Fitting instruction issued to workshop or approved installer.
2. Installation completed and job sheet signed.
3. Photos or fitment evidence uploaded to the vehicle record.
4. Permit application or update completed where required.
5. Vehicle status changed to compliant only after review.

This matters because the dispatch decision often happens outside the compliance office. A planner seeing a unit as available may allocate it unless the system clearly shows hold, non-compliant, or VOR. DVS should feed into that same availability control.

For operators using integrated systems, there is a strong case for treating DVS as one more hard stop in the workflow. If you are already tracking insurance through askMID checks, policy evidence from the Motor Insurers' Bureau or MIB, driver entitlement through DVLA checks, and tachograph deadlines, then DVS belongs in the same operational control set. It should not sit in a separate spreadsheet maintained by one person.

This is also where connected systems can help. Some fleets use a REST API or webhooks to move status changes between planning, workshop and compliance tools. Others export records into internal reporting or BI tools such as Fleetalyse or Logivo.AI. The important point is not the technology label. It is that the planner can see, before dispatch, whether the London vehicle is compliant.

If you need a quick visual check of whether the route enters the area, our map of the London DVS area is useful for planners and traffic office staff.

What the result means for planning and dispatch

Once the check is complete, the result needs to turn into a clear dispatch decision. A DVS result is only useful if it changes what the traffic office does next.

If the vehicle passes, meaning it meets the DVS rules for the intended London journey and any permit is valid, the unit can remain available for allocation. The vehicle record should show compliant status, and the planner can assign it in the normal way.

If the vehicle is non-compliant, remove it from London work immediately. That does not necessarily mean the vehicle is unusable for all jobs. It may still be suitable for work outside Greater London. What matters is that your planning controls stop it being sent into the zone by mistake.

If the result shows that a permit is missing, expired, unverified or conditional on equipment that has not been evidenced, treat the vehicle as unavailable for London work until the issue is resolved. In operational terms, that usually leads to one of four actions:

• reallocate the job to a compliant vehicle
• swap the route with another unit already on the plan
• subcontract the movement to a compliant carrier
• delay or refuse the job until compliance is in place

This is where a good transport office avoids expensive errors. The wrong decision at 16:30 can mean a failed night trunk, missed delivery slot, customer complaint, and a compliance exposure that should have been caught at allocation stage.

We recommend using a simple internal status model for DVS-sensitive vehicles, for example:

• Compliant for London
• Compliant with permit
• Pending evidence
• Non-compliant for London
• Out of scope

Those labels are easier for planners to act on than long notes in a document field.

Dispatch teams should also understand that DVS status is date-sensitive. A vehicle may be compliant today and unavailable tomorrow if a permit condition changes, a safety system is removed for repair, or the vehicle is returned to service after VOR without the necessary equipment check. That is why DVS should be reviewed as part of return-to-service control, not only at first application.

For hired vehicles and subcontractors, make the check part of onboarding and job release. Do not wait until the driver is at the gate. We would treat this in the same way as checking operator-licence authority, insurance, MOT, annual-test and driver documents. If the records are not present, the vehicle does not get the London job.

What records operators should keep after a DVS check

After the check, keep enough evidence to show what was checked, when it was checked, what result was reached, and who acted on it. This is basic operator control. If there is later a customer dispute, an internal incident review, or wider scrutiny of your systems, you need a dated record rather than a verbal account.

The core records to retain are:

• dated DVS check result
• name or role of the person carrying out the check
• registration and vehicle identity details
• star rating evidence or manufacturer confirmation
• permit copy or permit reference
• safety equipment fitment records
• internal status assigned to the vehicle
• any dispatch restriction applied
• communication sent to planners, drivers or subcontractors

Keep these records in the vehicle file and in a central fleet list. The central list matters because it allows transport managers to audit the whole London-capable fleet at a glance, rather than reviewing one unit at a time.

A good DVS control record should show:

• which vehicles are in scope
• which are compliant
• which rely on a permit
• which are awaiting fitment or evidence
• which are barred from London allocation

If your operation works to weekly planning cycles, it can be useful to review the in-scope fleet by ISO week so planners know which units are cleared for upcoming contracts. That is especially helpful where vehicles rotate between regional and London work.

Retain internal communication as well. If a vehicle has been marked non-compliant, keep the email, task note or system alert sent to planning and driver management. If a driver has been instructed not to enter Greater London in a specific vehicle, keep that instruction on file. The point is to show that the check led to operational control, not just passive record keeping.

For audit readiness, we would also keep:

• screenshots or exports of the fleet DVS status list
• copies of any permit application submissions
• workshop sign-off for safety equipment
• exception logs where a planned London vehicle was changed
• management review notes where repeated issues were found

This sits naturally alongside the rest of the operator’s compliance evidence. The same file discipline that supports a Traffic Commissioner inquiry or DVSA visit should apply here. If your systems already capture signed inspections, tachograph analysis, driver licence checks and document expiry, DVS records should be retained to the same standard.

That is one reason we built Operator Compliance around real fleet control rather than generic CRM-style records. Fleeta Limited runs trucks under an operator licence itself, so we know the difference between a document being stored somewhere and a transport manager being able to prove control on the day. If you need a system that keeps those records visible and usable, you can compare compliance tools and operator controls or speak to us about your fleet setup.

A DVS check before a London delivery is not complicated, but it does need to be deliberate. Confirm scope, confirm star rating or permit, confirm any required equipment, then record the result in a way the traffic office can act on. Done properly, that prevents avoidable contraventions and keeps the right vehicles available for the right work.

What does DVS stand for in fleet compliance?

DVS means Direct Vision Standard. It is used in London to assess how much an HGV driver can see directly through the cab windows and what safety measures may be required.

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

No. A DVS check is about London direct vision and permit compliance for relevant HGVs. It does not replace MOT, annual-test or any operator-licence maintenance requirement.

Do all fleet vehicles need a DVS check?

No. It is relevant where the vehicle type and journey fall within the London scheme rules. Operators should check each vehicle used for affected work rather than assume the whole fleet is covered.

Can a transport manager keep DVS evidence in the same system as other compliance records?

Yes. Many operators keep DVS evidence alongside inspection dates, MOT or annual-test records, driver documents and other compliance files so the Traffic Commissioner file is easier to maintain.

Should drivers rely on memory for DVS permit status?

No. Permit status should be checked and recorded by the operator, then communicated clearly to planners and drivers so the right vehicle is sent to the right job.