Deviation and quality event management

0:00 The problem: one deviation, scattered everywhere

On a line, in a lab, or in a clinic, something goes wrong some days. The write-up is called a deviation, and it must be investigated and closed. The trouble is where it lives: paper forms and logbooks, spreadsheets and lists, e-mail and chat, a shared drive, and the old system nobody fully trusts. Something went wrong on batch twenty-four, one-seventeen. What was done about it, and is it closed?

0:26 One list for every deviation

Complere keeps every deviation in one list, and each row shows how far it has come. It calls them quality events.

0:36 One example: DEV-1, rated on a ready-made severity scale

Here is one; its ID is DEV-1. Batch 24-117 was a test run: broth instead of medicine, to prove the line stays sterile. Two vials turned cloudy: germs had grown in them. Luis Herrera reported it, with the batch, the room, and how serious it is: High, Major, so the next batch waits. That rating comes from a seven-level scale that ships ready to use, from negligible to catastrophic.

1:04 Where it started: a ready form

Luis didn't start from a blank page. The deviation template filled in the ID, the fields to record, who signs, and the deadline. Each kind of event gets its own template: set it up once, and every event of that kind starts the same way.

1:22 Set steps, a signer for each, and a time limit

In regulated work, each step needs a named person's sign-off before it moves on. So DEV-1 was logged, then investigated, then checked, then signed off by quality, and finally closed, each step with its own signer and time limit. Marcus Chen, who runs the case, signed first to open the investigation: which germ it was, the room's cleanliness records, and the gowning log.

1:47 What caused it: the built-in cause library

Amara Diallo, the investigator, picked the cause from a library that comes ready to use: seventeen categories and more than a hundred common causes, from human error to supplier issues. You decide which teams see them, and you add your own beside them. Everyone uses the same list, so you can see which problems keep coming back. DEV-1 was filed under Environment, where the germ turned up.

2:13 Why it happened: evidence, 5 Whys and a second check

Then she checked the evidence. The germ in the vials matched one found on a gown: a skin germ. She asked why, five times. Why on the gown? The operator had adjusted their goggles after putting gloves on. Why? The gowning steps never set that order, and nobody checked. She wrote down what it meant for other batches, and signed. Marcus Chen checked her work and signed: cause confirmed, a fix raised and linked, and a stop-gap in the meantime, with a second person checking the gowning before anyone goes in.

2:49 What it set in motion: linked records and where each stands

The fix became its own record, and so did everything it started. Each shows its status today. The corrective action, the plan to stop it happening again, has its tasks done, and the check that they worked is still open. The gowning procedure was rewritten. Of the two people trained on it, Luis has finished and Jake has not yet, so the training stays open. A risk assessment is under review. Each one links back to DEV-1.

3:17 Signed with a password, closed by quality

Nothing moves on until the named person signs with their password, and the record keeps their name, role and the time. Grace Kim, from the quality team, closed it on the second of October, with her reason on the record: cause confirmed, the fix tracked under the linked corrective action.

3:38 Every step kept: the audit trail

Every step is kept: who, when, and the note they signed with. That history is the audit trail, and it exports. Even retiring a closed deviation takes another signature and a written reason.

3:53 The answer, and what an inspector checks

The answer: the cause was the order of goggles and gloves. Amara Diallo investigated, Marcus Chen confirmed it, Grace Kim closed it on the second of October. Anything still open, like Jake's training, stays on the record with its status. Recorded and rated. Investigated to the cause. Impact assessed. Closed by quality. Every step recorded, every sign-off signed. A deadline on the record, the corrective action linked. Deviation handling you can show an inspector. See how one connected record can anchor your whole quality system. Request a demo.