top of page

What FDA is Looking For in a 483 Response

Writer: Dan Simonsen
Dan Simonsen
Jul 2
3 min read

I spent years as an FDA Investigator drafting and issuing 483 Inspectional Observations to noncompliant firms. I read dozens of 483 responses as a Compliance Officer and noticed that companies across food, supplements, and cosmetics write bad 483 responses for the same reason: they do not know what the agency is actually looking for.


The 15-day window is real

When an investigator hands you a 483 at the close of an inspection, you have 15 business days to submit a written response. If you provide a response, the agency will review it in detail, and is required to respond back. Miss the deadline and the agency will take automatically take action.


Fifteen business days goes fast. You have to understand the observations, investigate root cause, develop corrective actions, and get executive sign-off before you write a word of the actual response. Companies that treat the first week like runway run out of time. I watched it happen.


The response that does not work

FDA published draft guidance in March 2026 on how to respond to Form 483 observations. It is technically for drug CGMP inspections, but the problem is still the same.


A company gets an observation about failure to develop a hazard analysis. The response comes back: "We acknowledge the observation. We are working to develop a hazard analayis over the next few months." FDA reads that and the questions it asks are: okay, but do you actually have it under control right now? are you continuing to produce food without a hazard analysis now? what records do you have to demonstrate that?


Here's the point: The agency considers a response that says you will do things later as an inadequate response.


A strong response tells FDA:


  1. what was wrong and how far back it goes

  2. what you found when you looked

  3. what you did with affected product or batches

  4. what the actual root cause was (not the first thing that sounded like one)

  5. what corrective actions you have taken and when were they taken,

  6. who specifically is accountable for these corrective actions, and

  7. what was outcome of these corrective actions


Oh, and these corrections must be documented - just saying that you've done these things is not enough. That is the difference between a response that closes a file and one that starts a Warning Letter.


Root cause is where companies lose the most ground

FDA's draft guidance says explicitly: do not accept the first plausible explanation. The agency calls this "bias-aware" investigation, and what it means practically is that you should not let the person who owns a process lead the investigation into their own process.


If you get an observation about environmental monitoring failures, "the swabbing schedule was missed" is almost certainly not the root cause. That is what happened. Why it happened is a different question, and the answer probably has something to do with training, accountability, resources, or a program that was not designed for the actual facility. Those require different fixes.


I read a lot of draft 483 responses where the corrective action is the equivlent of putting a band-aid on a rash - it may look better, but certainly doesnt fix the underlying problem, and most likely will make it worse. That kind of response does not demonstrate control and FDA will notice and take action on that.


If your team is working through a 483 right now

Do not treat the response as a paperwork exercise. What you send back will either give FDA a reason to close the file or a reason to escalate. A well thought out and thougrough response that shows genuine investigation and specific accountability does the first. A promise to correct or form letter does the latter.


If you want a second set of eyes or need someone to take the lead on the response, you can reach me at sigconsultinggroup.com or dan@sigconsultinggroup.com.

Comments


bottom of page