How to check DVS zones before a lorry is turned away

A practical guide to checking DVS zones, permits and routes so UK haulage operators can avoid refused entries, delays and missed delivery slots.

If a lorry is being turned away at the gate, the DVS check was left too late. The point of checking a DVS zone is not to satisfy a box on a compliance list. It is to confirm, before the truck moves, whether that job enters a controlled area and whether the vehicle assigned to it is allowed to make that movement.

For most operators, this matters when the day is already tight. The delivery slot is booked, the driver is loaded, there is another job waiting after it, and somebody assumes the route is fine because “we go there all the time”. A proper DVS zone check stops that kind of assumption. It tells us whether we can send that vehicle, whether we need a different unit, and whether the customer needs warning before the wheels turn.

What a DVS zone check is actually for

A DVS zone check is there to answer a simple operational question, can this specific heavy goods vehicle legally enter the area needed for this job?

In London, the Direct Vision Standard applies to HGVs over 12 tonnes gross vehicle weight. If the journey enters the DVS enforcement area, the operator must make sure the vehicle meets the required standard or holds the right permit. That is separate from LEZ and ULEZ. A truck can be emissions compliant and still fail on DVS.

On a live haulage job, the check is about more than the destination pin on the map. We need to confirm whether the movement, approach road, collection point, delivery point, diversion route or waiting area takes the vehicle into the controlled zone. If it does, the assigned vehicle must be suitable before the planner commits it.

That is why we treat a DVS check as part of job planning, not as a driver problem at the gate. By the time the driver is being refused entry, the damage is already done. We have lost time, burned fuel, missed a slot, and created a customer service issue that somebody in the office now has to explain.

If you want a quick way to visualise whether a movement crosses the controlled area, our London DVS zone map for route planning is there for exactly that purpose.

Which jobs need checking before they go out

Not every job needs the same level of checking, but plenty do, and the mistake usually starts when a planner assumes a familiar customer is “outside London” or a port run is “nowhere near the zone”.

In practice, we flag a job for DVS checking when any of the following apply:

The delivery point is inside Greater London and the vehicle is over 12 tonnes GVW
The collection point is inside the DVS enforcement area
The route between two non-London points is likely to cut through the area
The customer has given a postcode that sits near the boundary
The job involves a timed slot, event delivery, construction site, waste movement or urban distribution run where diversion options are limited
The job is being covered by a subcontractor and we do not control the vehicle day to day
The original job has changed after booking, for example a redelivery, a site move, or an extra drop added later

Container operators need to be especially careful here. A box coming out of a port may not be destined for central London, but the empty return, repositioning move or backload can still take the vehicle into the controlled area. The same goes for storage compounds, devanning sites and customer yards near the boundary. One wrong assumption can upset container turnaround, create demurrage exposure, and knock the rest of the day out of sequence.

The practical way to spot risk early is to check jobs at entry stage, not at dispatch stage. When the work is first booked, we should be asking:

Where exactly is the collection?
Where exactly is the delivery?
Is there more than one drop?
Is the route fixed by customer instruction?
Is this likely to involve waiting, diversion, or a return leg through London?
What class of vehicle is needed?

If the answer to any of those points suggests London movement, the job should be marked for DVS review while there is still time to assign the right lorry.

This is one reason we keep jobs visible in a proper planning screen rather than buried in message threads. In Logivo, operators use the job planning grid for traffic desk work to see which jobs need attention before they become same day problems.

What to confirm on the vehicle before you commit the job

Once we know the job may enter a DVS-controlled area, the next step is to confirm the vehicle details, not just the customer details.

The main checks are practical:

The vehicle’s gross weight, because DVS applies to HGVs over 12 tonnes GVW
The registration mark, because the permit and compliance position attach to the specific vehicle
Whether the vehicle meets the applicable DVS requirement
Whether the vehicle has the right safety equipment where that is part of the permit basis
Whether a valid permit is in place for that registration
Whether the vehicle being sent is the same one originally planned

That last point matters more than people admit. A job may have been planned against a compliant unit, then changed at short notice because of a defect, service booking, tyre issue, trailer mismatch or driver hours. If the replacement vehicle has not been checked, the original DVS decision is worthless.

For mixed fleets, hired-in units and borrowed cover vehicles, we need the permit position confirmed before dispatch. The same applies if a subcontractor is covering the work. Do not assume that because a carrier “does London work” every truck on their fleet is ready for every DVS movement. Get the registration, confirm the permit, and keep a record against the job.

This also sits alongside normal compliance discipline. If we are careful about O-licence undertakings, maintenance records, driver defects and insurance, we should be just as careful about urban access rules that can stop a job dead on the day.

Where operators come unstuck is not usually the rule itself. It is the handover. The planner knows the job is in London, the driver swaps units, the office is busy, and nobody updates the record. So the check needs to sit against the actual vehicle allocated, not just the customer account.

How to check the route without relying on guesswork

The worst way to do a DVS check is from memory. “That postcode should be fine” is not a transport process.

Postcodes are useful, but they are not enough on their own. A postcode can cover a wider area than people realise. Site entrances are not always where the postcode lands. Industrial estates can straddle boundaries. Construction projects often use temporary access points. A route that looks safe on paper can still enter the controlled area because of the actual road approach.

The right way to check is to look at the planned movement on a map and confirm whether the route, or any realistic route to complete the job, enters the DVS zone. That means checking:

The exact collection address
The exact delivery address
The likely road approach for an HGV
Any customer-mandated routeing
Any additional drop, shunt or return movement attached to the same job
Whether the journey clips the zone even if neither endpoint is inside it

This matters especially around the boundary. A planner may think they are safe because the customer address sounds like Essex, Kent, Surrey or Hertfordshire. But if the route enters the London enforcement area, the name of the county does not help.

It also matters when habits take over. If we have been serving a site for years, we can easily miss that the job has changed. The customer may move the delivery gate, use a different holding area, or redirect vehicles because of site works. One change to the access arrangement can turn a non-issue into a DVS issue.

That is why we prefer a visible route check rather than a verbal one. Use a current map, check the actual movement, and save the decision with the job where the traffic office can see it. If the route changes on the day, the check should be revisited.

For operators who want a quick visual reference before assigning a vehicle, our live map view for planned and active jobs helps the office see where a movement sits in relation to the day’s work, rather than relying on memory and postcode shorthand.

What happens when the check is missed

When a DVS check is missed, the first consequence is usually operational, not legal. The driver gets near the delivery, realises there is a problem, and phones in at the worst possible moment.

Then the day starts to unravel.

The obvious outcome is refused entry. The site cannot take the vehicle, or the driver will not risk entering the area. The load then has to be held, rebooked, transhipped, or reassigned to another unit if one is available. That creates wasted mileage straight away.

After that come the knock-on effects:

The delivery slot is missed
The collection booked after it is now at risk
Driver hours are consumed on a job that has not been completed
The office starts making apology calls instead of planning the rest of the fleet
A replacement vehicle may have to dead run in
The customer may impose a redelivery process or reject same-day rebooking
The POD is delayed because there is no completed delivery to close off
In container work, quay or return timings may be missed, affecting container turnaround
If a box sits longer than planned, demurrage or related storage costs can become part of the argument
Invoicing slips because the job is no longer straightforward

For a small operator, one failed access check can spoil a whole day’s margin. Not because the rule itself is complicated, but because everything around it is time-sensitive. The six o’clock phone call becomes a nine o’clock customer complaint and then a Friday invoicing dispute.

There is also the internal admin mess. Somebody has to record why the job failed, speak to the customer, amend the planner, brief the driver, chase the replacement, and sort out whether the wasted trip is chargeable. If you are still running much of that through WhatsApp, paper notes and memory, the detail gets lost quickly.

And if the job was passed to a subcontractor, the problem can get harder to unwind. You may still own the customer relationship, but you do not control the vehicle records directly. If the DVS check was assumed rather than evidenced, the argument about who should absorb the cost starts immediately.

Building the check into the job sheet and POD process

The fix is not a huge compliance project. For most small and mid-size operators, it is a short, repeatable step built into the normal life of a job.

We suggest treating DVS as part of job creation, allocation, driver briefing, completion and invoicing.

At job creation:

Add a simple yes or no field for “DVS check required”
Record the exact collection and delivery points, not just customer names
Flag boundary locations and London work at the point of booking

At allocation:

Match the job to a specific registration, not just a vehicle type
Confirm the permit position before the job is committed
If using a subcontractor, record who checked the registration and when

At driver briefing:

Make sure the driver sees the relevant site details and any route note
If the vehicle changes, require the office to reconfirm DVS before release
Avoid verbal-only handovers for London jobs

At completion:

Keep the job notes, arrival issues and delivery outcome against the same record
If access failed, capture the reason properly so it can be billed or challenged later
Tie any redelivery or aborted trip back to the original movement

At invoicing:

Separate completed work from failed access, waiting time, wasted mileage or reattempts
Make sure the POD or exception note is already attached before the invoice is raised
Do not leave the traffic office and finance team to reconstruct the story two weeks later

This is where a lightweight TMS earns its keep. Not by giving you a grand theory of transport, but by making sure the check, the vehicle allocation, the driver brief, the POD and the invoice all sit in one place.

In Logivo, we build that into the ordinary workflow. The office plans the job, the driver gets the brief, the delivery record comes back as ePOD, and finance can see what is billable without chasing paper. If a job aborts or changes, the record changes with it. That matters when the issue is not “was this delivered” but “why did this movement fail and what do we charge for now”.

Our POD to invoice workflow for haulage jobs is designed for exactly that gap between the truck finishing and the invoice actually going out.

For small fleets, the important thing is to keep the process proportionate. You do not need an implementation project or a dedicated compliance clerk to stop basic DVS mistakes. You need a clear trigger, a visible check, and one place where the answer is recorded.

If you are still depending on memory, paper job sheets and scattered messages, DVS is one more thing that can be missed on a busy day. Build it into the job record once, and it stops being a scramble every time a London movement appears.

If you want to see how we handle planning, driver briefing, ePOD and invoicing without adding a heavy admin layer, get in touch about your current traffic desk process.

What does DVS mean for a haulage operator?

For an operator, it means checking whether a vehicle is allowed to enter the relevant controlled area for that job and whether any permit requirement has been dealt with before dispatch.

Do I need to check every job for DVS?

No. But any job that may enter a DVS-controlled area should be checked before the vehicle is assigned. The mistake is assuming a regular customer or familiar postcode is always safe.

Is checking the delivery postcode enough?

Not always. A route can enter a controlled area even if the collection or delivery point looks borderline. Check the actual movement, not just the address on the job.

Can a driver sort the DVS issue out on the day?

That is risky. By the time the driver is near the site, you may already have lost the slot, wasted mileage and created a problem for the return leg or backload.

Who should be responsible for the DVS check?

Usually the person planning or allocating the job. The driver still needs a clear briefing, but the check should be done before the work is committed to a vehicle.