Pull the review period's batch, deviation, out-of-specification, change, complaint, return and stability inputs into one pack, reconciled to the registers they came from — the conclusion stays with the heads who sign.
A period closes, and the batch list, deviation register, results, changes, complaints and returns pull in.
02
A register is read once and reconciled to the batch list, so two tables in one pack cannot disagree.
Reason
03
An input is normalised across the quality, manufacturing and laboratory systems, each figure kept with its source.
04
A closed deviation, CAPA or change arrives as an input from your quality-event work, and is reviewed, never reopened.
05
A failing result arrives already settled by the laboratory; whether it could be set aside was decided before this.
Decide
06
A variation granted mid-period is marked against the limit it moved, so no line is drawn across two specifications.
07
A previous open item travels forward with its owner, its due date and whether it moved since the last review.
Out
08
A US pack carries the basis of representativeness, because 21 CFR 211.180(e)(1) asks for a representative number.
09
Writes run only inside the approval boundaries agreed at implementation, and never onto a signed review.
→Product statement
The agent assembles and makes no GMP determination; a named quality head concludes, and a second named person evaluates it.
Example workflow
One review period, inputs to signature
AgentHuman
1Period closesBatch list, deviation register, LIMS extract, change log, complaints or stability data
2Inputs reconciledBatches, deviations, results, changes, complaints and stability points, each against its register
3Pack draftedElement coverage, reconciliation, trend picture, open items and confidence
4Controls appliedReconciliation checks, element-coverage checks, grouping checks and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is concluded at any of them — the agent is assembling, and the quality head's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the site quality head.
Low confidence
Adds a second quality read first.
Quality-head review
The pack is held with its inputs, its unreconciled lines and the confidence.
Sign · Query · Send for a second read
Signed — conclusion recorded▼
6Quality systems updatedOnly where write access and approval policy allow it
7Outcome evaluatedElement coverage, unreconciled lines, amendments and delivery against the agreement
Amendments
A pack read a year later is read against the registers, and that is what it has to survive.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Concluding that the process remains in control.
Determining that CAPA or revalidation is due.
Writing the conclusion for any review element.
Deciding a grouping is scientifically justified.
Automation boundaryAgent acts unaided
✓Pull each element against the register it comes from.
✓Reconcile the batch list against the deviation and the result registers held.
✓Show the trend and the open items from the last review.
✓Test the pack for coverage and hold it for the signatories to read first.
Writes stay inside the boundaries set at implementation, and never onto a signed review.
Reopening or closing a deviation or a change.
Deciding whether a failing result may be set aside.
Extending or waiving the date the agreement fixes.
Changes to element, grouping or trend rules.
Example output
One element, annotated
What the agent assembles is attached to the register it was drawn from.
Review-pack output · single elementIllustrative example
Element
Assembled line
Element cited
Register of record
Confidence
Owed to
Significant deviations
Four deviations in the period sit against batches outside the batch list this pack was built on
EU GMP 1.10(iv)
Deviation register
88%
Contract-giver, by agreement
As receivedTaken from the deviation register and the batch list — nothing on this side is written by the agent.
Inputs usedDeviation registerBatch list for the periodPrevious review actions
Why this elementIt is the element the input has to satisfy and a person still decides.
ActionSignQuerySend for a second read
What the score decidesBelow the configured threshold the pack picks up a second quality 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 elementFrom the source register
03Assembly
Start where the event is
The deviation, CAPA and change page closes the event; the OOS page settles the result. This one consumes both.
01Approved path
The conclusion is a signature
No instrument names a signatory. The signature exists because your procedure and technical agreement create it.
02Human review
The deadline is contractual
EU GMP 1.11 requires a technical agreement between the parties, and that is the only place a review date exists at all.
04Build an evidence trail
The input, the register it came from and the head who concluded stay on the review.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Integration availability depends on the client's existing systems and API access.
Agent controls
Six layers between the model and the review
Six checks stacked inward. Anything the whole stack misses is written into the map below.
L6 · Outermost — last line of defenceInward → L1 · closest to the model
L6Rollback / safe modePull the agent back to input tracking when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt, element-list and trend-rule configuration changes.Track
L4Input traceabilityRecord the registers, the pack, the amendments and the signature time.Record
L3Quality-head sign-offHold packs for the named heads; the gate governs release, not whether the conclusion is sound.Gate
L2Policy guardrailsTest packs against element coverage, reconciliation and grouping rules; a failure returns the pack and writes no conclusion.Restrict
L1Confidence thresholdsRoute low-confidence packs to a second quality read before the heads see them.Require review
Model corePack assembled — element coverage, reconciliation, trend picture, open items and confidence
L1 – L2Test whether a pack may stand
L3Puts the conclusion in named hands
L4 – L5Keep the input and the register behind it
L6Holds the review at unconcluded when signals degrade
How Nestack evaluates it
Evaluate the assembly workflow — not only the signed pack.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the pack the contract-giver reads
Depth of coverage ▼
E1Final-output evaluationDid each element carry its input, its register and its period?
E2Step-level evaluationDid the agent use the right period, the right registers and the current template?
E3Tool evaluationDid it read and write the correct product and the correct field?
E4Confidence calibrationDo low-confidence packs actually attract more amendments in review?
E5Slice evaluationHow does performance change across specific product families?
E6Business outcomeHow many packs were amended, and how many went out late against the agreement?
Floor — the outcome the site answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, each placed where in the lifecycle it starts.
Agent lifecycleDirection of processing →
01 · Retrieval1 mode
FA-03
Register read as current
The list as it stands now, not as it stood then.
Stage gathersBatch list, registers, results, changes and stability
02 · Reasoning2 modes
FA-04
Trend crosses a moved limit
A period is trended against a specification that changed.
FA-06
Conclusion filled in
An assembly line reads as a conclusion it may not make.
Stage proposesCoverage, reconciliation, trend and confidence
03 · Tool / write2 modes
FA-02
Pack issued unreconciled
Two tables in one pack count the period differently.
FA-05
Open item carried unchanged
The previous open item repeats with no owner or date.
Stage writesOnly where write access and approval policy allow it
04 · Output1 mode
FA-01
Element left uncovered
A required element is absent and the pack still ships.
Stage returnsThe pack the two named signatories read and sign
05 · Change / Version1 mode
FA-07
Silent element drift
A model or rule change drops a required element.
Stage tracksModel, prompt, element list and trend-rule config
Sev-1 · writes onto a signed reviewSev-2 · an unreconciled pack is signedSev-3 · a register degrades, the pack holds
A site-level input-completeness figure can read as settled while a few product families carry most of the unreconciled inputs and the late packs. Nestack reports the unreconciled-input rate by family, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Contract-manufactured products
6.3%
3.6×
Review
Campaign and seasonal products
4.4%
2.5×
Review
Grouped dosage-form reviews
3.3%
1.9×
Watch
Single-site routine products
1.2%
0.7×
Normal
Bar: unreconciled-input-rate lift vs. the single-site routine baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A cycle ends with one more test
A cycle closes when the missing input is a regression case. That suite is what the next review pack assembled is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Unreconciled inputs rise in one family.
02Diagnose
The review the contract-giver was owed in January and read in June is walked back until the cause narrows to one.
03Improve
The fix carries a number, and the inputs that forced it travel with it.
04Verify
Nothing goes out until every touched review case has passed again.
05Learn
It is kept permanently, and the input rules are amended alongside it.
Learn → DetectThe return edge. Next time the detection runs against a longer suite.
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, review workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Review-period workflow discovery and boundary work.
02Register and batch-list source assessment.
03Element, grouping and trend procedure mapping.
04Input ingestion and register mapping.
05Reconciliation logic and source binding.
06Confidence scoring and exception routing.
07Quality-head sign-off workflow.
08Register and batch-system integration.
09Input and trend cases.
10Guardrails and conclusion controls.
11Review-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal 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 tierPilotOne product, one siteProductionProduction quality systemsAdvancedMultiple sites / partners
Introduced at Pilot
Assembly to your review template✓✓✓
Quality-head sign-off✓✓✓
Input-completeness baseline✓✓✓
Introduced at Production
Reporting by product family—✓✓
Sign-off workflow in your systems—✓✓
Approved write-back—✓✓
Register-and-batch integration—✓✓
Introduced at Advanced
Complex element and template sets——✓
Multi-stage quality sign-off——✓
High product-count portfolios——✓
Multi-party review controls——✓
Build priceFrom $5,000From $8,000Custom 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 review template and element list→Input ingestion and register mappingWeek 1
02Representative signed reviews→Assembly baseline, element extraction and source bindingWeek 2
03Your grouping and trend procedure→Procedure mapping and automation-boundary definitionWeek 1
04Access to relevant APIs, feeds or exports→Register, batch and laboratory assessment, then integration setupWeek 2
05Reviews you would not want delivered late→Input cases and the evaluation suiteWeek 4
06What no review may conclude without→Confidence scoring, exception routing, guardrails and sign-off controlsWeek 3
07Named quality heads to review the pack→Quality-head sign-off workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phase widths follow the calendar the work needs, so the doubling at week five is work, not padding.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Review discovery, procedure mapping and the automation boundaryW2Register integration and the assembly baselineW3Assembly workflow, confidence logic and sign-off controlsW4Evaluation suite, guardrails and failure-mode testingW5Laboratory and stability integration, pilot packs and correctionsW6One review period run under the quality head, then Agent Care handover
Reading the bandEach bar spans only the weeks its own work is named in. The week 5 overlap is two phases running, not padding.
At the end of W6When the review pack validates, Agent Care takes the agent on.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Biotechnology AI agent
Build a product quality review agent around your quality unit.
Show us your review template, your registers and who signs. The conclusion is carried by named people on both sides — the quality head at the manufacturer, and the person the marketing authorisation holder names to evaluate a review it did not write — and this agent never becomes either of them. What it does instead is narrow and checkable: it pulls each element against the register it came from, reconciles the batch list to the deviation, result, change, complaint, return and stability inputs, shows the trend those inputs make, and carries the previous review's open items forward with their owners and their dates. Here is what this page does not claim. It does not claim that a current review gates batch certification: EudraLex Annex 16, in operation 15 April 2016, enumerates the conditions a Qualified Person must secure before certifying, and a full-text check returns no occurrence of product quality review or annual product review anywhere in it. Where that dependency exists at your site, your own procedure or your technical agreement created it — and both bite: 21 CFR 211.180(e) requires written procedures to be established and followed, and EU GMP 1.11 requires the technical agreement that is the only place a review date exists at all. It does not claim regulators are coming for you either. We searched FDA warning letters for 2025 and 2026 and found no citation of 211.180(e) against a conventional drug manufacturer; the CDER Office of Compliance FY2025 report, published April 2026, does not break its counts down by CFR section; MHRA has published no GMP inspection deficiency data since 2016. We are not going to build a threat out of an absence of finding. The case here is contractual, and it is the stronger one: a contract-giver is owed this pack, on a date it set, in a template it dictated, from a party it can sue. On the frequency question, EMA has said since February 2015 that review timeframes can be appropriately adjusted for manufacturing and campaign duration with adequate justification; the revised EU GMP Chapter 1 out for joint European Commission and PIC/S consultation, closed 3 December 2025, codifies that and hardens the grouping rules, and remains draft with no final text located as at 20 August 2026. Draft EU/PIC/S GMP Annex 22 — consultation closed 7 October 2025, no final text located on the same date — says generative models should not be used in critical GMP applications, and this agent is built so that it is not one. The counterweight is MHRA's Inspectorate of 29 June 2026: GxP submissions must be technically reviewed by appropriately experienced people and signed off by someone with authority and accountability. If your quality-event work closes at the deviation and your laboratory work ends at the result, this is the year those registers have to agree across.
