Close matches: why I and 1 cause disputes
How look-alike characters lead to wrong calls in the lot, and how a plate lookup can flag them first.
On this page
One character, two different cars
Take two plates: TST-1234 and TST-I234. On a screen they’re clearly different. On a dusty plate in a dark garage, read by flashlight at the end of a long shift, they’re easy to confuse. The same goes for O and 0.
Plate issuers know it. California’s DMV refuses personalized plate requests that use 1 and I, or 0, O and Q, interchangeably. In 2026 Pennsylvania added a slash through the zero on its plates to tell it apart from the letter O, and PennDOT acknowledged that some plate reader cameras may at first have trouble telling an eight from a zero. If DMVs and cameras have to design around look-alike characters, a person reading a plate by flashlight will sometimes get one wrong.
Misreads aren’t the only source. Residents sometimes mistype their own plate when they register. Either way the result is the same: the plate in the lot doesn’t exactly match the plate in the record, even though the car is allowed to be there.
How a misread becomes a dispute
When a lookup is a plain yes or no, a single wrong character turns a resident with a valid permit into a “not registered” result. If action follows, the dispute that comes after is hard on everyone. The resident knows they registered. The partner knows what the lookup said. The property team is left to work out who was right, often without a shared record.
The fix isn’t to ask people to read plates more carefully. It’s to have the lookup notice when a plate is almost a match.
What a close-match flag does
When the plate you enter isn’t registered but one that looks almost the same is, the lookup tells you before you act. Look-alike characters like I and 1 or O and 0 are flagged in every patrol lookup.
Three answers, always with the reason
A Laneo patrol lookup returns one of three results, and each comes with a reason and a sensible next step. Tow accounts see only whether the plate is valid.
| Result | What it means | Next step |
|---|---|---|
| Valid | The plate has an active resident permit or guest pass at this property. You see which one, and when a guest pass ends. | Nothing to do. The plate belongs here. |
| Not valid | No active permit or pass right now. The lookup shows why, for example a guest pass that ended at 11 PM. | Follow your agreement with the property, and log what you see. |
| Close match | This plate isn’t registered, but one that looks almost the same is. It might be a misread or a typo. | Check the plate again before any action. |
The reason matters as much as the result. Each property sets its own rules, and the lookup shows the ones that matter for that plate, like when a guest pass ended or how many nights in a row a guest has stayed. Partners work from the same rules as the property.
Write it down
Close matches are exactly the kind of moment worth recording. Partners can log what they see with photos and notes. Each entry keeps the plate, the property, the time and the lookup result, and the property team sees the same log. Every lookup is also saved to the audit trail, with who looked up which plate and when.
If a resident did mistype their plate, they can fix it with a free plate swap in the app, which removes the close match for next time.
Who decides
A close-match flag is information, not a decision. Laneo shows whether a plate is valid. Towing and booting decisions belong to the property and its licensed partner, under their agreement and local rules, and no money is tied to tows.
See how plate lookup works for partners on the enforcement partners page.
Sources
- Vehicle Industry Registration Procedures Manual §21.180: personalized configurations, mandatory refusal, California Department of Motor Vehicles.
- 0 and 8 on new PA license plates causing confusion for recognition tech, NBC10 Philadelphia, 2026.
See it with your property’s numbers.
We’ll model guest revenue with your spaces and rules, and walk through the resident, guest and partner flows.