# 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.

| Field | Completed example |
| --- | --- |
| System | PRA-01 v0.8; model M-2026-09-eval; P-03 / PAR-02 / RET-04 |
| Users / process | Qualified validation personnel reviewing production-equipment validation protocols |
| Inputs / outputs | Controlled English text protocols and approved requirement revisions; draft source-linked candidate findings |
| Permitted use | Controlled evaluation of candidate mismatches; full required review remains |
| Exclusions | No approval, production release, source editing, workflow actions or unsupported scans/languages |
| Review | Verify each accepted finding; independently complete required review and escalate conflicts |
| Acceptance / owner | Evidence plan TP-01 and risks R-01–R-06; validation process owner |
| Triggers | Model, prompt, parser, source, permission, interface, user or reliance changes |

## Related guidance

- [Read chapter 3: Defining Intended Use for AI](https://csvtocsa.com/ai-assurance-academy/ai-in-csv-csa-chapter-3-intended-use-and-context-of-use)

- [Read chapter 7: AI Validation Evidence Plan](https://csvtocsa.com/ai-assurance-academy/ai-in-csv-csa-chapter-7-data-governance-provenance-and-alcoa-for-ai)

- [Read chapter 20: AI Release Decision: Complete Case Study](https://csvtocsa.com/ai-assurance-academy/ai-in-csv-csa-chapter-20-end-to-end-case-study-and-inspection-readiness)

Canonical page: https://csvtocsa.com/worksheets/ai-intended-use