Veterinary Drug Manufacturing: From Lot Packet to Reporting
Build a traceable US finished animal-drug lot packet, then carry its evidence into distribution, complaint review, and regulatory reporting.

In Short
- Veterinary drug manufacturing readiness means being able to connect a finished lot to its application, materials, manufacturing instructions, test evidence,…
- Create the packet before scheduling production.
- Build material genealogy from receipt, not from dispensing.
Define the Operating Boundary
Veterinary drug manufacturing readiness means being able to connect a finished lot to its application, materials, manufacturing instructions, test evidence, labeling, quality decision, and distribution history. This guide builds that connection for US finished animal drugs under approved NADAs or ANADAs. Regulatory references reflect eCFR text as of October 20, 2026. The deliverable is a controlled lot packet—not merely a completed production form.
Parts 210 and 211 provide the drug cGMP framework for this workflow; animal drugs are not outside that framework. Applicable regulations supplement one another, and a product-specific regulation takes precedence over a conflicting general provision. Start with the product category and operations actually performed, rather than assuming that every animal-health product follows the same manufacturing route.
| Product Boundary | Regulatory Anchor | Operational Routing |
|---|---|---|
| Finished animal drug under an approved NADA or ANADA | 21 CFR Parts 210/211; applicable approved-application obligations | Use this lot-packet workflow with the product's controlled requirements. |
| Medicated feed | 21 CFR Part 225 | Route to the feed manufacturing owner; this is not a feed production protocol. |
| Type A medicated article | 21 CFR Part 226 | Route to the Type A manufacturing owner; do not substitute a finished-dose packet. |
| USDA-licensed veterinary biologic | 9 CFR 113.1: licensed biological-product serials/subserials in licensed establishments; also covered imported shipments | Route to the biologics owner; this guide does not establish serial-release procedures. |
Conditional approval, indexed products, compounded products, and extralabel use are not interchangeable with this approved-NADA/ANADA workflow. They are outside this guide's operating scope. Have regulatory identify the applicable pathway before adopting the packet.
Section 514.80 also applies to approved Type A medicated articles, with specified alert and adverse-experience provisions extending to those articles incorporated in feeds. Its records and reports are additional to Parts 211, 225, and 226 cGMP records. Designated medical gases are excluded from 514.80 and follow Part 230 for these records and reports.
Assign the Packet and Its Owners
Create the packet before scheduling production. Give it one lot identifier and an index that points to controlled records without replacing them. A reviewer should be able to distinguish the application baseline from the master revision, and both from the executed record. Record species as a product-identification field; do not assume that a familiar trade name identifies the entire authorized presentation.
| Packet Element | Recommended Content | Accountable Owner |
|---|---|---|
| Application/Product Assignment | NADA or ANADA identifier; applicant; product code; name; strength; dosage form; species; pack size | Regulatory, with quality confirmation |
| Manufacturing Baseline | Master identifier/revision; batch size; specification and method revisions; effective labeling; relevant change assessment | Manufacturing and quality; regulatory for application impact |
| Material Genealogy | Supplier and internal lot identifiers; receipt/shipment links; sample and identity-test references; material disposition | Warehouse and laboratory; quality authorization |
| Execution Evidence | Equipment/line identities; quantities; step records; results; yields; deviations; sampling | Production and packaging |
| Release Evidence | Test register; laboratory review references; label accounting; investigations; quality disposition and quantity | Laboratory and quality unit |
| Post-Distribution Links | Shipments; complaint identifiers; applicant contacts; reporting assessment; submissions and follow-up | Distribution, quality, and regulatory |
Application and Product
Applicant, application identifier, species, strength, dosage form, presentation
Authorized Baseline
Master, specifications, methods, labeling, and applicable change assessment
Finished Lot
Unique lot identity, manufactured quantity, status, and disposition
Upstream Evidence
Component shipments, internal lots, samples, identity results, and material release
Execution and Review
Production, packaging, laboratory data, deviations, and quality decision
Downstream Evidence
Consignees, complaints, regulatory assessments, and report references
The quality control unit has authority to approve or reject materials and drug products, review production records, and approve or reject products made or held under contract. Its responsibilities and procedures must be written and followed. A contract arrangement therefore needs an explicit evidence handoff, not an assumption that the other company has completed the review.
Use the shared Part 211 readiness guide for the broader cGMP control system. This packet concentrates on the animal-drug application/product connection and the lot-to-reporting handoff.
Execute the Controlled Master
Master production and control records are required for each drug product and each batch size. Section 211.186 specifies preparation, dating, signing, and an independent second-person check. The lot's executed record must accurately reproduce the appropriate master and document significant manufacturing, processing, packing, and holding steps under 211.188.
Before the first issue, compare the packet cover with the master: product, strength, dosage form, batch size, revision, and intended presentation. Confirm that the species/product assignment and labeling references agree with the regulatory baseline. This is a recommended eligibility check, not a claim that the regulation requires a separate master for every species.
Written production and process-control procedures must be followed and documented at the time of performance. Deviations must be recorded and justified. Capture actual equipment and line identities, component lots and quantities, step performers/checkers, sampling, results, and yields—not just a succession of completion marks.
Keep Change Assessment Separate From Deviation Handling
Section 514.8 requires applicant notification of changes to approved-application conditions beyond permitted variations, using the applicable route. The holder must assess the effects of a manufacturing change before distributing drug made with it. A local master revision number alone does not answer that application question. Use the NADA/ANADA change-readiness guide for the change routes.
- At a pause or interruption, identify the material state, equipment state, unfinished step, and responsible person.
- Record a departure where it occurred and connect it to the deviation record; preserve the original observation.
- Carry open issues into the next operation's handoff instead of allowing a completed downstream step to conceal them.
- At execution closeout, compare actual and theoretical yields at the phases defined in the master.
For detailed record structure, use the shared batch-record section. The animal-drug-specific addition here is an unbroken connection between the executed instructions and the assigned application/product baseline.
Separate Test Results From Review Status
For the finished drugs in this workflow, 211.165 requires appropriate laboratory determination of satisfactory conformance to final specifications, including each active ingredient's identity and strength, before release. Appropriate microbiological testing is required as necessary for products required to be free of objectionable microorganisms. Build the test register from the applicable product requirements; do not adopt a generic test list as a universal panel.
| Recommended Status | What It Means | Evidence Still Needed |
|---|---|---|
| Not Sampled | Required sample has not been collected | Sample collection and traceable laboratory receipt |
| Testing Pending | Sample exists; required testing is incomplete | Complete results and supporting data |
| Result Available; Review Pending | An analyst result exists, even if within limits | Documented review of the original record |
| Reviewed; Meets Criteria | Result and supporting record have been reviewed | Inclusion in the quality-unit batch review |
| Exception Under Investigation | Result, method execution, or record raises an unresolved issue | Investigation and quality assessment; not a substituted passing status |
Laboratory records must contain complete data from tests needed to assure compliance. Section 211.194 also requires a second person's initials or signature showing review of the original records for accuracy, completeness, and compliance. A summary certificate should point to that evidence rather than conceal its review state.
For each required test, record the sample, method/specification revision, result and units, criterion, analyst/date, reviewer/date, and exception reference. Keep 'not applicable' distinct from 'not done,' with a product-specific basis. If a result changes after review, preserve the prior result and its investigation trail.
Products failing established specifications or other relevant quality-control criteria must be rejected under 211.165(f); any reprocessed material must meet the appropriate requirements before acceptance and use. Route result problems through the site's out-of-specification process, not through selective omission from the packet.
Close Packaging Accountability
Packaging closeout should answer two different questions: were the correct materials used, and can the quantities be accounted for? Section 211.130 requires written procedures for correct labeling and packaging, examination of materials for suitability and correctness, and documented pre-use inspection of the packaging area. Section 211.134 requires label examinations during finishing and of a representative sample at completion, with recorded results.
Use the effective label specimen as the comparison point. Check product identity, strength, species/product assignment, pack size, lot coding, and expiration information against their controlled references. For this workflow, expiration dating must be supported by appropriate stability testing and related to labeled storage conditions under 211.137.
- Record label item code, revision, issued quantity, and issuance to the identified lot and line.
- Separate labels applied to accepted units from labels on rejected units.
- Count setup waste and damaged labels separately from unused labels; document their disposition under the site's procedure.
- Reconcile each controlled labeling item independently. A balanced bottle-label count does not establish an insert count.
- Record finishing examinations and the quantities/statuses of product removed for sampling, rejection, or other purposes.
A useful practice equation is: issued labels = labels on accepted units + labels on rejected units + documented waste + documented unused labels. Do not force the equation to balance by changing an unexplained category. Investigate the difference and retain both the original discrepancy and its resolution.
Maintain the identity and quantity of filled containers held for later labeling. Section 211.130 specifically addresses identification of such containers to preclude mislabeling. The packet should make an unlabeled hold understandable without requiring the reviewer to reconstruct it from operator memory.
Make the Quality Decision Explicit
Section 211.192 requires quality-unit review and approval of production and control records, including packaging and labeling, before release or distribution. Unexplained discrepancies and specification failures must be thoroughly investigated whether or not the batch has been distributed. Investigation must extend to potentially associated batches and products, with written conclusions and follow-up.
Prepare a disposition page that identifies exactly what the reviewer is deciding: lot, presentation, quantity, location, and proposed status. Link the completed test register, executed master, label accounting, deviations, and application-related change assessment. Avoid a single 'QA complete' field that leaves the scope of the decision uncertain.
Resolve These Questions Before Signing
- Does the executed record correspond to the assigned product, batch size, and authorized master revision?
- Were used materials authorized, and can their identities and quantities be traced?
- Are required results complete and reviewed, including investigations affecting their interpretation?
- Do packaging evidence and label quantities agree with the finished-unit accounting?
- Have discrepancies been investigated with a documented product-impact assessment and appropriate associated-lot scope?
- Is the human quality decision recorded with its quantity, date, rationale, and any applicable restrictions?
Separate investigation conclusions needed for disposition from longer-term corrective-action tracking. Do not use an open action list to conceal an unresolved product-quality question. Likewise, a completed corrective action does not retrospectively erase the event or its original evidence. The shared Part 211 quality-unit review and investigation section covers investigation records in greater depth.
For contract work, identify which organization provides each record and how the responsible quality unit obtains it. Missing evidence remains missing even when the manufacturing partner reports that the lot is ready. Quality disposition and regulatory reporting assessments should remain separate, linked decisions.
Work a Fictional Lot Through the Packet
Assign lot F260914 to Fictional Product F: a nonsterile solution containing fictitious active F at 10 mg/mL, identified for dogs, in 100 mL bottles. The applicant is Fictional Harbor Animal Health; the internal application alias is NADA-DEMO-A, not a real application number. The packet specifies master M-F-1000 revision 04, final specification S-F revision 03, and label L-F-100 revision 06.
The packet links active-component lot AF061 and vehicle-component lot VF018 to reviewed identity results and quality release dated September 11, 2026. Bottle lot B091 and closure lot C014 have their own examination/test evidence and release references. The executed record contains formulation quantities; this abbreviated example does not provide a manufacturing recipe.
Manufacture occurs September 14 and packaging September 15. The theoretical bulk quantity is 1,000 L, equivalent to 10,000 nominal 100 mL bottles. The arithmetic assumes nominal-volume equivalents only; it is not a fill-setting instruction. Documented process loss is 20 L, leaving 980 L represented by 9,800 filled bottles.
| Quantity Category | Amount | Accounting Treatment |
|---|---|---|
| Theoretical Output | 10,000 bottle equivalents | 1,000 L ÷ 0.1 L |
| Documented Process Loss | 200 bottle equivalents | 20 L; not packaged units |
| Filled Output | 9,800 bottles | 980 L; 98.0% of theoretical output |
| QC and Reserve Samples | 60 bottles | 20 laboratory + 40 reserve; separately identified, not sale-labeled |
| Prelabel Closure/Visual Rejects | 40 bottles | Segregated before sale-label application |
| Bottles Entering Sale Labeling | 9,700 bottles | 9,800 − 60 − 40 |
| Labeled Packaging Rejects | 30 bottles | Damaged-label units; rejected without rework |
| Accepted Finished Units | 9,670 bottles | 9,700 − 30; 96.7% of theoretical output |
The fictional master sets investigation limits of 97.0–99.5% for filled output and 95.0–99.0% for accepted finished output. Both observed yields are within those training limits. The entire balance is 200 process-loss equivalents + 60 samples + 40 prelabel rejects + 30 labeled rejects + 9,670 accepted units = 10,000 theoretical equivalents.
| Sale-Label Category | Final Count | Evidence |
|---|---|---|
| Issued | 10,000 | Lot-specific issuance record |
| Applied to Accepted Units | 9,670 | Accepted packaging tally |
| Applied to Rejected Units | 30 | Rejected-unit record |
| Setup/Damaged Waste | 120 | 96 initially recorded + 24 recovered from the setup tray |
| Unused | 180 | Counted and destroyed under the fictional site's procedure |
| Accounted For | 10,000 | 9,670 + 30 + 120 + 180; difference zero |
The initial waste entry was 96 labels, leaving an unexplained difference of 24. Deviation D-F-017 records the discrepancy, inspection of the setup tray, recovery and witnessed destruction of 24 damaged labels, and the review supporting the final count. The original entry remains visible. A balanced final total does not replace that investigation record.
At 09:00 on September 16, identity, appearance, pH, and fill results are reviewed; assay has an acceptable analyst result but awaits second-person review; microbiological testing remains pending. The lot stays on hold. On September 17, the fictional packet records satisfactory reviewed results for all required tests, closure of the label discrepancy, and the quality unit's release of 9,670 bottles. The 60 samples and 70 rejected bottles are not included in the released quantity.
Connect Distribution and Retention
Section 211.196 requires distribution records to contain product name and strength, dosage form, consignee name and address, shipment date and quantity, and lot/control number. Connect those records to the released quantity rather than relying on a sales total without lot detail.
| Fictional Movement | Date | Quantity | Balance or Record |
|---|---|---|---|
| Release to Available Stock | 2026-09-17 | 9,670 bottles | Lot F260914; Product F, 10 mg/mL solution, 100 mL |
| Shipment to Fictional Cedar Animal Supply | 2026-09-18 | 6,000 bottles | 100 Example Way, Rockville, MD 20850; fictional address |
| Shipment to Fictional Meadow Wholesale | 2026-09-21 | 2,500 bottles | 200 Example Lane, Frederick, MD 21701; fictional address |
| Remaining Warehouse Stock | After both shipments | 1,170 bottles | 9,670 − 6,000 − 2,500; no other movements assumed |
Keep shipment-level evidence even when regulatory also needs aggregate distribution information. Reconcile the lot ledger to shipping documents and identify returns or later movements separately; do not overwrite the original shipment. Distribution totals and available inventory answer different questions.
| Record Family | Retention Anchor | Packet Practice |
|---|---|---|
| Batch-Specific Production, Control, and Distribution Records | 211.180(a): at least one year after batch expiration for the dated products in this workflow | Retain the expiration reference with the lot index. |
| Component, Container, Closure, and Labeling Records | 211.180(b): at least one year after expiration of the last incorporating/using lot for these dated products | Preserve links to all affected finished lots. |
| Complaint Records | 211.198(b): at least one year after product expiration or complaint receipt, whichever is longer, for these dated products | Connect the complaint date and implicated lot expiration. |
| 514.80 Records and Reports | 514.80(e): five years after submission | Preserve submission dates and report relationships separately from batch release. |
Part 211 records or copies must be readily available for authorized inspection during retention at the establishment where the activities occurred; immediately retrievable electronic records from another location can satisfy that provision. As a practice, test actual retrieval permissions and readability. A filename in an index is not proof that the underlying record remains accessible.
Retrieve Records From a Fictional Complaint
On Monday, September 28, 2026, at 09:00, Fictional Cedar Animal Supply receives a complaint identifying lot F260914. The caller describes leaking bottles and an animal event requiring professional intervention. Photographs show wet cartons and loosened closures. No returned units have yet arrived. Cedar's name appears on the product label and it distributes the product; the exercise treats Cedar as a nonapplicant.
Cedar sends the original information to the applicant at 10:00; applicant receipt is documented at 10:05. The applicant's record-retrieval drill starts at 10:05; all minute targets below run from that time. Do not wait for the record-retrieval exercise to finish before escalating. For this scenario, regulatory documents that the reported event is serious and unexpected and that the suspected distributed-product defect may result in serious adverse drug events. These are fictional assessments, not a conclusion that the drug caused the event.
Section 211.198 requires procedures for written and oral complaints, quality review of possible specification failures, an investigation-need determination, and review for serious and unexpected adverse experiences requiring reporting. Complaint records include available product/lot details, complainant, nature of complaint, and reply. If no 211.192 investigation is conducted, the reason and responsible person's name must be recorded.
| Exercise Target | Retrieve or Establish | What the Reviewer Tests |
|---|---|---|
| First 10 Minutes | Original complaint, receipt timestamps, photographs, contact details, lot identification | Facts remain distinct from inference; regulatory has the initial information. |
| By 25 Minutes | Packet cover, release decision, shipment records, current stock | 6,000 + 2,500 distributed; 1,170 still in warehouse; no unrecorded movements assumed. |
| By 40 Minutes | Closure C014 records, line/equipment references, packaging inspections, test data | Can the team retrieve original evidence rather than only summaries? |
| By 55 Minutes | Other lots using C014 or relevant equipment; complaint history; initial investigation scope | Is associated-lot scope considered despite the original release decision? |
| By 60 Minutes | Quality action log and regulatory handoff worksheet | Named owners, known facts, unknowns, clocks, next actions, and evidence locations. |
These are internal drill targets, not statutory response periods. Quality places the remaining 1,170 bottles on hold for the exercise and assesses distributed-product actions with regulatory and distribution. The investigation examines the 40 prelabel closure/visual rejects, closure-lot evidence, equipment records, and potentially associated lots. It does not assume that the earlier label-count deviation explains leakage.
Pass the retrieval exercise only if another reviewer can open the underlying records, reproduce the quantity balance, identify evidence gaps, and locate the decision owners. Record failures such as inaccessible raw data, an unlinked closure lot, or a shipment without a consignee address. Assign corrective work without changing the original complaint receipt time.
Hand Off the Reporting Clocks
Under 514.3, the applicant owns or holds the NADA/ANADA approval on the owner's behalf. A nonapplicant is another person whose name appears on the label and who manufactures, packs, distributes, or labels the product. A contract manufacturer's business role alone does not establish nonapplicant status. Identify the actual legal roles and contacts before a complaint occurs.
Applicants and nonapplicants must maintain indexed, complete safety/effectiveness files under 514.80(a)(1). Nonapplicants provide required information to the applicant, and the applicant reports to FDA. These US obligations include information from domestic and foreign sources. Use the 514.80 glossary for reporting definitions and distinctions.
- Receive and PreserveOriginal information, receiving entity, timestamp, product/lot, reporter, and source
- Escalate to Named OwnersQuality examines potential product failure; regulatory identifies applicant/nonapplicant duties
- Assess Independent TriggersNonapplicant ADE forwarding; possible serious-risk product defect; serious and unexpected event
- Document Reporting DecisionsTrigger basis, original clock start, confirmed counting convention, deadline, and responsible person
- Maintain Follow-UpSignificant new information, investigation progress, report references, and periodic-report handoff
| Obligation | Trigger and Timing | Handoff Evidence |
|---|---|---|
| Nonapplicant ADE Forwarding: 514.80(b)(3) | Forward adverse-drug-experience reports to the applicant within 3 working days of first receipt. | Original receipt; applicant name/address; report copy; forwarding date. |
| Field Alert: 514.80(b)(1) | Product/manufacturing defect that may result in serious adverse drug events: within 3 working days of first awareness that a defect may exist. | Awareness facts and timestamp; applicant assessment; FDA District Office/local resident-post report reference. |
| Initial Alert: 514.80(b)(2)(i) | Each serious, unexpected adverse drug event, regardless of source: within 15 working days of first receiving the information. | Receipt record; seriousness/unexpectedness assessment; applicant's FDA report reference. |
| Significant-Information Follow-Up: 514.80(b)(2)(ii) | Follow-up within 15 working days of receiving significant new information; promptly investigate the underlying alert event. | New-information receipt, initial-report date, added information, and follow-up reference. |
| No-Information Follow-Up: 514.80(b)(2)(ii) | If additional information is sought but not obtained within 3 months of the initial report, submit a follow-up describing efforts and why information was not obtained. | Initial-report date and documented contact/investigation attempts. |
Fictional Working-Day Worksheet
For arithmetic only, assume Saturdays and Sundays are non-working days, every Monday through Friday is working, and no holiday exclusions apply—including October 12. Treat each triggering date as day zero and start counting on the next assumed working day. These are exercise assumptions, not a legal definition. The original nonapplicant receipt and applicant receipt/defect awareness all occur September 28 in this scenario.
| Clock | Assumed Count | Exercise Deadline | Fictional Action |
|---|---|---|---|
| Nonapplicant Forwarding | Sep 29 = 1; Sep 30 = 2; Oct 1 = 3 | 2026-10-01 | Forwarded Sep 28 at 10:00; applicant receipt 10:05. |
| Three-Day Field Alert | Sep 29 = 1; Sep 30 = 2; Oct 1 = 3 | 2026-10-01 | Applicant records a simulated field-alert submission Sep 29. |
| Initial 15-Day Alert | Sep 29–Oct 2 = days 1–4; Oct 5–9 = 5–9; Oct 12–16 = 10–14; Oct 19 = 15 | 2026-10-19 | Applicant records a simulated initial alert Sep 30. |
| Significant New Information Received Oct 5 | Oct 6–9 = days 1–4; Oct 12–16 = 5–9; Oct 19–23 = 10–14; Oct 26 = 15 | 2026-10-26 | Applicant records a simulated follow-up Oct 8, referring to the Sep 30 initial report. |
| Alternative No-Information Branch | Three calendar months from Sep 30 initial report | 2026-12-30 checkpoint | Not the actual exercise branch: significant information arrived Oct 5. Use this branch if information is sought but not obtained. |
Attach a blank version to the handoff: receiving entity; first receipt; first defect awareness; trigger assessment; applicable report type; counting convention confirmed by; excluded dates; calculated deadline; applicant owner; transmission evidence; significant-information dates; and next follow-up review. Preserve separate timestamps when they differ. Do not reset a clock to the date a completed investigation reaches regulatory.
Keep the Periodic Reporting Handoff Open
Under 514.80(b)(4), periodic drug experience reports are generally required every six months for the first two years after approval and annually thereafter. Six-month reports are due within 30 days after the period ends; annual reports within 90 days of the approval anniversary, subject to permitted or required schedule changes. The section addresses distribution data, labeling, studies, and adverse experiences, including defects and experiences not previously reported under the alert provisions.
Send regulatory a reconciled distribution extract, current labeling references, complaint/defect inventory, prior-report identifiers, and unresolved information requests. Reporting under 514.80 is not an admission that the drug caused or contributed to an event. Preserve the facts and assessment without demanding a causation conclusion as a prerequisite to escalation.
Maintain the Operating Handoff
Make the lot packet a continuing record connection, not a document closed permanently at release. At each shift or organizational handoff, identify the current physical quantity, its status, unresolved evidence, responsible person, and next review point. After distribution, use the same lot identifier to connect complaints and investigations without rewriting the original release decision.
- Production hands over actual execution and quantity exceptions, not only a completion date.
- The laboratory distinguishes incomplete tests from completed results awaiting review.
- Packaging supplies item-level label accounting and finishing-examination evidence.
- Quality records disposition and investigation scope, including any post-release reassessment.
- Distribution supplies consignee-level records and subsequent movements.
- Regulatory acknowledges receipt, identifies applicable clocks, records reportability decisions, and maintains submission/follow-up references.
For the next readiness review, choose one released lot and one recent complaint. Have a person unfamiliar with the production run navigate from application assignment to component identity, reviewed tests, accepted-unit accounting, consignee records, and regulatory handoff. Turn each broken link into an assigned correction. The objective is a packet that remains understandable when its original authors are unavailable.
Questions
Does this guide apply to every veterinary product?
No. It addresses US finished animal drugs under approved NADAs or ANADAs. Medicated feed, Type A medicated articles, and licensed veterinary biologics have different manufacturing boundaries. Conditional approval, indexing, compounding, and extralabel-use pathways are outside this guide.
Can a supplier certificate replace component identity testing?
Not under the component supplier-analysis provision in 211.84(d)(2). The manufacturer must conduct at least one specific identity test and establish supplier-analysis reliability through appropriate validation at appropriate intervals. Containers and closures have a separate provision.
Is a passing analyst result enough to mark the lot ready?
No. Distinguish the result from review of its original laboratory record. Required final-specification evidence and quality-unit review of production and control records must support release; a result awaiting review should remain visibly pending in the packet.
Is every contract manufacturer a nonapplicant under 514.80?
No. Under 514.3, nonapplicant status requires that the person's name appear on the label and that the person engage in manufacturing, packing, distribution, or labeling, while not being the applicant. Identify the actual role rather than assigning it from the contract-manufacturer title.
Does every complaint require a 15-day report?
No. The initial 15-working-day alert applies to each serious, unexpected adverse drug event. Assess the separate field-alert trigger, nonapplicant forwarding duty, and applicable periodic reporting obligations rather than assigning one deadline to every complaint.
How should working days be counted?
Confirm the counting convention with regulatory. The supplied 514.80 text does not define working day. The worksheet's weekend exclusions and day-zero treatment are expressly fictional arithmetic assumptions, not a regulatory definition.
Can the entire packet use one five-year retention rule?
Do not assume so. Section 514.80 uses five years after submission, while applicable Part 211 batch and material records use expiration-related anchors and complaint records have their own longer-of rule. Map each record family to its applicable retention requirement.
Sources
- 21 CFR 210.1 — Drug cGMP Status
- 21 CFR 210.2 — Applicability
- 21 CFR 210.3 — Definitions and Manufacturing Boundaries
- 21 CFR 211.22 — Quality Control Unit
- 21 CFR 211.84 — Material Testing and Release
- 21 CFR 211.100 — Procedures and Deviations
- 21 CFR 211.130 — Packaging and Labeling Operations
- 21 CFR 211.134 — Finishing Inspections
- 21 CFR 211.137 — Expiration Dating
- 21 CFR 211.165 — Testing and Release
- 21 CFR 211.180 — Record Retention and Availability
- 21 CFR 211.186 — Master Records
- 21 CFR 211.188 — Batch Records
- 21 CFR 211.192 — Review and Investigation
- 21 CFR 211.194 — Laboratory Records
- 21 CFR 211.196 — Distribution Records
- 21 CFR 211.198 — Complaint Files
- 21 CFR 514.3 — Animal-Drug Reporting Definitions
- 21 CFR 514.8 — Approved-Application Changes
- 21 CFR 514.80 — Experience Records and Reports
- 21 CFR 225.1 — Medicated Feed Boundary
- 21 CFR 226.1 — Type A Medicated Article Boundary
- 9 CFR 113.1 — Licensed Biological-Product Serials
Practical orientation, not legal advice. Rules differ by jurisdiction; your quality and compliance team decides what applies.
The Pharmaceutical Operations Guide
Right material. Right record. Released by a person.
- Who decides, and who may not
- Supplier to finished bulk
- Test, review, investigate
We ask for your name and email so we can handle this request. The full guide then opens on this site, ready to translate, print or save. Privacy policy. Practical orientation, not legal advice; your quality unit decides which rules apply.
UltimateFree guide
The Pharmaceutical Operations Guide
Right material. Right record. Released by a person.

