This is a ready-to-use protocol for an engineering (demonstration) run at a receiving site, paired with a fixed-agenda after-action review designed to surface surprises while they are still cheap to fix. Replace every <<FILL: ...>> placeholder with your own specifics and route it through your normal document control, review, and approval. A worked filled specimen follows. Verify each cited reference against the current source before you rely on it.
Document control header
| Field | Entry |
|---|---|
| Document title | Engineering Run Protocol for <<FILL: product / process>>, Run <<FILL: number>> |
| Document number | <<FILL: e.g. ER-2026-011>> |
| Version | <<FILL>> |
| Effective date | <<FILL>> |
| Receiving site | <<FILL>> |
| Linked transfer plan / risk assessment | <<FILL: TTP-ID / RA-ID>> |
| Protocol owner | <<FILL>> |
1. Objective
This engineering run demonstrates that the receiving site can execute <<FILL: process / unit operation>> under its own equipment, facility, and personnel, before any batch from this transfer is called a validation or process performance qualification batch. Its purpose is to fail safely: to find equipment, procedure, and operator gaps here, where they are cheap, rather than during PPQ, where they are not.
2. Scope
| Dimension | Decision |
|---|---|
| Process steps covered | <<FILL>> |
| Batch scale | <<FILL: commercial scale? if not, state the bridging rationale>> |
| Material disposition | Not for commercial release |
| Run number and sequence | <<FILL: e.g. run 1 of 2, equipment fit>> |
3. Roles
| Role | Responsibility |
|---|---|
| Run lead | Owns protocol execution, calls the deviation-versus-observation decision in real time. |
| Receiving site operators | Execute the batch record as written, document any deviation from it as it happens. |
| Sending site SME (if present) | Observes, compares to sending-site experience, does not operate equipment. |
| Quality Assurance | Reviews the run in real time or near-real time, dispositions deviations. |
| Analytical / QC | Executes in-process and release testing per the transferred or bridged methods. |
4. Entry criteria
| Criterion | Status |
|---|---|
| Facility qualified for this process | <<FILL>> |
| Equipment IQ/OQ complete | <<FILL>> |
| Personnel trained on the receiving site’s version of the procedure | <<FILL>> |
| Materials released | <<FILL>> |
| Analytical methods needed for this run transferred or bridged | <<FILL>> |
Gap assessment <<FILL: GA-ID>> closed for all rows affecting this run | <<FILL>> |
The run does not start until every entry criterion is met. “Materials expected to release before results are needed” is not a met criterion.
5. Exit criteria
| Criterion | Status |
|---|---|
| Batch record executed to completion, or terminated with a documented rationale | <<FILL>> |
| All deviations dispositioned: closed, or escalated to formal investigation | <<FILL>> |
| In-process and release data reviewed against the process’s CPP/CQA ranges | <<FILL>> |
After-action review held within <<FILL: e.g. 5 business days>> of run completion | <<FILL>> |
| Run lead and QA sign-off on whether this run supports proceeding to the next stage | <<FILL>> |
6. Data collected
State what data this run generates: critical process parameters, critical quality attributes, in-process test results, yield, cycle time, and any parameter flagged in the linked risk assessment as a change driver for this transfer.
7. Deviation handling during the run
Every deviation observed during the run is logged in real time, with an immediate call on whether root cause is already known or needs a formal investigation. No deviation is deferred to “review later”; the after-action review agenda below is where the disposition gets finalized, not where the deviation first surfaces.
8. After-action review: fixed agenda
Hold this review within days of the run, while operators still remember what felt different from the batch record. Run the agenda in this order, every time:
- Step-by-step walk of the batch record against what was actually planned.
- Every deviation opened during the run, with its disposition: root cause known and closed, or escalated to formal investigation.
- Operator and analyst observations that never made it into the record: the moments that felt different from the procedure but didn’t trigger a deviation.
- Any in-process or release result trending toward a limit, even one that technically passed.
- Closing round: each attendee names one thing to change before the next run.
| Agenda item | Finding | Disposition (MPI change / risk assessment update / no change needed) | Owner | Due |
|---|---|---|---|---|
| Batch record walk | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
| Deviations | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
| Undocumented observations | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
| Results trending toward a limit | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
| Closing round actions | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
Assign an owner and a due date to every action before the meeting ends, not in a follow-up email.
9. Summary and recommendation
State plainly whether this run supports moving to the next stage (next engineering run, or PPQ), and list any action from section 8 that must close before that next stage can begin.
10. References
FDA guidance, “Process Validation: General Principles and Practices” (January 2011). ICH Q10, Pharmaceutical Quality System. ICH Q9(R1), Quality Risk Management.
Confirm the current version of each reference before issue.
11. Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL>> | <<FILL>> | Initial issue. |
12. Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Author (Run lead) | <<FILL>> | ||
| Receiving site process owner | <<FILL>> | ||
| Approver (QA) | <<FILL>> |
Filled specimen
Extract from engineering run 1 of Acme Therapeutics’ ATX-207 lentiviral-vector CAR-T process transfer to a CDMO. Company, product, and numbers are illustrative.
| Agenda item | Finding | Disposition | Owner | Due |
|---|---|---|---|---|
| Results trending toward a limit | Viral vector titer approximately 30 percent below the sending site’s historical range on a split sample tested at both labs | Root cause investigation opened same day; risk assessment RA-TT-041 updated to reflect the reference-material variable as confirmed, not hypothetical | Analytical lead | Immediate |
| Undocumented observations | Receiving-site analyst noted the qPCR standard curve used a locally sourced reference material lot, a detail not called out in the transferred method document | Method document updated to explicitly name the qualified reference material lot and prohibit local substitution without a bridging study | Analytical lead | Before run 2 |
| Closing round actions | Run lead: schedule the reference-material bridging study before run 2. QA: hold run 2 pending bridging study closure. Sending-site SME: confirm no other reagent substitutions occurred that were not documented. | All three actions logged with named owners | See finding | Before run 2 |
Summary and recommendation: run 1 does not support proceeding to run 2 until the reference-material bridging study closes. The titer gap, caught by the standing after-action review item reviewing any result trending toward a limit, was resolved as a documented reference-material equivalency rather than a full assay revalidation, at a cost of roughly two weeks. The same gap found after a pivotal batch shipped for release testing would have meant a batch on hold and a comparability question over every prior pivotal batch’s titer result.
Common inspection findings this protocol prevents
- An engineering run with no defined entry or exit criteria, so “was this run adequate” has no documented answer.
- A deviation observed during the run and only informally discussed, never logged or dispositioned.
- An after-action review held, if at all, with no fixed agenda, so the same category of finding gets missed every time.
- A result that technically passed but was trending toward a limit, never flagged because nobody’s job was to look for it.
- Action items from the after-action review with no owner or due date, so they quietly do not happen.
How to adapt this protocol
- Set your document number and link it to the transfer plan and risk assessment it serves.
- Confirm every entry criterion in section 4 against actual qualification and release records before the run starts, not against a plan that assumed they would be ready.
- Hold the after-action review within the stated window every time, even under schedule pressure; a review held weeks later loses the details that make it useful.
- Never skip the fixed agenda order in section 8; the “results trending toward a limit” item is the one most often dropped under time pressure, and it is the one that caught the titer gap in the specimen above.
- Track every action from section 8 to closure before the next engineering run or PPQ batch starts.