SystemQuality Operations & CAPA

Deviation & CAPA Trending

Deviation trending that reads what each deviation says, groups the same event across lines whatever category it was filed under, tells real rises from noise and logging changes, and drafts the council pack with a source on every sentence.

See nine line-clearance events become one recurrence ↓
Watch with transcript →
The problem

Labels left on four packaging lines were filed as three different causes

Each month the trend analyst exports the deviation register into a spreadsheet and charts it by the cause category the investigator typed. A label left on a packaging line is filed as human error on one line, equipment on another and procedure on a third, so the chart shows three small bars and no pattern.

Small counts make every month look like news, and a new logging rule looks like a real rise. The council reads the charts, minutes an action or two, and the same event closes as operator error, retrained, on the next line.

Built forHeads of quality operationsQA trend analystsQuality council chairsSite quality heads

The Problem Today

Trend charts count deviations by the category typed, so one event filed three ways on four lines never adds up.

Built by hand every month

  • Exports
  • Charts
  • Repeat box
  • Slides
  • Noise reads as newsSmall counts and new logging rules look like rises
  • Retraining on repeatThe same event closes the same way, line after line

The Solution

  1. Grouped by what happenedEach deviation placed by what it says; its color stays the category filed
  2. Each change testedRates per thousand batches: a real change, small-count noise or a logging change
  3. The chair's questions firstA challenger asks what the council would, the agents' own draft included
  4. A person acceptsAfter reading the records; the chair approves a pack sourced line by line

Built-in controls

  • No council item without a person's signature
  • Preparer and approver are different people
  • Each client sees its own products only

What You Get

The council stops reading category charts and decides on named recurrences, each with an owner who has already agreed.

  • Caught while still smallA pattern named while each event was still found by the plant's own checks
  • Plants compared by what happenedAll plants' deviations read on one map, whatever the category
  • A new analyst asks the chair's questionsThe challenger asks them before the council meets
Features

Deviation trending features, from the meaning map to a council action

The head of quality operations prepares the monthly council on ten months of deviations from four plants, the day before the pack locks.

demoPlants, lines, clients, people and counts here are all sample data.

  1. 01Meaning map

    Deviation trending by what each event describes, across plants and lines

    • Placed by description and investigation. Events that say the same thing sit together, so a recurrence shows even when investigators filed it differently.
    • Color keeps the category filed. A group of mixed colors is exactly the recurrence a category chart cannot show, visible to quality operations at a glance.
    • Groups labeled in plain words. The council reads labels such as cleaning hold times and records instead of category codes.
  2. 02Logging check

    Real rise or reporting change, checked against the procedure history

    • Logging rules checked by date. A rise that began the week a procedure changed what gets logged is named as a reporting change, so the council spends no meeting on it.
    • The record opened from the answer. The analyst reads the revision itself, and the open is logged as read.
  3. 03Records

    Recurring deviations across lines read side by side as one sheet

    • All member records on one sheet. The head of quality operations reads what each event said before deciding whether they are one recurrence.
    • Closure causes in view. Seeing the same closure cause beside the same event on four lines tells the council where retraining has not worked.
  4. 04Accepted

    A recurrence accepted for the council, signed after reading its records

    • Repeats by meaning against repeats marked. The gap between what investigators marked and what actually recurred is shown for each group.
    • Signed acceptance, with what it means. A group becomes a council item only when a person signs it, and the signature says what was accepted.
    • Withdrawn the same way. Taking an item back needs a signed reason, and it clears the pack's signatures.
  5. 05Trends

    Deviation trend report per thousand batches, each move tested

    • Rates on a signed denominator. Deviations are counted per thousand batches made under a signed definition, so a busy month is not read as a worse one.
    • Real change, noise or logging change. Each line says which it is and how it was tested, so the council argues about real movements only.
    • Repeat deviation rate by meaning. Recurrence is counted by what happened beside the investigators' repeat box, a measure the council can defend.
  6. 06Chair's questions

    CAPA trend analysis questioned as the council chair would, before the meeting

    • Questions asked of every finding. The analyst arrives with the chair's questions answered, each with its source.
    • The agents' draft questioned too. A summary that quoted the repeat box while page three counted by meaning was rewritten before anyone read it.
    • Judgments sent to the person who owns them. Whether a plant's closure causes stand goes to that plant's site quality head, and the pack waits.
  7. 07Council pack

    Quality council pack for management review, each sentence with its source

    • Five pages drafted, every sentence sourced. An inspector reading the management review can trace each statement to its record.
    • Preparation blocked until a question is answered. The pack cannot be prepared while a site quality head still owes the chair an answer.
    • Preparer and approver read all pages. Two different people sign, and a change after either signature clears both.
  8. 08Council action

    CAPA trend report turned into a council action with an agreed owner

    • The action drafted from the recurrence. The council sees a concrete action tied to the records, where the events happened.
    • The owner asked before the meeting. The packaging manager agrees or declines in advance, so the council decides with the owner's answer in hand.

Each site quality head answers for their plant before the council sees it

Quality operations decides what reaches the council, the analyst runs the month, and the chair approves the pack.

Heads of quality operations

Own the monthly council pack and decide which groups become council items

  • Recurrences across lines, named and sourced
  • The records behind each group on one sheet
  • A pack that holds until questions are answered
QA trend analysts

Run the month, keep watched groups and prepare client summaries

  • Rates and tests computed from the registers
  • Logging changes separated from real rises
  • The chair's questions answered in advance
Quality council chairs

Approve the council pack, learned rules and looser settings

  • Decisions on named recurrences with owners
  • A source behind every sentence
  • Rules that apply only after their signature
Site quality heads

Answer the chair's questions about their plant before the council

  • Their plant's month on the network's measures
  • Questions on their investigations in advance
  • Groups at their plant with their state

Nine events closed as retraining were one recurrence on four lines

One event, three categories, four lines

Nine line-clearance events filed as 7 human error, 1 equipment and 1 procedure; retraining closed 7 of them, and investigators marked 1 of the 8 repeats.

A fivefold rise that was a logging rule

One plant's documentation count went from 2.5 to 13.7 a month after a procedure revision began logging minor entries; without them it is 2.7.

A summary sentence from the wrong count

The draft quoted recurrence at 23% from the repeat box while its own page three counted 58% by meaning; the drafter rewrote it.

Overdue CAPAs that only looked worse

14 of 138 open CAPAs past due against an average of 10.4; count test p = 0.17, so the line says watch.

demoSample data, from the working solution.

More screens

Nine of the fifteen groups hold more than one filed category

Behind the map: the list of groups and the register, one plant's month, the groups the council watches, the settings and the trail.

Every group, with how it was filedEach group the clusterer proposed, with events, plants, the mix of categories filed and its state; the full register of 1,212 deviations sits one tab away.
One plant's month, and the question it owesThe site quality head sees the month per 1,000 batches made, the plant council date, groups at the plant and the chair's question waiting for an answer.
Groups the council watches, month by monthLabels the council accepted before are counted again each month, and a rule learned from last month's ruling waits for the chair.
Settings the chair must sign to loosenLook-back, when a change counts as real, smallest group, denominator, council and lock times, retention and sources; looser changes wait for the chair.
Agents and people on one trailEach step of the run and the signed acceptance by quality operations, with the reason, signature meaning, record and session.

demoSample data, from the working solution.

A CAPA owner agrees or declines before the council ever sees the action

Head of quality operations
Sees
Each group's member records, its category mix and the chair's question
Signs
Accepts or withdraws council items, prepares the pack, releases client summaries
Head of quality, council chair
Sees
All five pages and the records behind each new item
Signs
Approves the pack, learned rules and any looser setting
Site quality head
Sees
The chair's question about the plant's own investigations
Signs
Answers whether the closure causes stand
CAPA owner
Sees
The proposed action and the records it rests on
Signs
Agrees or declines before the council meets
QA trend analyst
Sees
The month's run, the watched groups and each client's lines
Signs
Prepares each client's summary for release

Procedure revisions show when a rise is only a change in what gets logged

Deviation registerDescriptions, investigations, filed categories, lines, shifts and closure causes from the QMS.
CAPA registerOpen CAPAs, due dates and states at each month end.
ERP batch countsBatches made under the signed definition, bulk and packaging orders, by plant and month.
Procedure revision historyWhich revision changed what gets logged, and from which date, at each plant.
Council minutesEarlier rulings, accepted labels and actions with their owners.

What quality councils ask about deviation trending

What is deviation trending?

Deviation trending is the monthly review of deviations and CAPAs for patterns a quality council should act on. Here the deviation trending groups events by what they describe across plants, tests whether each change is real, and drafts the council pack with a source on every sentence.

How is a real rise told apart from a reporting change?

The trend reader checks when the rise began against the procedure revision history. A rise that starts the week a revision began logging new entries is shown with and without those entries, and named a reporting change.

Do the agents change a deviation's category?

No. Filed categories, records and CAPAs are left as they are. The map keeps each event's filed category as its color, and the group sits beside it.

Who decides what reaches the quality council?

The head of quality operations accepts a group as a council item after reading its records, and the council chair approves the pack. The preparer and approver are different people.

Does this support management review under ICH Q10?

It drafts the pack that management review reads, with process performance, recurrence and CAPA measures, each sentence sourced. The council still reviews and decides.

What does a client see?

Each client gets a summary of its own products only, prepared by the trend analyst; the head of quality operations releases it. A person at the plant answers each client question; the question alone changes nothing.

Why count deviations per thousand batches made?

A busy month makes more deviations without the plant getting worse. Each month is counted against the batches made under a signed definition, bulk and packaging orders included, and a count test says whether a move is real or noise from small numbers.

Send us ten months
of deviations.

Send a deviation register and its batch counts, and the map will show which events recur across lines whatever they were filed as.