A residential complex with 54 flats, 58 parking spaces, and a shared Excel file that three property managers ago was last kept properly up to date. Twenty-seven plates on the list belong to former residents. Eleven current residents aren't on it because they bought a new car, sent an email, and heard nothing back. The barrier opens for people with no right to be there and stays shut for people who've had that right for months.
Revtek · 16 June 2026
A licence plate whitelist is simply a list of plates that have access rights to your site. The ANPR camera reads each arriving plate; if it's on the list, the barrier rises. If not, it stays closed. The technology is a solved problem. The challenge is the list itself: who should be on it, who needs to come off it, and who is actually responsible for keeping it current.
In many complexes, that responsibility falls to the property manager or the residents' association board. They have other things to do. The result is a list that's accurate at handover and then slowly drifts — until enough complaints accumulate to justify going through it again from scratch.
A complex with 50 residential units typically has 60 to 70 registered vehicles at any given time. In the Netherlands, residents move on average once every seven years — which means in a building of that size you can expect 7 to 9 changes per year: new residents moving in, old ones leaving, new cars, sold cars, changing company lease vehicles.
Each of those changes requires someone to update the list. In practice the sequence goes: the resident sends an email, the manager processes it when they have a moment, the change is made, the barrier works again. But between the email and the update, the resident buzzes their neighbour's flat three times to get in. And the person who left two months ago can still drive into the car park.
The problem is not the technology. It's the process around it. A whitelist maintained by email and a spreadsheet has structural friction built in — and friction means delay.
The better approach is to give residents direct control over their own plate registration, within limits you set. One parking right, one active plate per right. A resident buys a new car, updates their plate via a portal or WhatsApp message, and the change takes effect immediately. No email to the manager, no waiting.
Modern systems tie these limits to each parking right: you define how many plates a given flat may register at any one time. Some complexes allow two plates per household, others one. Residents manage their own entries within those rules; the manager sees in the dashboard exactly who has registered what.
For the manager this means fewer manual requests, fewer recurring barrier complaints, and an up-to-date register that residents have maintained themselves. For residential complexes, this is one of the most meaningful practical improvements over fob or code-based access.
The whitelist isn't only for permanent residents. Visitor access is one of the most-used features in practice. A resident generates a temporary access link via the platform or via WhatsApp — the visitor enters their plate number, it's added to the list for the configured period, and removed automatically when it expires.
No call to the manager, no explanation at the barrier, no sign reading "ring this number". The resident handles it in 30 seconds. The visitor drives straight in.
For complexes with paid visitor parking this can be taken further: the visitor pays via Mollie, their plate is authorised for the paid duration, and the transaction is logged. The association gets a complete picture of visitor traffic and revenue — with zero manual steps.
A consistent blind spot in many management setups: removing access is treated as optional, something that gets done "at some point". But a departed resident's plate that still has access two months later is a real security gap — and a source of frustration for the new resident who hasn't been added yet.
In a properly configured system, the move-out date is the trigger. Once the property manager logs a departure date, the associated plates are removed from the list on that date. Not when someone remembers. On the day it's supposed to happen.
For complexes that also use Paxton for building access alongside parking, the combination is particularly clean: the Paxton–ANPR integration means a single departure action removes access to the building entrance and the parking barrier at the same time. Two systems, one action.
The operational gain from automated whitelist management doesn't primarily show up as cost savings — though there are some — it shows up as an absence of small daily friction: the call to the manager because the barrier won't open, the AGM agenda item about a former neighbour still using visitor bays, the new resident who three months in still hasn't been added to the system.
For the manager: fewer ad hoc requests, fewer recurring issues, and an audit log showing exactly who had access and from when. That last point matters for more than tidiness: if there's ever a dispute about unauthorised access, you have a timestamped record — not a spreadsheet with "last edited" set to eighteen months ago.
The Revtek platform manages the whitelist from €175 per month per site. The list is unlimited — no per-plate cost. Every change is logged with a timestamp and the user who made it. Access reports are available per site, per resident, and per period.
A well-managed whitelist is invisible in operation: the barrier opens for the right people and stays shut for everyone else. That sounds obvious. The reason it's not the default is that a spreadsheet and good intentions aren't a management system.
Book a free demo and find out what Revtek can do for your site.
Book a demoOr email us at info@revtek.nl