Post-Release Deviation Regulatory Reporting SOP

This is a ready-to-use standard operating procedure for determining whether a deviation, complaint, or quality signal reaching the sponsor from a contract manufacturer triggers a Biological Product Deviation Report (BPDR) or a Field Alert Report (FAR), and for filing it inside the applicable statutory deadline. It applies whenever the triggering information originates at a CDMO rather than inside the sponsor’s own facility. Replace every <<FILL: ...>> placeholder. A filled specimen follows.

Document control header

1. Purpose

This SOP defines how the sponsor classifies, investigates, and files a post-release regulatory report, Biological Product Deviation Report under 21 CFR 600.14 or Field Alert Report under 21 CFR 314.81(b)(1), when the triggering information about distributed product originates at a contract manufacturer, so that the statutory filing clock is met even when the sponsor was not the first party to learn of the event.

2. Scope

This SOP applies to every deviation, complaint, out-of-specification result, or other quality signal concerning product already distributed, discovered at, or communicated by, any CDMO in the sponsor’s network. It does not cover a deviation caught before product release and distribution, which is handled under the sponsor’s standard deviation and batch disposition procedures.

3. Responsibilities

4. Definitions

5. Procedure

5.1 Pathway classification (performed once per product, reviewed at least annually)

1. For every product manufactured in whole or in part by a CDMO, document whether it is approved under a Biologics License Application, subject to BPDR under 21 CFR 600.14, or under a New Drug Application or Abbreviated New Drug Application, subject to FAR under 21 CFR 314.81(b)(1).
2. Record the classification in the product’s regulatory reporting record, referenced by every quality agreement covering that product.
3. Re-confirm the classification whenever a product’s approval basis changes, and at least annually as part of the quality agreement review described in Deviations and change control across a CDMO network.

5.2 Determining the information-receipt date

4. On learning of a quality signal concerning distributed product from any CDMO, immediately request, in writing, the date the CDMO itself first acquired information reasonably suggesting the event, not the date the CDMO’s investigation reached a conclusion and not the date the sponsor was notified.
5. Treat the information-receipt date from step 4, not the date of sponsor notification, as the start of the applicable statutory clock. Document the basis if the two dates differ, since they will differ whenever the quality agreement’s internal confirmation step took real time.
6. Escalate to regulatory affairs and Quality Assurance concurrently with opening the technical investigation; do not wait for the investigation to reach a root cause before starting the reportability assessment.

5.3 Reportability assessment and filing

7. Assess the signal against the applicable trigger: for a BPDR product, whether the event may affect the safety, purity, or potency of distributed product; for a FAR product, whether it is a significant chemical, physical, or other change or deterioration, a specification failure, or a mix-up risk in distributed product.
8. Where the assessment is reportable, file within the applicable deadline measured from the information-receipt date established in step 5: no later than 45 calendar days for a BPDR, no later than 3 working days for an initial FAR.
9. Where the full investigation is not complete by the filing deadline, file with the information available and state plainly what remains open; a FAR in particular is explicitly designed to accommodate an initial report followed by follow-up and final reports, not to wait for a completed investigation.
10. Submit follow-up and final reports as required (additional information for a BPDR; follow-up and final FARs stating root cause and corrective action) and retain the full filing history in the product’s regulatory reporting record.

6. Acceptance criteria

A post-release regulatory reporting event meets this SOP’s bar when: the product’s pathway classification was documented and current at the time of the event; the information-receipt date was established from the CDMO’s own records, not assumed from the sponsor-notification date; the reportability assessment was made and documented regardless of outcome; and, where reportable, the initial report was filed within the applicable deadline measured from the information-receipt date.

7. Records generated

8. References

21 CFR 600.14, Reporting of biological product deviations by licensed manufacturers. 21 CFR 314.81(b)(1), Field alert report. FDA guidance, “Biological Product Deviation Reporting for Blood and Plasma Establishments” (as applicable scope). Deviations and change control across a CDMO network.

Confirm the current version of each reference before issue.

9. Revision history

10. Approvals

Filled specimen

Extract for Acme Therapeutics’ BLA-licensed cell therapy product, manufactured by CMO Beta.

The specimen shows what this SOP exists to prevent: using the 2026-09-30 sponsor-notification date as the clock start would have left 45 days from that date, overstating the time actually available and risking a late filing once the correct start date was reconstructed.

Common inspection findings this SOP prevents

• A Biological Product Deviation Report or Field Alert Report filed using the sponsor-notification date as the clock start, when the information-receipt date at the CDMO was materially earlier.
• No documented, standing pathway classification for a product, so the applicable deadline, 45 calendar days or 3 working days, is determined for the first time during a live event.
• A report held pending a completed root cause investigation, missing the statutory deadline, when an initial report with an acknowledged open investigation would have met it.
• No written record requesting the CDMO’s own information-receipt date, leaving the sponsor dependent on the CDMO’s self-reported notification date with no independent verification.

How to adapt this SOP

1. Set your document number, owner, and applies-to scope in the header.
2. Build the pathway classification record in Section 5.1 for every product in your network before the first event, not during one.
3. Confirm your quality agreements require the CDMO to state its own information-receipt date, not just its notification date, on every quality signal it raises.
4. Align this SOP’s escalation trigger with the escalation ladder in Deviations and change control across a CDMO network, so a reportable signal bypasses the ladder’s lower rungs rather than waiting its turn.