The wrong mobile LPR purchase leaves a property with the same parking issues and a new invoice. Staff may still stop at every vehicle, cover only part of the lot, and depend on guests to report problems after they happen. Unauthorized vehicles remain difficult to find, repeat violators face inconsistent consequences, and leadership wonders why the new “enforcement” feature has not reduced the workload.
That happens because mobile license plate recognition is no longer a single category of technology. A vendor may describe fixed entrance cameras, camera arrays mounted on a dedicated vehicle, one-at-a-time photo capture, or continuous smartphone scanning with the same three letters. Those systems have different costs, coverage, staffing needs, and operating results.
Properties should evaluate mobile LPR by the pain it must remove. Can the team cover the property frequently enough to change driver behavior? Can it find unauthorized vehicles before a problem arises? Can it move efficiently from an observed plate to a documented response? If the answer is no, the technology has not solved the operating problem.
Vert began as a computer-vision company specializing in mobile LPR. Its continuous scanning is native to a complete platform for permits, guests, assignments, payments, private parking violation notices, appeals, and towing workflows. These capabilities are included in the subscription. The questions below help buyers determine whether a proposed system will actually stop the recurring burden or merely digitize another step.
Questions About Capture and Patrol
1. Does the system scan continuously while the patroller moves?
Ask for a direct demonstration. Continuous scanning should not require the user to tap a shutter for every vehicle.
2. Can it support a real drive-through patrol?
The vendor should demonstrate a safe, representative route rather than show a single parked vehicle. Confirm mounting, speed guidance, and how flagged vehicles are reviewed.
3. How does a walking patrol work?
Observe how often the patroller must stop, aim, tap, or correct results. A mobile workflow should reduce device interaction.
4. How many vehicles can a team cover in a typical patrol?
Request measured results for a property similar in size and layout to yours. Define whether the metric counts attempted, observed, or confirmed plates.
5. Can the system scan both sides of an aisle?
Device placement and route design affect coverage. Ask what configurations are supported and how the property should plan lanes.
6. What happens in garages or low-connectivity areas?
Confirm whether scanning, record access, and queued activity remain usable when service is weak, and how data synchronizes later.
Questions About Accuracy and Computer Vision
7. How is read performance measured?
Useful measures include capture rate, confirmed character accuracy, false-alert rate, missed-plate rate, and time to review uncertain reads. Ask for methodology, not a headline percentage without context.
8. What conditions are included in testing?
Look for night and daylight, glare, shadows, angled vehicles, close spacing, dirty or damaged plates, mixed jurisdictions, and garage transitions.
9. Does the system use multiple frames or a single image?
Continuous systems can use repeated observations to select stronger evidence. One-at-a-time capture depends heavily on the quality of one image.
10. How are low-confidence reads handled?
The system should make uncertainty visible and support human review before significant action.
11. How does the technology improve over time?
Ask how computer-vision updates are tested, deployed, monitored, and communicated. Vert’s positioning emphasizes a software foundation that can improve without replacing dedicated camera hardware.
12. Can the vendor run an onsite pilot?
A realistic pilot is more persuasive than a staged video. Use known test vehicles and repeat the same route under multiple conditions.
Questions About Data and Authorization
13. Is LPR native to the parking platform?
Determine whether the vendor owns the scanning technology and data model or relies on a third party. Native capability generally reduces handoffs and support ambiguity.
14. How quickly do permit changes reach the patrol workflow?
A new plate, expired guest, move-out, payment, or assignment change should be reflected quickly enough to avoid incorrect alerts.
15. What records are checked after a plate is read?
The system should consider resident permits, guests, assigned spaces, paid parking, time restrictions, zones, and relevant exceptions.
16. What evidence is stored?
Ask about image handling, timestamp, location, plate result, confidence, device activity, and retention. The policy should balance operational need with privacy and security.
17. How are permissions controlled?
Patrollers should have access only to the information necessary for their role. Review role-based access, audit history, device controls, and offboarding.
Questions About Private-Property Enforcement
18. What happens after an unauthorized vehicle is identified?
The answer should go beyond “call a tow.” Look for configurable warnings, privately administered parking violation notices, fines where permitted, documentation, and escalation.
19. Can the team issue printed and digital notices?
Ask the vendor to show both workflows, including evidence, delivery, numbering, status, and the connection to the vehicle history.
20. Is an appeal workflow included?
An appeal should connect the driver’s submission, original evidence, property review, decision, and final status without relying on scattered email.
21. Can the system identify repeat violations?
History should help authorized personnel apply property rules consistently and distinguish an appropriate first warning from repeated abuse.
22. How does the platform support towing?
The workflow should document the property’s authorization and relevant history without implying that software replaces posted rules, lease terms, towing laws, or required notices.
23. Does the notice design clearly reflect private property?
Avoid municipal-looking colors, seals, badges, terminology, or layout. The vendor should support clear property branding and a private review process.
Questions About Cost and Accountability
24. Is continuous mobile LPR and violation management included in the subscription?
Ask for a written list of included modules, device limits, scan limits, printing costs, integrations, support, and fees. A low base price can become expensive if effective patrol requires another product.
25. Who owns the complete outcome?
When a permit update, plate read, notice, payment, or appeal fails, determine whether one provider resolves it or the property coordinates several vendors.
Evaluation Scorecard
Category | Weight | Evidence to request |
Continuous patrol performance | 25% | Walking and drive-through field test |
Accuracy and review | 20% | Documented methodology and seeded-route results |
Native authorization matching | 15% | Live permit and guest updates |
Private-property workflow | 20% | Notice, appeal, payment, and tow demonstration |
Total cost | 15% | Three-year written cost model |
Security and support | 5% | Controls, retention, service ownership |
Adjust the weights to match the property. A community with a large open lot may assign more weight to drive-through productivity; a dense assigned garage may emphasize location and space accuracy.
How to Run a Fair Vendor Pilot
Choose a representative area and seed known scenarios: authorized permit, valid visitor, expired visitor, unregistered vehicle, wrong assigned space, and vehicle with prior activity. Have every vendor use the same route and devices appropriate to its workflow. Record time, coverage, confirmed reads, misses, false alerts, manual interactions, and time to complete the response record.
Before acting on any real vehicle, validate property policy and applicable requirements. A technology evaluation is not authorization to issue fines or tow.
Frequently Asked Questions
Is a mobile phone camera automatically mobile LPR?
It may read plates, but buyers should distinguish continuous scanning during movement from one-at-a-time photo capture.
Should the highest accuracy percentage win?
Not without a shared test method. Coverage, conditions, review workload, and connection to authorization data determine operational performance.
Do properties need dedicated LPR hardware?
Not necessarily. Vert provides continuous mobile LPR on supported ordinary mobile devices, avoiding dedicated LPR vehicles or fixed-camera dependence for patrol.
What should a buyer ask about pricing?
Ask what is included in the subscription and model the full cost of hardware, integrations, patrol labor, outside services, payment fees, and administration.
How should a property address legal and compliance questions?
Review lease terms, posted rules, privacy practices, consumer-protection requirements, towing laws, and state or local rules with qualified counsel. Private notices should never imply government authority.
Put Vert's Mobile LPR to a Real Test
Demo Vert's continuous mobile LPR as part of the complete parking workflow, not as a standalone camera feature.
Use the 25-question checklist to expose whether a vendor can stop the problems—not merely read one plate.
or
