Custom STOP integration development
Appfront builds integrations with STOP, the Standard for Official Publications. Government bodies submit decisions and regulations under STOP to the Landelijke Voorziening Bekendmaken en Beschikbaarstellen (National Facility for Publication and Availability), which publishes them and makes the applicable version available. We connect your own systems, such as a meeting management system or regulations management, to that submission process: converting decisions to STOP, checking them before submission, and returning the status of each publication to your system.
What is a STOP integration?
Government bodies officially announce decisions and regulations. STOP, the Standard for Official Publications, describes how those publications are drafted and delivered: the text, the amendments, the metadata, and when something takes effect. The Landelijke Voorziening Bekendmaken en Beschikbaarstellen (LVBB, the National Facility for Publication and Availability) receives the submission, handles publication and makes the consolidated, currently valid version available. Governments submit via the bronhouderkoppelvlak (the source-holder interface).
At many government bodies a decision is drafted in one system, adopted in a meeting management system, and then prepared again for publication. Amendments to a regulation must be submitted in a way that keeps the consolidated version correct. An error in the metadata leads to a rejected submission, and the LVBB's feedback lands in a mailbox nobody monitors. For environmental documents, IMOW annotations come on top of that.
We build custom software because the integration has to fit your process: where decisions are drafted and adopted, which types of publication you issue, which software you already use, and who is responsible for publication. The standard and the interface are managed by the national 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 returned
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 converted to STOP, with metadata.
Checks before submission, and submission via the bronhouderkoppelvlak.
Status per publication reported back, and maintenance when new versions of STOP and the interface are released.
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 to STOP.
Changes
Amendments to regulations so that the 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 bronhouderkoppelvlak.
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, bylaws and the environmental plan. Delivery is the core.
Provinces and water boards
Regulations and decisions. Consolidation matters most.
Council clerk's offices
Decisions from the meeting-management system. Connecting to it is what's needed.
Software suppliers
Publishing from your own product. The standard is the core.
Technology and integrations
This page is about submitting publications under STOP. For annotations on environmental documents, see our page on an IMOW integration; for the Environment and Planning Act (Omgevingswet) in general, see our page on Environment and Planning Act software; and for municipalities, our page on software for municipalities. You can read about our approach at getting software built.
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 delivery, see our environmental plan amendment tool.
Why Appfront for your STOP integration?
A publication that is rejected postpones its entry into force. We build around that: decisions that come from your own system, validation up front, and a status you can track.
Fewer rejections
Errors are caught before delivery.
No duplicate work
The decision comes 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 handles decisions that may be confidential before publication. Access details 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 start.
The Standard for Official Publications describes how government bodies draw up and deliver decisions and regulations for publication. It records the text, the amendments and the metadata, so that the Landelijke Voorziening Bekendmaken en Beschikbaarstellen (National Facility for Publication and Availability) can publish them and show the version in force.
The Landelijke Voorziening Bekendmaken en Beschikbaarstellen (National Facility for Publication and Availability) receives publications from government bodies, handles publication and makes consolidated regulations available. Governments submit via the bronhouderkoppelvlak (the source-holder interface).
STOP covers the text and publication of decisions and regulations. IMOW describes the annotations that belong to environmental documents, such as activities and locations. For environmental documents they are used together; IMOW has its own page.
Yes. Every submission is checked against STOP and the LVBB rules before it is sent, with clear messages about anything that does not match. That way an error can be fixed before the entry-into-force date is at risk. After submission, the LVBB's feedback reaches your system at publication, so you can see whether it has been processed.
Yes, if that system has an interface or export. An adopted decision then moves from the meeting system to the publication process 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. In management, we adapt the integration to these changes so that your submissions keep working. We test a new version in a test environment first, before it is used for live publications.
For government bodies with their own systems for decisions or regulations for which no standard solution exists, and for suppliers that need to support STOP in their product.
Decisions from your own system to the LVBB?
Tell us which publications you handle, which systems decisions are made in, and how you currently submit them. We will show you what the integration would look like.