At the gate, not in the office Works without a connection Attendance alongside the notification

Custom app development for access control for foreign temporary workers

The notification sits in a portal and the people stand at the gate. As long as the two never meet, your duty to check is an administrative act with no link to who actually walks in. And that comparison is exactly what an inspector makes on site.

Why the comparison belongs at the gate

Foreign service providers notify the Dutch notification portal before work begins about who is coming to work, where and when. As the Dutch client, you must check that notification and report any inaccuracies within five days of the start.

In the office, that is a comparison between two lists. On site, it is a comparison between a list and a person, and that is the only comparison that tells you anything. A crew whose composition changes because someone is ill turns up the next morning with a different person on site while the notification remains unchanged.

That discrepancy arises daily and disappears daily. If you only discover it at the quarterly check, you can no longer pass it on within the deadline, and you cannot prove afterwards who was on site and when. At the gate it takes a few seconds and produces exactly the evidence you need.

How we build this

Here, the access control point is the unit of work. If the comparison with the notification is made there, the duty to check follows from it rather than from a separate administrative round.

1
Look at how people currently get in

A gate, a site hut, a supervisor who nods people through. What happens now determines whether an app gets used or bypassed, more than what the law requires.

2
Bring the notification to the gate

Who has been notified for this project and this period, available offline on the device at the entrance. Without that, there is nothing to compare against.

3
Pass on discrepancies immediately

Anyone who is not in the notification is recorded on the spot and sent as an action to the project manager. The five-day deadline is already running.

4
Build up evidence without extra steps

The checks at the gate automatically produce an attendance record. That is a second benefit for which nobody has to do anything extra.

What the app actually does

The app makes one comparison and must always be able to make it. Which components you need depends on how your site is set up.

Check a person against the notification

Scan a pass or search by name and see whether this person has been notified for this project and this period. The answer is green or red, not a list someone has to search through.

Document validity taken into account

Alongside the notification, identity documents and, where applicable, social security declarations come into play. Anything expired blocks entry; anything about to expire triggers a warning.

Record discrepancies on the spot

Someone who has not been notified, or a period that does not match. The notification is assigned an owner and reaches the project manager, because your deadline to correct it runs from the start of the work.

Working fully offline

At a gate on a building site or in a warehouse, there is rarely any signal. The app keeps the notification list locally and syncs later, showing clearly which checks are still outstanding.

Attendance as a by-product

The checks show who was on site and when. That is useful during an inspection, after an incident and when asking how many people actually worked.

Connecting to your own register

The notification data comes from the register where your service providers submit it, via integrations. That side runs on WagwEU software.

Who we build for

How access is organised determines the design. Four situations.

Building sites with a gate

There is often already access control with passes. The comparison with the notification is added there as a layer, so your people do not do the same thing twice.

Production sites with seasonal peaks

Large numbers arriving at the same time and changing quickly. Speed at the check determines here whether it gets done or the queue grows too long.

Distribution centres and loading docks

Short stays, many different parties and drivers who do not always fall under the same scheme. What does and does not need to be notified is for your legal team to decide; the app applies that rule.

Sites without a fixed gate

A job in an existing building, with no fence and no gatekeeper. The site supervisor then does the check on their own device, and the app has to work in a few taps, just like a field service app.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

The app is the field side of your notification register, not a second administration. What it records ends up in the same file you use to demonstrate your duty to check.

React Native or native iOS and Android Offline notification list per project Pass scan or search by name Validity checks on documents Discrepancy with owner and deadline Attendance registration from the checks Integration with the notification register Integration with existing access control Roles per project and per location Limited offline storage of personal data Remote management of the device Works with gloves on and in bright light Audit logging per check Hosting in the EU

Why Appfront

The only comparison that tells you anything

Laying two lists side by side can be done in the office. Laying a list next to a person can only be done on site, and that is what an inspector does too.

The deadline is already running while you find out

We pass the discrepancy on to the project manager immediately, because five days after the start is short if the finding only comes up at the monthly check.

There is no signal at a gate

Offline is the starting point. An app that stalls there gets replaced by a nod from the site foreman, and then the check does not exist.

As little as possible on the device

What is on display at the gate concerns people who are not employed by you. We only show what the check requires and store no more than necessary.

Security and privacy

A device at a gate holding names, nationalities and document details of people who are not employed by you calls for restraint. You process this data on the basis of a legal obligation, which means you may not show more than the check requires. We limit the offline list to the project and the period in question, avoid showing document numbers where a name will do, and make sure a lost device can be disconnected remotely.

There is also something else that affects the design. The person being checked is dependent and often does not speak the language, and the person doing the checking is not their employer. What the app shows must therefore be factual and limited: notified or not notified, valid or expired. Notes about behaviour or suitability do not belong there, and we do not build a field for them. What the app does record must be immutable, because it is your evidence. How we handle security ourselves is set out in our information security policy; reports from outside go through our coordinated vulnerability disclosure (CVD) policy.

Frequently asked questions about access control for subcontracted labour

Whether you may deny someone access depends on your contract with the service provider and on your own site rules, not on the notification obligation itself. What the law asks of you is to check and to pass on inaccuracies. What you then do about access is a choice you define in advance; agree this with your lawyer.

Yes, that is the starting point. The notification list for the project is stored locally on the device and the checks sync as soon as there is a connection. Without that, the app gets bypassed during the first morning rush and the check still does not exist.

Often it can, and that is preferable to a second system at the same gate. If you already work with passes, the comparison with the notification is added there as a layer. Whether that is possible depends on your current installation; we map that out beforehand.

That is exactly what this is for. The notification is a snapshot and the crew is not. Every discrepancy at the gate becomes an action towards the service provider, who can amend their notification, and you can demonstrate that you identified it and passed it on.

Yes, as a by-product of the check. That is useful during an inspection, after an incident and for the question of how many people actually worked. If you also want to attach hours to it, that is a different kind of system with its own requirements; we deliberately keep the two separate.

Then you spot it at the gate, which is better than not spotting it at all. The discrepancy goes to the project manager and to the service provider, with the deadline attached. Your evidence is not that everything was correct, but that you checked and followed up.

This app is the field side: the comparison at the gate. The WagwEU software is the register, with the portal for your service providers and monitoring of the five-day deadline. They share a single data source.

That depends on the number of sites, whether it integrates with existing access control, and how demanding the offline functionality is. Checking against the notification list is usually quick to put to use; integration with gate hardware costs more. We give a well-founded estimate after the discovery phase.

Checking where people enter?

Go to the gate tomorrow morning and ask whether the crew is the same as in the latest notification. The answer to that question is what you cannot demonstrate right now. We build this as a standalone app and as part of a broader custom app or custom software project.

Edit content