Custom JCDR integration
JCDR is the standard for references to local regulations: by-laws and other rules from municipalities, provinces and water boards. The standard is managed by KOOP and is on the Forum Standaardisatie list. Appfront builds integrations that create, read and check JCDR references, so your system points to the right regulation and the right version, and a link does not break when a regulation changes.
What is a JCDR integration?
JCDR stands for Juriconnect standard for Local Regulations (Decentrale Regelgeving). It defines how a computer refers to a regulation of a local government body that is held in the CVDR, the Central Facility for Local Regulations (Centrale Voorziening Decentrale Regelgeving). Such a reference has a fixed structure with the regulation's number in the CVDR, the version and, where needed, the article. KOOP manages the standard. Since November 2013, JCDR has been on the Forum Standaardisatie's comply-or-explain list, which applies to governments and institutions in the public sector.
In practice, many systems still refer to regulations with an ordinary link or just the regulation's title. That goes wrong when the regulation is amended: the link points to an old version or breaks, and nobody notices. A case management system that refers to an article of the APV (the general local by-laws) in a decision, a website with the rules for a subsidy, or a legal database with thousands of references: everywhere, the reference has to be correct at the moment someone uses it.
We build custom because systems differ: which regulations, which types of references, and where they are used. How the integration retrieves the data from the CVDR is something we look at in the first step, together with you. Environmental documents under the Omgevingswet (Environment and Planning Act) run through a different standard, STOP; there is a separate integration for that.
References that work
To the regulation, the version and the article.
Always up to date
An alert when a regulation changes.
According to the standard
JCDR as KOOP manages it.
How we build your JCDR integration
We start with your system: where local regulations are referenced, how that is done now, and which references go wrong. We often begin with a check of the existing references, because it shows how many are already no longer correct. Then we create new references according to JCDR and keep them up to date. Alerts for new versions and the integration with your case management system or website follow once the foundation works well. That way you quickly see what the integration delivers, and afterwards we maintain it as the standard or the CVDR changes.
Where, how, and what goes wrong.
Existing references checked.
Create, read and keep up to date.
Go-live, monitoring, and maintenance when things change.
What a JCDR integration actually does
The components below feature in almost every JCDR integration. Which ones you need depends on your system.
Create a reference
Regulation, version and article.
Read a reference
To the right text.
Validation
Broken and outdated.
New versions
Alert on change.
Search
Regulations per government body.
Log
Every change recorded.
Who we build a JCDR integration for
The integration is intended for organisations that refer to local regulations. The more references you have, the more an integration delivers.
Municipalities and provinces
Their own regulations. Referencing in decisions matters most.
Regional environmental agencies
Rules from many government bodies. Overview is the core.
Legal publishers
Many references. Staying up to date is what counts.
Software suppliers
Case management systems and licensing, supervision and enforcement (VTH). The standard is the core.
Technology and integrations
This page is about references to decentralised regulations. For national laws and regulations there is our page on the BWB integration, for court rulings our page on the ECLI integration, and for environmental documents our pages on the STOP integration and the IMOW integration. You can read about our way of working on building software.
Why choose Appfront for your JCDR integration?
A reference that points to an outdated version, or breaks without anyone noticing, undermines a decision or an advisory opinion. That is what we build against: references that work, an alert when a regulation changes, and an integration that follows the standard.
Right version
Always the current text.
No broken links
Checked, not hoped for.
Comply
In line with the mandatory standard.
Security and privacy in a JCDR integration
Regulations in the CVDR are public. The integration does run inside your own systems, however, such as a case management system containing decisions about individuals and businesses; that is why access is set up per role and every change is logged.
The integration runs in a European data centre, with encrypted storage and daily backups. Where personal data is processed, we record this in a data processing agreement.
Frequently asked questions about a JCDR integration
Questions organisations ask before they get started.
JCDR is the Juriconnect standard for Decentralised Regulations. It defines how a computer refers to a regulation issued by a municipality, province or water board in the CVDR, specifying the regulation, the version and, where needed, the article. KOOP manages the standard.
JCDR has been on the Forum Standaardisatie's "comply or explain" list since November 2013. Government bodies and public sector institutions must apply it for electronic references to decentralised regulations, or explain why they do not.
BWB is the base register for national laws and regulations, while ECLI is the identifier for court rulings. JCDR is for regulations issued by decentralised authorities. A legal system often needs all three.
The integration compares the references in your system with the versions in the CVDR. If there is a new version, you receive an alert listing the references it affects. For each reference, you choose whether it should move to the new version or deliberately keep pointing to the old one.
Often, yes. Existing links and titles are read and, where possible, matched to the correct regulation. Anything that cannot be matched automatically is queued for review, so no incorrect reference is created.
Environmental documents under the Environment and Planning Act, such as the environmental plan, are published in line with STOP via the LVBB. That requires a different integration. JCDR remains relevant for regulations in the CVDR, such as bylaws outside the environmental plan.
Municipalities, provinces and water boards that refer to regulations in their decisions and on their websites, environmental services, legal publishers and knowledge platforms, and suppliers of case management systems and software for permitting and enforcement. The more references you have, the more it delivers.
References to decentralised regulations that stay accurate?
Tell us where your system refers to regulations and what currently goes wrong. We will show you what the JCDR integration looks like.