An FDA investigator arrives at your facility, presents credentials, and issues a Notice of Inspection. For a device manufacturer asking, “what happens during FDA inspection?” the practical answer is that the agency will test whether the quality system described in your procedures is operating as intended in day-to-day practice. The inspection is not simply a document review. It is an assessment of whether your people, records, facilities, suppliers, and post-market processes support devices that are safe, effective, and manufactured under control.

For leadership teams, the stakes extend beyond the inspection days themselves. A well-managed inspection can demonstrate maturity to regulators, customers, and investors. Poor preparation can expose systemic gaps, consume internal resources, delay commercial priorities, and create enforcement risk.

What Happens During an FDA Inspection?

FDA inspections of medical device establishments may be routine surveillance inspections, preapproval inspections, for-cause inspections, or follow-up inspections after prior observations or corrective actions. The scope depends on why FDA is visiting, the device type and risk profile, the establishment’s compliance history, and information available to the agency.

An inspection is generally conducted on site, although FDA may request records remotely or conduct a remote regulatory assessment in certain circumstances. Those activities should not be treated as interchangeable. A records request can still require disciplined coordination, careful review, and prompt, complete responses.

Since February 2, 2026, FDA’s Quality Management System Regulation, or QMSR, has applied to device manufacturers under 21 CFR Part 820. The regulation incorporates ISO 13485:2016 by reference, with FDA-specific requirements. During an inspection, the investigator will evaluate compliance with the requirements applicable to your operations and the period under review. For records created before the QMSR effective date, the regulatory context may differ, but incomplete historical documentation remains a potential concern.

The opening meeting sets the operating rules

The inspection typically begins with the investigator presenting FDA credentials and Form FDA 482, Notice of Inspection. The organization should verify credentials, notify its designated inspection team, and establish a controlled workspace and communication process.

The opening discussion often covers the facility’s operations, products, organizational structure, quality system, and inspection scope. It is not the moment for an extended corporate presentation or unsupported assurances. A concise, accurate overview helps the investigator understand the business while keeping the discussion anchored in documented facts.

The most effective inspection teams have clear roles: an inspection coordinator who manages requests and logistics, subject matter experts who answer questions within their areas, a document-control lead who tracks every record provided, and a scribe who captures questions, responses, documents, and informal observations. One person should coordinate communications with the investigator so that answers are consistent and requests do not bypass the review process.

FDA follows the trail from procedure to evidence

Investigators commonly begin with a high-level review, then select samples that allow them to trace how the quality system works in practice. They may tour production areas, warehouses, laboratories, complaint-handling functions, and cleanrooms or controlled environments. They may interview employees who perform receiving inspections, manufacturing, quality review, complaint evaluation, or regulatory reporting.

The central question is usually straightforward: can the company show that it followed its own procedures and that those procedures meet regulatory requirements? A polished procedure cannot compensate for missing training records, unexplained production deviations, overdue supplier evaluations, or complaint files that lack documented investigation and closure.

The review may move across connected processes, including design and development, risk management, purchasing controls, process validation, acceptance activities, change control, nonconforming product, CAPA, complaints, medical device reporting, and management review. The depth of review depends on the firm’s activities. A contract manufacturer may receive intense attention on production and validation controls, while a legal manufacturer introducing a novel device may face more detailed questions on design changes, clinical evidence, risk controls, and post-market surveillance.

Investigators often use a single record as an entry point. A complaint may lead to questions about reportability, trend analysis, CAPA, service records, and risk management updates. A supplier nonconformance may lead to supplier qualification, incoming acceptance, purchasing agreements, and manufacturing impact assessments. This is why inspection readiness cannot be built around isolated binders or a last-minute document clean-up.

Document requests require control, not delay

FDA may request procedures, completed records, electronic data, training evidence, device history records, validation protocols and reports, complaint files, CAPA files, and organizational information. The organization should log each request, identify the record owner, review the material for completeness and relevance, and provide it in an organized format.

Review is not an excuse to withhold or unnecessarily delay requested information. It is a quality-control step that prevents accidental submission of draft documents, incomplete attachments, duplicate versions, or records outside the request’s scope. If a requested record does not exist, do not create it retrospectively or guess at an answer. State the facts, document the request internally, and involve the appropriate quality and regulatory leaders.

Electronic systems deserve particular attention. If quality records live across multiple platforms, the team should know in advance how to retrieve controlled versions, audit trails where relevant, approvals, and linked evidence. A slow search for records can signal weak document governance even when the underlying process is sound.

Daily management matters during an FDA inspection

Investigators frequently raise questions or potential concerns as the inspection progresses. Hold a daily internal debrief to compare notes, identify documents that may be requested next, confirm the accuracy of responses, and escalate emerging issues. This is not a time to argue every point. It is a time to understand the investigator’s concern and determine whether the available evidence fully addresses it.

Employees should answer truthfully and only within their direct knowledge. They should not speculate, volunteer unrelated information, or attempt to explain away a gap. If an employee does not know the answer, the appropriate response is to say so and identify who can provide an accurate answer. Calm, factual communication is more credible than defensiveness.

For global manufacturers, additional planning may be needed for translation, time zones, records maintained at different sites, and coordination with corporate quality functions. A US agent or corporate representative cannot substitute for clear site-level evidence. FDA inspects what the establishment actually does.

The closeout meeting and Form FDA 483

At the end of the inspection, the investigator generally conducts a closeout discussion. If the investigator observes conditions or practices that may constitute violations of the Food, Drug, and Cosmetic Act or related regulations, they may issue Form FDA 483, Inspectional Observations.

A Form 483 is serious, but it is not a final agency determination and it is not the same as a warning letter. It communicates observations that require prompt executive attention and a disciplined response. Some inspections end without a 483; others involve observations that can range from narrowly documented gaps to indicators of broader quality-system failure.

Do not respond to a 483 with generic commitments such as “we will retrain staff” or “the procedure will be revised.” FDA will look for evidence that the company understands the scope and root cause of each observation. A credible response explains the immediate correction, the corrective action to prevent recurrence, the affected products or processes, ownership, target dates, and how effectiveness will be verified.

Although a 483 response is not legally required, a substantive written response submitted within 15 business days is generally the most prudent course. FDA considers timely responses as it determines next steps. Missing that window can limit the agency’s ability to consider your corrective-action plan before further compliance decisions are made.

What happens after the investigator leaves

The inspection does not end at the closeout meeting. The investigator prepares an Establishment Inspection Report, and FDA reviews the inspectional findings. The agency may classify the inspection as No Action Indicated, Voluntary Action Indicated, or Official Action Indicated. Depending on the facts, follow-up can include additional record requests, a warning letter, import-related action for foreign firms, enforcement activity, or a future follow-up inspection.

The right post-inspection response is proportionate. A limited documentation gap may need a focused correction and effectiveness check. Repeated CAPA failures, inadequate complaint handling, or validation weaknesses may require a broader remediation program with governance, resource planning, independent assessment, and management oversight. Treating a systemic problem as a one-document fix often creates a more difficult second inspection.

The strongest preparation begins well before Form FDA 482 is presented. Conduct realistic mock inspections, trace critical records from complaint or design input through closure, test electronic retrieval, and ensure leaders can explain how quality metrics drive decisions. When an FDA inspection occurs, the goal is not to perform compliance for the investigator. It is to demonstrate, with clear evidence, the quality system your organization already operates.