Free management resource

Workplace AI Risk Checklist

A practical 20-point check for managers and professionals before introducing, approving or expanding an AI use case at work.

AI risk depends on more than the tool. It also depends on the task, the information involved, who may be affected and what happens if the system is wrong. Use this checklist to identify gaps before an AI use case becomes routine.

How to use it: Check each statement you can confidently answer “yes” to. Every unchecked item is a control gap to investigate or resolve. A high score does not replace legal, privacy, information-security, HR, compliance, safety or other specialist review.
1. Purpose and potential impact

Define the use case and understand what could happen if it fails.

2. Data, privacy and security

Control what information enters the system and where it may go.

3. Accuracy and transparency

Make verification possible and avoid treating fluent output as proof.

4. Fairness and people impact

Consider who may benefit, who may be disadvantaged and how concerns will be handled.

5. Governance and ongoing oversight

Assign ownership and monitor the use case after launch.

Your readiness score: 0/20 Pause and assess the fundamentals.
17–20: Ready for formal reviewControls are broadly defined. Resolve remaining gaps and obtain required approvals.
12–16: Strengthen controlsImportant safeguards remain incomplete. Address them before proceeding.
0–11: PauseThe use case is not ready. Rework the fundamentals before approval or launch.
Important: This checklist is a practical management aid, not legal, regulatory, privacy, security, HR or safety advice. The appropriate review depends on the use case, jurisdiction, industry and consequences of error.

Frequently asked questions

Does a high score mean the AI use case is safe?

No. A high score indicates that common risk controls have been considered. It does not prove safety, compliance, accuracy or fitness for purpose.

Should every AI use case receive the same level of review?

No. Review should be proportionate to the information involved, the people affected and the consequences if the system performs poorly.

When should specialist review be required?

Seek qualified review whenever the use case involves sensitive data, regulated activity, employment decisions, safety, financial or legal consequences, vulnerable people or other material risk.