Deviation, CAPA & Change-Control AI Agent

What this agent does

Assembles the event, never closes it

A deviation is raised, and the batch record, the equipment history and the events before it are pulled in.

An event is normalised across the quality, manufacturing and laboratory systems, each fact carried with its source.

Reason

A discovery time is entered by a person: when the information arrived, not when the record was opened.

A clock runs from that time — 3 working days under 21 CFR 314.81(b)(1), 45 calendar days under 21 CFR 600.14.

A scope is drawn past the batch that failed, to other batches and other products, as 21 CFR 211.192 requires.

Decide

A recurrence search runs on event signature rather than free text, so a third occurrence reads as a third.

A CAPA carries the effectiveness metric and window your own procedure states, and the evidence behind it.

Out

A change is read against the registered dossier, and what it may need filed is put in front of the reviewer.

Writes run only inside the approval boundaries agreed at implementation, and never onto an approved record.

→ Product statement

The agent assembles and makes no GMP determination; a named quality unit approves or rejects, and a named person signs the reportability decision.

Example workflow

One event, discovery to approval

AgentHuman

1Event raisedLine record, laboratory result, complaint, excursion or contract-site notice

2Evidence assembledBatch records, equipment history, prior events and the entered discovery time, each with its source

3Assessment draftedScope and impact, candidate causes, CAPA draft, clock status and confidence

4Controls appliedCompleteness checks, 21 CFR 211.192 scope checks, clock checks and confidence threshold

No human action required

Stages 1 to 4 run unaided, and nothing is closed at any of them — the agent is assembling, and the quality unit's lane opens at the confidence gate.

5DecisionBranches at the confidence threshold

High confidence

Goes to the quality unit to approve.

Low confidence

Adds a second investigator read first.

Quality-unit approval

The event is held with its evidence, its open questions and the confidence.

Approve · Amend · Send to second review

Approved — closure authorised▼

6Quality system updatedOnly where write access and approval policy allow it

7Outcome evaluatedInvestigation completeness, effectiveness-check outcomes, days to report and inspection findings

Reopenings

A closure reopened lands on the quality unit's record, and on the file inspected later.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required8 items

Closing the deviation or approving the investigation.

Determining that an event is reportable.

Signing or passing an effectiveness check.

Setting the discovery time the clock runs from.

Automation boundaryAgent acts unaided

✓Assemble the event record and the evidence behind it.

✓Run both reportability clocks from the entered time.

✓Search prior events by signature, not by title.

✓Test the pack for completeness and hold it for the quality unit.

Writes stay inside the boundaries set at implementation, and never onto an approved record.

Assigning the filing category for a change.

Naming human error as the cause of an event.

Notifying responsible officials under 21 CFR 211.180(f).

Changes to investigation, CAPA or approval rules.

Example output

One event, annotated

Everything the agent assembles is attached to the record it was drawn from.

Quality-event output · single deviationIllustrative example

Event

Assembled line

Rule cited

Source of time

Confidence

Clock

Filling-line stoppage

A stoppage on this line was recorded twice before under other names

21 CFR 211.192

Operator-entered

88%

Runs from the entered time

As receivedTaken from the quality, manufacturing and laboratory systems — nothing on this side is written by the agent.

Evidence used Prior events on the line Equipment history Batch record page

Why this ruleIt is the scope the US rule sets, and how far it reaches is still the quality unit's call.

ActionApproveAmendSend to second review

What the score decidesBelow the configured threshold the event picks up a second investigator read before it goes up.

Value

Where AI adds value

The same four claims, placed at the point in the workflow where each one applies.

Where the value landsValue 01 – 04

Every eventFrom the quality record

03Assembly

Take what the laboratory hands over

The out-of-specification page works the result; this one starts where the event, the clock and the CAPA begin.

01Approved path

The clock starts at discovery

Not at record creation. A missed date is a dateable violation, and no later investigation repairs it.

02Human review

Recurrence, not throughput

No regulator publishes a deviation cycle time or a CAPA backlog figure, and we will not borrow a vendor one.

04Build an evidence trail

The event, the threshold it was read against and the officer who reported stay on the file.

Integrations

Typical integrations

Five system groups connect to the same agent. Which of them are in scope is decided in discovery.

Quality managementVeeva Vault QMS · TrackWise
MasterControl · ETQ Reliance

Manufacturing executionWerum PAS-X · Syncade
Tulip · Rockwell PharmaSuite

Laboratory systemsLabWare · STARLIMS
Empower · LabVantage

Agent

Deviation, CAPA & change

Reads the event
Assembles the pack
Holds for approval

Regulatory and recordsVeeva Vault RIM
Document control · archive

Observability & evaluationOpenTelemetry · Langfuse
Supported monitoring/evaluation sources

Integration availability depends on the client's existing systems and API access.

Agent controls

Six layers between the model and the record

The six are read from the outside in. What none of them stops is set out in the map below.

L6 · Outermost — last line of defenceInward → L1 · closest to the model

L6Rollback / safe modeHold assembly at evidence-only when evaluation or production signals degrade.Roll back

L5Version monitoringTrack model, prompt, clock-rule and procedure-mapping changes.Track

L4Event traceabilityRecord the sources, the pack, the amendments and the approval time.Record

L3Quality-unit approvalHold events for the named quality unit; the gate governs release, not whether the closure is sound.Gate

L2Policy guardrailsTest packs against completeness, scope and clock rules; a failure returns the pack and does not judge the cause.Restrict

L1Confidence thresholdsRoute low-confidence events to a second investigator read before the quality unit sees them.Require review

Model coreEvent assembled — scope, candidate causes, CAPA draft, clock status and confidence

L1 – L2Test whether a pack may stand

L3Puts the closure in the quality unit's hands

L4 – L5Keep the event and the reportability line behind it

L6Reverts to evidence assembly when signals degrade

How Nestack evaluates it

Evaluate the assembly workflow — not only the closed record.

Coverage runs the whole depth of the workflow, and every layer is cut by slice.

Surface — the record an inspector reads

Depth of coverage ▼

E1Final-output evaluationDid the pack carry the scope, the evidence and the clock status?

E2Step-level evaluationDid the agent use the right event, the right scope rule and the current procedure?

E3Tool evaluationDid it read and write the correct event and the correct field?

E4Confidence calibrationDo low-confidence events actually attract more quality-unit amendments?

E5Slice evaluationHow does performance change across specific event classes?

E6Business outcomeHow many events were reopened, and how many effectiveness checks failed?

Floor — the outcome the site answers for

Failure modes

Where each failure originates in the agent

Seven failure modes, each placed at the stage where it originates.

Agent lifecycleDirection of processing →

01 · Retrieval1 mode

EH-03

Prior events missed

The recurrence search never reached the earlier two.

Stage gathersBatch records, equipment history and prior events

02 · Reasoning2 modes

EH-04

Scope stops at the batch

Other products the failure touched are left out.

EH-06

Cause named as human error

Process and system causes are not excluded in writing.

Stage proposesScope, causes, CAPA draft, clock and confidence

03 · Tool / write2 modes

EH-02

Clock started at creation

Days are counted from the record, not the discovery.

EH-05

Effectiveness window early

The check runs before the batches exist to support it.

Stage writesOnly where write access and approval policy allow it

04 · Output1 mode

EH-01

Change filed nowhere

A change needed a variation and got none.

Stage returnsThe record the quality unit approves and FDA reads

05 · Change / Version1 mode

EH-07

Silent scope regression

A model or rule change narrows what is investigated.

Stage tracksModel, prompt, clock rules and procedure mapping

Sev-1 · acts on an approved record Sev-2 · a report misses its statutory date Sev-3 · evidence degrades, event holds

See the complete Biotechnology failure-mode catalogue →

Affected slices

One event class can carry most of the failures

A site-level investigation-closure rate can look settled while a few event classes absorb most of the reopenings and the late reports. Nestack reports the reopening rate by event class, not only in total.

Slice performance — reported separately, not only in aggregateIllustrative example

Slice	Failure rate	Lift	Status
Contract-site discoveries	8.6%	3.7×	Review
Sterile and biologic events	6.5%	2.8×	Review
Complaint-driven events	3.9%	1.7×	Watch
Routine in-process deviations	2.1%	0.9×	Normal

Bar: reopening-rate lift vs. the routine in-process baseline · scale 0–4.0× · tick marks the 2.0× review threshold 2 of 4 slices over threshold

Evidence-linked improvement

No cycle closes without a new test

The loop shuts when the late report is a regression case. That suite is what the next event worked is measured against.

Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn

01Detect

Reopening rate rises in one event class.

02Diagnose

The finding somebody made on a Friday afternoon is read back until the cause narrows to one.

03Improve

Any change goes out numbered, with the events that caused it attached.

04Verify

One quality-event case still failing is enough to hold the release back.

05Learn

One case joins the suite, one line joins the deviation record.

Learn → DetectThe return edge. The next detection is measured against a suite one case longer.

Typical build scope

Twelve workstreams across six weeks

The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, event workflow, evaluation, integration, then production validation and handover.

Workstream Week 1Week 2Week 3Week 4Week 5Week 6

01Quality-event workflow discovery and boundary work.

02Quality and MES source assessment.

03Reportability, scope and CAPA procedure mapping.

04Event ingestion and evidence normalisation.

05Assembly logic and source binding.

06Confidence scoring and exception routing.

07Quality-unit approval workflow.

08Quality-system and MES integration.

09Reportability and CAPA cases.

10Guardrails and approval controls.

11Event-trail instrumentation.

12Deployment, documentation and Agent Care handover.

12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel Final scope and sequence confirmed in discovery

Engagement tiers

What each tier includes

Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.

Capability✓ in scope · — not at this tier PilotOne site, one event class ProductionProduction quality systems AdvancedMultiple sites / regions

Introduced at Pilot

Assembly to your event record✓✓✓

Quality-unit approval✓✓✓

Investigation-completeness baseline✓✓✓

Introduced at Production

Reporting by event class—✓✓

Approval workflow in your systems—✓✓

Approved write-back—✓✓

Quality-system integration—✓✓

Introduced at Advanced

Multi-site procedure sets——✓

Multi-stage quality approvals——✓

High event volume——✓

Multi-site reportability controls——✓

Build price From $5,000 From $8,000 Custom quote

Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.

Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.

What we need from you

What you bring, and what we build with it

Each input maps to a piece of build scope and a week in the delivery timeline.

You bringWe build with it

01Your event record structure and procedures → Event ingestion and evidence mappingWeek 1

02Representative closed investigations → Assembly baseline, scope extraction and source bindingWeek 2

03Your CAPA, clock and escalation procedure → Procedure mapping and automation-boundary definitionWeek 1

04Access to relevant APIs, feeds or exports → Quality, MES and laboratory assessment, then integration setupWeek 2

05Investigations you would not want re-opened → Clock cases and the evaluation suiteWeek 4

06What no closure may leave unanswered → Confidence scoring, exception routing, guardrails and approval controlsWeek 3

07Named quality-unit reviewers to approve events → Quality-unit approval workflow, then pilot and production validationWeeks 5–6

Nothing else is required Deployment, documentation and Agent Care handover are ours.

Delivery timeline

Four phases across six weeks

Each band spans the weeks its own phase actually takes, and that is why week five holds a pair.

Phase W1W2W3W4W5W6

Discovery W1

Build W2 – W3

Evaluate W4 – W5

Pilot & Launch W5 – W6

Week focus W1Quality-event discovery, procedure mapping and the automation boundary W2Quality-system integration and the assembly baseline W3Assembly workflow, confidence logic and approval controls W4Evaluation suite, guardrails and failure-mode testing W5MES and laboratory integration, pilot events and targeted corrections W6One quality cycle run under the quality unit, then Agent Care handover

Reading the bandEach bar spans only the weeks its work is named in. The week 5 overlap is two phases running, not padding.

At the end of W6Once the event cycle validates, Agent Care assumes the running agent.

DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Biotechnology AI agent

Build a quality-event agent around your quality unit.

Show us your deviation procedure, your quality system and who approves. Closing the deviation, deciding what is reportable and signing the effectiveness check stay with the quality unit. Draft EU/PIC/S GMP Annex 22 — consultation closed 7 October 2025 — says generative models should not be used in critical GMP applications, and this agent is built so that it is not one. If your batch-release work stops at the release package, this page picks the event up.

Discuss this agent →

Nestack Agents · Deviation, CAPA & change controlAGT-BT-14 · Agent Care available after launch