Check whether your route enters the DVS area

If you send vehicles into London, a postcode check is a quick way to see whether a delivery, collection, site visit or passenger movement falls inside the Direct Vision Standard area. It helps planners and transport managers answer the first question fast, does this route touch the DVS enforcement zone at all?

That matters because checking the location is only one part of compliance. A postcode result does not make a vehicle lawful to enter. You still need to confirm whether the vehicle needs a safety permit, whether that permit is in place, and whether the specific vehicle being assigned matches the permit status you have on record. In practice, the postcode check works best when it sits inside a wider process for vehicle records, route planning and audit evidence, which is exactly the sort of control we build into Operator Compliance.

What a postcode checker is actually for

A Direct Vision Standard postcode checker is there to answer a practical planning question, not a legal one in isolation. It tells you whether a postcode you are dealing with is likely to fall inside the DVS area, or whether your route planning needs a closer look because the destination, collection point or stop is on or near the boundary.

For day to day operations, that is useful at several points.

A planner can use it when pricing work. If a customer asks for a job into London, the first check is often the collection and delivery postcodes. If the destination is inside the DVS area, the job may need a vehicle with the right permit status. If the collection is outside but the route into the customer site crosses into the zone, the same issue applies.

A traffic office can use it during vehicle allocation. If one vehicle is permitted and another is not, the postcode result helps the planner choose the right unit before the job is released. That is much better than discovering the problem when the driver is already on the road.

It also helps subcontracting decisions. If we are passing work to another operator, we need to know whether the movement enters the zone so we can ask the right compliance question at the point of booking, not after the invoice arrives.

For passenger fleets, the same logic applies. A bus, coach, taxi or private hire movement may begin outside the area and still enter it during the job. A postcode check gives dispatchers an early warning that the route needs to be matched against vehicle status.

Used properly, a postcode checker is a filtering tool. It gives us a quick first pass so that only the jobs that need a deeper compliance review are escalated. That saves time, but it only works if everyone understands what the result does and does not prove.

If your team needs a visual check as well as a postcode search, our London DVS zone map for route planning is useful for boundary jobs and awkward sites.

What the checker can and cannot tell you

A postcode checker can tell you whether a location appears to be in the DVS area. It can help identify jobs that are likely to require a compliant vehicle and the right permit arrangements before entering the zone.

It cannot confirm that a vehicle is compliant.

That distinction matters. Compliance depends on the vehicle, not just the location. Two jobs to the same postcode can have different outcomes if one vehicle has the correct permit status and the other does not. Equally, one fleet may have mixed status across vehicles, so assuming that every lorry, van or passenger vehicle is covered in the same way creates obvious risk.

A postcode check also has practical limits because postcodes are not perfect route instructions. Some cover a wider area than operators expect. Some sites sit close to the boundary. Some jobs are booked to a head office postcode, while the actual delivery point is a yard, depot entrance or construction gate elsewhere. If the booking team checks only the invoice address, the result may not reflect the real movement.

Another limit is that the checker usually focuses on the destination or point entered, not every road the vehicle might use. A route can enter the area even where the main customer postcode does not. That is why planners should think in terms of the whole movement, not just the named stop.

There is also a difference between checking the DVS area and checking permit requirements. The area check asks, does this movement go into the zone? The permit check asks, can this specific vehicle legally enter? Those are separate steps and should be recorded separately.

For UK operators, this is a domestic London compliance issue rather than a general EU rule. If you run into Europe as well, do not assume that a process built for London DVS answers local urban access rules in other countries. It does not. The same applies in reverse. A European low emission or city access check is not the same as a DVS check in London.

Where operators sometimes get caught out is by treating a postcode result as final proof. It is not final proof for enforcement, management review or the Traffic Commissioner file. It is operational evidence that a location was checked and flagged. The stronger evidence is the full chain, the job details, the postcode result, the vehicle assigned, the permit status checked, and the record showing who made the decision and when.

When operators should run a postcode check

The best time to run a postcode check is before the job becomes urgent.

At quotation stage, it helps us understand whether the work may require a vehicle with a particular status. That matters where the available fleet is mixed, where permit holding vehicles are limited, or where a subcontractor may be needed. It also avoids promising a time slot that can only be met by using a vehicle that should not enter the area.

At booking stage, the check should be repeated if the job details have changed or if the original enquiry used a different address. This is common where a customer first gives a head office postcode and later supplies the actual delivery point, site entrance or event location.

At route planning stage, it should be part of the planner's release process. Before a vehicle is assigned, the planner checks whether any stop on the route enters the DVS area. If yes, the planner confirms the assigned vehicle's permit status before the work is sent to the driver.

When subcontracting, we should run the check before instructions go out. If the movement enters the zone, the subcontractor needs to confirm that the vehicle they intend to use is eligible to enter. This is especially important where the subcontractor might switch vehicles after the booking is accepted.

For last minute job changes, a fresh check is essential. A same day diversion, a changed delivery postcode, a missed slot requiring a different site entrance, or a return collection added to the route can all change the compliance position. These are exactly the moments when people rely on memory and assumptions.

Night work and weekend work need the same discipline. Compliance failures often happen when the usual office team is not present and decisions are made quickly by duty staff. If the process depends on one experienced planner remembering the boundary from memory, it is not a robust process.

Owner-drivers and smaller operators should still follow the same principle. Even if one person handles quoting, planning and driving, the check should be done at the point when the job is accepted and then confirmed if the details change.

If you want the permit side set out clearly, our guide to checking DVS safety permit requirements for HGV movements covers the next step after the postcode result.

How to use postcode results in a compliance process

The postcode result becomes useful when it is turned into a repeatable workflow.

A simple process looks like this.

First, record the job postcode or postcodes in the job file. If there is more than one relevant location, collection point, delivery point, depot exit, event venue, site gate, all should be listed clearly enough for another person to understand the movement.

Second, run the postcode check and record the result. That record should show what was checked, who checked it, and the date. If your system allows attachments or notes, keep a screenshot or saved result where practical. The point is not bureaucracy for its own sake. The point is that a manager can later see that the check happened before the vehicle moved.

Third, if the result indicates the movement enters or may enter the DVS area, the planner must check the assigned vehicle's status. This is where fleet records matter. The transport office should be able to see exactly which vehicle is being used, what permit status is recorded against it, and whether there are any restrictions or pending issues.

Fourth, if the assigned vehicle is not suitable, reallocate before dispatch. If no suitable vehicle is available, the job needs to be re-timed, subcontracted, or escalated. What should not happen is a planner sending the nearest available vehicle and hoping the route can be adjusted on the day.

Fifth, keep the evidence with the rest of the transport record. In a well run operation, that sits alongside MOT, annual-test, inspection, defect, insurance and driver evidence. For mixed fleets, it is also helpful to link vehicle compliance status to operational availability, so a non-permitted vehicle can be treated much like a VOR restriction for certain types of work.

This is one reason we built Operator Compliance around actual transport controls rather than a generic task list. If a planner, transport manager or compliance manager needs to show what checks were done, the answer should be in one place with the vehicle and job records, not buried in emails or a notebook.

In practical terms, a good process also needs named responsibility. The booking team may gather the postcode. The planner may run the check. The transport manager may review exceptions. But someone must own the final decision to release the vehicle. If that is left vague, gaps appear as soon as the office is busy.

For larger operators, it helps to standardise the check in the same weekly management rhythm you already use for roadworthiness and driver compliance. Some fleets work to an ISO week structure for reporting. That can make it easier to audit how many London jobs were checked, how many required escalation, and whether any were changed after planning.

Evidence matters beyond internal management. If an issue is ever reviewed by a customer, an insurer, the DVSA or the Traffic Commissioner, a dated record of the decision process is far stronger than saying the office normally checks these things. The same mindset already applies to Driver CPC records, DQC checks, DVLA licence checks, tachograph analysis and insurance verification through askMID or the Motor Insurers' Bureau, also known as MIB. DVS area checking should be treated with the same routine discipline.

Where businesses want systems to exchange data automatically, this can also be built into wider workflows through a REST API or webhooks, depending on how the planning and compliance systems are set up. The important point is not the technical method. It is that the result should become part of the transport record, not remain a separate, untracked action.

Common mistakes that create avoidable risk

The most common mistake is relying on memory.

Someone in the office thinks they know whether a postcode is inside the zone, because they have planned jobs there before. That may be true most of the time, but memory is not a control. It breaks down when the postcode is near the boundary, when the job uses a different entrance, or when a new member of staff takes the booking.

Another common mistake is checking only the depot postcode or only the customer's main office address. Neither tells you enough if the actual movement goes somewhere else. Construction sites, retail parks, industrial estates and event venues are frequent problem areas because the trading address and the vehicle access point are not always the same.

Boundary locations create their own risk. If a postcode sits close to the edge of the DVS area, do not treat the first result as the end of the matter. Check the exact site and planned route more closely. A visual review against a map is often sensible here.

A further mistake is assuming every vehicle in the fleet has the same status. Mixed fleets are normal. Vehicles change. New units arrive. Older units leave. Some are allocated to one contract and not another. If the office works from assumption rather than a live vehicle record, planners will eventually assign the wrong unit.

Subcontracting is another weak point. Operators sometimes check the postcode themselves but fail to verify that the subcontractor's actual vehicle is the one with the correct status. A subcontractor saying "we are covered for London" is not the same as confirming the specific vehicle being used for that movement.

Last minute changes are where good processes often fail. A planner may carry out the original check correctly, then a customer changes the postcode, adds another stop, or requests a different gate after the vehicle has been allocated. If no one repeats the check, the original record becomes misleading because it no longer matches the movement.

Poor record keeping is a quieter but serious problem. If the check is done but not recorded, managers cannot prove it happened. That makes internal review harder and weakens your position if a complaint, investigation or audit follows.

The answer is not a complicated process. It is a consistent one. Check the actual location. Record the result. Match it to the actual vehicle. Recheck if the job changes. Keep the evidence with the rest of the compliance file.

That is the approach we take in Operator Compliance, because transport compliance works best when routine checks are built into the same system as the rest of the operator's obligations. If you want to see how we structure records and accountability across fleets, drivers and vehicles, read more about how our compliance platform is built by operators for operators.