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 registerWhat is a bias profile under ISO 42703?
It is the through-life record of the bias work for a system. For every task it keeps the initial, the intermediate and the most recent version of the documents, and each clause reads it and writes back to it. It is not a one-off report and it is not replaced by the latest version.
Last updated: . Written from the published source and the ISO record. Not legal advice; does not certify.
What goes in it
The bias requirements and boundaries, the values statement, the stakeholder reference set, the data map and metadata, the risk and impact assessment, the evaluation document and the monitoring plan. Each entry has a version and a source, so a later reader can reconstruct the state at the time of a decision.
Why versions matter
A bias found in production has to be traced to the data, stakeholders and risk assessment that were current when the output was produced. If only the latest version is kept, the investigation starts from a reconstruction. The clause requires the earlier versions to sit beside the new one.
How the clauses use it
Clause 4 creates the first version. Clause 6 adds the stakeholder set. Clause 7 adds the data map and metadata. Clause 8 adds the assessment. Clause 9 adds the evaluation and the monitoring plan. The five-part review at the end of each monitoring iteration revisits all of them.
What it is not
It is not a model card, a data sheet or a risk register on its own. Those can be inputs, but the profile is the record that ties them together and shows the iteration. It is also not a public disclosure document; it is the internal record the assurance case rests on.
Related clauses
Questions
Can a spreadsheet be the bias profile?
A spreadsheet can hold the index and the versions if it has a version column, an owner and a link to each document. The risk is that links rot. A repository with version control is better, but the standard asks for the record, not a particular tool.
Who owns it?
Name a position, not a committee, and a deputy. The profile owner is usually the programme lead or the AI governance lead, with each clause owner contributing their section.
Does it have to be public?
No. The standard asks for the record, not publication. A customer or regulator may ask for parts of it, and the assurance pack should say what can be shared.
Run the free scope check / Open the register / The kit and the watch
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.