A property manager in Rotterdam looks after eleven residential complexes. At eight of them, licence plate registration runs on a spreadsheet — several versions, spread across multiple colleagues. When a resident at block 7 moves out, it typically takes weeks for their plate to disappear from all the lists. Multi-site parking management is not complicated — but it has to be systematic, or it falls apart.
Revtek · 4 August 2026
At a single site, parking management is manageable. You know the residents or tenants, the barrier works, and when something changes you update the list. At three sites the admin starts to grind. At ten it's unsustainable.
The problem is almost always fragmentation. Each site has its own approach: one runs a management app, another uses a spreadsheet, a third has a code pad at the barrier. There's no central view of the whole portfolio. There's no way to see at a glance how many unknown plates tried to enter across all sites today. And when something happens at site 4, you're searching for the login credentials to that specific system — if you can even find them.
This is not an edge case. Organisations that have built their parking portfolio through acquisition or organic growth almost always run into it: separate systems per site, separate reports, no shared definition of who actually has access.
Revtek manages ANPR parking across multiple sites from a single dashboard. That sounds straightforward, but it has concrete consequences for how you work day to day.
Licence plate whitelists are held per site, but you manage them from the same screen. A new resident at block 7 is added in the same dashboard where you handle blocks 1 through 11. You don't log in again or switch environments — you select a different site in the same menu.
Unknown-plate alerts arrive centrally. If on a weekday morning an unusual number of unrecognised vehicles turn up at three sites simultaneously — perhaps because there's an event nearby or a local parking ban in force — you see it at once, without logging into each site separately to check.
Not every team member needs to see every site. The dashboard lets you set per user which sites they can manage and what actions they can perform. A site manager for block 3 sees only block 3. A regional manager sees the four sites in their area. The portfolio manager sees everything.
This also matters for auditing. If a plate is added or removed incorrectly, the logs show who did it, when, and at which site. No hunting through email threads or chat history afterwards.
Every ANPR camera logs entries and exits. Across multiple sites, that produces insight that a single site cannot provide: which complex has the highest proportion of unknown plates (possibly a enforcement problem)? Which site has the busiest peak hours — useful if you're considering introducing paid parking or visitor time slots?
That reporting is available as an export or a live dashboard for the manager who reports periodically to a VvE board or client. You don't need to log into each site and manually merge data into a spreadsheet.
For commercial operators this matters equally. An investor with five office buildings across the Randstad who lets parking spaces wants a consolidated view of occupancy and usage — even when those buildings are in the same system but administered as separate units. See the commercial car parks page for what that reporting looks like at site level.
One dashboard does not mean one policy. Each site keeps its own licence plate whitelist, its own visitor rules, its own barrier hours and — where paid parking applies — its own rates. Those settings are configurable per site.
That's the point. You don't want a system where you have to re-enter the basic configuration every time, but you also don't want one that forces every site to work identically. A residential complex operates differently to a commercial car park on a business estate. The office buildings page gives a sense of the specific settings relevant in that context.
Switching to a central platform makes clear sense when you manage three or more parking sites with separate systems or lists, when you need periodic portfolio-wide reports for a board or client, or when you want to assign site managers without giving them access to the entire portfolio.
It also makes sense when you're processing frequent resident or tenant changes and no longer want to maintain two or three separate systems in parallel. That's the point at which managing lists manually costs more than it saves.
Larger residential property managers, commercial operators with multiple buildings, and hotel groups with properties in more than one city are the organisations that encounter this most often. A healthcare organisation with three sites at separate addresses can benefit from consolidated oversight in the same way.
The Revtek subscription starts indicatively at €175 per month per site. For managers with multiple sites, a portfolio arrangement is in almost all cases more favourable than the sum of individual subscriptions. The exact cost depends on the number of sites, the type of entry points and any integrations with existing systems such as Paxton. The pricing page gives a first indication.
What it delivers: fewer admin hours per site, fewer errors during changes, and a single point of contact for support across the whole portfolio — instead of separate conversations with multiple suppliers.
Almost every manager who moves to a central platform begins with the site causing the most problems: the list that's most out of date, the location with the most complaints, or the place where the barrier gets the most manual overrides.
From that first site we build out the rest of the portfolio at whatever pace suits your organisation. We don't do generic demos — we look at your situation and propose an approach that builds on what you already have. Book a call using the button below.
Book a free demo and find out what Revtek can do for your situation.
Book a demoOr email info@revtek.nl