Failure Mode and Effects Analysis — what it is and when you need it
PlannedStructured failure-mode analysis scoring severity, occurrence and detectability to prioritise design and test controls.
- Who writes it
- The engineering function, with the joint carrying ownership.
- When it appears
- Design stage — How the solution will meet it.
- What requires it
- ICH Q9 — clause Annex I.3
- IEC 60812
- Traceability
- Traces back to URS requirement IDs. Each acceptance criterion here should name the requirement it verifies.
What it must contain
- Scope, system identification and the revision it applies to.
- The responsibilities of each contributing function, and the approvers.
- A traceability column linking every item back to the URS requirement it addresses.
- 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.
- Broken traceability — requirement IDs renumbered without updating this document.
- 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.
Pharma4i does not generate this document yet
The URS module is the only generator available today. Leave your address and you'll hear once this one exists — signups decide what we build next.
Related in Planning & Specification