Inspection Readiness: How to Demonstrate a Genuine State of Control

Inspection readiness is one of those phrases that gets used to describe everything from a two-week document sprint before a scheduled FDA inspection to a genuine, sustained operating posture that makes inspections unremarkable events. The difference between the two is visible to experienced inspectors almost immediately.

This article is about building the second kind, actual inspection readiness, not the performance of it. It covers what FDA and EMA inspectors look for at a broad level, how front room and back room logistics actually work, the roles people play, and the specific preparation that matters when data integrity is in scope. The principles apply across drug, biologic, medical device, and combination-product sites, and across manufacturing, testing, and clinical operations. The goal throughout is the same: a site that is genuinely in control reveals that fact under scrutiny, and a site that is not reveals that too, no matter how well rehearsed the day is.

Why “Readiness” and “Compliance” Are Not the Same Thing

A site can be compliant and still inspect badly, and a site can inspect well and still have serious gaps. The two failure modes look different.

Compliance is the underlying condition: are the systems validated, the records contemporaneous, the procedures followed. Readiness is the ability to show that condition clearly and quickly under the pressure of an inspection. A compliant site that cannot locate its own validation summary report, cannot explain its audit trail review cadence, and cannot put the right subject matter expert in front of the inspector within a reasonable time will generate observations that have nothing to do with its actual quality. The inspector did not see the control, so for the purposes of the record, the control was not demonstrated.

The inverse is more dangerous. A site that is well drilled but not actually in control can manage the first day, then unravel when the inspector follows a thread the rehearsal did not anticipate. Inspectors are trained to pull threads. An answer that is too smooth, a binder that is too clean, a deviation log that is suspiciously short, all of these invite the next question. Readiness without compliance buys a few hours and then costs more, because it reads as concealment.

The target is both: a real state of control plus the operational discipline to show it. The phrase “state of control” is not decorative. FDA’s process validation guidance (2011) defines it as a condition in which the set of controls consistently provides assurance of continued process performance and product quality, and ICH Q10 (2008) builds an entire pharmaceutical quality system around establishing and maintaining it. Inspection readiness is the visible face of that condition.

What Inspectors Are Actually Looking For

The FDA’s inspection authority comes from Section 704 of the Federal Food, Drug, and Cosmetic Act, and the agency’s general expectation is that a facility complies with current good manufacturing practice as codified in 21 CFR Parts 210 and 211 for drugs, 21 CFR Part 600 series for biologics, and 21 CFR Part 820 (the Quality System Regulation, now harmonized to the Quality Management System Regulation, 21 CFR Part 820 as amended effective February 2026) for devices. The European framework rests on EudraLex Volume 4, the EU GMP guide, and its annexes, with device manufacturers inspected against ISO 13485 and the EU Medical Device Regulation (EU) 2017/745. Those are the rules. What experienced inspectors are looking for is evidence that the rules are lived, not just written down.

Signs of a genuine state of control tend to cluster around a few patterns.

Records that show problems were found internally and investigated. A site with a healthy deviation and CAPA program has records showing that things go wrong and get addressed. A site with almost no deviation records, or with CAPAs that all close promptly with minor corrective actions, can look clean on the surface. Experienced inspectors read that as evidence that problems are not being found, not that they are not occurring. A mature quality system surfaces its own failures. See deviation management and what is a CAPA for how this program is supposed to function.

Consistency between documentation and practice. Inspectors interview personnel and observe operations as well as reviewing records. An SOP that describes a procedure no one follows is a finding. A gap between how a procedure is documented and how it is actually performed raises questions about the integrity of the documentation itself, which is a worse problem than the original gap.

Data that coheres internally. Audit trail timestamps that match batch record entries. Instrument logs that match what the batch record says was run. Sequence files in a chromatography data system that line up with the analyst’s notebook. When the data does not cohere, it is either a sign of an integrity problem or a sign of controls weak enough to allow one. Both are findings.

People who understand their own work. An analyst who can explain why a step exists, not just that it is required, signals a culture where quality is understood rather than enforced. The opposite, staff who recite procedures they clearly do not understand, signals training that exists on paper.

The Three Readers in the Room

It helps to remember that an inspection serves three different audiences at once, and readiness has to work for all of them.

For someone new to GxP, the lesson is simple: the inspector is checking whether the written system and the real system are the same system. Everything else follows from that.

For the working practitioner, readiness is about fluency with their own tools. The person who runs the LIMS daily should be able to show the audit trail, explain the configuration, and produce a record without hunting. That fluency cannot be faked in a two-week sprint.

For the senior or program-level reader, readiness is a measure of the quality system’s maturity. A program that has internalized inspection expectations does not run a fire drill before each one. The metrics, the periodic reviews, the management review cadence, and the internal audit findings already tell the inspection story before the inspector arrives. See quality metrics and KPIs and management review under ICH Q10 for the systems that carry that story.

Types of Inspection and Why the Type Changes Your Preparation

Not all inspections are the same, and treating them identically wastes effort. Knowing the type tells you what the inspector arrived to do.

A PAI is application-specific: the staged document packages, the validation summary reports, and the batch data behind the filed process matter most. A for-cause inspection is narrow and adversarial: the inspector is following a thread and will not be diverted by a polished overview. Surveillance is broad: the inspector samples across the system, so no single area can carry the day. Read FDA inspection readiness for the FDA-specific procedural detail and BLA readiness data package for what a pre-approval inspection of a biologics application expects.

Before the Inspection: What Actually Matters

System Readiness, Not Document Readiness

The most important preparation is confirming that your quality systems are actually functioning. That means:

• Validated systems are in their validated state, with configurations matching what is documented in the validation package. See change control for validated systems for how that state is maintained.
• Audit trails are enabled and configured to capture creation, modification, and deletion of GxP records, with prior values retained.
• Calibration and qualification records are current for every instrument in use. See the calibration and metrology program.
• CAPA records reflect genuine investigations with corrective actions proportionate to the problem.
• Training records are current and tied to the procedures people actually perform. See the GxP training program.

A documentation sprint can clean up obvious gaps, but it cannot create the appearance of a functioning quality system where one does not exist. Inspectors read the history in your records. When were these documents created? When were they last revised? Do the revision histories look like an organization that reviews and improves its procedures, or like an organization that touched everything in the last month? A flurry of recent effective dates across unrelated SOPs is itself a tell.

Personnel Preparation

Every person who might interact with an inspector needs to understand a few things clearly.

• What the inspection is looking for, in general terms, not memorized answers to anticipated questions.
• How to respond: answer what is asked, do not speculate, do not volunteer information outside the scope of the question, and escalate anything you cannot answer to the back room.
• Their specific role in front room and back room operations if the site uses that structure.
• How to produce records under inspection conditions, meaning quickly, accurately, and with the chain of custody intact.

Subject matter expert training matters most. The analyst who uses the LIMS every day should be able to explain the audit trail configuration, walk through a batch record, and answer questions about how results are generated and reviewed. They do not need to recite regulations. They need to know their own systems cold.

One discipline worth teaching every SME: it is acceptable, and often correct, to say “I do not know, let me find out.” A fabricated or guessed answer that turns out to be wrong does far more damage than a brief delay. Inspectors expect that some questions require checking. They do not expect, and do not forgive, confident answers that the records later contradict.

A short set of behavioral rules, taught and drilled, prevents most self-inflicted findings:

• Answer only the question asked. A question about one batch is not an invitation to discuss three.
• Tell the truth, every time, with no exceptions. A single caught misstatement reframes everything else as suspect.
• Pause before answering. Silence is fine. A considered answer beats a fast wrong one.
• Do not guess, estimate, or characterize a number from memory when a record exists. Pull the record.
• If you do not understand the question, ask for it to be restated.
• Bring requested documents to the inspector through the agreed channel; do not hand over anything not requested.
• Never alter, backdate, or “tidy” a record during an inspection. That converts a deficiency into a data integrity finding and potential fraud referral.

Mock Inspections

A mock inspection, a structured simulation run by an internal team or external consultant, is the single most valuable pre-inspection activity. It surfaces gaps that document review alone misses: process gaps, training gaps, and inconsistencies between documentation and practice.

Effective mock inspections are run by people who are not responsible for the areas being examined, so they bring an outside eye. They should include observation of operations, personnel interviews, record review, and live system walkthroughs at the keyboard. The output is a prioritized gap list and remediation plan, ranked by likely inspection focus and by how long each fix will take. A gap that needs a validation effort to close cannot wait until two weeks before the inspection, which is the whole reason to run the mock early. The dedicated mechanics of running one are covered in the mock inspection program.

The related discipline of the internal audit program feeds this. A site whose internal audits already find real problems is rarely surprised by a mock.

A Practical Readiness Timeline

The point of the table is the top row. Sites that treat readiness as a continuous condition rather than a countdown do less in the final weeks, not more.

Acceptance Criteria: What “Ready” Looks Like

Readiness is not a feeling. A site can be judged ready against concrete tests:

• Any released batch record can be retrieved and presented within minutes, complete with its supporting raw data and audit trail.
• Every named SME has a backup who can answer in their absence.
• The most recent mock inspection findings are either closed or have a dated remediation plan with an owner.
• The document index is current: someone can name where the VMP, the site master file, the quality manual, the validation summary reports, and the training matrix live, and produce them on request.
• The front room and back room roles are assigned by name, and those people have practiced the handoff.
• There are no open critical or major internal audit findings without an active, on-schedule CAPA.
• The site can describe its own known issues and what is being done about each.

If any of these fails, that is the work, and it belongs before the inspection rather than during it.

Roles and Responsibilities

Inspection readiness is a team sport with defined positions. Confusion about who does what is itself a common cause of a poor inspection.

The single most important rule about roles: the host directs traffic, but does not answer questions that belong to an SME. An inspector who sees the host intercepting and reframing every technical answer reads it as narrative control, which invites suspicion. Let the person who does the work explain the work.

Front Room and Back Room Operations

The front room and back room model is a logistics approach for managing information flow during an inspection. It is worth understanding clearly because it is commonly described and less commonly run well.

Front room. The room where the inspector meets site personnel. The core front room team usually includes an inspector host, often the site quality head or equivalent, a scribe taking detailed notes of everything asked and answered, and the relevant SMEs called in as needed. The front room’s job is to be responsive, professional, and accurate. Answer questions, provide requested documents, and help the inspector reach what they need without friction.

Back room. A separate space where additional personnel monitor the inspection in real time, through the scribe’s notes or a communication channel, and coordinate document retrieval, SME availability, and response preparation. The back room team includes document control leads who can pull requested records quickly, technical SMEs who can research specific questions, and a coordinator who manages the flow between front and back.

What the back room is for. It lets the front room say “yes” to reasonable requests quickly, because the resources to execute those requests are already coordinated. A front room that scrambles to find a validation report, or stalls because no SME is available, looks unprepared. A front room that says “we will have that record within fifteen minutes” and then delivers it looks in control. The back room also runs the request log, drafts daily summaries, and prepares the team for the next day based on where the inspection is heading.

What the back room is not for. It is not for coaching front room personnel on what to say, screening information, or deciding what to reveal and what to conceal. Obstruction, delay, or refusal of an FDA inspection can render a drug adulterated under Section 501(j) of the Federal Food, Drug, and Cosmetic Act, added by the FDA Safety and Innovation Act of 2012 to address exactly this. The back room’s job is logistics, not strategy. A back room that crosses into managing what the inspector is allowed to learn has stopped being a readiness function and become a liability.

Document Control During the Inspection: The Two-Copy Rule

Every document that goes to the front room should be quality-checked first and copied. The discipline that prevents most document problems:

• Nothing reaches the inspector without a quick review for the right version, completeness, and legibility.
• Two copies of everything provided are made: one for the inspector, one kept by the back room with the request log entry, so the team knows exactly what the inspector has.
• Provide what is requested and only what is requested. If a binder contains the requested SOP plus three unrequested ones, provide the requested SOP.
• Mark documents that contain genuinely confidential commercial information appropriately, but never refuse a record the inspector is entitled to. Refusal is itself a finding.
• Keep the request log live: request number, time requested, document description, time provided, who provided it.

A Sample Inspection Request Log

The log is not bureaucracy. If a Form 483 lands, the response team reconstructs exactly what the inspector saw from this log plus the scribe’s notes, and the difference between a precise log and a vague memory is days of rework.

The Scribe Is the Most Underrated Role

Whatever the inspector says, asks, observes, and is told should be captured contemporaneously by a dedicated scribe. This record drives the back room’s coordination during the inspection and becomes the foundation for any response afterward. If a 483 lands, the response team works from the scribe’s notes to reconstruct exactly what was observed and said. Thin or sloppy notes here cost real time and accuracy later. Assign a capable, fast writer who is not also expected to answer technical questions.

Good scribe notes capture, for each exchange: the time, who from the inspection team asked, the exact question as asked, who answered, the substance of the answer, any document referenced or provided, and any concern the inspector voiced. The scribe does not editorialize and does not soften. A note that reads “inspector asked why the second integration was not documented; analyst said it was a re-injection, no written explanation found” is worth more than a tidy summary that hides the gap.

Data Integrity-Specific Inspection Preparation

Data integrity inspections require preparation beyond general GMP readiness, because inspectors have developed sophisticated ways to find integrity gaps. The expectations draw on the FDA guidance “Data Integrity and Compliance With Drug CGMP” finalized in December 2018, the MHRA “GXP Data Integrity Guidance and Definitions” issued in March 2018, the PIC/S guidance PI 041 on good practices for data management and integrity, and the WHO guidance on good data and record management practices (WHO Technical Report Series 996, Annex 5). The recurring framework across all of them is ALCOA, that data be Attributable, Legible, Contemporaneous, Original, and Accurate, extended to ALCOA+ with Complete, Consistent, Enduring, and Available. For the underlying principles, see the ALCOA+ principles in detail and data integrity foundations.

Know your system configurations. Be able to demonstrate, with the inspector at the keyboard, that the audit trail in your LIMS or chromatography data system is configured to capture prior values for all GxP-critical fields. Know where the audit trail lives, how to pull it for a specific batch, and what it shows. If you cannot demonstrate this fluently, the inspector reasonably concludes that audit trail review is not actually happening. The mechanics of doing this well are covered in audit trail design and review and the day-to-day routine in operationalizing audit trail review.

Know your user account status. Be ready to show that there are no shared accounts and that every account has access proportionate to the role. Have the user account reports staged: active accounts, historical activity, access control settings, and the periodic access review records. Shared logins remain one of the most cited integrity failures in published warning letters, because they break attributability at the root. See access control and cybersecurity for validated systems for the controls behind this.

Control system time. Be able to show that the system clock is locked to a controlled, traceable source and that ordinary users cannot change it. Timestamp manipulation is a classic integrity attack, and an inspector will check whether a user could have backdated a result. See time stamps and system clock control.

Be prepared to explain anomalies in advance. If your systems have known issues, a time synchronization problem that produced some apparent timestamp discrepancies, a batch where an analyst used a backup login, a CAPA still open for an audit trail gap, be ready to explain each one accurately and completely. An inspector who finds an anomaly you have already identified and documented as under investigation is in a very different posture from one who discovers it alongside you. The first sees a functioning quality system catching its own issues. The second sees an issue you did not know about.

Pre-prepared document packages. For a pre-approval inspection or a GMP inspection where data integrity will be a focus, staging packages for recently released batches saves time and signals preparedness. A useful package includes the batch record, an audit trail summary, any out-of-specification records, instrument qualification certificates, and the relevant analytical raw data. The batch record review and OOS investigation processes feed directly into what these packages should contain.

The data integrity story. Be able to describe your program coherently from memory: the system inventory, the criticality tiering, the audit trail review process, and the governance structure that oversees it. When an inspector asks “how do you ensure data integrity in your chromatography data system,” they should hear a clear, structured answer, not an improvised one. The architecture behind that answer is the subject of the data governance framework and data criticality and data risk.

A Short Inventory of Self-Checks

Before any data-integrity-focused inspection, a site should be able to answer each of these without hesitation:

• For any released batch, can we produce the full audit trail in minutes?
• Can every analyst who touched that batch be identified by unique login?
• Are there any orphan data files, aborted runs, or trial injections, and can we explain them?
• Is system time locked to a controlled source, and can users change it?
• Who reviews audit trails, how often, against what procedure, and where is the evidence?

If any answer is uncertain, that is the gap to close before the inspection, not during it.

A Worked Walkthrough: The Chromatography Data System Question

Inspectors often choose a single released lot and trace it end to end through the chromatography data system. Here is the path a prepared analyst walks, and what good looks like at each step.

1. The inspector names a lot. The analyst opens the data system, navigates to the sequence for that lot, and shows it on screen. Good: the analyst does this without hunting, and the sequence matches the batch record.
2. The inspector asks how many injections were run. The analyst shows the full injection list including any aborts or re-injections. Good: every injection is accounted for, and any re-injection has a documented reason linked to a deviation or notebook entry. A finding pattern: injections that exist in the system but not in the record, or aborted runs with no explanation.
3. The inspector asks to see the audit trail for the integration. The analyst opens the audit trail and shows that the original integration, any reprocessing, and the identity of who did it are captured with prior values. Good: no manual integration without a documented, approved reason.
4. The inspector asks who reviewed the result and when. The analyst shows the second-person review record and the review of the audit trail itself. Good: the audit trail review is evidenced, not assumed.
5. The inspector asks whether the analyst can delete data. The analyst shows that delete permissions are restricted and that the role-based access matrix reflects this. Good: the analyst does not have privileges they should not have.

The lot trace is the most common data integrity exercise. Practicing it on real lots, at the keyboard, in a mock, is the single best preparation. The supporting article is chromatography data system integrity.

The Inspection Itself

Establishing day one. The first hours set the relationship and the inspector’s initial read of the site. Present professionally, keep the introductory overview short, ideally under twenty minutes, introduce the team, and be clear about what the site does and how it is organized. Answer questions directly. The tone you set early tends to hold. For the moment-to-moment mechanics of running the day, see managing a live inspection.

Document requests. When an inspector requests a record, produce it as fast as you can. “We will have that in a few minutes” beats a long explanation of where records are stored. Keep a running log of everything requested and everything provided, with timestamps. That log protects both sides and feeds the response if a 483 follows.

Observation responses. When an inspector watches an operation and asks a question, let the relevant SME answer it directly and accurately. Do not insert yourself between the inspector and the person who actually knows. Redirecting questions away from the operator reads as control of the narrative, which invites suspicion.

Managing the day. The inspector controls the schedule, the pace, the areas of focus, and the requests. The front room host’s job is to ease access, not to steer attention. End each day with a debrief: what was covered, what is open, what is coming, and what needs to be staged overnight.

The closeout for the day. At the end of each inspection day, many inspectors will note areas of concern. Capture these precisely. They are the early signal of where observations will land, and they give the back room a head start on root cause work before anything is formally written.

A note on tone and cooperation. Cooperation is not the same as agreement. You can be fully cooperative, produce every record, answer every question, and still, at the closeout, calmly note where you see a matter differently. What you cannot do is delay, obstruct, or selectively withhold. The cooperative-but-precise posture is the one that holds up.

After the Inspection: Preparing for the 483

Not every inspection produces an FDA Form 483, the Inspectional Observations form issued at the close of an FDA inspection. EU inspections instead conclude with a written report and, where applicable, a deficiency classification of critical, major, or other, against the criteria in the PIC/S and EMA classification guidance. When a 483 does land, the response process is its own discipline, covered in the 483 response strategy and in warning letter response strategy. What matters while the inspection is still closing:

• Ensure the scribe’s notes capture everything the inspector said, observed, and questioned.
• Begin preliminary root cause analysis for any findings the inspector disclosed during the inspection, while the context is fresh. See root cause analysis techniques.
• Confirm that any commitments made verbally during the inspection are written down accurately, so the written response does not contradict what was said in the room.

The 483 is issued at the closeout meeting, where you can discuss the observations. This is not the moment to argue whether an observation is justified. It is the moment to ask clarifying questions, confirm your understanding of what was observed, and signal that you will review the findings carefully in preparing a written response. FDA expects a response within fifteen business days for the agency to consider it before deciding on further action such as a warning letter, so the clock effectively starts at closeout.

For practitioners who want to understand how the two regulatory systems differ in tone, scope, and procedure, FDA versus EMA inspection dynamics maps the practical contrasts, FDA warning letter patterns shows what recurring findings actually look like in the public record, and regulatory intelligence on 483 trends shows how to track where inspectional focus is moving.

Common Mistakes and Real Finding Patterns

These patterns recur across published inspectional findings, regardless of modality or company. None of them require an actual quality problem to generate an observation; several are pure readiness failures.

• The two-week sprint. A flurry of recent effective dates across unrelated SOPs, freshly tidied logbooks, and binders assembled the week before. Inspectors read document metadata. Recency that does not match a normal review cadence reads as window dressing.
• The suspiciously short deviation log. Few or no deviations in a busy operation signals that problems are not being captured, which is worse than having them.
• The host who answers everything. When the QA host intercepts every technical question, the inspector concludes the operators cannot answer for themselves, or that the narrative is being managed.
• The SME who guesses. A confident answer that the records later contradict converts a routine question into a credibility problem that taints the rest of the inspection.
• Shared logins. Generic or shared accounts break attributability and are among the most cited data integrity failures. “It is only for the standalone balance” is not a defense; it is a finding.
• Audit trail review claimed but not evidenced. A procedure that says audit trails are reviewed, with no records showing it happened, is a gap the inspector will find within minutes at the keyboard.
• Orphan and unexplained data. Aborted runs, trial injections, test data in production systems, with no documented explanation. Inspectors look for data that exists but was never reconciled.
• Records altered during the inspection. Correcting, backdating, or completing a record while the inspector is on site. This is the single most dangerous mistake because it converts a deficiency into a potential fraud referral.
• Commitments that contradict the response. Something said in the room that the written 483 response then contradicts. The scribe’s notes exist to prevent this.
• No backup for the named expert. The one person who can explain the LIMS is out sick on day two, and the inspection stalls.

Interview-Ready: Questions and How to Answer Them

Inspection readiness comes up in interviews for QA, quality systems, data integrity, and validation roles. The interviewer is testing whether you understand the difference between real control and theater, and whether you have actually been in the room. Concrete answers beat textbook ones.

“What is the difference between compliance and inspection readiness?” Compliance is the underlying condition, that systems are validated, records contemporaneous, procedures followed. Readiness is the ability to demonstrate that condition quickly and clearly under inspection pressure. You can have one without the other, and the dangerous case is readiness without compliance, because it reads as concealment the moment a thread is pulled.

“Walk me through how you would prepare a site for a pre-approval inspection.” Start months out, not weeks. Confirm system readiness first, validated systems in their validated state, audit trails configured and reviewed, training and calibration current. Run a mock inspection led by people outside the area, generate a prioritized gap list, and close the slow-to-fix gaps first. Stage document packages for the batches behind the filed process. Assign and drill the front room and back room roles. In the final weeks, do logistics, not remediation.

“What is the back room for, and what is it not for?” It is for logistics: pulling records fast, coordinating SME availability, running the request log, preparing for the next day. It is not for coaching what people say, screening information, or deciding what the inspector is allowed to learn. Obstruction can render product adulterated under the FD&C Act as amended by FDASIA in 2012. The back room enables a fast honest “yes,” not a managed narrative.

“An inspector asks you a question and you do not know the answer. What do you do?” Say so, then commit to finding out. “I do not know, let me confirm and come back to you” is a correct and respected answer. Guessing is the failure mode, because a confident wrong answer that the records contradict damages credibility far more than a short delay.

“How do you demonstrate audit trail review during an inspection?” Be able to do it live at the keyboard: open the audit trail for a specific named batch, show that it captures prior values for critical fields, and show the records that the review actually happened, who reviewed, when, against which procedure. If you can only describe it and not show it, the inspector concludes it is not happening.

“What does an inspector reading as a red flag that your records look too clean?” Almost no deviations in a busy operation, CAPAs that all close fast with trivial actions, and a uniform recent revision date across unrelated documents. A healthy quality system surfaces its own problems and shows a normal history of review and improvement. Implausible cleanliness invites the inspector to dig.

“What is a state of control and where does the term come from?” A condition where the set of controls consistently assures continued process performance and product quality. FDA’s 2011 process validation guidance defines it and ICH Q10 builds the quality system around maintaining it. Inspection readiness is the visible demonstration of that condition.

“Tell me about a finding pattern you would expect around data integrity.” Shared or generic logins that break attributability, system time that users can change, orphan or aborted data with no documented explanation, and manual chromatographic integration without an approved reason. These are among the most cited integrity issues because they are concrete and easy to demonstrate at the keyboard.

Practical Tips

• Treat readiness as a continuous condition. The site that does least in the final two weeks is usually the best prepared, because the work was already done.
• Name a backup for every SME and document control role. Inspections do not pause for sick days.
• Practice the lot trace on real lots in a mock. The end-to-end walkthrough at the keyboard is the exercise most likely to appear and most likely to expose a gap.
• Keep the request log and scribe notes from day one. They are the raw material for any 483 response, and reconstructing them later costs days.
• Never let a record be altered during an inspection. If a gap exists, it is better as an honest deficiency than as a manipulation.
• Brief management on what they own: opening and closing meetings, the tone of cooperation, and any commitment made on the record.
• Cross-link your own preparation. The internal audit program, quality metrics and KPIs, management review under ICH Q10, and the mock inspection program are the systems that make readiness continuous rather than a sprint. For interview preparation across GxP topics generally, see GxP quality interview preparation.

The State of Control Standard

The goal of inspection readiness is not to pass an inspection. It is to be an organization that, when examined carefully, demonstrates genuine control over the quality of what it produces. An organization in real control of its quality processes does not scramble before inspections. It has operational discipline, reliable data, and documented evidence of ongoing quality management, the same things its pharmaceutical quality system is supposed to deliver every day.

That is the longer definition of “state of control.” An inspection-ready organization is not one that looks good under scrutiny. It is one that is good under scrutiny, because scrutiny only reveals what already exists. Build the first thing, the real state of control, and the second thing, a clean inspection, tends to follow. Try to build only the second, and the first absence shows.