Own the strategy, re-check hazards, decide on gaps and author revisions
- Each control beside its newest record
- Interventions counted by access point
- Revisions drafted with a source per line
A contamination control strategy drawn as one bowtie per hazard, with each control re-checked against its records the day a new record touches it.
See one glove hazard re-checked, screen by screen ↓A sterile plant's strategy is written by a team led by QA, approved, and read again at the annual review. The proof behind each control lives somewhere else: glove test logs on the filling line, plates in the environmental monitoring system, the simulation protocol in validation, deviations and change controls in the QMS, training in the learning system. Between reviews, nobody reads the strategy against them.
So the text and the floor drift apart. Operators start making a routine refill through a second glove port, one the last simulation used only for other work. A sporicide schedule changes without anyone checking it against the strategy, and a sentence keeps promising a test that is still only planned. An inspector reading the batch records can find it first, and so can the client's auditor.
Built forSterility assurance leadsQA headsEnvironmental monitoring specialistsValidation engineers
The strategy gets one careful reading a year, while the glove logs, plates and batch records behind it change daily.
Read side by side once a year
Built-in controls
An inspector or a client's auditor reads a strategy that matches the plant on the day they open it.
Five new records touch an isolator's glove hazard. The sterility assurance lead re-checks it, finds a refill port no simulation covered, decides, and sends the revised strategy to the QA head.
demoThis isolator and its plant, people and numbers are sample data.
The lead owns the strategy, the QA head signs every change to it, and specialists answer their own points.
Own the strategy, re-check hazards, decide on gaps and author revisions
Approve revisions, amendments, rules and settings; assess batches under deviation
Read plates and answer pattern questions about monitoring points
Own the simulation protocol and draft its amendments
Each control points at the system that holds its proof, and each status names the record it came from.
The rest of the strategy, read from the same links as the bowtie.
demoSample data, from the working solution.
Each agent hands its sources to the next, and the sterility assurance lead reads the result before deciding.
Finds new records that touch a control and queues the hazard for its owner.
Links each control to the records that prove it, with the passage each link rests on.
Reads each record against the strategy text and marks the control clean, stale, open or contradicted.
Counts interventions by type and port in batch records against the authorized list and the simulation protocol.
Drafts the revision and the annual review, citing a record for each statement.
Questions the bowtie, and the drafter's own text, as an inspector would.
Each signer opens a named record first; the signature records what it means.
A contamination control strategy is the documented set of controls a sterile plant relies on against contamination. EU GMP Annex 1 asks that it define critical control points, assess how well every control works and be actively reviewed. Here each hazard is a bowtie, and each control is re-checked against its records whenever a new one touches it.
Annex 1 lists the elements to weigh, from design, premises and personnel to utilities, materials, vendors, validation, cleaning, monitoring and continuous improvement. Changes are assessed against the strategy, and its effectiveness feeds management review.
Annex 1 asks the aseptic process simulation to include routine interventions in a manner and frequency similar to routine work. The agents count each intervention in the batch records by type and access point and set it beside the protocol, citing the line; whether the number per run is enough stays the validation engineer's call.
The QA head, under a deviation that lists every batch in the window by where it stands; Annex 1 asks that such an intervention be considered during batch disposition. The client's qualified person makes the market release decision for its batches, and the notice telling the client goes out under the QA head's signature.
A re-check falls due five business days after a new record touches a control, and within one business day for a Grade A record. Each kind of evidence also goes stale on its own window, and a new window takes effect only once the QA head signs.
Packages reach the client already checked the way the client's own reviewer checks them, so its release is not held up by send-backs.
1-min demoDeviation Reporting & ClassificationEvery report heard in the operator's own words, contained at once, classified by QA the same day.
1-min demoDeviation Impact AssessmentEvery batch that shares a cause is found, held or cleared the same day, and the client hears first.
1-min demoShare one hazard's controls with its glove test log, a month of batch records and the last simulation protocol, and we can show which controls the records still prove.