Actions
Eight actions turn the inputs into the profile: collect records, represent sensitive attributes, set accountability, list life cycle requirements, build the profile, write values, set boundaries, and establish procedures.
What clause 4.4 asks
Eight tasks make up this step. Gather the required records (business requirement, design record, governance material, including the interface and experience design) and the suggested ones (a feasibility study, the IEEE CertifAIEd ontologies, ISO/IEC/IEEE 24748-7000 and other records about how the system is built and run). List the sensitive attributes the work must speak for, test whether the team reflects them, and bring in outside advocates where it does not. Choose who is accountable and show where that sits in the governance structure. List the other requirements across the life cycle, retirement included. Build the profile. Write the values statement. Set the limits of acceptable use across diversity, inclusion, disability, culture and accessibility. Put the method in writing so another person could follow it.
Why it matters
The eight actions are the substance of clause 4. Two of them are easy to skip and expensive to omit. The sensitive-attribute action asks not only which attributes matter but whether the team can represent them; the external advocate is the remedy when it cannot. The accountability action connects the bias work to the governance framework, which is what makes the signature in clause 8 meaningful. The other actions build the record, the values, the boundaries and the procedures that the later clauses depend on.
What good looks like
Work through the eight actions in order and record an output for each. For the sensitive-attribute action, write the list, test the team against it, and record the advocate decision. For accountability, name the position, not the person, and show the line to the governance framework. For the life cycle requirements, include retirement. For the procedures, write how a new team member would do the work, not only what the current team knows.
Evidence an assessor asks for
The assessor will sample the eight actions. The two that most often have no evidence are the representation test and the decommissioning requirement. A missing representation test undermines the stakeholder work that follows.
- Records index Necessary and recommended records, with what exists and what does not
- Sensitive attribute list The attributes, the team representation test and the advocate decision
- Accountability map The position that controls the system and its link to the governance framework
- Life cycle requirements The other requirements, including decommissioning
- Procedures The written method for bias consideration in this context
Where it commonly fails
- The sensitive attribute list is written but the team is never tested against it
- Accountability is assigned to a committee rather than a position
- Decommissioning is left out of the life cycle requirements
What to do before publication
Produce one artefact per action before moving to clause 5. The profile cannot be complete while an action is open.