SystemQuality Operations & CAPA

GMP Inspection Readiness

GMP inspection readiness that runs the front room and the back room on one screen: each request on its clock, each page read for gaps before it goes in, and the QA head deciding how a gap is shown.

Follow one glove integrity request into the front room ↓
Watch with transcript →
The problem

The investigator found the blank verifier line before the QA head did

On inspection day the scribe types the investigator's words into a spreadsheet, a runner carries them to the back room, and someone searches the QMS, the document system and scanned paper logbooks. The pages come back with the clock running, and QA skims them on the way to the door.

So the missing second signature or the extension nobody can explain is read first by the investigator, in front of the plant head. At a contract manufacturer the finding travels: each client with product made in that plant reads it, and some are deciding where their next product goes.

Built forQA headsBack-room leadsSubject matter expertsPlant heads

The Problem Today

Pages go into the front room skimmed under the clock, so the investigator is the first to see a blank signature.

243
FDA FY2025 citations for quality procedures not followed published

The back room today

  • Typed notes
  • Logbooks
  • Spreadsheet
  • Stopwatch
  • Past questions live in headsWhat earlier investigators asked leaves with the people who heard it
  • A plant's finding reaches clientsEach client with product in that plant reads the observation

The Solution

  1. Said, then a timed requestThe scribe's sentence becomes a numbered job with its own clock
  2. Scope checked against old asksA failure filed under another category is pulled back in
  3. Each logbook line pre-readTested-by and verified-by columns read on each page in scope
  4. QA head decides the gapShown as it stands, with its own deviation, and no late signature

Built-in controls

  • Records go in as they stand, unaltered
  • Nobody reviews a record they retrieved
  • A held request goes in only on the QA head's decision

What You Get

The investigator learns of a gap from the site's own QA head, deviation number attached, before reading the page.

  • Experts rehearse what was asked herePast investigators' and auditors' questions, with answers that held
  • One back room serves every plantAuthority inspections and client audits on the same rules
  • Clients get their lines that eveningTheir own product's requests from the daily summary
Features

GMP inspection readiness features, traced on one glove integrity request

A mock inspection of a sterile fill-finish plant, nineteen days before FDA arrives. The mock investigator asks for all glove integrity failures on one isolator since the start of last year, with the investigations.

demoThe plant, the CDMO, its client, the people and the records are sample data.

  1. 01Scribe line

    Inspection request log: the scribe's words become timed back-room requests

    • The investigator's sentence quoted on the request. The back room fetches what was asked word for word, so no runner's paraphrase sends anyone to the wrong shelf.
    • A clock, retriever and reviewer per request. The back-room lead sees which request is drifting toward a delay that could read as limiting an inspection.
  2. 02Scope check

    A challenger agent widens the scope with a rule a past inspection taught

    • The first retrieval attacked by its own challenger. A failure filed under a different deviation category is pulled in before the investigator asks why it is missing.
    • Invalidated tests included with their memo. The question an earlier investigator raised about invalidations is answered in the first delivery this time.
  3. 03Held request

    Pre-read of each logbook line for a missing second-person verification

    • All lines read, no sampling. The gap reader read 662 port results and found the one with no verifier before anyone in QA had to.
    • The scanned logbook page beside the flag. The reviewer judges the original logbook line itself rather than an agent's account of it.
    • Send blocked while the request is held. A page with a gap cannot reach the front room until QA has decided how it is shown.
  4. 04Review packet

    Back-room document review: each record opened and read before it goes in

    • One record at a time, timed on screen. No back-room lead can agree with a flag on a stack of records they clicked past.
    • Each record's reader shown. When the investigator asks who reviewed a page, the answer is on screen.
  5. 05Flag agreed

    The back-room lead confirms the gap on the page and hands it to the QA head

    • Agreement given with a reason code. The back-room lead's judgment on the gap is recorded ahead of the QA head's decision.
    • Two choices: as it stands, or retrieve more. A late signature on the blank line is not an option on the screen, so nobody is tempted under the clock.
  6. 06Gap disclosed

    Data integrity gap disclosed with its own deviation, no late signature

    • A deviation opened in the QMS at the decision. The investigator reads about the gap with its deviation number already attached, as the plant's own finding.
    • Classification left to QA. The deviation arrives as proposed major, and the quality unit decides what it is after initial assessment.
    • A cover note read to its end. Each sentence that leaves the back room has been read by the QA head who signs for it.
  7. 07In the front room

    Request turnaround measured from the investigator's words to the front room

    • Minutes from words to front room. The back-room lead sees a held request still land inside the plant's own target, with every record read and the gap disclosed.
    • The cover note kept as sent. What the plant told the investigator stays with the request for the closing meeting and the response.
  8. 08Daily summary

    Daily inspection summary written from the request log

    • Requests, documents and pages, counted from the log. The evening debrief starts from what the investigator actually received rather than from what people remember handing over.
    • Two signatures on the day's record. The back-room lead prepares it and the inspection lead signs; a change after signing clears the signature.
  9. 09Storyboard

    Inspection storyboard frame reopened when a record contradicts it

    • A citation on each storyboard sentence. The subject matter expert says in the front room only what a record shows.
    • Signature cleared when a record disagrees. The expert rewrites the frame before the real inspection instead of repeating a claim the logbook has just disproved.

The QA head decides what is shown; the back-room lead reads it first

The scribe and the retrievers feed them, and these four carry inspection day.

QA heads

Lead the inspection, decide each held request and sign the summary and responses

  • Gaps found before the investigator sees them
  • A decision screen with only honest choices
  • Learned rules that wait for their approval
Back-room leads

Run the request queue, assign retrievers and review each record before it goes

  • Each request's clock, retriever and state at a glance
  • Records pre-read, with the gap on the page
  • A daily summary drafted from the log
Subject matter experts

Own the storyboards for their area and answer the investigator in the front room

  • Storyboards with a source on each sentence
  • The questions asked here before, to rehearse
  • A frame reopened before it misleads anyone
Plant heads

Host the investigator in the front room and co-sign the responses

  • No page in the front room that QA has not read
  • Topics ranked on the plant's own open records
  • Responses they co-sign as the second person

Scanned paper logbooks are read line by line, beside the QMS and the eBR

Quality management systemDeviations, investigations, CAPAs, extensions and change controls, with categories as filed.
Scanned paper logbooksEquipment use and glove integrity logs from the document system, read line by line.
Document management systemProcedures in the version effective on the record's date, reports and invalidation memos.
eBR, LIMS, monitoring and trainingBatch records, test results and settle plate reads, plus training and equipment history.
Past inspections and client auditsWhat each investigator and auditor asked here, and which answers held.
More screens

Nine past questions on glove integrity shape what the expert rehearses

Before the inspection the agents rank topics and rehearse the expert; after it, the response kit counts the days.

The isolator ranks first on the plant's own open recordsTopics ranked by published inspection themes times the plant's own signals, such as an extended CAPA action.
Each model answer cites a record; the expert's own words go to the QA headQuestions asked here before, plus the challenger's new ones, each with a cited model answer.
One answer that did not hold became a corrective actionQuestions that come back, whether each answer held, and the rules the agents learned, active only once the QA head approved them.
The fifteenth business day lands after a holiday is skippedMock observations in rehearsal, the steps to the plant head's signature, and the business-day count without the federal holiday.
Each record the reviewer opened is a line in the audit trailEach step with its reason, what each signature meant and the session, agents marked as agents, kept for export with the inspection file.
Loosening any control needs the QA head's signatureThe request clock, who sends held items, the gap reader's checks and the plants in scope; tightening applies at once.

demoSample data, from the working solution.

A rule learned at another plant's inspection pulled back a missed failure

Each agent hands its result to the next or to a named person, and none of them alters a record.

Request maker

Turns the scribe's line into a structured request with record type, equipment and dates, quoting the words it came from.

  • Shows any narrowing or widening of what was said
  • Asks when it cannot structure a line
Retriever

Queries the QMS, eBR, LIMS, the monitoring system, the document system and the logbook scans.

  • Edits, signs or annotates no record
Gap reader

Reads each page and line in scope for missing signatures, superseded procedures, late entries, open actions and contradicted storyboards.

  • Fixes no record and drops no page
  • Calls no sample the whole
Challenger

Plays the investigator: asks the next question, and attacks the agents' own scope and drafts.

  • Decides nothing about what is shown
Topic ranker

Ranks topics by FDA's published themes against the plant's open CAPAs, extensions, excursions and investigation ages.

  • Uses no source outside the plant's quality records
Storyboard writer

Drafts storyboards and model answers for the experts, each sentence cited.

  • Writes no sentence it cannot cite
Summary writer

Writes the daily summary from the request log: requests, documents, pages, gaps and commitments.

  • Adds nothing that is not in the log
Response drafter

Drafts each observation's response: investigation, correction, CAPA, dates and evidence.

  • Sends nothing
  • Commits no date the records do not support

A daily summary needs two signatures, and a response needs the plant head's

Back-room lead
Sees
Each record in a request's packet, and the flagged line on its page
Signs
Agreement with each flag, each clean request sent, and the daily summary as preparer
QA head
Sees
The flagged page itself, the back-room lead's reason and the cover note to its end
Signs
How each held request is shown, the deviation for a gap, the daily summary and each learned rule
Regulatory affairs lead
Sees
The drafted responses and the challenger's points against them
Signs
The wording check before the QA head signs
Plant head
Sees
The response kit once the inspection lead's signature is on it
Signs
Each response as the second signature, a different person from the first

What quality teams ask about GMP inspection readiness

What is GMP inspection readiness?

GMP inspection readiness is a plant's ability to answer an investigator's requests quickly with records that hold up. Here it covers the day itself: the scribe's words become timed requests, agents retrieve and pre-read the records for gaps, and the QA head decides how anything found is shown.

How do the front room and back room work in an FDA inspection?

The investigator sits in the front room with a host, a QA lead and a scribe who logs each request. The back room, often called the war room, retrieves and reviews each record before it goes in.

What happens when the back room finds a gap in a record?

The request is held. The back-room lead reads the records and confirms the gap on the page, then the QA head decides: present the record as it stands with a deviation opened for the gap, or retrieve more. A late or backdated signature is not offered, in line with FDA's data integrity guidance.

Why does each request run on a clock?

FDA's guidance on delaying, denying, limiting or refusing a drug inspection says a delay in producing records can be treated as limiting the inspection. The clock turns amber well before the plant's target, so a request can be reassigned in time.

How is a mock inspection run with it?

Internal audit plays the investigator and the plant runs the day as it would a real one. The challenger asks what investigators and client auditors asked here before, and each mock observation goes into the response kit and on to the CAPA system.

How long does a site have to answer FDA's inspection observations?

FDA considers a response received within fifteen business days of the observations before deciding on a warning letter. The response kit counts those days from the close-out without federal holidays, and the QA head and the plant head both sign each response.

Do clients see what happened in an inspection of their CDMO?

During an authority inspection, each client's quality person receives that evening the daily summary lines for their own products only, as the quality agreement sets out. In a mock inspection the extract is rehearsed and stays unsent.

What does the gap reader look for on each page?

A missing second-person verification, a superseded procedure, a late entry or correction without its reason, an open action, and a record that contradicts a signed storyboard. Switching a check off needs the QA head's signature.

Name the record you would
least like an investigator to find.

Send one logbook and the requests from your last inspection, and we will run them through a back room that reads each line first.