How to Read an FDA Compliance Program Guidance Manual

Before an FDA investigator walks into your facility, they’re already working from a script. Compliance Program Guidance Manuals (CPGMs) are FDA’s own instructions to its field staff — what to review before arriving, what records to request, and how a finding gets weighed. They’re published on FDA’s website, not confidential, and almost nobody outside a quality or regulatory function reads them before they need to.

In brief

A CPGM is FDA’s own instructions to its investigators for a specific program area — what to check, in what order, and how the visit gets scoped.
CPGMs are public. FDA posts them by program on its compliance-manuals page, so the investigator’s own script is available to read before an inspection, not just reconstructed afterward from the establishment inspection report.
For device manufacturers, this instructional framework sits alongside FDA’s Quality System Inspection Technique (QSIT), which scopes a visit around a small number of interconnected subsystems rather than a line-by-line walk through 21 CFR 820.
Reading the manual for your product type won’t tell you what an investigator will find. It tells you what they were instructed to look for, which is the more useful thing to know in advance.

What a compliance program guidance manual actually contains

Each CPGM sets out the background and objective of a specific inspection program, the establishments and products it covers, and — for a device manufacturer under QSIT — which subsystems get sampled depending on how the visit is scoped. Management controls, design controls, CAPA, and production and process controls are the usual anchors; a shorter, abbreviated inspection samples a subset of these, while a comprehensive one covers more ground. It’s the closest thing to a public answer key for what an inspection is structured to cover, even though it says nothing about what your own records will show once someone actually reads them.

Where the value actually is

The practical use isn’t memorizing a document — it’s reading the manual for your facility’s program area before a scheduled or reasonably expected inspection, and using it to sanity-check your own procedures against what an investigator is instructed to sample. Two guardrails matter here. First, “not mentioned in the CPGM” isn’t the same as “off-limits” — the manual sets a default scope, not a ceiling, and an investigator who notices something adjacent to it is well within their authority to follow it. Second, the manual describes a program, not a promise: how a specific visit actually unfolds, and what it turns into afterward — an establishment inspection report and, depending on what’s found, an inspection classification — still depends on what the investigator observes on the day.

Where this goes wrong

Assuming it’s confidential

CPGMs are public documents on FDA’s own website. Not reading yours before an inspection is a self-inflicted disadvantage, not a matter of access.

Treating it as a checklist you can fully game

The manual sets structure and priorities; it doesn’t replace an investigator’s judgment about what’s worth following up on once they’re on site.

Confusing the manual with the outcome

The CPGM is the instructions. The inspection report and any findings are what actually happened — reading one doesn’t substitute for the other.

Reading the compliance program guidance manual for your own product type costs less than an hour and tells you, in FDA’s own words, what an inspection is built to look for. That’s a cheap habit for a function that already treats reading primary sources as a discipline worth building.

Sources & further reading

FDA — Compliance Program Guidance Manuals fda.gov
Regulatory Academy — How to Read an FDA Establishment Inspection Report regulatoryacademy.com
Regulatory Academy — How to Read an FDA Inspection Classification regulatoryacademy.com
Regulatory Academy — How to Build a Regulatory Intelligence Habit regulatoryacademy.com

This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal, regulatory, or career advice.