Solutions · By role

Deviations on record the day they are raised.

Deviations get written up from memory, CAPAs close without a cause and critical steps go unmarked. Each one costs a slipped batch, a second lot or a held run.

The deviation raised on the CDMO call

“A deviation came up on the weekly CDMO call and was written up days later from memory. By then the batch it hit had slipped, and the work order behind it was at risk before finance heard.”

What usually happens

The deviation lives in meeting notes until someone opens a form in the quality system, and the CDMO tracker and contracts sit somewhere else.

What SI 42 does

  1. 1An agent drafts the call's next steps.
  2. 2A next step about the problem goes to the quality events register as a deviation candidate linked to the meeting, and goes no further until a person confirms it; a next step that names the CDMO arrives in the CDMO board to accept as a commitment.
  3. 3When a batch is at risk, the CDMO board adds up the signed agreements linked to that batch or its program.

The outcome

A deviation candidate is ready the day it is raised and becomes a record when approved, and you can see what money depends on the batch it hit.

CDMO callDeviationCommitmentBatchWork orderYouwritten up latefix owed by CDMOneed-by datevalue at riskraised next callCDMO callDeviationCommitmentBatchWork orderYou
Breaks todaywritten up lateYouconfirms the deviation and accepts the commitment

The CAPA closed without a root cause

“A supplier lot failed incoming checks. The CAPA was closed with no root cause, the same material failed again, and we paid for a second lot we could not use.”

What usually happens

A spreadsheet lets anyone mark a CAPA closed, and the supplier hears about it in an email nobody reviewed.

What SI 42 does

  1. 1In SI 42 a CAPA cannot close without a root cause and a corrective action, and nothing closes without a named approver; the close form lists what is missing.
  2. 2The supplier board scores each supplier on delivery, price variance and rejection rate, so repeat rejections show before the next order.
  3. 3An agent drafts the email asking the supplier for its corrective action, and it passes a buyer review and a second approval before it goes.

The outcome

A closed CAPA has its root cause and action, and the supplier's score shows the problem before you reorder.

Incoming checkCAPARoot causeSupplierPurchase orderYouclosedwithout causefailure loggedaction requestedscore beforereordernext lot arrivesIncomingcheckCAPARoot causeSupplierPurchaseorderYou
Breaks todayclosed without causeYouapproves the CAPA close and the supplier email

The critical step nobody could confirm

“A critical step needed a supervisor, nobody running the batch knew which step it was, and the batch was held while its materials sat on the shelf.”

What usually happens

Steps are printed from a document, and run notes and yields are written up afterwards.

What SI 42 does

  1. 1SI 42 keeps the steps for each product version, marks the critical control points that need a supervisor, records the run and any deviation raised, and flags low yield.
  2. 2The costing board holds each product formula's cost at its batch size, in the same app, so the team can weigh a low-yield run against what the batch cost.
  3. 3An agent drafts the low-yield flag; a person decides what happens to the batch.

The outcome

Everyone running the batch sees which steps need a supervisor, and a low-yield run is flagged with its cost in view.

Product versionCritical stepRun logYieldBatch costYoucritical steps unmarkedsupervisorstep markedrecorded per runlow yield flaggedprice reviewedProductversionCriticalstepRun logYieldBatch costYou
Breaks todaycritical steps unmarkedYoudecides on a flagged batch

Related

See a deviation drafted from your next meeting.