Medical devices, IVDs, cosmetics and compliance technology.Explore SMEDTEC OS
← Back to Insights
Fda Compliance StrategyRegulatory Audit ReadinessQuality Management Systems

FDA Post-Approval Inspections: What Section 704 Demands Now

Sherif Elkhadem
30 October 2026
6 min read
Quality management system documentation and FDA inspection materials arranged on an industrial workspace with manufacturing equipment visible in soft focus.

The FDA inspection after 510(k) clearance or PMA approval is not a courtesy visit. It is a statutory examination under section 704 of the Federal Food, Drug, and Cosmetic Act, designed to verify that your quality management system meets 21 CFR Part 820 requirements and that every claim in your submission can be traced back to documented evidence. For many manufacturers, this is the moment when abstract compliance documentation meets the reality of investigator scrutiny. The encounter sets the tone for every interaction with FDA that follows, and the consequences of unpreparedness extend far beyond a Form 483.

Greenlight Guru's latest guidance on post-approval inspections underscores what experienced RA and quality teams already know: FDA investigators arrive with a specific mandate, a defined inspection scope and access to your entire submission history. They are not there to offer advice or interpret your procedures. They are there to determine whether your QMS, as implemented, matches the representations you made during the review process. That divergence, where documented practice and operational reality part ways, is where most 483 observations originate.

What Section 704 Authorises and What It Demands

Section 704 of the FD&C Act grants FDA investigators broad authority to enter and inspect manufacturing facilities, examine records, take photographs and collect samples. This is not discretionary. Once your device is cleared or approved for marketing, your facility is subject to inspection at any reasonable time. The Quality Management System Regulation (QMSR) at 21 CFR Part 820, now converging incrementally with ISO 13485 expectations, defines what the investigator will evaluate: design controls, risk management, document controls, CAPA processes, supplier management, production and process controls, and post-market surveillance systems.

The inspection is not limited to the scope of your cleared or approved device. Investigators can examine your entire QMS, including processes and products outside the immediate submission. If your facility manufactures multiple devices, expect scrutiny across all product lines. If you outsource manufacturing or testing, expect questions about supplier qualification, audits and traceability. The investigator's job is to determine whether your organisation has the capacity and controls to consistently produce safe and effective devices. That determination is based on objective evidence, not assurances.

Process

FDA Post-Approval Inspection: Typical Sequence

  1. Opening Meeting
    Investigator presents credentials, inspection scope and expectations. This is your opportunity to clarify facility boundaries and identify subject matter experts.
  2. Document and Record Review
    Investigator examines design history files, device master records, validation protocols, CAPA records and complaint files. Expect requests for specific batch records and traceability documentation.
  3. Physical Inspection
    Manufacturing floor walk-through, equipment verification, environmental monitoring records and personnel training records. Investigators observe processes in operation, not just on paper.
  4. Closing Meeting
    Investigator summarises findings, issues Form 483 if observations are identified and outlines expectations for written response. This is not a negotiation.
The inspection follows a predictable sequence, but the depth and duration depend on what the investigator finds. Preparedness at each stage determines the outcome.

Most manufacturers underestimate the adversarial nature of the process. FDA investigators are trained to identify gaps, inconsistencies and deviations. They will ask for evidence, not explanations. If your design validation report references testing that is not documented in your device history file, that is an observation. If your CAPA procedure requires root cause analysis but the records show only corrective actions, that is an observation. If your supplier audit schedule is overdue for a critical component vendor, that is an observation. The inspection is forensic, not advisory.

Where QMS Documentation and Operational Reality Diverge

The most common source of 483 observations is not the absence of procedures, but the gap between what those procedures describe and what actually happens on the manufacturing floor. This is where the risk lies. Your QMS manual might specify a robust design control process, but if engineers bypass the formal design review because timelines are tight, the investigator will find the evidence. Your CAPA procedure might require effectiveness checks, but if those checks are logged as complete without supporting data, the investigator will notice.

This divergence is not always the result of negligence. It often reflects the organic evolution of processes that outpace documentation updates, or the informal workarounds that arise when legacy procedures no longer fit operational realities. But FDA inspections do not accommodate informal practice. If it is not documented, it did not happen. If the documentation contradicts the records, you have a systemic control failure. The investigator's report will reflect that.

Table
Common 483 Observation Categories in Post-Approval Inspections
QMS ElementTypical ObservationRoot Cause
Design ControlsDesign validation incomplete or not traceable to user needsValidation executed before formal design freeze, records not updated
CAPARoot cause analysis missing or inadequateCAPA initiated for corrective action only, preventive analysis skipped
Supplier ControlsSupplier audits overdue or lacking critical quality agreementsSupplier onboarding not integrated with QMS audit schedule
Document ControlObsolete documents accessible in manufacturing areasVersion control process not enforced at point of use
Process ValidationInstallation qualification records missing for critical equipmentEquipment commissioned by external vendor, IQ/OQ/PQ documentation not requested
These observations are preventable with disciplined QMS execution and internal audit processes that mirror FDA expectations.

The Greenlight Guru guidance emphasises preparation as the only reliable strategy. That means conducting internal audits using FDA's own inspection tools, identifying gaps before the investigator does and remediating them with documented evidence. It means training personnel to speak to their documented procedures, not to what they think the investigator wants to hear. It means ensuring that every claim in your design history file can be traced to objective evidence, and that every piece of objective evidence can be retrieved within minutes, not hours.

What This Means for Device Manufacturers and RA Teams

For regulatory affairs and quality teams, the first post-approval inspection is a forcing function. It exposes the maturity of your QMS under external scrutiny and sets expectations for every subsequent interaction with FDA. A clean inspection, or one that results in minor observations quickly closed out, signals operational competence. It reduces the likelihood of follow-up inspections and positions your organisation favourably for future submissions. Conversely, a warning letter or repeat 483 observations trigger escalated oversight, consent decrees and, in the worst cases, product recalls or marketing suspensions.

The implications extend beyond compliance. Investors, partners and customers increasingly treat FDA inspection history as a proxy for operational risk. A pattern of 483 observations, even if closed out, suggests systemic quality issues that can derail funding rounds, partnership negotiations and customer contracts. For startups and emerging manufacturers, the first inspection is often the first time the organisation's quality culture is tested under adversarial conditions. That test is pass or fail. There is no middle ground.

This aligns with the broader trend toward post-market surveillance and continuous compliance that regulators now expect from manufacturers. The inspection is not an isolated event. It is part of a lifecycle oversight model where your QMS is continuously evaluated, not just at approval. FDA's shift toward risk-based inspection scheduling means that manufacturers with strong track records are inspected less frequently, while those with observations face increased scrutiny. The first inspection sets the baseline.

Practical Steps to Inspection Readiness

Inspection readiness is not a project. It is a state of continuous compliance where your QMS operates exactly as documented, and documentation reflects operational reality. That requires three things: disciplined internal audits, rapid document retrieval and trained personnel who understand that FDA inspections are adversarial by design.

Start by conducting a pre-inspection audit using FDA's own Quality System Inspection Technique (QSIT) framework. This is the same framework investigators use, and it covers the same subsystems: management controls, design controls, CAPA, production and process controls, and records and document controls. Identify gaps, remediate them with documented corrective actions and ensure those actions are verified through effectiveness checks. If your internal audit does not produce findings, it is not rigorous enough.

Next, test your document retrieval processes. Can you produce your design history file, device master record and all associated validation protocols within 30 minutes of an investigator's request? If not, your document control system is not inspection-ready. Ensure that every document is version-controlled, that obsolete versions are archived or destroyed and that personnel know where to find the current versions. Investigators will test this. They will ask for specific batch records, specific CAPA reports and specific supplier audit files. Delays signal control failures.

Finally, train personnel to respond to investigator questions with precision. The correct answer to a question about process deviations is not an explanation of what should have happened. It is a reference to the documented procedure, the deviation record and the CAPA that addressed it. Investigators are looking for evidence of systemic control, not individual competence. Ensure that personnel understand the difference.

Key Takeaways

  • FDA inspections under section 704 are statutory, adversarial and evidence-driven. The investigator's mandate is to verify that your QMS, as implemented, matches the representations in your submission.
  • The most common source of 483 observations is the gap between documented procedures and operational practice. If your QMS describes one process but records show another, that is a systemic control failure.
  • Inspection readiness requires continuous compliance, not pre-inspection preparation. Your QMS must operate exactly as documented, and documentation must reflect operational reality at all times.
  • The first post-approval inspection sets the baseline for every subsequent FDA interaction. A clean inspection reduces future scrutiny; repeat observations escalate oversight and trigger enforcement actions.
  • Internal audits using FDA's QSIT framework are the most reliable preparation strategy. If your internal audit does not produce findings, it is not rigorous enough to predict what an investigator will see.

The post-approval FDA inspection is not a milestone to survive. It is the operational validation of every quality claim you made during the regulatory review. For manufacturers, the lesson is unambiguous: build a QMS that can withstand forensic scrutiny from the outset, not one that looks compliant on paper but collapses under investigator questioning. The organisations that treat inspection readiness as a permanent state, not a pre-visit sprint, are the ones that build sustainable market access. For RA and quality teams navigating this landscape, the convergence of ISO 13485 and QMSR expectations offers a unified framework, but execution remains the only differentiator that regulators recognise.

Sources cited in this digest

Related Articles

Regulatory Strategy For Medtech

QMS logic meets regulatory alternatives: what RA teams need now

Greenlight's 2026 eQMS roundup arrives as MHRA joins the global push for animal testing alternatives. For device manufacturers, these signals reveal where quality architecture and regulatory expectations are converging.

2 October 2026
Quality Management

ISO 13485 and QMSR: The QMS Convergence Now Shaping Compliance

Greenlight Guru's updated ISO 13485 and 21 CFR Part 820 guidance arrives as global harmonisation pressures intensify. For device manufacturers, these aren't just reference documents, they're roadmaps through converging expectations.

16 September 2026
Regulatory Harmonization

QMSR and MHRA sandbox: dual signals for QMS strategy

FDA's QMSR adopts ISO 13485 while MHRA launches an NHS innovation sandbox. For device manufacturers, these parallel moves reveal where quality management and market access expectations are converging.

4 September 2026

Need Regulatory Guidance?

Get expert help with your medical device regulatory strategy. From EU MDR compliance to FDA submissions, we're here to help.

Get Started →More Articles