An FDA inspection response usually involves more than writing a letter. Someone has to understand the observation, gather the records, decide what needs investigation, assign work, review the evidence, and get the approved package out on time.
A simple workflow helps your team see who owns each step and what is still open. It also keeps a draft from getting ahead of the work on the floor.

This is an internal coordination model for food and dietary supplement teams. It is not a universal regulatory procedure. Product type, facility status, inspection program, and the letter or close-out instructions determine what requirements apply. Have qualified regulatory and legal advisers review issues that need that expertise.
For the response evidence file, see FDA 483 Response: Use AI to Organize Your Evidence Before You Reply. The FDA Warning Letter Response Prompts book can help your team draft reusable prompts for its own review process.
Start by setting the response clock and scope
At close-out, collect the Form 483 or other written observations, the inspection notes your team is permitted to use, and the instructions for any written response. If a Warning Letter arrives later, open a separate control record for that letter. Do not assume the response steps or deadline are identical.
FDA’s food inspection guidance describes a 15-working-day request for written responses after inspection close. It also recommends addressing written observations and verbal points discussed at close-out. A Warning Letter may specify its own response period, recipient, and submission instructions. Confirm the exact instructions supplied to your facility, then record the date, owner, and delivery channel.
Assign a response coordinator. This person tracks the schedule, version, and decision log. A coordinator does not replace the quality unit, preventive controls qualified individual, dietary supplement quality control personnel, counsel, or other reviewers whose approval is required by the facility’s process.
Step 1: make one controlled observation list
Copy each observation into a working list with a unique ID. Keep the official wording easy to find. Add a plain-language summary only if it helps the team understand the work. Do not paraphrase away a key condition or turn an investigator’s statement into an internal conclusion.
Add space for verbal points if your team intends to address them. Mark what came from the Form 483, what was discussed at close-out, and what the facility identified during its own review. Those are related but different sources.
Step 2: assign the right people to investigate
Bring in people who know the process and the records. Depending on the issue, that may include quality, production, sanitation, maintenance, purchasing, laboratory staff, or operations management. Set an owner for the investigation and a separate reviewer when your procedure calls for one.
Gather facts before deciding on a cause. Define the relevant product, line, lot, date range, shift, equipment, procedure revision, and records. Keep the working question narrow enough to answer. A vague instruction like “look into the sanitation issue” does not tell the team what evidence to collect.
If the facility uses AI for administrative support, it can help organize a de-identified record list or flag dates that appear inconsistent. Do not ask it to determine root cause or make a safety or regulatory decision.
Step 3: assess immediate conditions and product questions
Some observations raise immediate questions about ongoing operations or affected product. The appropriate people at the facility should assess those questions under the applicable process. Do not wait for the response letter to decide whether product needs to be held, evaluated, or escalated.
For facilities subject to 21 CFR Part 117 preventive control requirements, section 117.150 addresses corrective action procedures and records for circumstances involving preventive controls. It includes steps that may involve correcting the problem, reducing recurrence, evaluating affected food for safety, preventing affected food from entering commerce when safety cannot be ensured, and documenting the actions. The exact requirements depend on the applicable provisions and circumstances.
Dietary supplement operations require careful classification. FDA explains that Part 117 subparts C and G generally do not apply to a facility with respect to dietary supplement manufacturing, processing, packaging, or holding when the facility complies with Part 111 and the applicable serious adverse event reporting provision. Other Part 117 requirements may still apply. Dietary ingredients and mixed operations can change the analysis. Confirm your facility’s obligations rather than assuming “supplement” means “exempt from every food rule.”
Step 4: separate corrections, corrective actions, and planned work
Your quality system may use “CAPA” as a broad internal label. FDA rules and programs use specific terms in specific contexts. Do not assume that a company’s CAPA form is itself the regulatory requirement or that the same process applies to every product category.
For each observation, record what happened in clear status language:
| Work status | What the team should record |
|---|---|
| Immediate correction | Condition corrected, date, responsible person, and any required product or safety assessment. |
| Investigation open | Question, records or interviews needed, owner, and next review date. |
| Action approved | Specific process change, approval, scope, owner, and target completion date. |
| Implemented | Effective date, affected procedures or equipment, training or communication records. |
| Effectiveness review due | Method, sample or review period, decision owner, and escalation trigger. |
Never call planned work complete. If a decision is still open, say what is unknown and who will resolve it. That is better than filling a response with a confident claim unsupported by the record.
Step 5: connect every action to evidence
Build an evidence index as the work progresses, not on the last afternoon. Use a stable attachment ID and exact filename. Include the record date or revision. Check that the attachment covers the relevant product, line, location, and time period.
An action record can answer these questions:
- Which observation or internal finding does the action address?
- What was done, and what remains?
- Who approved or completed it?
- Which controlled records support that statement?
- What will demonstrate that the change was implemented?
- What review will show whether it is working as intended?
Use the evidence to support the response. Do not attach a pile of unrelated files and expect the reader to work out the connection. Redact only when appropriate and permitted, and make sure the remaining page is still understandable.
Step 6: review the package in two passes
First, ask the technical owners to confirm that the facts and actions are accurate. Then ask the response coordinator or a separate reviewer to compare each written claim with its attachment. Legal or regulatory review may be needed depending on the observation and response.
Check the package for:
- Every observation has a matching response section or an explicit status.
- Completed actions are supported by completed records.
- Planned actions have realistic owners and dates.
- Statements do not claim that FDA accepted an action or closed a matter unless FDA said so.
- Product, process, and time ranges are consistent across the narrative and attachments.
- The subject line, recipient, file format, and delivery method match the actual instruction.
AI can help flag a mismatch, but a qualified reviewer makes the decision. Try this prompt with approved, de-identified information:
“Compare each response statement with the evidence index below. Flag claims with no matching record, dates that conflict, actions labeled complete when the evidence shows they are pending, or statements that go beyond the cited record. Do not make regulatory conclusions or rewrite the response. Return the claim, cited evidence, and question for the responsible owner. Response and index: [paste approved text].”
Step 7: submit, save proof, and keep following through
The response coordinator should confirm that the approved version is the one sent. Use the contact and channel in the actual correspondence. Save the sent file, attachments, submission email or portal receipt, and any later FDA communication in the response file.
Submission is not the same as completion of every internal action. Keep tracking open work after the response is sent. Record implementation and effectiveness results through the facility’s normal system. If the review identifies a recurring issue, escalate it through the quality process and reassess the plan.
FDA states that a Form 483 is not a final agency determination. The agency reviews the form alongside other evidence and any response. Do not describe your submission as FDA-approved unless the agency has explicitly made that determination.
Use one board to keep the team aligned
A simple tracker can show the state of each item at a glance:
| Observation ID | Owner | Investigation | Immediate action | Evidence | Due date | Reviewer/status |
|---|---|---|---|---|---|---|
| 483-01 | Quality lead | Records being reviewed | Completed, record linked | EX-01, EX-02 | Confirm with letter | Technical review open |
| 483-02 | Production lead | Cause not yet confirmed | Open | Line records requested | Assigned date | Investigation in progress |
These sample rows are fictional. Replace them with your own controlled IDs and dates. Do not treat a tracker status as the official response, and do not share it outside the team unless it has been reviewed for that purpose.
Keep the workflow matched to your facility
FDA’s food inspection guidance describes how an inspection and close-out may work and encourages organized records and written responses. For covered human food facilities, read the applicable text of 21 CFR 117.150 with the rest of the rule. FDA’s FSMA FAQs on dietary supplements explain how Parts 111 and 117 may apply to supplement operations. These sources do not replace a review of the specific facts, exemptions, and instructions for your facility.
Next in this series, read FDA 483 and Warning Letter Questions: What Teams Must Verify and FDA Response Templates for Evidence, Owners, and Follow-Up. For the response gaps checklist, see 6 FDA 483 Response Gaps Food and Supplement Teams Should Fix Before They Reply. The FDA response pillar covers evidence organization and safe AI use. The related FDA Warning Letter Response Prompts book provides prompt patterns to adapt after review.
Frequently asked questions
What does a CAPA workflow do after an FDA inspection?
An internal CAPA workflow coordinates investigation, action ownership, records, review, and follow-up. It does not replace the legal requirements or approved quality system that applies to your facility.
Does 21 CFR Part 117 apply to every dietary supplement operation?
No. FDA explains that subparts C and G generally do not apply to dietary supplement operations complying with Part 111 and the applicable serious adverse event reporting provision. Other requirements may still apply.
Who should own an FDA response action?
Assign an accountable person with authority to do the work, a due date, a reviewer, and a record that will show completion. Use qualified staff for technical and regulatory decisions.
Can AI decide whether a corrective action is effective?
No. AI can help organize evidence or flag gaps. Qualified staff must define and review the effectiveness method and results.
When is the response workflow complete?
The submission stage ends after the approved package is sent through the instructed channel and delivery evidence is saved. Internal follow-up may continue until the planned work and checks are complete.