How the record is built and checked
One record, every output
One reviewed record holds each requirement, the evidence, the gaps, the crosswalk, the dates and a source pointer on every field. The clause pages, the Annex A pages, the free check, the kit and the watch all replay that record. A correction is made once and regenerated, so a page cannot drift from the register.
The requirement text is ours
The ISO 30301:2019 text is not reproduced. Each requirement line is a paraphrase written from our clause record, with the clause cited. Titles and defined terms remain as the standard names them. A seven-word overlap check runs against the public preview and the committee documents before release; the clause text is checked against the clause record at authoring, not copied from it.
What the draft layer can and cannot say
The PRF requirement text is not public. The draft layer therefore carries the stage record, the abstract and the fact that the text is not available. It does not state a draft requirement as if it were text, and it does not infer clause numbering from a family pattern. Where the public record is silent, the page says the record does not show it. The proven 2011 to 2019 change layer comes from the committee comparison and is labelled as history.
The dates
Stage dates to 50.00 are from the ISO page. No publication date is stated by ISO. The planning date of 18 February 2027 is 120 days from 21 October 2026, an estimate. The window is January to June 2027 (estimate). No ISO 30301 transition document has been issued; the illustrative case applies the Global ACI three-year precedent for ISO 9001:2026 and ISO 14001:2026, and the 18-month cut-off is a precedent too. Every date that is a target, a precedent or an estimate says so where it appears.
How the record is checked
- Every requirement has a clause citation and a source link. The draft status names the ISO page it rests on.
- The free check returns incomplete, not a lighter verdict, when an answer is blank or impossible.
- A strict word-overlap check against the public preview and the committee documents comes back clean; the standard text is not reproduced.
- The refresh script re-reads the ISO pages and the committee page and fails on an unexplained change.
- Every page is read on desktop and phone, with the free check run through its states.
What is not claimed
No claim that a page will be cited by a search engine or an AI assistant. No claim that the proof is final. No claim that a certification body will accept a transition plan. No invented statistics, reviews or dates.
The rules this is built from
Every line names its source. The 25 clause-level records and the 3 Annex A records for the requirements that apply today are written from the published ISO 30301:2019, in our words; the evidence and the common gaps are our reading, cited to the clause. The revision layer is read from the public ISO stage record and the committee's published comparison. Where the record is silent, the page says so. Read from the real rules, not invented.
ISO 30301:2019, clause by clause
Each clause page states the requirement in our words, the evidence, the gaps and what to do before the revision lands.
Open the clause indexAnnex A, normative
Processes, controls and systems. Requirements, not guidance, and each one has its own page.
Open Annex AWhat changed in 2019
The committee's own comparison of the 2011 and 2019 editions, with the old clause and its new home.
Read the comparisonThe ISO 30301:2019 text is not reproduced. The ISO/PRF 30301 text is not public and is not reproduced. The record this site reads is linked on the standards page.