Number plate reading at manned gates: handling poor images and mismatches

Treat the plate read as a draft, not a decision

Phone-based number plate reading can remove typing from a busy gate, but the result should begin as a candidate registration for the guard to check. A single wrong character can attach an arrival to the wrong saved vehicle, show an unrelated permit or leave the real vehicle without a matched departure. The safest operating principle is simple: capture, compare, correct if necessary, then record the movement.

Priority Service's published workflow follows that guard-led pattern. The Android app captures a vehicle and number plate, proposes the registration, and lets the guard review and correct it before saving IN or OUT. Manual registration entry is included. The public feature description also says recognition depends on the photograph, camera quality, lighting and plate condition. It does not advertise unattended fixed-camera enforcement or automatic barrier operation.

This matters because a technically successful read is not the same as an authorised visit. The registration may be accurate while the vehicle is at the wrong gate, outside its permit window or driven by somebody not expected. Conversely, recognition may fail on a vehicle that is genuinely approved. The gate procedure must keep the human access decision separate from the convenience of reading characters from an image.

Create a safe, repeatable capture position

Good results start with the gate layout. Choose a stopping point where the vehicle is stationary, the front or rear plate can be seen squarely and the guard can use the phone without stepping into a live traffic path. Mark the stop line and make the instruction clear to drivers. If the lane geometry forces a steep angle, long distance or obstructed view, treat that as an operational design problem rather than asking guards to compensate by moving into danger.

The Health and Safety Executive says workplace traffic routes need suitable lighting and that areas around junctions, buildings, pedestrian routes and regular vehicle movements require particular attention. Lighting should support safe movement without dazzling drivers. For the gate, that means testing the capture point in daylight, darkness, rain and when headlamps face the camera. Add or reposition site lighting only through the site's risk assessment and competent facilities process.

Keep the camera lens clean, make sure the device is charged and use the organisation's supported phone and application configuration. Ask the driver to stop fully before capture. Do not allow a queue to pressure the guard into photographing a moving vehicle or standing between vehicles. HSE guidance also stresses that visiting drivers need to understand the site layout and relevant procedures, so the stop-and-wait instruction should form part of the arrival information.

Use a short confirmation routine

The guard should compare the proposed result with the physical plate character by character. Read it in groups that match the displayed format and pay particular attention to pairs that can be confused in poor images. The check should happen before selecting the permit, category or IN/OUT action, because information shown after a wrong match can look plausible and encourage confirmation bias.

UK number plates generally use prescribed characters and colours. GOV.UK says modern plates must display black characters on white at the front and yellow at the rear, and plates fitted after 1 September 2021 must carry the BS AU 145e marking. DVLA's INF104 explains the formats and display requirements in more detail. Those rules improve consistency, but a compliant plate can still be difficult to photograph because of dirt, glare, damage, angle or a poorly positioned fixing.

Official MOT guidance specifically warns that fixing screws, bolts and delamination can prevent identification by ANPR cameras because non-reflective areas may be interpreted as black. A guard using a phone camera can face similar visual ambiguity even though the system and purpose are different. If one or more characters are uncertain, take another safe photograph or enter the registration manually from a clear visual check. Do not guess simply to keep the lane moving.

Resolve a vehicle-data mismatch before admission

Number plate reading and vehicle-data lookup are separate functions. On Priority Service, reading the registration from the photograph is included in the base plans. The optional Automatic vehicle details add-on can retrieve make, model and colour from a registration where available; without it, those details can be entered manually. A lookup is supporting information, not proof that the vehicle at the gate is the one described by the returned record.

If the registration appears correct but the returned make, model or colour does not match what the guard sees, pause the workflow. Recheck the characters and the physical vehicle. Consider legitimate explanations such as an outdated or broad colour description, but do not change the registration merely to make the lookup fit. Follow the site's exception route, which may mean referring the vehicle to a supervisor, contacting the host or moving it to a safe holding position.

The same caution applies to saved permits. A registration match may display an existing approved vehicle, but the guard should still review the permit details and current visit context. If a closely similar registration produces another contractor's record, correcting the plate before saving is essential. The system should help the guard find relevant information; it must not turn a near match into automatic access.

Record uncertainty without creating a false fact

The Information Commissioner's Office says organisations should have processes to check the accuracy of personal data they collect and keep the source and status of information clear. A vehicle registration or visit record can be personal data when it relates to an identifiable driver, visitor or incident. If a guard knows the automated result is uncertain, saving it as confirmed without checking can make the operational record misleading.

Define what the guard should do when the plate cannot be read safely. Options may include manual entry after a clear visual check, a second photograph from the approved position, supervisor referral or refusal under the site's policy. Avoid free-text inventions that obscure what happened. If the organisation needs an exception record, distinguish between the observed plate, the machine-proposed read, the corrected registration and any unresolved uncertainty using the fields and procedures it has approved.

Do not ask guards to police number-plate construction law unless that is genuinely part of their authorised role. A plate that appears dirty, damaged or unusually spaced may need escalation because it cannot be matched reliably, but the access decision should follow the site's rules. Preserve the vehicle photograph and event details only in accordance with the organisation's lawful purpose, retention policy and privacy information.

Correct errors through a controlled process

Sometimes an error is discovered after IN has been recorded: the host reports the wrong vehicle, the OUT attempt cannot find the earlier arrival, or an administrator notices that the photograph and registration differ. The procedure should say who may correct the record, how the original event is preserved or auditable, and how related permit or departure records are reconciled. Do not create a second fictional arrival to hide the first mistake.

Where the guard can correct the proposed registration before saving, use that control at the gate. Post-event amendments may require a supervisor or administrator depending on the customer's role design and the product's available permissions. Priority Service's public pages advertise guard correction before recording, role separation and administrator access to searchable history and CSV reports; they do not publish a full amendment workflow. Buyers should verify post-save correction and audit behaviour during a live demonstration.

Review repeat errors for patterns rather than blaming individual guards. Are failures concentrated after dark, at one gate, on one device or in wet weather? Are vehicles stopping too far from the line? Are guards skipping confirmation during delivery peaks? Use samples of photographs and corrected records under authorised access to improve lighting, positioning, training and staffing. The objective is fewer ambiguous captures and better decisions, not an unrealistic promise of perfect recognition.

Test failure cases before buying

A useful demonstration should include more than a clean plate in bright light. Ask the supplier to show a deliberately angled image, low light, glare, a partially obscured character and a registration that resembles an existing permitted vehicle. Confirm that the guard sees the proposed result, can correct it before saving, can enter a registration manually and can refer an uncertain or unapproved vehicle rather than forcing a match.

Then test the departure. Use the corrected registration to locate the earlier IN event and record OUT. Check what an authorised administrator sees in the visit history and export. If you intend to buy automatic vehicle details, test a mismatch between the photographed vehicle and the returned make, model or colour. Ask which action consumes a live lookup and confirm the commercial allowance; number plate photographs and IN/OUT records are described separately from the optional lookup service on the current pricing page.

Priority Service's current feature summary is at https://priorityservice.co.uk/#features, and its simulated guard workflow is at https://priorityservice.co.uk/demo. Use the enquiry at https://priorityservice.co.uk/#demo to request a test based on your real gate distance, lighting, vehicle mix and exception procedure.

Vehicle logging for your operation

Explore the workflow, plans and demo options for your team.

Explore gatehouse management software