A holiday park on the Zeeland coast with 240 pitches runs at full capacity through August. The barrier opens four hundred times a day. By early September most guests have left — but 31 residents live there year-round. Those residents need to reach their own home on a Tuesday evening in November just as easily as on a Saturday in July. Without that distinction baked into the system, the first weeks of autumn mean daily manual intervention.
Revtek · 11 August 2026
A holiday park typically has three categories of people with access rights: seasonal guests on the basis of a reservation, permanent residents who actually live on site year-round, and staff. During the high season, guests dominate — every pitch is occupied, the rhythm is temporary by nature. When September arrives, that picture shifts completely.
A guest who booked a chalet for two weeks in August has no right of entry after their departure date. That is the contract: time-limited access. More complex is the resident who has lived on pitch 83 for four years and needs to park there in November just as much as in July. Those two groups use the same barrier but have fundamentally different access rights — and a system that cannot tell them apart works poorly for both.
The transition from high season to autumn is not just a logistics task — closing the pool, reduced restaurant hours, winterising the facilities — it is also an access management task. Who still has access after 15 September? When do annual pitch-holders' passes expire? How do you prevent guests who left three months ago from still being able to drive in?
Without automated expiry dates, the answer comes down to one of two bad options: everyone who ever had a pass keeps it until someone manually revokes it, or the barrier effectively stands open for anyone and access control ceases to exist. Both outcomes are undesirable — and both are avoidable.
An ANPR system with time-limited plate lists handles this automatically. A guest with a week's booking in August has access from Saturday to Saturday. That expiry date is in the system at the point of creation, linked to the reservation. On departure day, access lapses without anyone needing to do anything. For a park with two hundred turnovers a week, that is not a nice-to-have — it is the only way to keep the system accurate.
On 3 July 2026, the Dutch Minister for Housing reached agreements with municipalities on protecting people who permanently reside on holiday parks. The agreements cover legalisation and safeguards against displacement — but they also signal how seriously the government now regards this group. According to CBS figures from early 2024, more than 60,000 people are registered as living permanently on recreation parks in the Netherlands.
For the park operator, that has a direct operational consequence. Permanent residents are not seasonal guests and cannot be managed as though they were. Their access does not end when the park closes to tourists. They need to get home at 10 pm in February — without calling the barrier intercom every time.
A combined whitelist — one large list mixing guests, residents, and staff — breaks down under these conditions. It becomes unmanageable, ages quickly, and makes enforcement impossible. The answer is a separate plate list for permanent residents with no expiry date, generating alerts only for exceptions. This gives the operator a clear view of who actually lives on site and prevents residents from inadvertently losing access when seasonal lists are archived.
The power of ANPR at a holiday park is not in the barrier itself — most parks already have one — but in the configurable plate lists and the connection to the reservation system.
When a guest books online, the system collects their licence plate as part of the process. On their arrival date the plate becomes active; on their departure date it lapses. The barrier recognises the vehicle on arrival and opens without any staff involvement. For annual pitch-holders, access runs until the agreed season end date — say, 15 October. After that the plate is inactive, unless the contract has been renewed. That renewal can be processed in the dashboard in a single bulk action for the whole group.
Permanent residents sit on a separate profile with no expiry date. If a resident gets a second car, they register the new plate through the resident portal or via WhatsApp. The plate is active within minutes. When a resident leaves — perhaps they have found other housing — the profile is removed and access lapses immediately, with no pass to collect.
The dashboard shows in real time which plates are on site and which group they belong to: guest, pitch-holder, or resident. An unknown plate — a delivery driver, a resident's visitor — triggers an alert; the operator can grant temporary access or open the intercom from the dashboard without leaving the office.
A transition without communication generates complaints. Guests who assume their pass is still valid. Annual pitch-holders wanting to retrieve belongings after 15 October. Suppliers who need to reach the site while the barrier is closed to unknowns.
WhatsApp is the most direct channel for this — not because it sounds modern, but because it actually gets read. A message to all active guests and annual pitch-holders a week before the closing date — "Your parking access expires on 15 October. Questions? Message us." — prevents dozens of calls to reception. Exception requests, such as a guest needing a one-off return trip after season, are handled through the chat: the operator sees the request, grants temporary access via the dashboard, and the barrier opens when the vehicle arrives.
For a broader look at how the WhatsApp concierge works across the holiday park — check-in, fault reporting, communication with residents outside office hours — see our article on the WhatsApp concierge for holiday parks.
August is the right moment to prepare your access management for the changeover. Four concrete steps:
Separate your plate lists. Check whether permanent residents are on a dedicated list with no expiry date. If they are mixed into a general seasonal list, correct that now — before you archive the seasonal list in one sweep.
Set expiry dates for annual pitch-holders. Choose a date per group — typically end of the recreational season — and enter it in the system. Renewals are then processed per individual or in bulk, not case by case.
Test the rejected-plate message. What does someone see if they try to drive in after the season ends? Is the display clear? Can they easily contact the park? An unhelpful barrier with no explanation produces frustrated former guests.
Communicate proactively. Send a WhatsApp message to all relevant contacts the week before the season closes. Not as a surprise after the fact, but as expectation-setting in advance.
This sounds like a project. With well-structured lists it is an afternoon's work in the dashboard. If the lists are currently one large unstructured mixture, this is the moment to fix that — before the changeover forces the issue. More on how the Revtek platform works for holiday parks is on our holiday park page. Pricing — from €175 per month per location — is on the pricing page.
Book a free demo and see what Revtek can do for your situation.
Book a demoOr email us at info@revtek.nl