FDA inspections and enforcement · Training guide
Warning Letter Response
Respond to an FDA warning letter within 15 working days, answering every violation and every item FDA asked for, with the data integrity remediation, management oversight and consultant FDA expects.
Open the tool at https://app.cmcfy.com/app/warning-letter-response.html. This guide is also online at https://cmcfy.com/guides/warning-letter-response.html
1. What this module does
You enter the letter, the date received and the date you will respond, one row per violation with its root cause, CAPA and retrospective review, and one row per item under "In response to this letter, provide" with your answer and attachment.
The tool counts the 15 working days, needs an answer to every violation and request, checks the three parts FDA asks for when data integrity is cited (comprehensive investigation, risk assessment, management strategy), needs management and quality unit oversight when violations repeat an earlier 483, and checks the consultant when the letter recommends one.
What you get
- A Word or PDF file: the warning letter response with each violation, the requests answered, the data integrity remediation, management oversight and the commitment schedule.
2. Before you start
Have these ready. You can still start with the example data and replace it piece by piece.
- The warning letter.
- Investigation, CAPA and retrospective review reports.
- The consultant agreement and scope, if recommended.
3. Step by step with the example
Open the tool at app.cmcfy.com/app/warning-letter-response.html. The example is loaded when the page opens, so every panel already has realistic data. Follow the steps to see how it works, then replace the example with your own data.
Enter the letter
Give the firm, the letter reference and date, when it was received, who issued it and who signs. Tick whether a consultant is recommended and whether the firm is on import alert.
Answer the violations
One row per numbered violation. Mark violations that repeat an earlier Form 483.
Answer what FDA asked for
One row per item FDA asks you to provide, linked to its violation number. Give the date for anything that will follow.
Read the result
The headline gives the outcome, for example "Every violation and FDA request answered".
Violations and FDA requests. Resolve alerts and download
A late response, an unanswered request, no retrospective review, a missing data integrity part and repeats without management oversight are critical. Then preview and download.
4. Field reference
Every input in the tool, panel by panel. Tables accept rows pasted straight from Excel, comma-separated text, or a loaded file; check the columns after loading a file. Fields marked “when it applies” appear only for the choices that need them.
1 · Warning letter
| Field | What to enter |
|---|---|
| Firm and site | Type it in. |
| FEI number | Type it in. |
| Warning letter reference | Type it in. |
| Letter date | Type it in. |
| Date received | Type it in. |
| Date the response will be sent | Type it in. |
| Issued by | Type it in. |
| Signed by (executive management) | Type it in. |
| The letter recommends a qualified CGMP consultant | Tick the box if it applies. |
| Consultant engaged and scope when it applies | Type it in. |
| The firm is on import alert (for example 66-40) | Tick the box if it applies. |
| Executive management and quality unit oversight actions | FDA reads repeat violations as a failure of management oversight; say what executive management now does. Type or paste text. |
2 · Violations cited
One row per numbered violation in the letter.
| Field | What to enter |
|---|---|
| Violations | A table. Columns: Item | Violation (as cited) | 21 CFR | Repeat of an earlier 483 (yes/no) | Root cause | CAPA | Retrospective review | Due | Status (complete/in progress). Paste rows from Excel, type comma-separated rows, or press Load file (Excel, CSV, Word, PDF or a scan). |
3 · What FDA asked for
One row per item under "In response to this letter, provide".
| Field | What to enter |
|---|---|
| FDA requests | Copy each "In response to this letter, provide" bullet as one row; the Item column is the violation number it sits under. A table. Columns: Request | Item | What FDA asks for | Our response | Attachment | Status (provided/to follow) | Date to follow. Paste rows from Excel, type comma-separated rows, or press Load file (Excel, CSV, Word, PDF or a scan). |
5. Checks and alerts
Calculations and pass/fail outcomes always come from fixed rules, never from AI. The tool checks:
- 15 working day deadline.
- Every violation and every FDA request answered.
- Data integrity remediation, management oversight and consultant.
How to resolve alerts
- Critical alerts block the download and must be fixed in the data. A failing result can instead be linked to an investigation: type the investigation reference and outcome and press Record.
- Major alerts block the download until you fix them or type a justification and press Accept justification.
- Minor alerts do not block anything. They are listed in the documents so the reviewer sees them.
- Some alerts have an Apply fix button that makes the change for you. Reopen undoes a justification.
Narratives
This module writes: Opening; Management oversight; Closing. Each narrative is written by fixed rules from your data. You can edit it in the box. Rewrite with AI (where your plan includes AI) rewrites it in regulatory style; every number in the text is checked against your data, and a number that does not match is flagged under the box and blocks the download until you correct it. Reset to rule-based text brings back the original.
6. Preview, gap review and download
- Press Preview next to a section, or Preview and download all. The document opens in a preview window, exactly as the Word file will read.
- The left side lists the review, run on your device: gaps in the data (missing values, open alerts), gaps in the report (missing content the guidance expects, placeholders such as [site] or TBD left in the text) and, if you load the approved protocol under Compare with the protocol, differences from the protocol (requirements, criteria, batches or time points it plans that the report does not show).
- Click a finding to jump to the place in the preview. Fix it in the tool, then preview again.
- Optional AI review: a second read for contradictions, claims without data and vague wording. The report text is sent to Claude only when you press it, and only where your plan includes AI. Check every AI finding; AI can be wrong.
- Press Download Word (.docx) or Download PDF. With several documents open, All as Word (.zip) and All as PDF (.zip) download the set. The download buttons stay disabled while a blocking alert is open; the preview still works.
Documents this module produces
| Section | Document |
|---|---|
| Report | Response to FDA warning letter |
Use Save project to keep your work as a file on your computer, and Open project to continue later. Start blank clears every field; Load example brings the example back. Nothing is stored on CMCfy servers.
7. US and EU submissions
US only: FDA warning letters (Regulatory Procedures Manual Chapter 4).
8. Working with other modules
- Track every commitment to close-out in the Remediation Tracker.
9. Common pitfalls
- Answering the violations but not the specific items FDA listed.
- Data integrity remediation without the extent of the problem and its effect on product.
10. Practice exercises
Each exercise starts from the example (press Load example to reset). We run these on every update of this guide, so the result you see should match.
Leave a request unanswered
Delete the answer to request B.
Expected resultThe unanswered request is critical.
Respond late
Change the send date to 2026-08-12.
Expected resultLate response is critical.