Home / Method
How the record is made
Five steps, the same for every record. The point is that a reader can repeat any of them and get the same answer.
1. Read the official record first
The designation, title, stage, stage date, committee, ICS and page count come from the ISO record feed for 89517, read on 21 October 2026. The base standard's edition and abstract come from the ISO record for 76382. Nothing on this site states a date that is not in one of those records or labelled as an estimate.
2. Read the text that is public
The amendment instructions come from the public draft text of the amendment. The base standard's contents, introduction and clauses 1 to 5.1.2 come from the publisher's public preview. Where the held text stops, the record stops. That is why some entries state a clause title and not a requirement.
3. Write the requirement in our own words
Each record states what the clause asks in plain English, separately from any quotation. Only clause codes, the names of mechanisms and defined terms stay as the text has them. A strict overlap check compares every field against the source and its prior edition before the record ships; a shared run of seven words fails the build.
4. Add the evidence and the test
Each record names the artefacts an auditor normally samples, the test a reader can run, the common failures and the artefact that closes the row. Evidence lines are concrete records, never a restatement of the requirement.
5. Keep it current
A refresh script re-reads the public ISO feed and compares the designation, title, stage, stage date, committee and ICS with the data file. Any difference fails the script and writes the diff. The paid watch sends that diff. When the published text lands, the record is rebuilt from it and the changelog says what moved.
What we will not do
- State a requirement we cannot cite
- Present an estimate as an ISO date
- Describe a standard as a certification when it is not
- Reproduce the text instead of paraphrasing it
Not legal advice; does not certify.