Human resources

As part of identifying resources, record the people and competences used for building, deploying, running, changing, maintaining, transferring and retiring the AI system and for integrating and verifying it. In practice the record is staffing and competence records per life cycle activity. For human resources the evidence is an inventory, not a statement.

What it asks

As part of identifying resources, record the people and competences used for building, deploying, running, changing, maintaining, transferring and retiring the AI system and for integrating and verifying it.

Where generative AI changes the answer

Human resources means the people who read the output before it is used, and their competence is part of the control, not an implementation detail.

Who it binds

The AI system owner and the functions that supply data, tooling, computing and people. For A.4.6 the named role is the owner of staffing and competence records per life cycle activity.

Evidence an auditor normally samples

• Staffing and competence records per life cycle activity
• Evidence diverse expertise was considered (data science, human oversight, safety, security, privacy, domain experts)

The test you can run

Compare staffing and competence records per life cycle activity with the use as it runs today; the gap between the two is the finding to record.

Common failures

• No competence recorded for decommissioning or transfer
• Human oversight roles not resourced

Before the draft publishes

For A.4.6, list the data, tooling, computing and people the use depends on, and mark which of them the organisation does not control. The first artefact to produce is staffing and competence records per life cycle activity.

Where this sits against the draft

The draft's published scope names controls for the risks it identifies, and A.4.6 (human resources) is the published ISO/IEC 42001 control closest to that work. The draft does not replace it, and an audit still tests it against the evidence listed here.