This is a ready-to-use work instruction for the case that comes up often: the 15-business-day response date is close and the full investigation is not finished. An interim response that lands on time is worth more than a complete response that lands late, because a late response may arrive after the district has already recommended a classification. This work instruction produces that on-time interim response. Replace every <<FILL: ...>> placeholder. A filled specimen follows. This content is educational and general, not legal advice.
Control header
| Field | Entry |
|---|---|
| Document title | Preparing an Interim FDA 483 Response Within the 15-Business-Day Window |
| Document number | <<FILL: WI-ID, e.g. WI-RA-030-01>> |
| Version | <<FILL: version>> |
| Effective date | <<FILL: date>> |
| Parent SOP | <<FILL: SOP-ID for FDA 483 and Warning Letter response management>> |
| Applies to | The response coordinator and observation owners preparing an interim response |
Purpose
To produce an interim 483 (or Warning Letter) response, submitted inside the 15-business-day window, that acknowledges every observation, states the immediate containment already in place, gives root cause where it is known, and commits to dated completion of the remaining work. The interim response holds your place in the agency’s review while the full investigation completes.
When to use this
Use an interim response when the full investigation, scope assessment, or corrective work genuinely cannot be completed and evidenced within 15 business days, and you would otherwise be forced to either miss the window or submit a thin, unfinished full response. Do not use it as a default stall; where a full response can be completed on time, complete it.
The steps
Step 1: Confirm the deadline and decide interim
- Confirm the 483 issue date and the 15-business-day response date.
- Confirm with the response lead and quality signatory that a full response cannot be completed and evidenced in time, and that interim is the right call.
Per-step acceptance: the deadline is fixed in writing and the decision to go interim is made and owned by the response lead.
Step 2: Acknowledge every observation
- Address each numbered observation, in FDA’s order, using the agency’s observation text as the heading.
- State that each observation has been reviewed and is understood. Do not argue the findings.
Per-step acceptance: every numbered observation is present and acknowledged; none is omitted or deferred without acknowledgment.
Step 3: State the immediate containment already done
- For each observation, describe the immediate actions already taken to contain risk: quarantine of affected material or data, added review steps, a temporary control, a paused activity.
- Where nothing is yet done, say what will be done immediately and when.
Per-step acceptance: each observation shows either containment already in place or a stated immediate action with a near-term date; there is no observation with no immediate response at all.
Step 4: Give root cause where known, and commit the rest
- Where the root cause is already established, state it to standard (a system or procedure cause, not a person).
- Where it is not yet established, say the investigation is in progress and commit to a specific date for the completed root cause and the full corrective plan.
Per-step acceptance: known root causes are stated to standard; unknown ones carry a specific completion date, not an open-ended “in due course.”
Step 5: Commit dated completion of the remaining work
- For every piece of outstanding work (full investigation, scope assessment, corrective actions, effectiveness checks), commit a specific calendar date and a named role owner.
- Enter each commitment on the commitment register and open the matching quality-system record with the same date.
Per-step acceptance: every outstanding item has a dated commitment on the register with a matching quality-system record; no commitment is vague or undated.
Step 6: Review, sign, submit, and diarize
- Run the applicable items of the pre-submission checklist that apply to an interim response (timing, mechanics, acknowledgment, containment, commitments).
- The quality signatory signs; submit to the correct office and contact inside the window; retain the archive copy.
- Diarize every committed date and the full-response submission.
Per-step acceptance: the interim response is signed, submitted inside the window to the correct office, archived, and every committed date is diarized.
Overall acceptance criteria
The interim response is acceptable when:
- It is submitted inside the 15-business-day window to the correct office and contact.
- Every observation is acknowledged, with immediate containment stated.
- Known root causes are given to standard; unknown ones carry a specific completion date.
- Every outstanding commitment is dated, owned, on the register, and matched in the quality system.
- A dated archive copy is retained and the full-response date is diarized.
Common inspection findings this work instruction prevents
- A response that misses the window entirely because the team waited for the full investigation.
- An interim response that acknowledges some observations but silently skips others.
- Open-ended commitments (“we will update the procedures in due course”) with no date.
- Interim commitments that never reach the quality system, so they are forgotten by the time the full response is due.
How to adapt this work instruction
- Point the parent-SOP and commitment-register fields at your real documents.
- Align the containment examples with your product and process (material quarantine, data hold, added review).
- Set which pre-submission checklist items apply to an interim versus a full response.
Filled specimen
The following shows an interim response summary for a three-observation 483, so you can see the expected shape. Illustrative content; replace with your own.
| Observation | Acknowledged | Immediate containment | Root cause | Committed completion |
|---|---|---|---|---|
| Obs 1: audit-trail review not performed | Yes | Second review added on all affected result sets pending fix | Established: result-review SOP omitted audit-trail review | SOP revised 2026-06-15 (CC-1042); 12-system scope 2026-08-01; effectiveness check 2026-09-15 |
| Obs 2: cleaning record missing agent lot | Yes | Reconciling cleaning dates vs agent receipt records | Established: form predated the cleaning validation conclusion | Form/SOP revised 2026-06-10 (CC-1051); effectiveness check 2026-08-10 |
| Obs 3: possible broader data-integrity gap | Yes | Affected system access restricted; retrospective review started | Investigation in progress | Root cause and full plan committed 2026-06-30 |
In this example the team met the window on day 12 with an interim response: every observation acknowledged, containment in place for each, two root causes already established with dated fixes, and the third committed to a specific date. The full response followed on 30 June with the completed Obs 3 investigation. On-time and honest beat late and complete.