Custom STOP integration development
Appfront builds integrations with STOP, the Standard for Official Publications. Government bodies submit decisions and regulations in the STOP format to the Landelijke Voorziening Bekendmaken en Beschikbaarstellen (LVBB, the national publication facility), which publishes them and makes the current version available. We connect your own systems, such as a meeting system or regulations management, to that submission process: converting decisions to STOP, checking them before submission, and sending the status of each publication back into your system.
What is a STOP integration?
Government bodies officially publish decisions and regulations. STOP, the Standard for Official Publications, describes how those publications are drawn up and submitted: the text, the amendments, the metadata, and when something takes effect. The LVBB receives the submission, handles the publication and makes the consolidated, current version available. Government bodies submit via the source-holder interface.
At many government bodies, a decision is drafted in one system, adopted in a meeting system, and then prepared again for publication. Amendments to a regulation have to be submitted in such a way that the consolidated version is correct. An error in the metadata leads to a rejected submission, and the LVBB's feedback ends up in a mailbox nobody monitors. For environmental documents, the annotations under IMOW come on top of that.
We build custom because the integration has to fit your process: where decisions are drafted and adopted, which types of publication you handle, which software you already use, and who is responsible for publication. The standard and the interface are managed by central government; we make sure your systems work with them, and keep working when a new version is released.
From decision to publication
Decisions and regulations from your own system converted to STOP, with the correct metadata and timestamps.
Checked in advance
Checks against STOP and the LVBB's rules before submission, so a publication is not rejected.
Status sent back
LVBB feedback processed, with the status of each publication shown in your own system.
How we build your STOP integration
We start with your publication process: which types of publication, which systems, who does what, and where things currently go wrong.
Your publication types, systems, responsible parties and the version of the standard.
Decisions, regulations and amendments from your systems into STOP, with metadata.
Validation before submission, and submission via the source holder interface.
Status per publication sent back, and maintenance for new versions of STOP and the interface.
What a STOP integration actually does
The components below feature in almost every STOP integration. Which ones you need depends on your publications.
Conversion
Decisions and regulations from your system into STOP.
Changes
Amendments to regulations structured so that consolidation is correct.
Metadata
Timestamps, entry into force and other data.
Validation
Validation against STOP and the rules of the LVBB.
Submission
Submission via the source holder interface.
Status
Feedback and status per publication.
Who we build a STOP integration for
The integration is intended for government bodies and suppliers that publish officially.
Municipalities
Council decisions, ordinances and the environmental plan. Submission is the core.
Provinces and water boards
Ordinances and decisions. Consolidation matters most.
Council clerks' offices
Decisions from the meeting system. What you need is the integration with it.
Software suppliers
Publishing from your own product. The standard is the core.
Technology and integrations
This page is about submission under STOP. For the annotations that go with environmental documents, see our page on an IMOW integration; for the Omgevingswet (Dutch Environment and Planning Act) in general, our page on Omgevingswet software; and for municipalities, our page on software for municipalities. You can read about our approach at custom software development.
For building environmental documents according to the correct application profile, see our page on a TPOD integration.
For preparing and bundling amendments to the environmental plan before submission, see our plan amendment tool for the environmental plan.
Why choose Appfront for your STOP integration?
A publication that gets rejected pushes back the entry into force. That is what we build around: decisions that come from your own system, validation up front, and a status you can follow.
Fewer rejections
Errors show up before submission.
No duplicate work
The decision goes out from the system in which it was made.
Status at a glance
You can see where each publication stands.
Security and privacy in a STOP integration
The integration processes decisions that may be confidential before they are published. Access credentials for the interface are stored encrypted and used only by the integration, and every submission is logged.
The integration runs in a European data centre or in your own environment, with encrypted storage and daily backups.
Frequently asked questions about a STOP integration
Questions that government bodies and suppliers ask before they get started.
The Standaard Officiële Publicaties (Standard for Official Publications) describes how government bodies draw up and submit decisions and regulations for publication. It defines the text, the amendments and the metadata, so that the Landelijke Voorziening Bekendmaken en Beschikbaarstellen (national publication facility) can publish them and show the current version.
The Landelijke Voorziening Bekendmaken en Beschikbaarstellen (national facility for publication and availability) receives publications from government bodies, takes care of the announcement and makes consolidated regulations available. Government bodies submit via the source holder interface.
STOP covers the text and the publication of decisions and regulations. IMOW describes the annotations that go with environmental documents, such as activities and locations. For environmental documents the two are used together; IMOW has its own page.
Yes. Every submission is checked against STOP and the LVBB's rules before it is sent, with clear messages about what is wrong. That way an error is fixed before the entry into force is put at risk. After submission, the LVBB's confirmation of the publication comes back into your system, so you can see whether it has been processed.
Yes, if that system has an interface or export. An adopted decision then goes from the meeting system straight into the submission, without being prepared again. The clerk's office can see in the same system when the decision has been published.
STOP and the interface are updated regularly. As part of maintenance, we adapt the integration accordingly, so your submissions keep working. We test a new version in a test environment first, before it is used for real publications.
For government bodies with their own systems for decisions or regulations for which no standard solution exists, and for suppliers who need to support STOP in their product.
Decisions from your own system to the LVBB?
Tell us which publications you make, in which systems decisions are created and how you currently submit them. We'll show you what the integration looks like.