FDA Inspection Classification: Why an OAI Finding Isn't a Warning Letter

FDA closes every inspection with one of three classifications: No Action Indicated, Voluntary Action Indicated, or Official Action Indicated. Most teams treat the three letters as a pass/fail scale with a warning shot in the middle. That is not how FDA itself describes them, and the gap between the two readings is exactly where quality and regulatory teams either under-react to a serious finding or over-react to a manageable one.

Three classifications, not one scale

FDA's own Inspection Classifications description sets out three outcomes. No Action Indicated (NAI) means the facility is in an acceptable state of compliance; it typically closes without a Form FDA-483. Voluntary Action Indicated (VAI) means FDA found objectionable conditions but is not recommending or taking regulatory action — the facility is expected to correct them voluntarily. Official Action Indicated (OAI) means the objectionable conditions are serious enough that FDA has determined regulatory or administrative action is warranted. These are three separate determinations about what FDA concluded and what it intends to do about it, not three points on a severity scale a team can average toward the middle.

Why OAI is not a Warning Letter

The most consequential misread sits here. An OAI classification means FDA has determined that regulatory or administrative action is indicated — it does not specify which action, and it is not itself the Warning Letter. FDA's classification database treats the two as distinct: a facility can carry an OAI classification while FDA pursues a range of follow-up paths, a Warning Letter among them, but also further inspection, an import alert, or referral toward a consent decree, and in some cases a Warning Letter never issues at all. Teams that treat OAI and “we got a Warning Letter” as the same event either panic prematurely or, worse, relax once a Warning Letter fails to arrive on the timeline they expected — while the OAI classification itself is still sitting on file.

Classification tells you what FDA concluded. It does not tell you which enforcement path follows, and it does not tell you the inspection is finished working against your file. Why OAI and a Warning Letter are separate questions

Classification runs per project area, not per firm

FDA's Inspection Classification Database is organized by project area, and a single inspection visit can produce different outcomes across the systems it covered. A combination-product site inspected against both quality system and production and process controls can close NAI on one project area and VAI or OAI on another from the same visit. Teams that ask “what was our classification?” as though the inspection produced one answer are asking the wrong question; the right one is which project areas carried which outcome, because that is the level at which corrective action, and FDA's next inspection, will actually be scoped.

• The Form FDA-483 is not the classification. It lists observations at the close of inspection; classification is FDA's internal determination made afterward, informed by the 483, the inspector's report, and the facility's written response.
• A VAI outcome is not a clean file. It means objectionable conditions were found and documented — FDA is simply not recommending action on them yet. Uncorrected VAI findings are a standing invitation to a tougher read at the next inspection.
• An OAI outcome is not automatically public or automatically enforced. It is a determination that action is warranted; which action, on what timeline, and whether it becomes publicly visible through a Warning Letter depend on what happens next, including the quality of the facility's response.
• Classification per project area changes how a 483 response should be built. A response that treats every cited system identically misses the chance to protect an otherwise-strong area from an unfavorable read spilling over from a weaker one.

How this fits the broader inspection picture

Classification sits downstream of two things device and drug quality teams are already tracking: how an inspection is actually run, and how a facility responds once it closes. FDA's shift toward the structure described in Compliance Program 7382.850 changed how a device inspection unfolds, but it did not change the three-tier classification outcome that follows. And classification is a separate question from whether FDA ultimately issues a Warning Letter or an Untitled Letter — that decision follows its own criteria, on its own track, after classification has already been determined. Building inspection readiness around all three layers — the inspection itself, the classification decision, and whatever enforcement path follows — is what keeps a single rough project area from reading, internally or to FDA, as a firm-wide failure.