Take each investigation to a signed root cause before its clock runs out
- The method fitted to the event, with its reason
- Each bone read against its own records
- The inspector's questions answered on the page
Root cause analysis that fits the method to the event, proves or rules out every fishbone cause from a cited record, and runs each proved cause down to the system that let it happen.
Follow one granulator investigation from method to approval ↓An investigator has a fixed clock to say why a batch left its validated range, and an inspector will read the answer. The method is whichever one that investigator knows best, the fishbone is drawn in a meeting, and the minutes call a cause ruled out with nothing on file to show why.
The work ends at the first physical cause. The seal was worn, so the seal was replaced. Nobody asks what let a weeping seal stay in service, or why a software update moved the high-torque alarm past what was validated, while the granulator next door carries the same limit.
Built forQA investigatorsProcess engineersQA investigation approversHeads of quality
A cause cleared in a meeting has nothing on file behind it, and an investigation that ends at the worn part lets the failure come back.
Pulled by hand, case by case
Built-in controls
Root causes that have already met the inspector's questions, with a record behind every cause ruled in or out.
A QA investigator works one wet-massing torque excursion on a high-shear granulator through each method, while the approver and engineering work on the same record.
demoEverything on these screens, from the plant and its clients to each person, batch and reading, is sample data.
The investigator works the case, engineering confirms what the readings mean, a separate approver checks it for QA, and the quality head owns the rules.
Take each investigation to a signed root cause before its clock runs out
Approve each root cause after reading the records behind it
Answer the process and equipment questions the bone readers raise
Own the method rules and approve what the agents learn from rulings
Each person signs under their own ID and password, with what the signature means and why.
Around the fishbone: what was cleared and by which record, the seal's history, the open investigations, the rules taken from rulings and the signatures.
demoSample data, from the working solution.
A recipe import during a software update moved the high-torque alarm from 340 to 380 N·m, and the change control had compared screens and reports only.
Both earlier deviations on the granulator ended at the seal, while the plan had no run-hour trigger and let a weeping seal run with the purge raised.
The binder lot was cleared by the same lot running in range on two other batches, with the certificate of analysis as the second record.
Signed batch record steps with second-person checks and the operator's requalification ruled out a slip, which EU GMP Chapter 1 requires before concluding human error.
demoSample data, from the working solution.
Each agent proposes from the GMP records it reads; the investigator and QA decide.
Reads the event's features and suggests the method or methods that fit, with the reason.
One per bone, each reads its own records and proves, rules out or keeps open each candidate with a cited passage.
Checks that the surviving causes explain each fact on the timeline and in the Is/Is-Not.
Runs a five-why from each proved cause to a system cause and builds the fault tree.
Argues as an inspector would against each draft, including the agents' own first one.
Writes structured requests to the supplier, maintenance and process engineering, and reads the replies.
Root cause analysis finds why a deviation happened, down to the cause that stops it returning once it is fixed. Here the method is chosen for the event, each candidate cause on the fishbone is proved or ruled out by a cited record, and a five-why carries each proved cause to the system that let it happen.
Is/Is-Not with problem analysis fits a sudden change on one asset where a comparison exists. A fault tree fits a protective layer that failed to act, FMEA a weakness across steps, products or a transfer, and a five-why a simple single cause, or a proved cause that still needs its system cause.
Only by a record. A setting that requires a cited record for each ruled-out cause is locked on, and a cleared cause remains on its bone, struck through beside that record, so a reader of the report sees what cleared it.
Not until the process, the procedure and the system around the operator have each been cleared by records, as the EU GMP guide asks. The people bone is read from the signed batch record steps and the training record, and no why-chain ends on retraining.
Agents open the batch record, historian, maintenance, calibration and change records bone by bone, a challenger questions the draft, and a cause test refuses a root cause that leaves a fact unexplained.
Requests go out in fixed fields, such as the retained sample's K-value and water, and only those fields can move a bone. A free-text note waits for the investigator, and nothing reaches an outside party unless the investigator sends it.
Plans that remove the cause from the system, with the test of success written before the work starts.
1-min demoCAPA Tracking & EscalationNo CAPA quietly drifts past its date: every slip is justified, signed and seen.
1-min demoCAPA Effectiveness CheckEvery CAPA verdict an inspector can follow, from the locked criterion to the batch record.
1-min demoSend one closed investigation with its batch record, historian data and work orders, and we will read each bone against its records.