Right-sizing in the Netherlands: WMCO, UWV, and why the timeline is longer than the board thinks.

Belgian founders underestimate the Renault procedure. Dutch founders underestimate something else entirely. In the Netherlands the sequence is not what slows you down. It is that the law decides who leaves, and you do not.

If you are right-sizing a Dutch engineering organisation, there are 3 things to get straight before you build a plan around them.

1. WMCO: 20 people, 3 months, one region

The collective dismissal notification act applies when you intend to end 20 or more employment contracts for business-economic reasons, within 3 months, inside one UWV working region. The count includes every route out: UWV permission, court dissolution, and settlement agreements. That last one catches people. Founders assume that if everyone signs a settlement agreement voluntarily, there is no collective dismissal. There is. The agreements count towards the 20.

You notify UWV and the trade unions, and you consult the unions. A waiting period of 1 month runs from the notification before terminations can take effect, unless the unions confirm they have been consulted and waive it. In practice that waiver is available, and getting it is a negotiation, not a formality.

2. The works council has an opinion and it has teeth

At 50 or more employees you have a works council, and a reorganisation of this size needs its advice. Not its approval, its advice, sought at a moment when it can still change the decision. Ask too late and the advice is worthless and the council knows it.

Deviate from a negative advice and you sit on your hands for a month while the council decides whether to take you to the Enterprise Chamber. I have watched that month cost more than the cut saved. The way through is not legal cleverness. It is having a defensible answer to the only question the council really asks, which is why this shape and not a smaller cut.

3. Afspiegeling: you do not pick

This is the one that reorders your plan. For business-economic dismissals, the reflection principle decides who goes. Within each group of interchangeable roles at a business location, employees are split into 5 age brackets. The dismissals are spread proportionally across the brackets, and inside each bracket the shortest-serving person goes first.

Say that back in engineering terms. You have 18 backend engineers you consider one interchangeable pool. You want to keep the 6 strongest. Afspiegeling does not care which 6 are strongest. It cares about age distribution and start dates. The senior engineer you hired 8 months ago to fix the platform is, on paper, the most dismissible person in her bracket.

There are ways through, and they are narrower than founders hope. A genuinely unique role sits outside the pool. Roles are only interchangeable if they are actually mutually exchangeable in content, required knowledge, level and pay, which is a real question in engineering and worth doing properly rather than assuming. The indispensable-employee exception exists and is small. A collective agreement can substitute its own committee and criteria.

The honest version: define your job architecture before the reorganisation, not during it, because the definitions you can defend are the ones that were already there. A senior platform engineer and a mid-level product engineer are not obviously interchangeable, but you will only win that argument if your levelling framework said so last year.

The two routes, and why most of it settles

You can ask UWV for permission, which takes roughly 4 to 8 weeks per case and requires you to have got afspiegeling right. Or you agree a settlement with each employee. Most Dutch reorganisations run largely on settlements, because they are faster and they let both sides avoid the selection fight.

Settlements are not free. The employee gets a 14-day reflection period after signing. The wording has to keep unemployment benefit intact or nobody signs. And a social plan, negotiated with the unions or the works council, usually sets a payment above the statutory transition payment of one third of a month per year of service. Budget the social plan as the real number, not the statutory minimum.

The timeline the board did not budget for

Add it up. Works council advice, 3 to 6 weeks if you prepared. WMCO notification and union consultation, 2 to 4 weeks running partly in parallel. The 1-month waiting period, or the negotiation to waive it. Social plan talks. Then settlements, individually, with a reflection period each. Realistically 3 to 5 months from first conversation to a smaller org, and the cost savings do not start on day 1 of that.

The pattern I keep seeing

A Dutch scale-up wants engineering from 55 down to 35 and wants it done inside the quarter so the burn plan lands before the bridge closes. Nobody has written a levelling framework. Every engineer has the title Software Engineer, which means every engineer is in one interchangeable pool, which means afspiegeling will hand back a team selected by birth year and start date.

What actually works: spend the first 2 weeks defining roles honestly, defensibly, and with the works council informed rather than ambushed. It feels like the slowest possible start. It is the only version that ends with the team you meant to keep.

When not to start

If you are 1 or 2 people over the WMCO threshold and the extra roles are marginal, look hard at whether a smaller cut done individually gets you the same burn number without the 3-month machine. And if the real problem is that engineering is unfocused rather than oversized, cutting will not fix it. That is a different piece: when to right-size and when not to.

Right-sizing is the work I take on. See right-sizing on the homepage. If the entity is Belgian, the mechanics change completely: what the Renault procedure does to your plan.

Written from patterns I've seen across engagements. If any of it sounds too specific to be general, that's why. This is how the process has run in the rooms I've been in, not legal advice. Get a Belgian or Dutch employment lawyer in the room early.