The three models: a patrolling controller who scans plates and issues fees on the spot; ANPR cameras at entrances that log every vehicle in and out; and pure self-service registration backed by occasional spot checks. Controllers fit areas with occasional, unpredictable misuse. Cameras fit large areas with constant outside pressure. Spot-check self-service fits small, calm associations. Most end with a hybrid: registration as the backbone, controller visits at a frequency the data justifies.
The controller: flexible, visible, per-visit cost
A controller's strength is judgment and presence: they see the moving van that explains the odd parking, talk to the confused guest, and their visits can be concentrated exactly when your data says violations happen. The cost scales per visit, so a calm area is cheap.
The weakness is coverage — a violator who parks between visits is never caught, and if visits follow a fixed pattern, regulars learn it. Vary the schedule, and let the platform's scan history show where and when visits pay off.
ANPR for parking: total coverage, total responsibility
Cameras never sleep: every entry and exit is logged, overstays are computed automatically, and enforcement becomes consistent by construction. For areas bleeding capacity to commuters or shoppers, that consistency is what actually changes behavior.
The price is paid in three currencies: hardware and installation up front; a hard dependency on power, connectivity and lighting; and a data footprint that registers everyone — which raises the GDPR bar substantially. Camera-shaped problems are real, but make sure you have one before buying the solution.
The decision in four questions
- How much outside pressure? Daily commuter parking argues for cameras; occasional strays argue for controllers
- How many entrances? One or two are cheap to cover with cameras; five are not
- What does your GDPR appetite look like? Cameras register everyone; controllers register suspects
- Can you decide on data first? Two months of scan history often settles the question cheaper than a pilot
3
Models: controller, ANPR, self-service + spot checks
1-2
Entrances where camera economics work best
Each extra entrance multiplies hardware
2
Months of measurement before choosing
Decide on data, not anecdotes
What the camera actually returns
A camera does not deliver certainty. It delivers a list. Most rows match a known plate, some are guests, and a few land in manual review.
The size of that last group is the honest measure of what an ANPR setup saves you. Ninety-seven per cent recognition still means someone opens the remaining rows, and that someone is usually a volunteer.
Filter the demo to the unknown plates. That group is what a camera actually puts on your desk.
Plate log
- 09:14Entry · North gateAB 12 345 Resident
- 09:11Entry · North gateQR 71 288 Guest
- 09:03Entry · South gateJK 18 043 Unknown
- 08:57Exit · South gateLM 62 551 Resident
- 08:44Entry · South gateCD 44 118 Resident
- 08:31Entry · North gateST 40 663 To manual
FAQ: Enforcement
Can we start with controllers and add cameras later?
Yes, and it's usually the right order: the registration backbone is identical, so cameras are an add-on, not a migration. The controller months also produce the data that tells you whether cameras are worth it — and at which entrance.
Who can issue the fees — must it be an external company?
In Denmark the formal requirements — appeals-board registration, complaint guidance, delivery on the car — attach to whoever issues the fee, external or not. Some associations run their own controllers on a platform like ours; others delegate to an operator. Choose based on who can meet the requirements consistently.
Do visible cameras deter by themselves?
Initially yes, permanently no. Deterrence decays unless violations actually have consequences — a camera that never results in a fee becomes street furniture within months. Whatever model you choose, the follow-through is the deterrent.