SOP: Real-Time Release Disposition for Short-Shelf-Life Cell and Gene Therapy Product

This is a ready-to-use SOP for disposing a cell or gene therapy product with a short shelf life, sometimes as little as 24 to 72 hours, using in-process and rapid test results rather than waiting on the full conventional final-release testing suite. The regulatory bar does not move because the clock is short. This procedure is built so the controls stay meaningful under time pressure instead of becoming a rubber stamp. Replace every <<FILL: ...>> placeholder with your own specifics, set your document numbers and dates, and route it through document control. A filled specimen follows. Verify each cited regulation against the current source before you rely on it. This is general guidance to adapt, not legal or regulatory advice.

Document control header

1. Purpose

This procedure defines how <<FILL: COMPANY NAME>> disposes a short-shelf-life cell or gene therapy lot for infusion using in-process and rapid test data, in place of, or ahead of, results that cannot complete within the product’s shelf life. Its objective is a disposition decision that is fast without being casual: every control a conventional release decision requires is still met, compressed into hours rather than days.

2. Scope

Applies to any product whose shelf life is short enough that one or more conventional release tests cannot complete before use, most commonly fresh (non-cryopreserved) autologous cell therapy product. It covers the disposition step itself and the handling of any test that remains pending (not yet resulted) at the time of disposition. It does not apply to products released on the full conventional testing suite with adequate shelf life margin; use the standard batch disposition SOP for those.

3. Responsibilities

4. Definitions

• Real-time release (testing): disposition of product based on a combination of in-process measurements and rapid tests that together provide assurance equivalent to the conventional final-release test suite, rather than waiting for every conventional assay to complete.
• Pending test: a test that has been initiated but cannot complete before the disposition decision or before product use (for example, classical compendial sterility on a product with a shorter shelf life than the test’s turnaround).
• Pre-staged disposition view: the assembled set of reviewable data, in-process results, rapid test results, identity confirmation, and critical audit trail records, built before the releaser begins the review, not gathered while the review is underway.
• Hold authority: the releaser’s ability to hold or reject product without first obtaining a manager’s agreement.

5. Procedure

5.1 Pre-stage the review

1. As results are generated, the system (or a designated person) assembles the pre-staged disposition view: in-process results, rapid sterility and endotoxin status where applicable, identity confirmation, and the critical audit trail records for the systems that generated them.
2. The pre-staged view is available to the releaser before manufacturing finishes the lot, so no assembly work remains once the clock starts on the disposition decision itself.

5.2 Make audit trail review a disposition gate

1. The disposition step requires the releaser to confirm the critical audit trails (result generation, any re-analysis or invalidation, relevant e-signatures) before a release decision can be recorded.
2. Where the system supports it, configure it so disposition cannot be recorded without this confirmation step completed. Where it does not, the paper or electronic disposition record includes an explicit sign-off line for it, and the record is incomplete without it.

5.3 Follow the pre-defined out-of-bounds path

1. Where an in-process or rapid test value is aberrant, atypical, or fails its acceptance criterion, the releaser follows the pre-approved path defined in Attachment A (section 9): who is notified, what additional data is reviewed, and what the default disposition is absent a documented, evidenced resolution.
2. No path is improvised at the bench. If a situation arises that Attachment A does not cover, the default is hold, and Attachment A is updated afterward through change control.

5.4 Protect the authority to hold

1. The releaser may hold or reject the lot without first persuading a manager or obtaining pre-approval. This authority is not conditional on time pressure, clinical urgency, or a treating site waiting on the product.
2. Any pressure applied to a releaser to release against their judgment is itself a quality event and is reported per <<FILL: SOP-ID for quality events>>.

5.5 Record the basis for any pending test

1. Where a test remains pending at the time of disposition (most often classical compendial sterility), the disposition record states which test is pending, the expected result date, and the pre-defined action plan if the result is later out of specification, including the patient notification path per <<FILL: SOP-ID / clinical protocol reference>>.
2. The pending-test action plan is agreed and documented before the first lot is released under it, not improvised the first time a pending result actually fails.

5.6 Disposition and communication

1. The releaser records the disposition decision (release, hold, reject) with the basis, signs and dates it, and communicates it through the defined channel to the treating site.
2. QA reviews a sample of real-time release disposition decisions on a defined cadence (see section 6) to confirm the gate is functioning as designed, not becoming a formality.

6. Acceptance criteria

• The pre-staged disposition view was complete and available before the disposition decision began.
• The critical audit trails were confirmed as part of the disposition record, not deferred or skipped.
• Any aberrant value followed the pre-defined path in Attachment A; no path was improvised.
• The releaser’s hold authority was exercised without requiring prior manager approval, where used.
• Any pending test carries a documented action plan, agreed in advance, including patient notification where applicable.
• QA’s periodic review of disposition decisions (at minimum <<FILL: frequency, e.g. monthly>>) confirms the gate functioned as designed for the sampled decisions.

7. References

21 CFR 211.165, 211.192 (testing and release requirements). 21 CFR Part 11 (electronic records; audit trails). EU GMP Annex 1 (contamination control, for real-time release testing principles) and Annex 16 (Qualified Person certification and batch release). ICH Q9(R1), Quality Risk Management. FDA guidance, Data Integrity and Compliance With Drug CGMP (2018). Confirm the current pharmacopeial alternative-methods framework applicable to any rapid sterility, mycoplasma, or endotoxin method used to support disposition.

Confirm the current version and clause numbers of each reference before issue.

8. Record generated: real-time release disposition record

9. Attachment A: pre-defined out-of-bounds paths (example, adapt to your assays)

10. Revision history

11. Approvals

Filled specimen

The following shows a completed disposition record for an example autologous lot with a pending compendial sterility result. Values are illustrative; replace them with your own.

In this example nothing about the review was skipped because the clock was short: the audit trail confirmation happened as part of disposition, not after, and the pending compendial sterility test carried an action plan the treating site already knew about before the product shipped. That is what makes a fast release defensible instead of merely fast.

Common inspection findings this SOP prevents

• A disposition decision recorded before the audit trail was actually reviewed, review deferred to “later” and never completed.
• An aberrant in-process value handled by improvised judgment at the bench rather than a pre-approved path.
• A releaser pressured to release against their own judgment, with no record that the pressure occurred.
• A pending compendial test with no documented plan for what happens if it later fails.
• Real-time release claimed for a test that was, in practice, simply never performed.

How to adapt this SOP

1. Set your document number, owner, and effective date in the header.
2. Rewrite Attachment A for your specific product’s in-process and rapid tests, and the real conditions that can occur.
3. Confirm which tests in your program are genuine real-time release candidates versus tests that must remain pending, and write the pending-test action plan for each before your first release under this procedure.
4. Point the cross-references to your real quality-event and clinical-protocol procedures.
5. Confirm every regulation in section 7 against the current published version before issue.