Vitalis Therapeutics Inc. — Inspection readiness for the VitaFlow (VTX-401) pre-approval inspection: what an inspector is actually assessing, how a PAI runs, the front room / back room model, conduct rules, the preparation undertaken, and the outcome.
1. What an Inspector Is Actually Assessing
The instinctive assumption is that a pre-approval inspection checks whether this product can be made correctly. That is part of it, and it is the smaller part.
They will trace a specific number from Module 3 of the application back to a raw instrument printout. But what they learn from that exercise is not really about the number — it is whether the organization can produce evidence on demand, whether the evidence is contemporaneous and complete, whether deviations were investigated properly, and whether the people who did the work can describe what they did.
A facility that answers one traceability request perfectly and the next three slowly has not passed three-quarters of an inspection. It has demonstrated that the first answer was preparation rather than practice.
The consequence for a program manager is worth stating plainly: you cannot prepare for an inspection in the month before it. The material being inspected was created over years, by people following procedures, recording what they did as they did it. What preparation achieves is narrower and still essential — it stops a sound quality system from failing on presentation.
2. Types of Inspection
| Inspection | Trigger | The question it answers | Consequence |
|---|---|---|---|
| Pre-approval inspection (PAI) | Triggered by an NDA under review | Can the facility make this product, to this process, at this scale, and is the data in the application supported by what is on site? | Gates approval. |
| Routine GMP surveillance | Risk-based schedule | Is the facility operating in a state of control across everything it makes? | Findings can affect all products at the site. |
| For-cause | Signal, complaint, recall or field alert | What went wrong, and is it contained? | Narrow scope, high intensity. |
| Bioresearch monitoring (BIMO) | Clinical sites, CRO, or the sponsor | Was the trial conducted to protocol and GCP, and does the data reconcile? | Can affect the credibility of the clinical package. |
That is the same cross-contamination effect described in the GxP Compliance Plan §ladder: a sponsor's exposure at a contract site includes everything else that site makes.
3. How a PAI Runs
| Stage | What happens | Note |
|---|---|---|
| Opening meeting | Scope stated, Form FDA 482 issued | The 482 is the notice of inspection. Scope is stated but not binding — an inspector may follow evidence wherever it leads. |
| Facility walkthrough | Flow of materials, personnel and product | Segregation, environmental controls, housekeeping. First impressions form here. |
| Systems review | Quality, production, laboratory, materials, packaging, utilities | The six-system model. An inspector rarely reviews all six; they choose based on risk. |
| Document review | Batch records, deviations, CAPA, validation, training | The bulk of the inspection. Deviations and investigations receive the closest attention. |
| Data traceability | A result in the application traced back to raw data | The single most common PAI activity: take a number from Module 3 and follow it to the instrument printout. |
| Interviews | Operators, analysts, supervisors, quality staff | Whether people can describe what they actually do, and whether it matches the procedure. |
| Daily wrap-up | Observations discussed as they arise | Nothing at the close should be a surprise if the daily meetings were used properly. |
| Closing meeting | Form FDA 483 issued if there are observations | Observations are read aloud and discussed. Clarification is possible; argument is not. |
It tests everything at once: whether the raw data exists, whether it is attributable and contemporaneous, whether any intermediate calculation is documented, whether the analyst was qualified, whether the instrument was calibrated, and whether the number in the application is the number the instrument produced. A single trace exercises the entire ALCOA+ set.
Note the seventh row. Daily wrap-up meetings exist so that nothing at the closing meeting is a surprise. An observation raised on day two can often be addressed, clarified, or contextualized before the inspection ends. An observation first heard at the closing meeting can only be responded to in writing, afterwards.
4. Front Room, Back Room
| Function | Who | Purpose |
|---|---|---|
| Front room | Inspector, host, scribe, subject-matter expert on call | Where the inspection happens. Deliberately sparse — only the people needed. |
| Back room | Document retrieval, SME staging, quality review | Requests are received, documents located, reviewed for completeness and relevance, then delivered. Nothing goes to the front room unreviewed. |
| Scribe | Records every request, every document provided, every question and answer | The contemporaneous record of the inspection. Without it, the response to a 483 is written from memory. |
| Daily debrief | Program, quality and site leadership | Assess the day, prepare for tomorrow, begin drafting responses to emerging observations. |
Without a back room, a request for a batch record produces someone walking to a filing cabinet and handing over whatever is in it — unreviewed, possibly incomplete, possibly the wrong version. With one, the document is located, checked for completeness and relevance, and delivered with someone available who understands it.
Nothing goes to the front room unreviewed. That is not concealment. Reviewing before delivering is how a sponsor avoids handing over an incomplete record and then having to explain why it looked incomplete.
The scribe is the role most often under-resourced and most consequential. Every request, every document provided, every question and answer is recorded contemporaneously. Without that record, a response to a Form 483 is written weeks later from memory, by people reconstructing what they think was asked.
5. Conduct
| Rule | Why |
|---|---|
| Answer only what is asked | A question about a batch record is not an invitation to describe the whole process. Volunteered information expands scope. |
| Say “I don't know, I will find out” when true | A wrong answer given confidently is far worse than a delay. It will be checked. |
| Never speculate | An inspector records what was said. Speculation becomes a finding. |
| Never argue at the closing meeting | Observations are clarified in the room and rebutted in the written response, which is where argument belongs and where it is on the record. |
| Do not offer documents not requested | A helpful instinct that reliably lengthens inspections. |
| Escalate anything touching data integrity immediately | Different category, different consequence, different response team. |
Answer only what is asked. Every experienced professional wants to be helpful, and being helpful during an inspection means volunteering context. Volunteered context expands scope: a question about one batch record becomes a discussion of the process, which becomes a request for three more batch records.
Say “I don't know, I will find out.” This feels like a failure and is the opposite. A confidently wrong answer is recorded, checked against the documents, and becomes an observation about the reliability of what the sponsor says — which is a far more damaging category of finding than the original question would ever have produced.
Never argue at the closing meeting. Observations can be clarified in the room — if an inspector has misunderstood a fact, say so — but disagreement belongs in the written response within fifteen working days, where it is reasoned, evidenced and on the record.
6. Preparation Undertaken
| Activity | Position |
|---|---|
| Mock inspections | 3, conducted by external GMP consultants unfamiliar with the site |
| Subject-matter experts trained | 41 across quality, production, laboratory and engineering |
| Storyboards prepared | 12 — one per anticipated line of questioning |
| Document retrieval target | ≤15 minutes from request to front room |
| Readiness audit | 2029-03-14 — three months before the inspection |
| Inspection held | 2029-06-12 |
Storyboards
A storyboard is a prepared narrative for a line of questioning an inspector is likely to pursue — the method transfer failure, the enrolment recovery, the deviation with the longest investigation. It assembles the facts, the documents, the timeline and the people in one place.
7. Outcome and What It Confirmed
| Measure | Result |
|---|---|
| Inspection held | 2029-06-12, Aldergate Biologics |
| Form 483 observations | 1 |
| Subject | Environmental monitoring documentation |
| Response | Within 15 working days |
| Status at the action date | closed |
| Effect on approval | none |
A documentation observation says something was done and inadequately recorded. It is a systems finding: real, correctable, and not a statement about whether the product can be made. A data integrity observation, or one going to the validity of the process itself, sits on the critical path to approval and is the most probable route to a Complete Response Letter — as the FDA Review Log records.
R-07 was never really the risk that Aldergate would fail an inspection. It was the risk that a finding of the wrong category would arrive with no time to remediate it. Fifteen working days of held response capacity, three mock inspections and a readiness audit three months out are what converted that from a program risk into an administrative one.
What the inspection confirmed is broader than the observation count. The commercial process was validated, the analytical methods transferred and re-qualified, the batch records complete and contemporaneous, and the people who ran the batches able to describe what they did. That is the CMC package in CMC Readiness demonstrated in person rather than on paper — which is the only demonstration that counts.