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 duties, so a list that is accurate at handover slowly drifts until enough complaints build up to go through it again.
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, so 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. Usually the resident sends an email, the manager processes it when they have a moment, and the barrier works again. Until then the resident buzzes a neighbour to get in, while someone who moved out two months ago can still drive into the car park.
The delay comes from the process. A whitelist kept by email and spreadsheet needs manual work for every change, and that work gets postponed.
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 is also widely used for visitors. A resident creates a temporary access link via the platform or WhatsApp. The visitor enters their plate, which goes on the list for the configured period and comes off again automatically.
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 sees visitor traffic and revenue without any manual work.
Many management setups put off removing access. A departed resident's plate that still works two months later is a security gap, and the new resident who has not been added yet is left frustrated.
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 and 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.
Automated whitelist management saves some money, but mainly removes small daily annoyances: 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 is a dispute about unauthorised access, you have a timestamped record instead of a spreadsheet last edited eighteen months ago.
The Revtek platform manages the whitelist from €175 per month per site. The list is unlimited, with 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