Implementing the Dutch Environment and Planning Act (Omgevingswet) adds a new level of technical and substantive complexity. The STOP/TPOD standards are extensive, validation rules are strict and agreements across the publishing pipeline continue to evolve.
For many suppliers, one component creates a particularly difficult set of puzzles: the Renvooi service.
This service acts as a legal difference engine. It does more than compare text:
- it tracks changes in structure and numbering;
- it determines differences between the @was and @wordt versions;
- it understands when structural elements must be moved;
- it handles the addition or removal of hierarchy levels without breaking STOP validation.
Every change in source data — an amended article, a moved paragraph, a hierarchy adjustment or a consolidation step — can introduce a new edge case. A small error can immediately result in failing STOP validation, delayed publication or repeated correction rounds.
Why rediscover what the pipeline already taught us?
Development capacity should go to features that create value, not endless investigation into:
- ambiguous XML specifications;
- renvooi exceptions that appear to contradict each other;
- modelling element moves between @was and @wordt correctly;
- adding or removing structural levels in legally complex content;
- consolidation sequences that behave slightly differently than expected;
- validation rules that introduce new surprises with each release.
These are the points where capable teams get stuck because legal logic, government agreements and implementation details are deeply intertwined and are not fully documented in one place.
The solution: direct expertise
Siebe Jongebloed has worked on the government side of this pipeline for the past eight years. He developed the Renvooi service and the Decision Preview service now used by almost every supplier in the market.
That experience covers both the technology and its hidden operational assumptions:
- moving structural elements correctly between @was and @wordt;
- safely adding or removing hierarchy levels in existing content;
- recognising assumptions and edge cases that are absent from the documentation;
- understanding how STOP/TPOD is applied in practice.
What Elk Solutions provides:
- Technical deep dives: investigation of difficult renvooi or validation failures in both code and XML.
- Architecture advice: integration of the services into a maintainable application architecture.
- Bridge function: shared language across software suppliers, KOOP and Kadaster, reducing time lost to missing context.
Bring in expertise that helped create these services, so your team can focus on product functionality instead of rediscovering the pipeline.