Technical buying guide
Handling Unreadable Plates in an ANPR Parking Workflow
An ANPR entrance can work smoothly for most vehicles and still need a clear plan for the one that cannot be read. A dirty or obscured plate, glare, an unusual format, a poor camera angle or a network fault can all produce a similar result for the driver: the gate does not open. The operator needs to know which problem occurred before granting access or turning a visitor away.
This article focuses on the exception process after the vehicle reaches the lane. It does not claim that a Zibor Park software package has a particular manual-review screen, temporary credential feature or automated fallback. Those functions must be confirmed for the quoted configuration. The Parking System Equipment category and LPR Cameras & Recognition Units page are the equipment context.
Separate four failure points before choosing a fallback
“Unreadable plate” should not become a catch-all label. The camera may fail to capture a usable image. Recognition may produce no plate string or an uncertain one. A correct string may be absent from the permitted list. Or the access system may authorize a vehicle while the barrier controller refuses to move because of a safety or equipment condition.
| What the operator sees | First evidence to inspect | Safe next decision |
|---|---|---|
| No usable image | Camera availability, lighting, lane position and recorded frame | Move the vehicle to an approved retry point or request staffed review |
| Image exists, no reliable plate result | Image quality and supported plate format | Check the plate by an approved method; log uncertainty |
| Plate read but no entitlement | Enrollment and visit/permit rules | Verify identity or visitor purpose; do not treat a read as permission |
| Authorization given, gate remains closed | Barrier status and safety inputs | Follow the gate fault procedure; do not bypass an active protection input |
This distinction changes the service call. Replacing a camera will not resolve an expired permit. Adding more light will not repair a broken barrier input. A structured event record saves the operator from guessing and gives the integrator evidence for the right fix.
Make retry predictable for the driver
Define where a vehicle may stop and whether it can reverse without blocking a second lane. If a driver should move forward to improve the plate view, the signage and staff instruction must be unambiguous. If the lane has no safe retry space, the design needs an assistance path before the system is launched.
Choose who may approve entry after a failed read. A staffed intercom, separate visitor credential or controlled manual release may be options, but do not promise them until the selected equipment and staffing model are known. Record the reason, operator identity and vehicle/visit reference according to the site’s policy. A fallback that leaves no record can undermine both billing and security.
In hospital parking, patients, visitors and staff may have different reasons for entering. The exception procedure should recognize those roles without making unsupported claims about emergency priority or integration with clinical systems.
Prevent one exception from corrupting the parking record
At a paid facility, a vehicle admitted manually still needs a defined stay record. Decide how the entry time, tariff entitlement and eventual exit are matched. If the plate becomes readable on exit, the system should not silently assume it belongs to an earlier failed-read event without a verified match. Ask how duplicate records, wrong-plate corrections and disputed charges are resolved.
At a permit facility, manual entry should not quietly create a permanent whitelist record. Specify whether the exception is valid for one passage, a visit window or an operator-managed period. These are design questions, not assertions about current Zibor Park software features. The project owner should set who is allowed to correct a plate and who can audit those corrections.
Keep personal data use proportionate to the operating purpose. Plate images and manual notes may contain sensitive details under local privacy rules. Define access, retention and correction responsibilities with the site owner and legal advisers rather than collecting every possible image indefinitely.
Test the real causes, not just a perfect plate
Commission with representative vehicle heights, plate styles and day/night conditions. Deliberately include permitted and unpermitted vehicles, glare-prone approach angles and an unreadable test case. Observe both the driver message and the operator record. Where possible, review actual image quality before changing recognition settings; increasing sensitivity can change false-match behavior.
Include the downstream gate in the acceptance test. A recognized plate must still produce the intended authorization decision; a command to open must be checked against the gate’s actual state. Test a lost network or camera connection through the manufacturer’s approved procedure, and record whether staff receive a clear fault indicator. The Axis license-plate capture white paper supports the general need for proper imaging and lighting, not any specific Zibor Park recognition rate.
Put the exception owner in the handover pack
A useful handover has a one-page decision tree, site contacts, operator permissions, the evidence to record and the procedure for restoring normal operation. Include a periodic review of exception counts by lane and time of day. A recurring pattern points to a configuration or site issue; individual one-off cases may simply need staffed assistance.
Send us the entry and exit workflow, lane images and expected visitor/permit rules when discussing an ANPR project. We can review the relevant parking equipment with your integrator, then identify which exception functions must be demonstrated by the actual proposed system.