I’ve been on both sides of audits and inspections enough times to recognize the difference between a QMS that’s alive and one that’s optimized for photo ops. Regulators (FDA, notified bodies under MDR/IVDR, auditors against ISO 13485) don’t come to admire your template library — they come to see whether the system actually influences day-to-day decisions.
Below are the concrete signals I’ve seen that tip an inspector off to "culture" vs "theater", and the short fixes that moved us from the latter toward the former.
What inspectors are actually looking for
Inspectors want evidence that the requirements have been integrated into the way the business makes decisions. They don’t just cross-check clauses; they trace behaviors back to outcomes.
Typical things they ask for and observe:
- Records that show not just completion, but intent and follow-through (e.g., CAPA documentation that links to verification activities, supplier corrective actions and the impact on production).
- How changes are handled in practice: was a risk assessment updated before the change was implemented, or after you discovered problems?
- Who actually knows the procedure — can a line operator explain the “why” behind a work instruction, not just the “how”?
- Open issues and trends: are problems hidden in folders, or being trended and acted on?
In one FDA inspection I supported, the investigator spent more time shadowing production personnel and tracing specific lots back to change records than they did poring over glossy dashboards. The dashboard looked impressive. The trace from a change to the risk file and the production decision was where the conversation got sharp.
Quality theater — common red flags
These are the things that look good at first glance but fail the “show me” test:
- Batch of training completions all signed on the same date with identical notes. (Often indicates retroactive sign-offs.)
- Design review minutes that are one-page, checklist-only, and lack linked actions or evidence that decisions changed design direction.
- CAPAs with corrective actions that are "training" only, no root-cause evidence or verification steps.
- Closed nonconformances where the evidence is a document revision but no verification that the problem stopped recurring.
- Supplier scorecards with perfect scores but unresolved open quality events.
Inspectors can often tell when records are produced to meet an audit rather than to support control. They look for consistency between what’s on paper and what happens on the shop floor or in the lab.
Signals of a living quality culture
Contrast that with the concrete behaviors that indicate a functioning culture:
- Findings become actions: a complaint or audit observation turns into a tracked quality event that someone owns, with timebound actions and measurable verification. (We use our QMS so a finding becomes a quality event and shows up on the owner’s dashboard.)
- Documents are living artifacts: work instructions evolve as improvements are discovered and those changes are captured with rationale and verification.
- Cross-functional ownership: design changes are reviewed by manufacturing, QA, RA, and service where relevant — meeting minutes include who disagreed and why.
- Transparent trending: recurring issues show up in management review and trigger strategy-level decisions (supplier change, design mitigation).
- People speak the system: operators and engineers can explain why a process exists, not just how to execute a SOP.
Those signals make an inspector comfortable that the QMS isn’t just a compliance exercise; it’s how the company manages risk.
Practical swaps: from theater to culture (what actually worked for us)
We implemented small, practical changes that had outsized effects during audits:
- Replace passive signoffs with active evidence: require a piece of work (a photo, a measurement, a code diff, a screenshot) tied to training or approval so signoffs aren’t just checkboxes.
- Force traceability links earlier: require a link from a change request to the risk assessment and to impacted documents before the change moves from “approved” to “released”.
- Make CAPA verification tangible: define measurable verification steps up front (sampling plan, metric threshold) and record their results in the CAPA.
- Day-in-the-life walkthroughs: before audits, do internal “shop-floor tracebacks” where an engineer follows a part through from receipt to shipping and documents what they saw.
- Surface open work: dashboards are fine, but we started embedding a short narrative in management review for each recurring theme — what was done and what’s next.
These are process changes, not heroic hires. They require discipline and tooling that supports traceability and ownership.
Tools help, but they don’t create culture
A connected QMS that links findings, changes, risk, and CAPA reduces friction. Automation that turns a finding into a quality event, or that forces a required link before state change, helps prevent theater. But tools won’t replace leadership and day-to-day behaviors.
I’d rather have imperfect records that reflect real problems being worked on than immaculate records that hide issues.
Wrap-up — what I watch during inspections
When I’m in an audit room now I listen for:
- Ownership (who will fix this and how will I know?)
- Evidence (can they show me the work?)
- History (has this been tried before? what changed?)
- Impact (did the decision change production, design, supplier choices?)
If those four threads tie together, it’s a culture. If not, it’s theater — and inspectors notice.
What have you seen in audits that made you think “this company gets it” — or the opposite?
Top comments (0)