Free check

Does the standard apply, and what is the next step?

Answer eight questions about the system and the record. The check returns a scope reading, the clause path that applies, the weakest step and three actions. It runs in your browser and sends nothing anywhere. It is a reading of your answers, not a compliance result.

Can different parties receive different outcomes from the system? Selection, allocation, ranking or decision-making all count. The technology does not decide scope.

Which life cycle event applies now? A new design, new data, a new context, an update or a decommission all bring the system into the process.

Is conformance claimed, or is the standard in a contract? The claim decides the consequence of a gap, not the good practice.

Do you have a bias profile with version history? The profile is the through-life record. A snapshot is not the same thing.

Do you have a stakeholder reference set with types and attributes? This is the population the data map and the tests must represent.

Do you have a data map, repeated after retraining? The map connects the data to the stakeholder attributes.

Is the risk and impact assessment signed, with the owner acceptance? The signature and the acceptance are the governance teeth.

Which evaluation is in place? The design evaluation and the ongoing evaluation are two different procedures.

Your planning dateThe site uses 13 September 2027 as an estimate. Put your own date here; the plan is yours.

Blank answers return "scope incomplete" and name what is missing. The check never assumes the lighter pathway.

JavaScript is off. The check needs JavaScript to compute the reading. You can still read the clause register and the dated plan. The six questions are: whether different parties can receive different outcomes; which life cycle event applies; whether conformance is claimed; whether a versioned bias profile exists; whether a stakeholder reference set exists; whether a data map exists and is repeated after retraining; whether the risk assessment is signed and accepted; and which evaluation is in place.

The answer today

IEEE Std 7003-2024 is the published source

The DIS is the joint ISO, IEC and IEEE project; IEEE Std 7003-2024 is its published IEEE edition. The clause path below is the same under either label. A DIS is not a published standard, so the check never calls anything conformant.

How the dates are used

The ISO page records stage 40.99 on 16 September 2026. No publication date is recorded. The planning date of 13 September 2027 is an estimate for this site, not an ISO commitment. Your own date replaces it in the result and the plan.

THE RULE

What each question applies

The clause

Input	How it is used	Source
Different outcomes	If no, and no trigger event applies, the system is out of scope. If unsure, the check returns scope incomplete.	Clause 1.4
Trigger event	New design, new data, new context, update or decommission each bring the system into the process.	Clause 1.4
Claim	A contract or internal claim makes the record an obligation. Guidance use changes the consequence, not the good practice.	Clauses 1.8, 1.9
Bias profile	A missing or versionless profile is the first gap, because every later clause writes to it.	Clauses 4.3, 5.2
Stakeholders	An incomplete reference set means the data map and the tests cannot be judged against the right population.	Clauses 6.3, 6.4
Data map	A map that is not repeated after retraining is out of date after the next model.	Clause 7.4.2.3
Risk	An unsigned assessment, or one without the owner acceptance, is incomplete governance.	Clauses 8.4 f, 8.5
Evaluation	The design evaluation and the ongoing evaluation are both required; one without the other is a gap.	Clauses 9.2, 9.3

A blank or impossible answer returns "scope incomplete" and names the missing item. The check never guesses a lighter pathway.

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

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 register

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 annexes

ONE 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 record

The 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.

The check is a reading of your answers, not an audit and not a compliance result. It does not decide whether the system is lawful, safe or unbiased. It does not certify anything and it is not legal advice.