How do you respond to FDA 483 observations about batch records and documentation?
By Savi C., Co-Founder · Published Nov 16, 2026
What the 15 business days mean
The window comes from FDA’s Review of Post-Inspection Responses notice in the Federal Register of August 11, 2009. FDA said it would generally allow 15 business days to respond to 483 observations and would conduct a detailed review of a timely response before deciding whether to issue a warning letter. The notice also said that ongoing or promised corrective actions generally do not preclude a warning letter. A 483 lists inspectional observations; it is not a final agency determination of compliance.
In March 2026 FDA issued a draft guidance, Responding to FDA Form 483 Observations at the Conclusion of a Drug CGMP Inspection. It is a draft and not for implementation, but it shows current agency thinking. As summarized by several law firms, it recommends a single comprehensive response, signed by an executive with authority to deliver the commitments, with structured root cause analysis, a patient and product risk assessment, attached objective evidence, and, for complex issues, at least a CAPA plan and timeline within the 15 business days.
Common categories of documentation observations
Documentation observations usually fall into a few groups, each tied to a regulation. Batch records that are incomplete or do not reflect what was done (21 CFR 211.188). Deviations from written procedures that were not recorded or justified (211.100(b)). Production records released without a complete quality unit review, or discrepancies not thoroughly investigated (211.22 and 211.192). Entries that were not contemporaneous, corrections that obscured the original, uncontrolled blank forms, and audit trails that were not reviewed. The guide What are the most common batch record errors found in review? covers the page-level errors behind many of these.
What a documentation 483 response should contain
For each observation
- The observation restated exactly as written on the 483
- Whether you agree, and if not, the specific factual basis, with evidence attached
- Immediate corrections to the records cited, made under good documentation practice so the original entry stays legible
- A product impact assessment for every batch the cited records support, including batches already distributed
Scope beyond the example
- A retrospective review of other batch records for the same weakness, with the sample size and selection method stated
- The same check extended to other products, lines and sites that use the same forms or procedures
- A comparison with internal audit findings and earlier inspections to show whether this is a repeat
Root cause and CAPA
- Root cause analysis that asks why the error happened and why batch record review did not catch it
- Corrective and preventive actions with an owner and a completion date for each
- Changes to forms, master records, training or review procedures, attached in draft or final form
- A defined effectiveness check, such as error rates in records reviewed over a stated period after the change
Follow-through
- Response sent within 15 business days of the 483, with any items still in progress clearly scheduled
- Progress updates sent on the dates you committed to
- Evidence of completed actions kept ready for the next inspection
How Litewave fits
Retrospective record reviews are where responses most often run out of time. Litewave reads paper or electronic records, checks every entry against your master record and specifications, and shows QA only the exceptions, each linked to the page it came from, which makes it practical to review the full population of affected records rather than a small sample. Litewave proposes, qualified people approve. It supports 21 CFR Part 11 electronic records, signatures and audit trails. For what inspectors ask about AI-assisted review itself, see Will AI-assisted batch record review hold up in an FDA inspection?
Questions we get asked
Is responding to a 483 mandatory?
No. A response is voluntary, but FDA reviews timely responses before deciding on a warning letter, so a firm that does not respond within 15 business days loses that opportunity.
Does a good response prevent a warning letter?
Not necessarily. FDA’s 2009 notice says ongoing or promised corrective actions generally do not preclude a warning letter. Completed corrections backed by evidence and a convincing scope assessment carry more weight than commitments.
Should we only fix the batch records the investigator cited?
No. Investigators cite examples. FDA expects the response to assess whether the same weakness affects other batches, products and sites, and to explain why your existing review process did not detect it.
Sources
- FDA, Review of Post-Inspection Responses, 74 FR 40211 (Federal Register)
- FDA, Responding to FDA Form 483 Observations at the Conclusion of a Drug CGMP Inspection, draft guidance (March 2026)
- King & Spalding, FDA issues draft guidance on responding to FDA Form 483 observations
- Covington, FDA publishes draft guidance on responding to FDA Form 483 observations
- Arnold & Porter, FDA issues guidance on responding to FDA Form 483s
- 21 CFR 211.22, Responsibilities of quality control unit (eCFR)
- 21 CFR 211.100, Written procedures; deviations (eCFR)
- 21 CFR 211.188, Batch production and control records (eCFR)
- 21 CFR 211.192, Production record review (eCFR)
