Document Intended Use and Clear Acceptance Expectations
How to describe what a computerized system is actually used for, and how to turn its most important needs into acceptance expectations that someone can observe. Includes a weak statement, an improved one and a copyable paragraph.
Written by CSV/CSA Maturity Editorial TeamPublished 9 min read
On this page13 sections
An intended-use statement for a computerized system says, in one paragraph, who uses the system, for which activity, with which inputs, to produce which outputs or records, and what it is not used for. Acceptance expectations then turn the most important needs behind that use into results someone can observe, stated so that two reviewers would judge them the same way. Write both from the process as it actually runs, not from the supplier's feature list.
This guide covers operational intended use: how your organization uses a system, such as a quality workflow, inside its own processes. It does not cover the regulatory "intended use" of a medical device product, which is a separate concept explained in the next section. The steps support the intended use practice area of the CSV/CSA Maturity Assessment, a self-assessment of computer system validation (CSV) and computer software assurance (CSA) practices. CSV here does not mean comma-separated values.
Two meanings of "intended use"
Device manufacturers meet both meanings, so the distinction matters most to them. FDA's final guidance on computer software assurance [S02], issued in February 2026, gives nonbinding recommendations for software used as part of medical device production or the quality management system. The guidance document [S03] gives no recommendations for validating software that is itself a device. Within its scope it names identifying the intended use as the first step of its framework, recommends examining the intended use of individual features, functions and operations, and lists the intended use among the contents of the record. The guidance is nonbinding, but it says the underlying regulation requires device manufacturers to validate such software for its intended use.
For EU GMP for medicinal products, Annex 11 [S36] says user requirements should describe the required functions of the system and be traceable through the life cycle (clause 4.4). As of November 12, 2026, the EudraLex Volume 4 index [S04] lists Annex 11 as the January 2011 revision.
Our reading is that both sources treat the description of use as the reference point for the work that follows. The structure and examples in this guide are ours, not theirs, and which text applies to your systems is a question for your quality and regulatory specialists.
Step 1: Describe the operational activity
Start from the process, not the product. Write one sentence that says who does what with the system and to what end. If the sentence could describe any organization's use of the product, it is still a product description. Where you can, watch a user carry out the task first. The statement should describe what happens, workarounds included.
Step 2: Identify users and inputs
List the roles that touch the system and what each one does there. Include readers and approvers, not only the people who enter data. Then list what goes in (documents, data, decisions) and whether each item is typed in by a person or arrives from another system.
Step 3: State outputs and boundaries
Say what comes out and who relies on it: a record, a decision, a report, a file passed to another system. Then state the boundary, which is the easiest part to leave out. Write what the system is not used for, which neighboring process covers that, and which installed functions are not used. A clear boundary lets a reviewer set a function aside for a stated reason.
Step 4: Separate intended use from the supplier's feature list
A feature list says what the product can do. Intended use says what you rely on it to do. The supplier's description is a useful input, and the assessment's note on this question is direct: answer for real operational use, not only a generic supplier description. One test helps. If the supplier could have written your sentence without visiting your site, the sentence describes the product.
A weak statement and an improved one
Illustrative example. Both versions describe the same synthetic document control workflow at "Site A", the entry SYS-001 used in the inventory template with three synthetic rows. No real system, supplier or organization is described.
Weak version. "The document management system is used to manage controlled documents in line with GMP. It provides configurable workflows, version control, electronic signatures, search, dashboards and reports."
Improved version. "Site A uses the document control workflow (inventory entry SYS-001) to move controlled procedures through drafting, review, approval, issue and periodic review. Authors in any department draft and revise procedures. Reviewers comment, the head of the owning department and a quality approver approve, and document control staff set the effective date. The workflow receives the draft, its document type and owning department, review comments and approval decisions. It produces the effective version with its approval record, withdraws the superseded version from general view, and lists procedures due for periodic review. Staff rely on it to find the current effective procedure. It is not used for batch records, completed forms or training records, which other processes handle, and printed controlled copies are issued by hand outside it. The reporting module is installed and is used for workload planning only. Accountable owner: head of document control. This statement is reviewed when the workflow, its user groups, its configuration or the records it produces change."
What changed between the two:
| Element | Weak version | Improved version |
|---|---|---|
| Activity | "Manage controlled documents" | Names the five stages the workflow carries out |
| Users | None named | Authors, reviewers, two approvers, document control staff, and staff as readers |
| Inputs and outputs | None | Draft, document type and decisions go in. The effective version, its approval record and a due list come out |
| Boundaries | None | Batch records, completed forms, training records and printed copies are outside |
| Features and use | Lists what the product offers | Says which functions are relied on, and that reporting is not used for quality decisions |
| Ownership and review | None | Names an owner and the events that trigger review |
The improved version is longer, and length is not the point. Every added sentence answers a question a reviewer would otherwise have to put to the author.
Copyable intended-use paragraph
Adapt the wording. A system that only passes data between two others needs a different emphasis from a workflow with human approvals, and the same sentences will not suit both.
Step 5: Capture the important needs
From the statement, pull out the needs whose failure would matter: a wrong record, a missed approval, a superseded procedure still in use. Keep the list short enough to discuss in one meeting. Many teams record these as user requirements with acceptance criteria. The assessment calls them needs and acceptance expectations so that its question fits any document format.
How much assurance each need deserves is a separate decision. The guide to connecting functional risk to a proportionate assurance approach takes it from there.
Step 6: Define observable acceptance expectations
An acceptance expectation is observable when it names a condition, an action and a visible result, so that two reviewers watching the same demonstration would agree whether it was met. "The approval workflow works correctly" fails that test. "A procedure with a missing quality approval cannot be made effective" passes it.
Agree the expectations with the people who use the system and with quality. The table links four needs from the document control example to an expectation, an owner and an evidence reference. It is a synthetic sample: the identifiers, roles and dates are invented.
| Need | Acceptance expectation | Owner | Evidence reference |
|---|---|---|---|
| N-01. Staff see only the current effective version of a procedure | When version 3 of a test procedure becomes effective, a general user who searches for it is shown version 3 only. Version 2 is marked superseded and opens only for document control staff. | Head of document control | Test record TR-001-03 |
| N-02. A procedure cannot become effective without both required approvals | An attempt to set an effective date while the owning department's approval or the quality approval is missing is refused, and the document stays in approval. | Quality approver | Test record TR-001-05 |
| N-03. The approval record shows who approved, in which role and when | The effective version shows each approver's name, role and the date and time of approval. None of these can be edited after approval. | Head of document control | Test record TR-001-06; approval sample AP-0077 |
| N-04. Procedures due for periodic review are identified in advance | A procedure whose review date is 60 days away appears on its owner's due list. | Document control coordinator | Report sample RS-001-02 |
The evidence reference is a pointer to a record held in your own system. It is not the evidence itself. Each row can then be followed forward to the assurance activity and its result, and the how-to on reviewing traceability with one evidence chain picks up at that point.
Step 7: Review when use changes
Review the statement and its expectations when the workflow, the user groups, the configuration, an interface or the records produced change, and when a supplier release alters a function you use. Then check the statement against actual use: ask a user to show you the task and compare. In the example, the day a department starts storing completed forms in the workflow, the boundary sentence is wrong and the statement needs its owner's attention.
Finish with a reviewer test. Hand the statement and the table to a colleague who did not write them. If that person can explain the boundary and the expected behavior without asking the author, the record is doing its job.
How this maps to the assessment
The intended use practice area has two questions. The table quotes their third and fourth practice descriptions.
| Question | Third description (score 2) | Fourth description (score 3) | Evidence to have on hand |
|---|---|---|---|
| Q03, intended-use descriptions | Intended use identifies the users, activities, boundaries and outputs relevant to the selected scope. | Owners review those descriptions when workflows change and check them against actual use. | A current intended-use statement and the owner who approved it |
| Q04, needs and acceptance expectations | Responsible users and quality stakeholders agree specific needs and acceptance expectations. | Changes, review feedback and observed use are used to maintain those needs and expectations. | An approved requirements sample with clear acceptance expectations and a change history |
Select a description only if you can point to the record behind it, and choose "I do not know yet" if you cannot. You can read both questions in the intended use area of the assessment.
Limitations
- The example is specific enough to adapt. It is not a validated requirements package, and the same wording will not fit every system.
- A clear statement does not show that a system is fit for its intended use. It gives later assurance work something definite to test against.
- This guide deals with operational intended use only. It says nothing about the regulatory intended use or classification of a medical device product.
- The FDA guidance cited here covers software used in medical device production and quality management systems, and Annex 11 belongs to the EU GMP guidelines for medicinal products. Neither is extended beyond its scope in this guide.
- Answers in the assessment are self-reported. A higher practice description means the group selected it, not that anyone verified the records.
Related reading
- Risk-based software assurance: from functional risk to an assurance activity: the next decision after intended use, with a synthetic decision record.
- Review validation traceability by following one need to its evidence: takes a single need through its evidence version, finding and disposition.
- Build a GxP computerized system inventory you can maintain: where the one-line summary of each intended use is kept, next to its owner.
This article describes assessment model csa-maturity-2.0.0.
Sources and references
- S02Computer Software Assurance for Production and Quality Management System Software. U.S. Food and Drug Administration.
Final guidance (nonbinding), dated February 2026; covers software used in medical device production and quality management systems.
- S03Computer Software Assurance for Production and Quality Management System Software: Guidance for Industry and Food and Drug Administration Staff. U.S. Food and Drug Administration.
Final guidance document (PDF), issued February 3, 2026; nonbinding; supersedes the final guidance issued September 24, 2025.
- S04EudraLex - Volume 4 - Good Manufacturing Practice (GMP) guidelines. European Commission.
Official index of EU GMP guidelines; listed Annex 11 as 'Computerised Systems (revision January 2011)' when checked on November 12, 2026.
- S36EudraLex Volume 4, Annex 11: Computerised Systems. European Commission.
EU GMP guideline, revision 1, with a stated deadline for coming into operation of June 30, 2011; the version linked from the EudraLex index on November 12, 2026.