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
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 ↓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
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
Built-in controls
Each client leaves trusting how its own data, and its neighbors', were handled.
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.
Four people between an auditor's request and the record that reaches the room.
Host each client audit, log every request and keep its clock
Write and sign each disclosure summary and each audit response
Read each record as the auditor will see it, then release or send back
Own findings, responses and commitments for each client
From the plan to the response, the agents draft and check; QA people sign, release and send.
Logs each request, starts its clock, assigns a retriever and a reviewer, and keeps the record of what was shown.
Reads the audit plan, the agreement's audit clause and the client's past audits, and proposes pre-pulls.
Finds each record in the logbook, QMS, LIMS, eBR and document system, with its linked records.
Marks other clients' products, batches, people, prices and process settings, cites each mask, and flags what needs a summary.
Asks what this client's auditor would ask of the walled record, including of the agents' own work.
Drafts each disclosure summary from the cited records.
Reads a client's report into findings, drafts responses with CAPA and evidence, and links repeat findings.
Masked with another client's production run, the note would have left the client unable to learn why a work request was raised.
With the previous product masked, the limit's basis is shown as a number and its calculation, without the product's name.
Asked whether recovered solvent from another process reached the client's product, the answer went into a signed summary.
A client's finding matched another client's open CAPA, so the draft links to it instead of opening a second one.
Around the dryer log: the day's requests, the earlier questions, the rulings, promises per client, the trail and the settings.
demoSample data, from the working solution.
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.
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.
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.
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.
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.
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.
Answers an auditor can verify on site, and past answers kept true for each client.
1-min demoCDMO Project Tracking & Status ReportsThe client sees each week what waits on it, and a late answer is caught while the date can still be saved.
1-min demoTechnology Transfer Gap AnalysisClient products reach PPQ sooner, with every gap closed by evidence.
1-min demoSee a shared dryer's log page masked, summarized and released on sample data, then map it to your own quality agreements.