Planning · worksheet · CSVtoCSA editorial

AI functional risk assessment

Version 2.0 · Updated 2026-09-21 · Planning

Connect a specific failure to its consequences, controls, tests and residual-risk decision.

Adapt this template to your intended use, applicable requirements, and approved procedures.

When to use it

Use when you need to connect a specific failure to its consequences, controls, tests and residual-risk decision.

Information needed before starting

  • Defined AI use, authority limits and assessed configuration
  • Controlled sources and independent reference results relevant to this worksheet
  • Applicable risk assessment, acceptance basis and responsible reviewers

Field instructions

  • Requirement or function: Identify the specific intended behavior and stable requirement ID.
  • Failure and cause: Describe a missed, wrong, unauthorized or unavailable behavior and credible contributing factors.
  • Consequence and severity: Trace the process effect and apply the organization’s severity rubric.
  • Existing control: Identify the control that interrupts the failure, including its owner.
  • Control evidence: Link tests or other evidence showing the control works.
  • Remaining gap: Record uncertainty, failed criteria and unresolved controls.
  • Residual-risk decision: State accept, restrict, defer or other locally defined disposition with rationale.
  • Owner and trigger: Identify who acts and which change or result triggers reassessment.

Completed fictional example

Fictional risk rows from PRA-01. No universal numerical risk score is implied.

Risk / requirementFailure and consequenceControl and evidenceResidual decision
R-01 / REQ-01AI omits critical alarm challenge; protocol coverage could be inadequateFull required review and T-01/T-03 evaluation; two AI critical misses and one final assisted critical missExpanded reliance withheld; DEV-01/02 open
R-02 / REQ-02Unsupported requirement misdirects reviewApproved-source verification; T-02 identifies six false AI findings, T-03 leaves two acceptedDEV-03 open; improve and retest
R-04 / REQ-04Unauthorized action or source disclosurePermission boundaries; T-04 blocks six of six planned attemptsSupported only for tested scope; retain technical restrictions

Blank template

System / record ID: ____________________

Prepared by / date: ____________________

Required review / approval under local procedure: ____________________

FieldYour entry
Requirement or function____________________
Failure and cause____________________
Consequence and severity____________________
Existing control____________________
Control evidence____________________
Remaining gap____________________
Residual-risk decision____________________
Owner and trigger____________________

Blank results or assessment rows

Risk / requirementFailure and consequenceControl and evidenceResidual decision
________________________________________________________________________________
________________________________________________________________________________
________________________________________________________________________________
Relevant regulations and guidance

These sources apply within their stated scope. The suggested worksheet fields, test designs and fictional decisions are practitioner recommendations, unless a source requirement is expressly identified. Completing a template does not establish compliance.

Computer Software Assurance for Production and Quality Management System Software ↗

Regulatory guidance / GMP guideline · United States · February 2026

Scope: Medical-device manufacturers assuring software used in production or their quality management system.

Relevance: For medical-device production or QMS software, supports selecting assurance activities from intended use, risk and available evidence. It is nonbinding guidance and does not determine other sectors’ obligations.

Status: Final / published · Checked 2026-09-21

Publication identity, scope and status checked against the linked official source. This is not an independent audit of every retained guide statement.

Read source details and applicability →

EudraLex Volume 4, Annex 11 — Computerised Systems ↗

Regulatory guidance / GMP guideline · European Union · January 2011 revision

Scope: Computerised systems supporting activities in the applicable EU pharmaceutical GMP context.

Relevance: For computerised systems used in EU GMP activities, informs lifecycle, supplier and record controls. Confirm applicability to the actual activity; the example does not establish it.

Status: Final / published · Checked 2026-09-21

The Commission index confirms the January 2011 operative revision. The linked PDF could not be retrieved in this check; retained detailed section mappings need review against an authorized copy.

Read source details and applicability →

Artificial Intelligence Risk Management Framework (AI RMF 1.0) and NIST AI 600-1 ↗

Industry guidance / framework · United States · AI RMF 1.0 (2023); GenAI Profile (2024)

Scope: Cross-sector AI governance and risk management, including generative AI.

Relevance: A voluntary framework for describing AI risks, evaluation and ongoing management. Its suggested practices are not regulatory requirements.

Status: Final / published · Checked 2026-09-21

Publication identity, scope and status checked against the linked official source. This is not an independent audit of every retained guide statement.

Read source details and applicability →
Was this useful? Leave feedback

Was this resource useful?

Was this template clear and useful? Tell us which instruction or field could be improved.

Loading contribution options…

Questions and moderated discussion

Questions and discussion

Ask a question or share a perspective. Contributions are reviewed before publication.

Loading contribution options…

Suggest a correction

Sent privately to the editorial moderation queue. Your account email and correction are not published as a comment. Do not include confidential or personal information.

Resource: AI functional risk assessment

Loading sign-in status…

Correction details