Inputs
The inputs are the business case with its first stakeholder record, the technical requirements, the context of use, other necessary information and the bias profile.
What clause 6.2 asks
Clause 6 has five inputs. The first is the business case for the AIS, which has to contain a first record of the stakeholders and the initial order of their importance to the organization. The second is the technical requirements. The third is the context of use. The fourth is any other information the identification team needs. The fifth is the bias profile. The business case can give the order directly or contain information from which it can be derived.
Why it matters
The business case input is often thinner than the clause expects. A case written for funding will name customers and maybe regulators, but not the people whose lives change when a decision is automated. The clause asks the identification team to start from that record and then improve it, using the technical requirements and the context. The profile input is what connects the work to clause 4, so the team can see the requirements and boundaries it is serving.
What good looks like
Check the business case for a stakeholder record before the workshop. If it has none, record that as a gap and build the first record in the workshop. Read the technical requirements for interfaces and data flows, because those reveal stakeholders the business case missed. Bring the context of use in writing, including the jurisdiction and the affected population. Open the current profile so the team can see the requirements it is working to.
Evidence an assessor asks for
The assessor will read the business case first. If the stakeholder record there is only a customer list, the assessor will look for the record of how the wider set was found.
- Business case extract The first stakeholder record and the initial order of importance
- Technical requirements The interfaces, data flows and dependencies that reveal stakeholders
- Context of use The jurisdiction, population and conditions of use
- Profile reference The clause 4 requirements and boundaries the identification serves
Where it commonly fails
- The business case has no stakeholder record
- The technical requirements are read only by the engineering team
- The context of use is assumed rather than written
What to do before publication
Repair the business case stakeholder record before clause 6, or record why it cannot be repaired and how the workshop compensates.