Your configurator is "suitable for" monitoring. In Dutch law, that is the whole question.
When we talk to a Dutch manufacturer about a production or quoting system, the works council rarely comes up on the first call. It comes up on the third, usually as a surprise, usually when the project is already built.
The surprise is avoidable, because Dutch law is unusually plain about when the ondernemingsraad has to be involved. The trouble is that the plain words are broader than almost anyone expects.
"Or suitable for" is written into the statute Article 27(1)(l) WOR · personeelsvolgsysteem · article 27(1)(k) WOR · processing of personnel data · instemmingsrecht
German law reaches the same place through fifty years of case law about what a system is objectively capable of. Dutch law puts the test directly into the statute and Dutch case law has developed how that test is applied. That makes it easier to state and harder to argue your way around.
Article 27 of the Works Councils Act (WOR) gives the works council a consent right an instemmingsrecht over the introduction, amendment or withdrawal of certain arrangements. Two of the listed grounds matter here.
Under (k), the consent right covers any arrangement concerning the processing and protection of the personal data of the people working in the undertaking.
Under (l), it covers arrangements for facilities that are "aimed at or suitable for" the observation or monitoring of the presence, behaviour or performance of those people in Dutch, gericht op of geschikt voor. Those systems are the personeelsvolgsystemen, the staff-monitoring systems.
Article 27 does not turn every piece of software into a works council matter. The question is whether a proposed decision establishes, changes or withdraws a regulation or facility a regeling falling within one of the matters the provision lists, and, for staff-monitoring facilities, whether it concerns all or a group of the workforce
Read the two words in (l) again: or suitable for. Not "intended for." Not "used for." Suitable for. A system can fall under the consent right even where nobody intends to monitor anyone, on the sole ground that it could be used that way.
Now apply that to a factory system. A quoting configurator with user logins is suitable for seeing who handled which enquiry and how long they took. An MES is suitable for showing throughput per operator. A production planning system is suitable for showing whose station a job stalled at. None of these is a monitoring system in intent. Every one of them is suitable for monitoring, and under Dutch law that is the test.
Add (k) on top: the same systems process personal data of staff names, logins, timestamps and an arrangement about processing that data is independently subject to consent. Most factory systems engage both grounds at once.
The Dutch question is not "did you build a monitoring system." It is "could this system be used to monitor." For a system with user accounts, timestamps or other employee-linked data, check the Article 27 test early: if the system is objectively suitable for observing attendance, behaviour or performance across a group of staff, plan for the consent procedure
This is a veto, not a consultation
It is worth being precise about how this right works, because it works differently from the German comparison people often reach for The employer must put the intended decision to the works council in writing, with reasons, and must discuss it with them at least once. Without the council's consent, the arrangement cannot lawfully be introduced. If the council refuses, the employer's route is not to proceed anyway but to ask the sub-district court the kantonrechter for substitute authorisation. The court may grant it where the council's refusal is unreasonable, or where the proposed decision is required by compelling organisational, economic or social reasons.
And there is a sanction with real teeth. If the employer introduces the arrangement without asking for consent, or after consent was refused and without the court's authorisation, the works council can invoke the nullity of the decision in writing. That right is subject to a statutory one-month period running from when the council learns of the decision. If the council validly invokes nullity within that month, the decision is void as though it had never been introduced. The nullity is not automatic; the council has to claim it, and in time.
For a software project that is a specific and expensive risk. A system rolled out without the required consent is not merely politically awkward. The decision to introduce it can be struck down after go-live, after training, after the old process was dismantled.
Projects don't stall on refusal. They stall on the questions.
This is the same pattern we describe for the German Betriebsrat, and it holds here for the same reason: the delay is not produced by conflict, it is produced by unanswered questions between meetings.
A Dutch works council assessing a personeelsvolgsysteem does not usually start from opposition. It starts from a checklist — and a good one, because the guidance available to Dutch councils on exactly this question is detailed. It asks: which personal data does the system record? Who can see it? How long is it kept? Could it produce an assessment of an individual's performance? Is that prevented in the software, or only promised in a policy?
These are answerable questions. They are answerable in an afternoon by whoever built the system, and not at all by a salesperson with a slide deck. When the answer is "we'll send that on," in practice that can push the question to the next council meeting rather than the project's timetable.
The delay, in other words, is often a documentation problem wearing the costume of a legal one. Close the documentation gap and the legal discussion can become much more focused.
Consent from the council is not consent under data protection law
One point that trips up projects: getting the works council's instemming does not discharge the employer's obligations under the AVG, the Dutch name for the GDPR. They are two separate tracks that happen to run over the same system. The council's consent is about the arrangement as a matter of employee participation. The AVG governs whether the processing is lawful at all a legal basis, proportionality, data minimisation, retention limits, and a genuine assessment of whether a less intrusive design would achieve the same purpose. A works council that knows its job will ask about both, and will expect the employer to have done the AVG analysis before the consent request, not after.
The practical consequence for system design is the same for both tracks, which is the useful part. A system that records only what it needs, shows performance data aggregated rather than per person, and cannot resolve an individual where it does not need to, is easier to get consent for and easier to defend under the AVG. The design that addresses the council's concerns is often also easier to defend under the AVG though the two assessments remain separate. Design the system so the intrusive version is impossible, not merely unused. A council and a data protection officer both trust a permissions model they can see far more than an assurance they are asked to believe.
The field list before the first council meeting
We supply the field list, the role model and the logging concept before the works council first sits not as an annex to the quotation, but as a working document for the council and any expert it brings in. Where a consent right is engaged, we say so. We would rather tell you a system needs consent than have the decision to introduce it declared void six months in.
Person-related fields disclosed, field by field
Which field, what purpose, which role can see it, how long it is kept. A company that builds the system can produce that list. A company that licenses one often cannot.
The commitments built into the software, not the policy
Reporting aggregated per work centre rather than per person. Role-based permissions where the reporting role cannot resolve individuals at all. Automatic deletion periods. No individual rankings. A council reading a permissions matrix negotiates differently from one listening to a promise.
The AVG analysis available alongside the consent request
Legal basis, proportionality, the less-intrusive alternatives considered and why they were rejected. The same underlying analysis can support both the council's process and the work of the data protection officer.
Success measured beyond go-live
The real test is whether the system is still delivering value in daily use months after go-live. A system whose introduction is voided for want of consent fails that test completely, which is why we settle the consent question before the quotation.
Five questions for any vendor, ourselves included
For anything with user accounts and timestamps, assume yes and plan the consent step in.
If not before the council asks, then when?
The answer determines how the council and the AVG both read the system.
Consent from the council does not replace it, and the council will ask.
Before build, at specification where a change still costs nothing.
This article describes practice from a software builder's perspective and is not legal advice. The assessment of whether a specific system engages article 27 WOR, and of the AVG obligations around it, should be made with Dutch employment and data protection counsel. Official guidance on staff-monitoring systems under article 27(1)(l) is published by the Autoriteit Persoonsgegevens (the OR-privacyboekje, including its assessment questions for personeelsvolgsystemen). This is the third part of a series on works-council obligations across the DACH and Benelux markets, alongside the German Betriebsrat and the Belgian CAO 39.
Works-council cluster read alongside: Germany · Why your configurator becomes a Betriebsrat matter (§ 87 BetrVG) Belgium · Language regime and CAO 39 when introducing manufacturing software Netherlands · this article (article 27 WOR) One theme a system touching employee data triggers a works-council duty nobody planned for under three different laws. The obligation does not transfer between them; each market has its own.
Thirty minutes, one real enquiry.
Bring an enquiry your sales team actually handled. We will walk it from request
to quote, show which personal-data fields it creates, and tell you plainly whether
it engages article 27 even if you carry on with someone else.
You run the factory. Leave the software to us.