AI Governance Institute
← AI Governance Playbook

Question 27 of 53

How do we perform an AI risk assessment?

By Cody Maxwell · AI Governance Institute · March 2026 · Last verified September 13, 2026

Assess data sensitivity, decision impact, and regulatory exposure before deployment. Match controls to each system’s risk level.

Editorial status
AI Governance Institute recommendationVerified by AI Governance Institute pipelineNext review December 12, 2026
  • September 13, 2026 · Source updateThe article already lists ISO 42001:2023 as a related framework, and its existing content covers risk assessment, impact assessment, human oversight, documentation, and audit trails, which are the core ISO 42001 requirements most relevant to an AI risk assessment practitioner guide. The article stays appropriately generic and does not assert anything that contradicts the ISO 42001 standard. No genuine gap or contradiction exists that would require a new section. (AI Governance Institute pipeline)
  • September 13, 2026 · Substantive updateThe article covers risk assessment and references the NIST AI RMF, but says nothing about documentation requirements that arise from a risk assessment conclusion. The NIST AI Documentation Guidance draft introduces specific documentation obligations (system purpose, intended use, performance characteristics, known limitations, external-facing disclosures, and audit-ready records) that practitioners completing a risk assessment would need to act on, particularly for high- and medium-risk systems. This is a practical gap a reader relying on this article would encounter. (AI Governance Institute pipeline)

How we verify and maintain this

If you only do 3 things, do this:

  1. 1.Score every system on three dimensions before assigning a risk tier: what data it processes, how consequential its decisions are, and what regulations apply.
  2. 2.Use a consistent scoring rubric across all assessments so that risk tiers are comparable across your portfolio. Ad-hoc assessments are difficult to defend and impossible to aggregate.
  3. 3.Document the assessment, get sign-off, and schedule the next review. An assessment that lives only in someone's memory is not an assessment.

The Situation

Who this is for: Risk, compliance, and product teams evaluating AI systems before deployment or during annual reviews

When you need this: Before any new AI deployment, when a system's use case changes materially, or during annual risk reviews

The Decision

What is the risk level of this AI system, and what controls does that risk level require before we can deploy it?

The Steps

  1. 1Define the system: what does it do, what decisions does it influence or make, and who does it affect?
  2. 2Assess data sensitivity: what categories of data are processed? (personal data, special categories, regulated data)
  3. 3Assess decision impact: how consequential are the decisions? Are they reversible? Can an affected person contest or appeal?
  4. 4Assess regulatory exposure: which regulations apply based on jurisdiction, sector, and use case?
  5. 5Score each dimension (1-3) and assign a risk tier using your scoring rubric
  6. 6Document required controls for the assigned tier and confirm they are in place before deployment
  7. 7Get sign-off from the appropriate authority and schedule the next assessment

The Artifacts

  • AI risk assessment form (standardized questionnaire covering all dimensions)
  • Risk scoring rubric (data sensitivity × decision impact × regulatory exposure → risk tier)
  • Risk tier control requirements matrix (what each tier requires)
  • Risk assessment sign-off template
  • Assessment review schedule
Open the implementation kit

The Output

A completed, signed risk assessment for the AI system, a documented risk tier with rationale, required controls identified and confirmed in place, and a review date set.

The five dimensions of AI risk

AI risk is multidimensional. A system that processes highly sensitive data but only makes suggestions to expert users is different from one that processes minimal data but makes automated decisions at scale. Effective risk assessment evaluates five dimensions: the sensitivity of the data processed; the impact and reversibility of the decisions influenced; the scale of deployment (how many people are affected); the degree of human oversight in the workflow; and the regulatory context (which laws apply).

Most organizations simplify to three primary dimensions: data sensitivity, decision impact, and regulatory exposure. This is a reasonable simplification that produces consistent, actionable results. The scoring should be calibrated to your specific context: what counts as "high" data sensitivity at a healthcare company differs from a marketing analytics firm.

Walking through the assessment

Data sensitivity assessment asks: what data does this system process? Assign a score of 1 if the system only processes aggregate or clearly non-personal data; 2 if it processes personal data without special categories; 3 if it processes special categories (health, biometric, financial, children's data, or other regulated categories).

Decision impact assessment asks: how consequential are the outputs? Assign 1 if the system only informs a human decision with no direct consequence; 2 if it significantly influences decisions that can affect individuals; 3 if it makes or effectively determines consequential decisions (hiring, credit, medical, legal, access to services). Irreversibility raises the score.

Regulatory exposure asks: which regulations specifically address this use case? Assign 1 if minimal regulatory attention applies; 2 if general privacy or sector regulations apply; 3 if specific AI regulations or high-risk classifications under major frameworks apply. The EU AI Act Annex III is a useful reference list for the highest regulatory exposures.

What the risk tier means in practice

High-risk systems (aggregate score 7-9) require the full governance treatment: technical documentation, bias assessment, human oversight arrangements, logging and audit trails, and a pre-deployment sign-off from risk and legal. They should be reviewed annually at minimum, and after any material change.

Medium-risk systems (score 4-6) require a documented risk assessment, basic testing records, a named owner, and a review schedule. They do not require the full documentation burden of high-risk systems, but they are not ungoverned. Low-risk systems (score 3) should appear in the model registry with basic metadata and a risk tier assignment, but do not require extensive supporting documentation.

Recording and disclosing assessment outcomes

Completing a risk tier assignment is not the end of the process. High- and medium-risk systems require documented records that can withstand external scrutiny, and NIST's draft AI documentation guidance provides a structured template for exactly this. The template covers system purpose, intended use, performance characteristics, known limitations, and the risk controls in place. Aligning your post-assessment documentation to that structure makes records reusable across governance approvals, audits, and regulatory inquiries.

External-facing disclosures are a separate requirement from internal governance records. Affected parties need a plain description of how the system behaves and what safeguards apply, not just a risk score. Retaining both the internal assessment record and any public-facing disclosure together creates a defensible audit trail if a third party or regulator asks you to substantiate your pre-deployment review.

Not sure where to start? Answer 3 questions and get a tailored compliance action plan.

What applies to me? →

More guidance like this, every week

New playbook articles, governance controls, and the regulatory changes driving them. Every Thursday.

Powered by Buttondown.