SOP: API Rejection, Reprocessing, Reworking, and Return Handling

This is a ready-to-use SOP for dispositioning an API or intermediate that fails to meet its established specification. Replace every <<FILL: ...>> placeholder with your own specifics, set your document numbers and dates, and route it through your normal document control, review, and approval. A worked filled specimen follows the template so you can see how a completed disposition reads. Verify each cited regulation against the current source before you rely on it.

Document control header

1. Purpose

This procedure defines how <<FILL: COMPANY NAME>> identifies, quarantines, and dispositions an intermediate or an active pharmaceutical ingredient (API) that does not meet its established specification, and how it evaluates and controls material returned from outside the manufacturer’s control. It implements ICH Q7 Section 14, Rejection and Reuse.

2. Scope

This procedure applies to every intermediate and API batch, or portion of a batch, manufactured or handled at the sites listed in the header that fails an in-process control, a release specification, or a stability specification, and to any intermediate or API returned to the manufacturer. It covers rejection, reprocessing, reworking, recovery of materials and solvents, and returns. It does not cover retest dating of conforming material, which is governed by <<FILL: SOP-ID for retest dating and stability>>.

3. Responsibilities

4. Definitions

• Rejection: identifying nonconforming intermediate or API and placing it under quarantine pending disposition (Q7 14.1).
• Reprocessing: running an out-of-specification intermediate or API back through a step the manufacturing process already uses and has validated, such as a repeat crystallization, distillation, filtration, chromatographic purification, or milling pass, to bring it into conformance (Q7 14.2).
• Reworking: bringing an out-of-specification intermediate or API into acceptable quality by routing it through a processing step, or a combination of steps, that the established, validated manufacturing process does not otherwise include (Q7 14.3).
• Recovery of materials and solvents: pulling usable value back out of a process byproduct, such as isolating a reactant or product left behind in a mother liquor or filtrate, or reclaiming a process solvent so it can go back into service (Q7 14.4).
• Return: an intermediate or API sent back to the manufacturer from outside the manufacturer’s control (Q7 14.5).

5. Procedure

5.1 Identify and quarantine

1. On confirmation that an intermediate or API batch fails an in-process, release, or stability specification, apply the quarantine status immediately and physically or electronically segregate the material.
2. Open a deviation record per <<FILL: SOP-ID for deviations>> documenting the nonconformance, the affected batch or lot, and the quantity involved.
3. Notify the Quality Unit and the process owner the same working day.

5.2 Decide the disposition path

1. Determine whether an established, already-validated process step can bring the material into specification unchanged in kind (the same crystallization, distillation, filtration, chromatography, or milling step already described in the batch record). If yes, proceed as reprocessing (5.3).
2. If no established step applies, but a different processing step not part of the validated process could bring the material into specification, proceed as reworking (5.4).
3. If neither applies, or the data generated under 5.3 or 5.4 does not support release, proceed to rejection and disposal (5.6), after considering recovery of a solvent or component material (5.5).
4. Document the disposition decision and its rationale before any processing of the quarantined material begins.

5.3 Reprocessing

1. Confirm the proposed step is part of the established, validated manufacturing process for that intermediate or API.
2. Assess the impact on the impurity profile: identify whether the reprocessing step could concentrate, introduce, or fail to remove an impurity relevant to the specification.
3. Execute the reprocessing step under the existing batch record or an approved reprocessing addendum.
4. Release the reprocessed material against the existing, unmodified specification. Do not loosen the specification to accommodate the reprocessed lot.
5. Record the reprocessing event, the batch or lot identity, the reason, and the release data in the deviation record.

5.4 Reworking

1. Define the proposed reworking step and document why it is not part of the established process.
2. Determine the analytical data required: at minimum, the full release specification, an assessment of the impurity and degradation profile introduced or affected by the additional step, and, where the additional processing could plausibly affect long-term stability, a stability commitment on the reworked lot.
3. Submit the rework plan, with the data requirement, to the Quality Unit for approval before the material is reintroduced to processing.
4. Execute the reworking step under an approved protocol or addendum, generating the data defined in 5.4.2.
5. The Quality Unit reviews the completed data package and approves or rejects release of the reworked material. Route to Regulatory Affairs per 5.4.6 before release if the rework activity touches anything represented in the marketing application.
6. Regulatory Affairs assesses whether the rework activity, or a pattern of repeated reworking of the same step, requires notification, a variation, or a supplement, before the reworked material or any lot made using the newly accepted step is released commercially.
7. Record the reworking event, the full data package, and the Quality Unit disposition in the deviation record.

5.5 Recovery of materials and solvents

1. Recovery of a reactant, an intermediate, or the API from a mother liquor or filtrate, or recovery of a solvent for reuse, is executed only under an approved, documented recovery procedure.
2. Assess whether the recovery step requires validation, following the same logic applied to any other process step.
3. Recovered solvents are used only against a documented specification appropriate to the use; recovered materials are not returned to a batch without confirming they meet the applicable specification for that use.
4. Record the recovery activity, the specification applied, and the disposition of the recovered material or solvent.

5.6 Returns

1. On receipt of a returned intermediate or API, apply quarantine immediately and record the shipping and storage history since it left the manufacturer’s control.
2. Evaluate whether the storage or shipping conditions during the return raise doubt about the material’s quality (temperature excursion, container integrity, elapsed time against the retest or expiry date).
3. If no doubt is raised and testing confirms conformance, the returned material may be returned to inventory.
4. If doubt is raised, disposition the material as reprocessing (5.3), reworking (5.4), or rejection and destruction (5.7), based on the evaluation and any confirmatory testing.
5. Record the return, the evaluation, the testing performed, and the final disposition.

5.7 Rejection and destruction

1. Material that cannot be reprocessed, reworked, or recovered, or for which the data does not support release, is formally rejected.
2. Destroy or otherwise dispose of rejected material per <<FILL: SOP-ID for waste and rejected-material disposal>>, with documented evidence of destruction.
3. Close the deviation record with the final disposition.

5.8 Repeated reprocessing

1. If the same lot, or the same process step across multiple lots, requires reprocessing more than <<FILL: number, e.g. two>> times in <<FILL: period, e.g. a rolling twelve months>>, escalate to a deviation investigation into the root cause of the underlying process step, rather than continuing to reprocess as routine.

6. Acceptance criteria

A disposition is acceptable when all of the following are true:

• The nonconforming or returned material was quarantined immediately on identification, with no use or further processing before disposition was approved.
• The disposition path (reprocess, rework, recover, return to inventory, or reject) is documented with its rationale, and reprocessing is limited to steps already part of the validated process.
• Reworking carries a documented data package (impurity, degradation, and stability as warranted) evaluated and approved by the Quality Unit before the material is reintroduced.
• Recovered materials and solvents are used only against a documented specification.
• Returned material is evaluated against its storage and shipping history before any decision to return it to inventory, reprocess, or rework it.
• Repeated reprocessing of the same step has triggered a deviation investigation into root cause, not continued as a routine practice.
• Regulatory Affairs has assessed reportability for any reworking activity or process change arising from repeated reprocessing.

7. References

ICH Q7, Good Manufacturing Practice Guide for Active Pharmaceutical Ingredients, Section 14 (Rejection and Reuse). ICH Q11, Development and Manufacture of Drug Substances (process understanding underlying the reprocess/rework distinction). ICH Q9(R1), Quality Risk Management. 21 CFR 211.115 (reprocessing, for the finished-dosage analog) and the corresponding API GMP expectations implemented through ICH Q7 in FDA and EU guidance.

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

8. Records generated

• Deviation record documenting the nonconformance, disposition decision, and closure.
• Reprocessing or reworking execution record (batch record addendum or standalone protocol).
• Analytical data package supporting a reworked lot’s release.
• Return evaluation record.
• Recovery record for recovered materials or solvents.

9. Revision history

10. Approvals

Filled specimen

The following shows a disposition worked through the procedure for an example intermediate batch. The company, batch numbers, and data are illustrative; replace them with your own.

In this example the batch qualified as reprocessing because the recovery step was already part of the validated process; had the same batch required a chromatographic polish step never described in the process, the disposition would have followed the reworking path in section 5.4, with a documented impurity and degradation data package and Quality Unit approval before the additional step was executed.

Common inspection findings this SOP prevents

• A rework documented and released as if it were routine reprocessing, with no impurity, degradation, or stability data package.
• Reprocessing executed and released without assessing whether the reprocessing step affects the impurity profile.
• Recovered solvent reused with no specification or documented recovery procedure.
• Returned material placed back into inventory with no evaluation of the shipping or storage history in between.
• The same process step reprocessed repeatedly with no deviation investigation into why the step keeps failing.

How to adapt this SOP

1. Set your document number, owner, and effective date in the header.
2. Point the cross-references in sections 2, 5.1, and 5.7 to your real deviation, retest/stability, and waste-disposal procedures.
3. Set the repeated-reprocessing threshold in section 5.8 to match your quality system’s escalation practice.
4. Confirm the Q7 clause numbers in section 7 against the current published version before issue.