Assessment · worksheet · CSVtoCSA editorial

AI intended-use statement

Version 2.0 · Updated 2026-09-21 · Assessment

Define the proposed use precisely enough to select risks, controls and evidence.

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

When to use it

Use when you need to define the proposed use precisely enough to select risks, controls and evidence.

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

  • System and configuration: Identify the application, version and relevant model/service identifiers.
  • Users and process: Name the qualified users and the activity supported.
  • Inputs and source documents: Identify source types, permissions, versions and supported formats/languages.
  • Outputs and reliance: State the output and how it can influence a decision or record.
  • Permitted use: Describe the bounded task and approved conditions of use.
  • Exclusions: State prohibited actions and unsupported uses.
  • Human review: Specify source verification, independent work, escalation and decision ownership.
  • Acceptance basis: Link intended use and failure consequences to the planned evidence.
  • Owner and reassessment triggers: Identify accountable roles and changes that require review.

Completed fictional example

Fictional record IU-01 for PRA-01. This is a restricted evaluation use, not an approval for production.

FieldCompleted example
SystemPRA-01 v0.8; model M-2026-09-eval; P-03 / PAR-02 / RET-04
Users / processQualified validation personnel reviewing production-equipment validation protocols
Inputs / outputsControlled English text protocols and approved requirement revisions; draft source-linked candidate findings
Permitted useControlled evaluation of candidate mismatches; full required review remains
ExclusionsNo approval, production release, source editing, workflow actions or unsupported scans/languages
ReviewVerify each accepted finding; independently complete required review and escalate conflicts
Acceptance / ownerEvidence plan TP-01 and risks R-01–R-06; validation process owner
TriggersModel, prompt, parser, source, permission, interface, user or reliance changes

Blank template

System / record ID: ____________________

Prepared by / date: ____________________

Required review / approval under local procedure: ____________________

FieldYour entry
System and configuration____________________
Users and process____________________
Inputs and source documents____________________
Outputs and reliance____________________
Permitted use____________________
Exclusions____________________
Human review____________________
Acceptance basis____________________
Owner and reassessment triggers____________________
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 intended-use statement

Loading sign-in status…

Correction details