Sources and method
Where the law on this site comes from
Everything we publish about a rule was read from the act itself. This page names the sources. It says what each one's terms let us reproduce, how often we read them again, and which checks have to pass.
The sources we read
One row per source family, with what we take from it and what its own terms allow. A source whose terms we have not read is treated as the strictest of the three, not the most convenient.
What we take The Official Journal of the European Union, read through EUR-Lex and through CELLAR, the Publications Office's own store behind it. Every regulation and directive we quote is read there, in the language the reader is reading.
May be republished, with the source named
TermsCommission Decision 2011/833/EU on the reuse of Commission documents
What we take A European standard printed inside an EU act, such as the ISO 14001 clauses reproduced in Commission Regulation (EU) 2017/1505. The annex sits in the Journal, the content belongs to the standards bodies, and the act's own footnote says so.
Nothing of its text goes out
TermsThe act's own footnote: reproduction for commercial reasons is not permitted
What we take The registers of national implementing measures, where a member state tells the Commission which act it passed to transpose a directive.
May be republished, with the source named
What we take The member states' own transposing acts, on the gazette or register that publishes them. A directive binds the state, so a duty reaches a reader through the state's act and not through the directive itself.
Our reading only, never its own text
TermsEach state's own reuse rules, which differ
Terms not yet read, so nothing of its own text goes out.
What we take The ENISA and CSIRTs Network listings of the national teams, for who takes an incident report where.
May be republished, with the source named
TermsCommission Decision 2011/833/EU, with ENISA's own attribution notice
What we take Tenders Electronic Daily, the Publications Office's record of public procurement notices, for what buyers actually ask suppliers to hold.
May be republished, with the source named
TermsCommission Decision 2011/833/EU, and the TED reuse notice
What we take The IAF mandatory documents that accreditation bodies hold certification bodies to, which is what makes the audit-day figures facts about what a certification will cost rather than estimates.
Our reading only, never its own text
TermsIAF's own copyright notice on the documents
Terms not yet read, so nothing of its own text goes out.
What we take ISO, IEC and CEN standards. They are sold under licence, so we publish clause numbers, editions and our own description of what a clause asks, and never the text.
Nothing of its text goes out
What we take The member states' company registers. Nothing from one is republished; a company's own website is where an address comes from.
Our reading only, never its own text
TermsEach register's own terms, recorded per register in companyRegisters.ts
Terms not yet read, so nothing of its own text goes out.
What we take Our own readings, descriptions, mappings and arithmetic. This is most of what the product is, and the published datasets carry it under Creative Commons Attribution 4.0.
May be republished, with the source named
TermsCreative Commons Attribution 4.0 for the published datasets
What has to pass before a sentence about the law is published
Six checks, each one a script in this repository and a step in the build. The list is built from the scripts themselves. A check that stops running has to come off this page in the same edit.
Every act that amends an instrument we quote has been read against our rows.
scripts/check-amendments.mjsNo wording we publish has been replaced by a corrigendum in the Official Journal.
scripts/check-corrigenda.mjsEvery claim about a system we do not control is re-checked before it goes stale.
scripts/check-external-claims.mjsEvery provision we quote appears word for word in the act, in all six languages.
scripts/check-quoted-verbatim.mjsEvery date on which we read a source is young enough to still stand behind.
scripts/check-readings-fresh.mjsEvery date in a sentence is a date the codebase holds, cited to its article.
scripts/check-regulatory-dates.mjs
How often we read a source again
The day we read a source is stored beside what we read. The build fails when one of those dates gets too old for the kind of source it belongs to.
180 days
Everything, by default
A published document that does not move on its own is still read again on this cycle. Our reading of it can be wrong whether or not the document changed.
90 days
Registers other people maintain
Competent authorities, national CSIRTs and the measures states have notified. These change without telling anyone, so they are the shortest window on the page.
365 days
Official Journal text
Here the date is provenance rather than evidence. The words themselves are held to the act corrigendum by corrigendum and amendment by amendment by two of the checks above, which is a stronger control than a calendar.
When we get it wrong
Corrections are published and dated, and the old reading stays visible. The regulatory changelog is the log of every change to what we say a rule requires, whether the legislator changed it or we had misread it.
Who writes this, where AI is used, and who answers for a mistake, are on the editorial policy.
Related:Editorial policyThe regulatory changelogAboutTrust center