User Requirement Specification — what it is and when you need it
AvailableStates what the system must do, in vendor-neutral terms, so design can be verified against requirements rather than against itself.
- Who writes it
- The engineering function, with the user carrying ownership.
- When it appears
- Specify stage — What is needed, and why.
- What requires it
- EU GMP Annex 15 — clause 3.2
- GAMP 5 — clause Appendix D1
- EU GMP Annex 11 — clause 4.4
- Traceability
- The URS is the origin of traceability: every downstream test references its requirement IDs.
What it must contain
- Scope, system identification and the revision it applies to.
- The responsibilities of each contributing function, and the approvers.
- References to the procedures and records it governs.
- Acceptance criteria or decision rules stated before execution.
- Handling of deviations, and how they are dispositioned before approval.
Common mistakes
- Writing it after the work, so it records what happened instead of governing it.
- Acceptance criteria that are unmeasurable, or added once results are known.
- Copying a template from another site without checking it matches local practice.
- Approvals collected from titles rather than from the functions that contributed.
Where it sits in the lifecycle
- Available
- In development
- Planned
- Connector lines show traceability back to URS requirement IDs.
Generate one
Pharma4i generates this document today, from guided questions across the nine contributing functions.
Create a URSRelated in Planning & Specification