This is a ready-to-use running log for tracking every deviation reported by a contract manufacturer, from the original event through confirmed notification, sponsor review of root cause, and a cross-network impact check. Replace every <<FILL: ...>> placeholder with your own specifics. Update it at every notification and review the open rows at every joint quality meeting, so a deviation at one site never stays a question that site alone gets to answer. A filled specimen follows.
Instructions
Log every deviation notified by a partner CDMO under the quality agreement, regardless of severity. Do not wait for the partner’s investigation to close before opening a row; open it at notification and update it through confirmation, sponsor review, and disposition. Retain per <<FILL: document retention period>>.
Field definitions
| Field | Format | Required | Who completes it | When |
|---|---|---|---|---|
| ID | <<FILL: sequential, e.g. CDMO-DEV-041>> | Yes | Supply chain quality | At notification |
| CDMO site | Named site | Yes | Supply chain quality | At notification |
| Event date | Date | Yes | Supply chain quality, from partner’s record | At notification |
| Confirmed date | Date | Yes | Supply chain quality, from partner’s record | At notification |
| Notification lag | Confirmed date minus event date | Yes | Supply chain quality | At notification |
| Within quality agreement window | <<FILL: yes/no>> | Yes | Supply chain quality | At notification |
| Partner severity classification | <<FILL>> | Yes | Partner, recorded by sponsor | At notification |
| Raw investigation reviewed, not just summary | <<FILL: yes/no, date>> | Yes | Supply chain quality | Before disposition |
| Same failure mode prior occurrence check | <<FILL: yes/no, reference if yes>> | Yes | Supply chain quality | Before disposition |
| Cross-network impact check: same step at another site | <<FILL: yes/no, site if yes>> | Yes | Supply chain quality | Before disposition |
| Disposition | <<FILL: closed / CAPA opened / escalated>> | Yes | Sponsor QA | At closure |
| Status | <<FILL: open / under review / closed>> | Yes | Supply chain quality | Ongoing |
Log
| ID | Site | Event date | Confirmed date | Lag | Within window | Severity | Raw investigation reviewed | Prior occurrence | Cross-network check | Disposition | Status |
|---|---|---|---|---|---|---|---|---|---|---|---|
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
Filled specimen
Two rows from an example three-site network. Company and site names are illustrative.
| ID | Site | Event date | Confirmed date | Lag | Within window | Severity | Raw investigation reviewed | Prior occurrence | Cross-network check | Disposition | Status |
|---|---|---|---|---|---|---|---|---|---|---|---|
| CDMO-DEV-041 | CMO Alpha, drug substance | <<FILL: date>> | <<FILL: date, 3 days later>> | 3 days | Yes, within the 5-business-day critical-deviation window | Major | Yes, reviewed 2026-XX-XX; causal chain traced to a calibration drift on a bioreactor pH probe, not stopped at “operator error” | No prior occurrence on this probe in the past 24 months | No, this unit operation does not run at CMO Beta or CMO Gamma | CAPA opened at CMO Alpha; probe calibration frequency increased | Closed |
| CDMO-DEV-042 | CMO Beta, fill-finish | <<FILL: date>> | <<FILL: date, 9 days later>> | 9 days | No, quality agreement specifies 5 business days for a major deviation | Major | Yes, reviewed; root cause was a fill-needle wear pattern | Yes, same wear pattern closed as “isolated” twice in the prior 12 months at this site | N/A, single-site equipment issue | Escalated to rung 3, joint quality review, as a pattern rather than a single event | Under review |
The specimen shows the log doing its job on both rows: CDMO-DEV-041 closes cleanly because the notification was timely, the raw investigation held up, and the cross-network check confirmed no other site shares the exposure. CDMO-DEV-042 does not close quietly. The notification lag breached the agreed window and the same failure mode has now recurred a third time, so the log itself is what surfaces the pattern that justifies escalating past the working level.
Common inspection findings this log prevents
- A deviation notification lag measured only against the event date informally, never checked systematically against the quality agreement’s stated window.
- A partner’s investigation summary accepted with no record confirming the sponsor reviewed the underlying raw investigation.
- A repeat failure mode at a single site closed each time as an isolated event, because no log connects the current row to the prior occurrence.
- No documented cross-network impact check on file, discovered only when the same failure mode later surfaces at a second site.
How to adapt this log
- Set the notification window field to match your own quality agreement’s stated timelines for each severity tier; a single generic window does not fit every agreement.
- Complete the cross-network impact check against your own live process-step map, not from memory; keep that map current as sites and processes change.
- Review every open and recently closed row at each joint quality review, not only when a new deviation arrives.
- Feed a confirmed pattern, not a single row, into the escalation ladder described in the paired article; this log is the evidence base that ladder runs on.