ANPR that works in the real world: what to decide before installation

Start with the decision or action

An ANPR system might open a barrier, alert security to a watchlisted vehicle, record visits, measure dwell time or support authorised investigation. Those are different outcomes and they need different software, integrations, availability and data handling.

Write down what should happen after a plate is read, how quickly it must happen, who is responsible and what the fallback is when a plate cannot be read. This becomes the testable purpose of the system.

Practical point“Capture number plates” is a technical feature. “Allow registered delivery vehicles through this entrance” is an operational requirement.

Choose a controlled capture point

The most reliable position is usually one where vehicles follow a predictable path. Lane width, camera distance, height, horizontal and vertical angles, vehicle speed and the possibility of queues all affect the plate image.

A wide overview that looks attractive on a monitor may leave too few pixels on the plate. It is often better to give the ANPR camera a focused job and use a separate overview camera when wider context is also needed.

• Look for vehicles changing lane or turning away from the camera.
• Allow for cars, vans, lorries and plates mounted at different heights.
• Check whether barriers, signs, landscaping or parked vehicles can block the view.
• Consider how the position can be reached safely for cleaning and maintenance.

Design for day, night and difficult weather

Reflective plates, headlights and low ambient light make ANPR different from ordinary CCTV. The camera exposure, shutter, infrared illumination and target position need to be configured for the expected speed and approach.

Commissioning should include darkness, bright sun, wet plates and the busiest period where possible. Seasonal change also matters: foliage, low winter sun and road spray can alter a view that worked well on a clear installation day.

Decide what happens when a read is uncertain

No camera will read every plate in every condition. The design should set an acceptable performance level and define the safe fallback. A barrier system may need an intercom or authorised manual release; a watchlist alert needs a staff procedure that accounts for a possible misread.

Test the complete chain, not only the camera. That includes the plate database, network, rules, alerts, barrier or gate interface, user permissions and the record available for later review.

Plan data governance before switching on

The Information Commissioner’s Office explains that vehicle registration marks will be personal data in most ANPR circumstances. Organisations should establish a genuine and proportionate purpose, complete the appropriate impact assessment, use clear signage and set access, retention and disposal rules.

Only collect what is needed for the defined purpose and keep matching data accurate. The ICO’s video-surveillance guidance is currently under review following changes in UK law, so the latest official guidance and the organisation’s data-protection advice should be checked before final approval.

Agree acceptance tests while the system is still being designed

A useful handover records what was tested and under which conditions. Include representative vehicles, front and rear plates where relevant, normal and peak speeds, daytime and darkness, allowed and denied actions, uncertain reads, loss of network connectivity and authorised data retrieval.

The result should be a system the client can operate and audit, supported by known camera positions, configuration records, user responsibilities and a maintenance route.