Check DVS postcodes before a London job goes wrong
A practical guide to using a direct vision standard postcode checker for UK haulage, and what to confirm before sending a vehicle into London.
If you are sending a lorry into London, a postcode check is not a box-ticking exercise. It is a quick way to answer one practical question before the motor leaves the yard, will this job take the vehicle into the Direct Vision Standard area, and if so, is the vehicle allowed to be there on the terms you think it is.
That matters most when the job looks ordinary. A same-day tip gets added at 06:10. A container drop turns into a collection from a different gate. A driver swaps onto another unit because of a defect. That is when people rely on memory, and memory is where expensive mistakes start. A proper DVS postcode check belongs in the same working routine as checking site restrictions, booking references and whether the POD will come back clean enough to invoice.
What a direct vision standard postcode checker is actually for
A Direct Vision Standard postcode checker is there to tell you whether the delivery or collection point is likely to fall inside the London area where DVS rules apply to HGVs. In practice, the traffic office is trying to answer three things.
First, is the destination or collection point inside the DVS enforcement area at all. If it is outside, you can stop there and get on with planning the rest of the job. If it is inside, the next question is whether the vehicle assigned to the work is compliant for that journey. Third, if the assigned vehicle is not compliant, can the job be reassigned before anyone moves the wheels.
That sounds simple, but the reason operators search for a direct vision standard postcode checker is usually not because they want a map for its own sake. They want a fast planning answer while the phone is ringing. The customer gives a London postcode, the planner wants to know whether that one line of address changes the vehicle choice, the route, the timing, or whether a subcontractor can cover it.
For small and mid-size hauliers, the point is not legal theory. It is avoiding a day that goes wrong in three stages. The wrong vehicle gets sent. The driver only finds out when they are already committed. Then somebody in the office spends the afternoon trying to explain why the job cost more than it earned.
A postcode check is also useful because many jobs are entered before the full address is cleaned up. You may get "SE15" on a text, a screenshot from a shipping line, or a purchase order with half the delivery details missing. A quick check against the postcode gives you an early warning that this is not a standard out-of-town run and needs another look before it is allocated.
If you are running containers, this matters even more. A late DVS problem does not just affect one movement. It can affect quay collections, timed deliveries, return slots, container turnaround, and whether demurrage or other avoidable costs start building because the original plan was wrong.
What a postcode check can tell you and what it cannot
A postcode check can tell you whether a postcode appears to fall within the London area where DVS controls are relevant. It can also help flag jobs that need a compliant vehicle or a closer review before dispatch. That is useful, but it is not the same as confirming the whole movement is fine.
The first limit is obvious but often ignored. A postcode is not always the exact point the vehicle will attend. Large sites can use a general postcode that covers several entrances. Industrial estates may sit on a boundary where one access route creates a different practical outcome from another. A port-related delivery might use a booking office address while the actual vehicle movement goes elsewhere.
The second limit is that the postcode does not tell you the whole job. It does not confirm the vehicle class, body type, trailer arrangement, load dimensions, or whether the unit originally planned is the one that will actually turn up. It does not tell you if the customer has changed the address since the order was taken, or whether the driver is being told by phone to go to "the other gate".
The third limit is responsibility. A postcode match is not a defence if the exact location or actual vehicle details are wrong. You still need to confirm the address, the access point, and the vehicle being used. If the movement is covered by a subcontractor, you also need to confirm what they are sending, not what they said they would probably send.
This is where people get caught by false confidence. Someone checks the postcode once, sees that it is outside the area, and assumes the whole job is safe. Then the delivery point changes to a nearby site inside the zone. Or they check a postcode that is inside the area and assume any vehicle with the right booking can go. Neither assumption is safe.
The sensible use of a postcode checker is as a planning filter, not as the final word. We treat it the same way we treat a booking reference or customer note. Helpful, necessary, but not enough on its own. The exact address and the exact motor still have to match the job.
If you want an easy visual check during planning, our London DVS zone map for traffic planning helps the office see quickly whether a London movement needs a closer look. It is useful because the question in the office is rarely abstract. It is, can this unit do this job today.
The job details you need before you send the motor
Before assigning a vehicle to any London job that may fall under DVS rules, we need a minimum set of details in the job record. Without them, you are planning on guesswork.
Start with the exact address. Not just the outward postcode, and not just the customer name. We need the full delivery or collection address, including site name, road, postcode, and where relevant the exact gate or access point. If the site has a different entrance for HGVs, that must be recorded.
Then confirm the movement itself. Is it a delivery, collection, tip, reload, container drop, empty return, or a backload added onto another job. Multi-stop work needs each stop entered properly, because one London stop changes the compliance requirement for the whole shift.
Next, confirm the vehicle type actually being sent. Unit only, rigid, artic, skeletal, curtainsider, tipper, tanker, or specialist kit. In practice, the office also needs to know which registration is planned, because broad assumptions such as "one of the Euro 6 artics" are how the wrong vehicle ends up at the wrong gate.
Timing matters too. We need the booking time, any delivery window, and whether the job is likely to move if the customer rings late. A job entered as "any time PM" often becomes "must be there by 11" after the driver has already started elsewhere. That is when people make bad swaps.
Site access details should sit with the job, not in somebody's head. Height limits, weight restrictions, waiting rules, PPE, booking references, whether the driver needs to call on approach, whether the site refuses early arrivals, and whether the customer requires a specific trailer type. DVS is only one part of whether the vehicle can attend successfully.
If a subcontractor is involved, the check needs another layer. We need to know who is doing the work, what vehicle they are sending, and whether they have confirmed the London requirement in writing. "He knows the score" is not a control. It is how liability gets blurred after the event.
This is exactly why a proper jobs grid for traffic planning matters. The office needs one place where the address, timing, vehicle assignment, driver notes and changes all sit together. If the critical details are split between a spreadsheet, a WhatsApp thread and a driver's memory, the DVS check will fail sooner or later.
Where DVS checks go wrong in a small haulage office
Most DVS mistakes do not happen because someone has never heard of the rule. They happen because the working day is messy.
The first failure is job instructions arriving through the wrong channel. A customer sends the original booking by email, then changes the address on WhatsApp, then rings the driver directly to say "go to the other side". The planner has checked one postcode, but the actual movement is now different. Unless the office controls where job changes are recorded, the check is already out of date.
The second failure is the late vehicle swap. The planned unit is compliant, but at 05:45 it will not start, has a warning light, or is blocked in. Someone grabs another vehicle to save the job. Nobody goes back to the London requirement because the pressure is all about keeping the customer happy. That is understandable, but it is still how a preventable problem leaves the gate.
The third is assumptions around regular work. A job that has gone to the same customer for months gets treated as known. Then the customer books a different branch, a different warehouse, or a temporary site. Because the customer name looks familiar, no one checks the actual postcode properly.
The fourth is incomplete subcontracting. A subcontractor is given a collection with a postcode and a time, but not the full compliance context. Or the office assumes the subcontractor will do their own checks, while the subcontractor assumes the principal has already done them. That gap is common, especially on busy afternoons when someone just needs cover for one awkward load.
The fifth is poor handover between traffic and accounts. This sounds unrelated, but it is not. If the job record is weak, the office often cannot prove later what address was instructed, what vehicle was sent, or when the change was made. The same weakness that causes a DVS error also causes invoice delays because the POD, waiting time, and chargeable extras are scattered across messages and scraps of paper.
Container operators know this pattern well. One bad assumption at planning stage can affect quay timing, customer delivery slot, empty return, and whether the box sits long enough for demurrage to become an argument. The DVS issue is not isolated from the rest of the operation. It is part of the same chain of control.
How to build the check into daily planning without adding more admin
The easiest way to make DVS postcode checking stick is not to create a separate compliance project. It is to put the check inside the steps you already do to move a job from booking to invoice.
At job entry, the postcode should be captured as a normal required field, alongside customer, site, booking time and movement type. If the postcode is in or near the London area, the job should be treated as needing confirmation before final vehicle allocation. That is not extra admin. It is part of entering the job properly the first time.
At planning stage, the assigned registration should be visible against the job, so a vehicle swap is not just a verbal change. If the unit changes, the planner should have one obvious place to confirm the London implications before releasing the work. That is much easier when the office can see jobs and allocations in one live view rather than piecing them together from messages and paper.
Driver briefing matters as well. The driver should receive the exact site details, not a shorthand postcode and "you know where it is". If the customer tries to divert the vehicle mid-job, the instruction should come back through the office and be updated against the job, not handled as an off-system side conversation. Our driver progress and live job updates help keep that change visible to traffic while the work is still in motion.
After delivery or collection, the POD and any notes about delays, refusals or site changes need to come back into the same record quickly. This is where many small operators lose money. The traffic side knows there was a problem, but accounts only sees a late paper POD and a basic rate. If the London job involved waiting time, re-direction, extra mileage or a failed first attempt, those details need to be there before the invoice is raised.
That is why we link planning to the money side. If the job details, POD and chargeable events are already in the system, the office can move faster from completed work to invoice without chasing the driver two weeks later. Our finance and invoicing workflow for haulage jobs is built for that exact gap between "job done" and "invoice finally sent".
For a small operator, the aim is not bureaucracy. It is fewer avoidable surprises. One source of truth for the address. One visible vehicle assignment. One place to record customer changes. One clean POD trail. If you do that, the DVS postcode check becomes part of normal dispatch discipline, not another forgotten spreadsheet tab.
That is the practical test for any TMS. Does it help at 06:00, when the job changes, the driver is asking questions, and the customer still expects the load on time. If it does, compliance improves almost as a side effect of running the day properly. If it does not, you are back to memory, screenshots and crossed fingers.
If you want to see how we handle that in day-to-day traffic work, contact us through our haulage software enquiry page. We built Logivo for operators who need the office to stay in control without adding an implementation project on top of the day job.
Does a direct vision standard postcode checker tell me if the whole job is compliant?
No. It helps you spot whether the postcode may fall within the relevant London area, but you still need to confirm the exact site, vehicle and permit position before the job runs.
Is checking the postcode enough if the customer says the site is in London?
No. Postcodes can cover more than one access point or a wider area than the actual gate. Check the full address, site entrance and any route instructions, not just the outward code.
Who should do the DVS check in a small fleet?
Usually the person planning the job or assigning the vehicle. In a small firm that may be the owner or transport manager. The key point is to do it before the driver is committed.
What happens if the delivery address changes after the job is planned?
Run the check again. A last-minute postcode change can turn a straightforward job into one that needs a different vehicle or a different plan, especially when the office is already under pressure.
Can a TMS help with DVS-related checks?
Yes, if it gives the office one place to hold the job address, vehicle allocation, driver brief and POD trail. That makes it easier to catch problems before the lorry is on the road.