Responding to an FDA Form 483

The inspection is over, the investigator has handed you a Form 483, and the room is quiet. What happens in the next fifteen business days will shape the outcome more than anything that happened during the inspection itself.

Why fifteen business days

FDA’s stated practice is that a response to a Form 483 received within 15 business days of the inspection close-out will be reviewed before the agency takes further action — including before it issues a Warning Letter.

That is the entire reason the window matters. After it closes, the agency may proceed on the basis of the inspection record alone. Inside it, your response is part of the record the decision is made from.

What a Form 483 is — and is not

A Form 483, Inspectional Observations, is issued by the investigator to site management at the conclusion of an inspection. It lists conditions that, in the investigator’s judgement, may constitute violations of the Food, Drug and Cosmetic Act and related regulations.

It is not a final agency determination of compliance. It is not a Warning Letter. It does not include every discussion held during the inspection, and it may not include everything the investigator noted.

Separately, the investigator files an Establishment Inspection Report (EIR), which is the fuller narrative record. The inspection is ultimately classified as No Action Indicated (NAI), Voluntary Action Indicated (VAI) or Official Action Indicated (OAI). Your response feeds into that classification.

The fifteen-day checklist

Days 0–2: contain and convene

• Transcribe every observation verbatim into a tracking document. Do not paraphrase — the exact wording is what you must address.
• Name a single response owner with authority to commit the site to actions and dates.
• Assemble the team: quality, the functional owner of each observation, and someone who was in the room during the inspection.
• Identify any observation with potential product impact. If there is a risk to distributed product, the health hazard evaluation and any field action decision run on their own clock, ahead of the response.
• Freeze nothing prematurely, but secure all records and systems referenced in the observations.

Days 3–7: establish root cause

• Run a real root cause investigation per observation. “Human error” is not a root cause; it is where the investigation stopped.
• Look across observations for a common systemic cause. Several findings pointing at one weak system is a stronger and more honest story than five unrelated fixes — and FDA reviewers look for exactly this.
• Determine scope: does the finding extend beyond the specific instance cited? To other batches, lines, products, sites? Answering this before FDA asks it is the single strongest move available to you.
• Gather the evidence for anything already corrected during the inspection.

Days 8–12: build corrective and preventive actions

• For each observation: immediate correction, corrective action addressing root cause, preventive action addressing recurrence elsewhere.
• Assign a named owner and a realistic completion date to every action. Dates you will miss are worse than longer dates you will meet — FDA follows up.
• Define how effectiveness will be verified, and when.
• Route the CAPAs through your own QMS. Actions that live only in the response letter and not in your CAPA system are the next inspection’s finding.

Days 13–15: write, review, submit

• Structure the response observation by observation, in the 483’s order and numbering.
• Attach evidence for completed actions — revised procedures, training records, data.
• Have someone who was not involved read it cold and mark every unsupported claim.
• Sign at a senior level. This is a commitment from the organisation, not from the quality department.
• Submit to the district office, addressed as the 483 directs, and keep proof of the submission date.

What each response section should contain

For every observation:

1. The observation, restated verbatim.
2. Whether you agree, and if not, the evidence for your position.
3. Immediate corrections already made, with evidence.
4. Root cause, with the method used to reach it.
5. Scope of impact — what else was checked, and what was found.
6. Corrective and preventive actions, each with owner and date.
7. Effectiveness verification — how you will know it worked, and when you will check.
8. Status — complete, in progress with a date, or planned with a date.

The mistakes that escalate a 483

Promising dates you will not meet. FDA tracks commitments. A missed date in a response is a credibility problem that outlasts the original observation.

Fixing the instance, not the system. If the observation cites one uncontrolled document and your response controls that one document, you have told the agency your document control system is still broken.

Skipping the scope question. An unanswered “does this affect anything else?” invites the agency to assume the worst.

Defensiveness without data. Disagreeing is legitimate. Disagreeing without evidence reads as not understanding the finding.

Silence on an observation. Every numbered item needs a response, including the ones that feel minor.

Actions that never enter the QMS. Commitments made in a letter and tracked in a spreadsheet are not a CAPA system.

After the response

Expect follow-up. The agency may request further information, and a subsequent inspection will very likely verify the commitments you made. Keep the response, the CAPAs and the effectiveness evidence together and retrievable — you will be asked for them, possibly by a different investigator who has read the file.

The uncomfortable part

Most 483 observations are not discoveries. They are things somebody inside the organisation already knew, raised, and could not get resourced — findings from an internal audit that closed without real action, a deviation trend nobody escalated, a procedure everybody knew was out of step with practice.

Which is the argument for a mock inspection run properly and early: the same findings, on your schedule, without the fifteen-day clock and without the file.