The ISO number is a draft
A DIS cannot be cited as the applicable standard and cannot be certified against. If a contract cites ISO 42703 today, the citation is premature. What the record shows.
ISO/IEC/IEEE DIS 42703 is the first ISO edition of the algorithmic bias standard. It is at stage 40.99, approved for registration as an FDIS, and it is not published. The substance is already public: the joint project carries the same title and technical source as IEEE Std 7003-2024, the published IEEE edition. This site states every clause in plain words, shows the evidence an assessor asks for, and separates the recorded dates from the estimate.
Read from the real rules, not invented. Every answer points to the official clause behind it, so you can check any line yourself.
No account for the free check. Not legal advice; does not certify.
Most teams can describe their model and cannot produce the record the standard asks for. The register turns each clause into the evidence an assessor will request, so the answer is ready before the question.
Photo: fauxels on Pexels, free licence.
A DIS cannot be cited as the applicable standard and cannot be certified against. If a contract cites ISO 42703 today, the citation is premature. What the record shows.
The joint project carries the same title as IEEE Std 7003-2024, the published IEEE edition. That standard is published and readable now, which means the clause work can start before the ISO label arrives. The clause register.
No publication date is recorded. The planning date used here is 13 September 2027, derived from the stage record and labelled an estimate. ISO has not committed to it. The dated timeline.
Each page states the requirement in our words, why it matters, the evidence an assessor asks for, the common failures and what to do before publication. Start with clause 4 if the system is new. Start with clause 5 if the record is the gap.
| Clause | Record | The answer in one line |
|---|---|---|
| 1.1 | Scope | The standard is a creation-time process for considering bias in an algorithmic system, not a live audit or a certificate. |
| 1.2 | Purpose | The purpose is to let a creator define, measure and communicate how bias is used in the system, and to show the practices behind that claim. |
| 1.3 | Word usage | Only shall creates a requirement. Should is a recommendation, may is a permission and can is a capability. |
| 1.4 | Field of application | Scope follows the outcome, not the technology, and five life cycle events bring a system into the process. |
| 1.5 | Limitations | The standard covers creation. It does not detect or evaluate a problematic algorithm in live use, and it does not track or certify. |
| 1.6 | Organization of the standard | Six normative clauses run around one record, the bias profile, and every clause is revisited as the system changes. |
| 1.7 | Audience | The standard is written for suppliers, procurers, developers, maintainers, auditors, operators, users and managers, including in-house teams. |
| 1.8 | Conformance | A project or organization can claim conformance, use the standard in a contract, or adopt it in-house. None of these is a certificate. |
| 1.9 | Disclaimer | The standard sets minimum criteria. It does not guarantee that the system meets its mission or that no harm will occur, and it does not replace legal or ethical duties. |
| 2 | Normative references | There are no normative references. Nothing else has to be read for the standard to apply. |
The check asks what the system decides, which life cycle event applies, whether conformance is claimed, and how far the record has got. It returns the clause path, the weakest step and three actions. It runs in your browser and sends nothing anywhere.
It never returns a compliance verdict. It returns a reading of your answers and names the missing one when scope is incomplete. The rule behind each question is printed on the page.
It will not audit the system, score maturity out of 100, or tell you that you conform. It will tell you which clause to open next and what evidence that clause expects.
The paid kit carries the full register, the evidence list and the dated plan.
| Date | What it is | Status | Source |
|---|---|---|---|
| 2026-09-16 | Stage 40.99, DIS approved for registration as an FDIS | Recorded | ISO page 95306 |
| 2024-12-11 | IEEE Std 7003-2024 approved by the IEEE SA Standards Board | Recorded | IEEE SA page |
| 2025-01-24 | IEEE Std 7003-2024 published | Recorded | IEEE SA page |
| 2027-09-13 | Planning date for ISO publication | Estimate, not an ISO commitment | This record, from stage 40.99 |
The FDIS ballot and publication dates are not recorded on the ISO page. A blank is not a prediction.
The full register, the evidence list and a dated plan, in PDF, CSV and XLSX. Written for the system you own, with an owner and a due date on every line.
One click to Stripe. The files unlock on the return page after payment.
An email when the rule, its guidance or its dates change. The watch reads the same record the pages are built from.
One click to Stripe. No account to create.
The standard is voluntary. The obligations around it are not. The rules page names the frameworks that matter to this buyer in the United States, the European Union, the United Kingdom and Australia, chosen by a scan of the frameworks held for each market, in that order. Read the four market page.
It applies to every algorithmic system involved in selection, allocation, ranking or decision-making where different parties can receive different outcomes, whatever the technology. It also applies when a system is designed, used with new data, moved to a new context, updated or decommissioned. Run the free check.
No. ISO records ISO/IEC/IEEE DIS 42703 at stage 40.99, DIS approved for registration as an FDIS, on 16 September 2026. A DIS is a draft and cannot be cited as the applicable standard. The planning date of 13 September 2027 is an estimate, not an ISO commitment.
IEEE Std 7003-2024, the published IEEE edition behind the joint ISO/IEC/IEEE project. It was approved on 11 December 2024 and published on 24 January 2025. Its clause structure is the one this register follows, and it is available from IEEE at no cost through the IEEE GET programme.
It is the through-life record of the bias work. Every task keeps its initial, intermediate and most recent versions, and each clause reads the profile and writes back to it. It is not a one-off report and it is not replaced by the latest version. Read clause 5.2.
The full 61 clause register, 269 evidence lines and a dated plan in PDF, CSV and XLSX, with an owner and a due date on every line. The labelled specimen shows the shape before you buy. The change watch is USD 49 a month.
No. It is a reference and a working register. The standard has no certification scheme and tracking and certification are outside its scope. Conformance is a claim the organization makes, and it does not replace legal, ethical or moral obligations.
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.
The requirement in our words, the evidence an assessor asks for, the common gaps and what to do before publication.
Open the registerAnnexes A to F are informative. Each page says so, because a finding cannot rest on guidance alone.
Open the annexesStage 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.