Start with the risk management cycle
Read the NIST framework overview, then use Govern, Map, Measure, and Manage to structure a first-pass review of one AI use case.
Start with: AI Risk Management Framework
RedLectern topic
Harms · responsibilities · bias · risk assessment · oversight · organizational controls.
For: Everyone · builders · organizations.
After this page you can: Identify a use case's risks and assign concrete controls.
Page reviewed
Part of: Artificial Intelligence
AI safety and governance asks what harms an AI use case could cause, who may be affected, and who is responsible for acting when something goes wrong. Harms can arise through misuse, design choices that overlook bias or safety, and unintended effects on people and communities. Ethical review therefore belongs throughout a project, not only at launch.
A practical way to organize the work is to set responsibilities, map the use case and its context, measure risks, and decide how to manage them. Risk review should reflect the system’s intended use and include relevant perspectives. Controls can include documented ownership, testing, monitoring, oversight, and routes to challenge or correct decisions. The goal is to make a reasoned choice about whether and how to use AI, then revisit that choice as the system and its impacts change.
Read the NIST framework overview, then use Govern, Map, Measure, and Manage to structure a first-pass review of one AI use case.
Start with: AI Risk Management Framework
Use the ethics and safety guidance to consider how harm can arise and why project teams need to assign responsibility.
Start with: Understanding artificial intelligence ethics and safety
Read UK public-sector guidance on accountability, fairness, oversight, and routes to challenge decisions.
Start with: Data and AI Ethics Framework
Begin with the people and communities who may be affected, the decision or service involved, and the ways harm could occur. Harms may result from misuse, design that has not considered bias or safety, or unintended effects. Ethical questions arise at different stages of a project, so the people doing the work need to cooperate and decide who can identify, address, and escalate concerns.
A risk statement should be specific enough to guide action: name a possible harm, who could experience it, and the conditions that might make it more likely. Consider fairness and non-discrimination alongside safety, privacy, and accountability. Bias is one concern to investigate; fairness is a broader question about the effects and treatment of people. Use the comparison page to explore that distinction.
Explains fairness and recommends assessing data representativeness, bias, and the possible impacts of data use.
AI safety
Work to identify and reduce harms caused by AI systems.
AI ethics
Examining values and responsibilities in AI development and use.
AI governance
Rules, processes, and accountability for developing and using AI.
Model bias
Systematic tendencies or errors that can disadvantage people or distort results.
Choose an AI use case, such as sorting service requests. Name one group affected, one possible harm, and one condition that could cause or increase it.
For a service-request sorter, people who write in an unfamiliar dialect could have requests misclassified. A possible harm is delayed access to help; a contributing condition could be test data that poorly represents those dialects.
Risk assessment connects a proposed use to its setting, purpose, affected people, and possible consequences. Ask what the system is intended to do, where its outputs enter a decision or service, and what could happen if it performs poorly or is used in an unexpected way. Include relevant people in the assessment so that assumptions about the use and its effects can be questioned.
Assessment is a continuing activity: test before deployment, monitor during use, and revisit the analysis when the system, context, or evidence changes. Record risks in a way that helps people compare their impact and likelihood, decide which need a response, and make the reasoning traceable. An assessment can also identify a viable non-AI approach or show that the intended use should not proceed.
Explains the Govern, Map, Measure, and Manage functions and the role of ongoing risk management.
For an AI system that prioritizes requests for a public service, write one risk question about the system’s context and one about its possible impact.
Context: Which requests and users are included in the system’s intended use, and where do staff see its output? Impact: Could a wrongly low priority delay support for a group of users?
A risk review becomes useful when each priority risk has an owner and a concrete response. Assign people to maintain the system, review its effects, and decide what to do when monitoring finds a problem. Document the roles, escalation route, decision process, and any residual risk that remains after controls are applied.
Controls should fit the use and its risks. Possible responses include testing, monitoring, review by people with authority to intervene, and a route for affected people to question or correct a decision. Keep records that let the organization trace what was assessed and what action followed. Revisit controls across the system’s lifecycle, and consider whether a non-AI approach could reduce potential impact.
Provides public-sector guidance on governance, oversight, responsibilities, and routes to challenge decisions.
Defines human-AI roles and oversight, and describes documenting human oversight processes.
For the risk of a request being wrongly deprioritized, assign one control, the person responsible for it, and an action if the control finds a problem.
A service owner reviews a sample of low-priority requests each week. If the review finds a pattern of harmful misclassification, the owner pauses automated prioritization for the affected requests and starts a documented review.
Jurisdiction-specific AI rules; privacy; copyright; duties; legal status and dates.
0 subtopicsAI interpretabilityExplanations of outputs; investigation of internal mechanisms; evidence and limitations.
0 subtopicsAI securityPrompt injection; data attacks; tool abuse; exfiltration; application security boundaries.
0 subtopicsAI alignmentMatching behavior to intended goals and constraints; feedback failures; oversight limits.
0 subtopicsNo recent updates are available.
Bernd Carsten Stahl, Doris Schroeder, Rowena Rodrigues · 2023
Real-world cases help readers examine how AI use can create ethical harms and what responses may address them. The hosted edition is open access and readable here.
Solon Barocas, Moritz Hardt, Arvind Narayanan · 2023
A detailed examination of discrimination, fairness measures, and possible interventions in machine learning. The authors provide the text under a CC BY-NC-ND 4.0 license.
Bernd Carsten Stahl · 2021
An ecosystem-level account of AI ethics that considers ethical issues and possible governance responses. The hosted edition is open access under CC BY 4.0.
David Leslie · 2019
Practical guidance for applying AI ethics and safety principles to system design and implementation, with attention to harms and governance. The hosted edition is open access and readable here.