SystemContract Manufacturing (CDMO)

Customer Audit Hosting & Response

A customer audit tool for CDMOs: it pulls each record a client's auditor asks for, masks other clients' data and cites the clause for each mask, and lets QA release only what the auditor may see.

See one shared logbook page masked and released ↓
Watch with transcript →
The problem

A shared dryer's logbook page names every client that used it

A drug substance CDMO makes many clients' actives on the same reactors and dryers, and each client has the right to audit the plant. On the day the auditor asks for record after record, and the back room finds each one in the logbook, QMS, LIMS or document system. Someone in QA then reads each page and blacks out what belongs to other clients before it goes in, against a clock.

Two things go wrong. Another client's product name, batch number or deviation slips into the room and breaks that client's confidentiality, or the record is withheld so heavily that the auditor writes a transparency finding. A deviation on shared equipment is the hard case: the client is entitled to know something happened on equipment its product uses next, but not whose batch it was, and the QA head is pulled off the floor to write that summary.

Afterwards the report arrives as a PDF, responses are typed in a word processor, CAPAs are typed again into the QMS, and the same finding raised by two clients gets two answers.

Built forQA compliance leadsPlant QA headsQA request reviewersClient quality liaisons

The Problem Today

On a shared plant, every logbook page an auditor asks for carries other clients' products, masked by hand under a clock.

Read and blacked out by hand

  • Use logs
  • Deviations
  • LIMS pages
  • Redactions
  • A neighbor's batch slips inOne missed batch number breaks another client's agreement
  • Withheld until distrustedHeavy black boxes read as a site with something to hide

The Solution

  1. Pre-pulled from the planThe client's audit plan and past audits read before the day
  2. A wall over each recordOther clients' products, batches and settings masked, each with its clause
  3. The client's auditor firstA challenger asks the client's questions and catches its own team's miss
  4. Signed, then releasedEach summary carries the QA head's signature; a second reviewer releases it

Built-in controls

  • Nothing reaches the audit room unreleased
  • A mask on another client's product never comes off
  • Each mask cites its quality agreement clause

What You Get

Each client leaves trusting how its own data, and its neighbors', were handled.

  • New hosts, the QA head's standardRulings applied from a host's first audit
  • One CAPA for one findingA repeat finding links to the CAPA already open
  • Prospects see care, not secrecyEach mask shows its reason and what stays visible
Features

Customer audit day on one shared filter-dryer's logbook page

One client audits a drug substance plant it shares with another; the audit host, the QA head, the request reviewer and the client liaison each work their part.

demoSample data: the CDMO, its clients, auditors, staff, batches and records.

  1. 01Before the audit

    Pre-audit request and plan read, likely records pulled and masked early

    • Pre-audit request answered in fields. Auditors, records wanted in advance and the confidentiality undertaking come back as fields; a free-text line waits until the host opens it.
    • Last audit's questions brought forward. What this client asked last time, and the rulings applied then, shape what the back room pulls this time.
    • Pre-pulls checked before anyone asks. Each likely record already carries its verdict, shown in full, with masks, summary only or not shareable, when the auditor names it.
  2. 02Entry check

    Shared equipment logbook checked entry by entry for other clients' data

    • Each entry read against the agreement. Another client's product, batch, people, prices and process settings are masked; this client's own runs and cleaning results stay plain.
    • A request clock in view. Each request runs on its clock with a named retriever and reviewer, so the front room knows what is late before the auditor asks.
    • Agents shown at work. Request clerk, plan reader, record puller and wall checker each show what they read and whom they hand to.
  3. 03Mask reason

    Redaction of other clients' data with the clause and ruling behind each mask

    • Clause and ruling on each mask. The auditor sees why a line is withheld and which agreement says so, which reads as care rather than secrecy.
    • What stays visible, listed. Dates, activity and equipment stay shown, so the record still answers the auditor's question.
    • Tightening at once, loosening signed. The host can add a mask at once; removing one needs the plant QA head, and a mask on another client's product stays.
  4. 04Auditor's questions

    Mock client audit questions that caught a note the masking had hidden

    • The client's auditor played first. How a cleaning limit covers a product the client cannot see is answered with the limit's basis, never the product's name.
    • Its own mistakes found. A low nitrogen pressure note hidden inside another client's masked entry moved into the summary, because it is an equipment event.
    • Questions only a person answers. Whether the fault affects the client's next batch is left to the plant QA head's own words.
  5. 05Disclosure summary

    Deviation on shared equipment summarized for the client in the QA head's words

    • Summarized, never withheld. A deviation on equipment the client's product uses next is told plainly, without whose batch it was or that client's limits.
    • Signed only after the records are read. The QA head reads the deviation and the work request before signing, and the reason offered matches what they did.
    • No other client named. Each draft is checked for another client, product or batch before it reaches the signature.
  6. 06Release

    Audit request released by a second QA reviewer after reading the exact copy

    • The retriever cannot release. A different QA person reads the copy the auditor will see, summary and basis included, and signs the release with its meaning.
    • Any later change withdraws it. A mask added, a summary signed again or a rule decision takes the record out of the room until it is read and released again.
  7. 07Audit room

    Client auditor's view of released records only, exactly as approved

    • Released copies only. The client's auditor reads each record as the reviewer approved it, watermarked and view only, and cannot open internal screens.
    • Masks explained in the room. Each withheld line names its reason, so the auditor's trust rests on something they can check.
  8. 08Responses

    Audit response letter drafted finding by finding, with repeats on one CAPA

    • The report read into findings. Each observation gets its number, grade and due date from the client's agreement, ready for a response.
    • One finding, one CAPA, every client. A finding another client or FDA already raised links to the CAPA already open, so every client hears the same answer.
    • Prepared by the liaison, signed by QA. Each response is prepared by the liaison who owns that client and signed by the QA head before it reaches the client's portal.

The host runs the room, QA writes the summary, a second reviewer releases

Four people between an auditor's request and the record that reaches the room.

QA compliance leads

Host each client audit, log every request and keep its clock

  • Requests pre-pulled from the plan
  • A verdict on each record before it is named
  • Questions answered before the auditor asks
Plant QA heads

Write and sign each disclosure summary and each audit response

  • Drafts built from the cited records
  • Rulings that become the house standard
  • Mask removals that wait for them
QA request reviewers

Read each record as the auditor will see it, then release or send back

  • The exact copy, summary included
  • A release withdrawn by any later change
  • No record they pulled themselves
Client quality liaisons

Own findings, responses and commitments for each client

  • Reports read into findings
  • Repeat findings linked to one CAPA
  • Commitments with dates and owners

The wall checker cites a clause for each mask and can lift none of them

From the plan to the response, the agents draft and check; QA people sign, release and send.

Request clerk

Logs each request, starts its clock, assigns a retriever and a reviewer, and keeps the record of what was shown.

  • Releases nothing
Plan reader

Reads the audit plan, the agreement's audit clause and the client's past audits, and proposes pre-pulls.

  • Shows nothing to the auditor
Record puller

Finds each record in the logbook, QMS, LIMS, eBR and document system, with its linked records.

  • Changes no record
  • Widens no request without a person
Wall checker

Marks other clients' products, batches, people, prices and process settings, cites each mask, and flags what needs a summary.

  • Removes no mask
  • Writes no summary
Challenger

Asks what this client's auditor would ask of the walled record, including of the agents' own work.

  • Answers nothing on the QA head's behalf
Summary writer

Drafts each disclosure summary from the cited records.

  • Sends nothing
  • Names no other client or product
Response writer

Reads a client's report into findings, drafts responses with CAPA and evidence, and links repeat findings.

  • Sends no response
  • Opens no CAPA

A low nitrogen pressure note was hidden inside another client's entry

An equipment note inside a masked entry

Masked with another client's production run, the note would have left the client unable to learn why a work request was raised.

A cleaning limit the client could not check

With the previous product masked, the limit's basis is shown as a number and its calculation, without the product's name.

Recovered solvent from another client's process

Asked whether recovered solvent from another process reached the client's product, the answer went into a signed summary.

A repeat finding answered twice

A client's finding matched another client's open CAPA, so the draft links to it instead of opening a second one.

More screens

One request ran past its clock: FDA's inspection outcome, at 58 minutes

Around the dryer log: the day's requests, the earlier questions, the rulings, promises per client, the trail and the settings.

The request that ran longAll of the day's requests with clock, retriever, reviewer, verdict and state; the record of what was shown exports from here.
Earlier records held to the same questionsQuestions raised on the dryer log and on the day's earlier records, each answered with its source or fixed.
A ruling on process settings, awaiting approvalThe plant QA head's past rulings on what a client may see, and a proposed rule that applies only once approved.
Promises by client, with owners and datesCommitments from each audit response by plant, finding, due date, state and owner, with the CAPAs that link findings across clients.
Each mask, summary and release in the trailWho did what, when and why, the stated meaning of each signature, and its session; client exports leave out the internal view under a mask.
Clocks that change only under the QA headRequest and summary clocks, the auditor's copy rules, the pre-pull window, wall rules per client, residency, retention and separation of duties.

demoSample data, from the working solution.

Read from the logbook, the QMS, LIMS and each client's agreement

Equipment use and cleaning logbooksEach shared item's entries, with product, batch, cleaning and result against its limit.
Deviations, CAPA and change controlFrom the QMS, including deviations on shared equipment that need a summary.
Laboratory results and batch recordsLIMS results and eBR records for the client's own batches.
Quality agreementsEach client's audit, disclosure and response clauses, cited on the masks.
Audit plans and past auditsWhat each client asked last time and how the QA head ruled.

What CDMO quality teams ask about customer audit hosting

What is a customer audit at a contract manufacturer?

A customer audit is a client's own GMP audit of the contract manufacturer that makes its product, a right ICH Q7 says the contract should give the contract giver. Here agents pull each requested record, mask what belongs to other clients, each mask citing its clause, and a second QA person releases exactly what the auditor sees.

What may a client see on a shared equipment record?

Its own runs, the cleanings before and after them, results against limits, dates and equipment status. Another client's product, batch, people, prices and process settings are masked, each with the clause that withholds it; FDA's guidance on quality agreements asks the agreement to say what a facility serving several owners reports to each about audit and inspection findings.

What happens with a deviation on shared equipment?

It is summarized rather than withheld. The QA head reads the records and signs wording that says what happened and what the client will be told, without naming whose batch it was.

Can a mask be removed?

A mask that hides another client's product or batch stays. A host-added or process-setting mask comes off only with the plant QA head's signature, and the record leaves the audit room until it is read and released again.

How does it help with the audit response letter?

The client's report is read into findings with grade and due date, responses are drafted with CAPA and evidence, and a finding another client or FDA already raised links to the CAPA already open. The liaison for that client prepares it; the QA head signs.

Does it run both the front room and the back room?

Yes. The host logs each request as the auditor says it, the back room retrieves, the agents mask and question each record, and the reviewer releases. The request log shows each clock, and the day's record of what was shown exports for both sides.

Walk one shared logbook page
through a client audit.

See a shared dryer's log page masked, summarized and released on sample data, then map it to your own quality agreements.