One page per clause
The requirement in our words, the evidence an assessor asks for, the common gaps and what to do before publication.
Open the registerA twelve-week path to the record
The plan below is the order the standard expects. It is a default, not a promise: a small system can compress it and a large one will extend it. The dates are relative to your start, and the planning date of 13 September 2027 is an estimate for the edition, not a deadline for you.
The page adds the calendar dates for week 1 and week 12. With JavaScript off, the relative labels still work.
| When | Clause | What is produced | Owner |
|---|---|---|---|
| Before the first workshop | Clause 4.2 inputs | Business requirements and the necessity record, design documentation, governance pack | System owner |
| Week 1 | Clause 4.4 | Bias requirements, sensitive attribute list, representation test, boundaries | Programme lead |
| Week 2 | Clause 4.3 and 5.2 | Bias profile version 1, values statement, version rule | Profile owner |
| Week 3 to 4 | Clause 6.4 | Stakeholder reference set, types, attributes, protected attributes | Stakeholder lead |
| Week 5 to 6 | Clause 7.4.2.1 and 7.4.2.2 | Data set record, metadata, proxy analysis, exploration | Data lead |
| Week 7 | Clause 7.4.2.3 | Data map, imbalance log, retraining link | Data lead |
| Week 8 | Clause 8.4 | Two risk inventories, metrics and rationale, signatures | Risk lead |
| Week 9 | Clause 8.5 | Owner acceptance and residual risk | System owner |
| Week 10 to 12 | Clause 9.2 | Design and output evaluation, nine-item report | Evaluation lead |
| Week 13 | Clause 9.3.4.1 | Monitoring list, recurrence rationale, feedback route | Operations lead |
| Every iteration | Clause 9.3.4.3 | Five-part profile review and new versions | Profile owner |
| At each trigger | Clause 1.4 | Re-entry: new data, new context, update or decommission | Programme lead |
Print this page for the project wall. The paid kit carries the same plan with an editable date, an owner column and a status column per line.
The profile and the requirements come first because every later step reads them. The stakeholders come before the data because the data map needs a population. The risk assessment comes after both because it takes them as inputs. The evaluation comes last because it tests the design against the requirements, and the monitoring comes after the evaluation because it needs the baseline. A plan that starts with the model will produce tests without a standard.
THE RULES THIS IS BUILT FROM
The rules this is built from
Read from the real rules, not invented. Every clause answer on this site points to the official rule behind it, so you can check any line yourself. The register holds 67 records, 269 evidence lines and 201 common failure lines. The dates come from the ISO record. The substance comes from the published IEEE edition behind the joint project.
61 CLAUSES
6 ANNEXES
Guidance, clearly labelled
Annexes A to F are informative. Each page says so, because a finding cannot rest on guidance alone.
Open the annexesONE STAGE RECORD
No invented date
Stage 40.99 is recorded on 16 September 2026. The planning date is an estimate and is labelled wherever it appears.
Read the recordThe ISO draft text is not public and is not reproduced. Each record cites the published clause it comes from. Where the public record is silent, the page says so.