Quality Technical Agreement — what it is and when you need it
PlannedDefines GMP responsibilities between contract giver and contract acceptor.
- Who writes it
- The quality function, with the joint carrying ownership.
- When it appears
- Specify stage — What is needed, and why.
- What requires it
- EU GMP Chapter 7 — clause 7.10
- Traceability
- Sits outside requirement traceability; it governs the system rather than verifying it.
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.
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 Quality System Records