WorkflowManufacturing & Quality

Annual Product Quality Review Auto-Author

Each product’s annual product quality review, drafted the morning after its period closes, with every number cited

Each product's annual quality review is drafted the morning after its period closes, with every number cited.

See one case, screen by screen ↓
target41hoursof author time per review, median, down from 122 by hand
target94%of reviews approved inside the 90-day clock, up from 63 % last year
target6,840numbers this year traced to their records, each counted in two systems
demo388cited numbers in a 14-chapter draft, built when the period closed
The problem

Why product quality reviews run late

Every product needs its review once a year: every batch made and its disposition, every deviation, OOS and change, complaints, returns and recalls, the stability programme, last year’s actions, qualification status and the quality agreements — all in one signed report, due 90 days after the period ends under the site’s review SOP. With 24 products across three plants and a contract manufacturer, a review is always due.

Most of the author’s hours go before the first sentence: exports from ERP, MES, LIMS and the QMS, counts that do not match between two systems, capability worked out in spreadsheets. The trending that the review exists for — a dissolution shift after a supplier change, a complaint cluster from one packing line — gets the hours that are left, and the QP and Head of Quality get the report late in the clock.

target122hoursof author time per review, by hand
target63%of reviews approved inside the 90-day clock last year
Where a review’s author hours goestimated
By hand122 days
With the solution41 days
  • Pulling exports from ERP, MES, LIMS and QMS40 → 2 d
  • Reconciling counts between systems18 → 3 d
  • Trending, capability and stability regression22 → 6 d
  • Writing 14 chapters and their charts30 → 18 d
  • Deciding findings and signing12 → 12 d

Estimated split for one product review, by hand and with the solution. The totals match the 122 h by hand and the 41 h median target.

How it works

How a review moves

Specialist agents collect, trend, reconcile and write every review; the product quality lead decides each finding and signs.

What comes in
Period closes8 systems · batch, lab, quality, regulatory and contract records
Agents at work
Batch collectorbatches + yields
Quality events collectordeviations, changes, complaints
Lab and stability collectorresults + stability
Regulatory and agreements collectorvariations + agreements
Then
Trend and capability analystcapability + trends
Reconciliation checkertwo systems per number
Then
Review writer14 chapters, cited
A person decides
Product quality leaddecides each finding; QP and Head of Quality sign
What comes out
Cited review
Findings with actions
Signed inside 90 days
One case, step by step

One review, from period close to signature

Corventa 20 mg film-coated tablets, made at Plant 2 — Shannon: 186 batches between Aug 1, 2025 and Jul 31, 2026, review due Oct 29. Here is what happens, screen by screen, in the working solution.

  1. 01Morning, Oct 7

    The whole review year, on one screen

    Priya Raman · Product quality lead

    Priya opens the review year: 24 product reviews due across 3 plants and 1 contract manufacturer, 16 approved and 8 in progress. Five things need her decision — 4 findings and 1 count to reconcile — and one review, Talvexa oral solution, is 9 days late waiting for the QP signature.

    Agents at work: “Reconciliation checker — complaint count differs for Corventa 20 mg — 58 vs 57.”

  2. 02Period closed

    A review built the day its period closes

    The agents

    Veltrimab drug substance closed its period on Sep 30. The collectors pull 58 production orders and 58 batch records, 27 deviations, 1 OOS, 18 changes, 290 release results, 3 stability studies, 2 variations and 4 agreements. The trend analyst raises one finding — host-cell protein trending up — the reconciliation checker confirms all 37 counts agree in two systems, and the writer drafts 14 chapters with 388 cited numbers.

    “Seven agents pull 58 batches and every linked record from ERP, MES, QMS and LIMS, trend them, reconcile every count and write all 14 chapters.”

  3. 03Drafted Oct 1, 06:31

    Corventa 20 mg, already written

    Priya Raman · Product quality lead

    Chapter 1 summarises the period: 186 batches, 181 released, 2 rejected and 3 awaiting disposition at period end. Against last period: 41 deviations (6 major) against 47, 4 OOS with 1 confirmed, 23 changes, 58 complaints against 61, no recalls. Three findings wait for her, and the conclusion is left blank on purpose.

    “The writer drafts the conclusion once the 3 remaining findings are decided — the conclusion is yours, built from your decisions.”

  4. 04Chapter 4

    A dissolution shift nobody had seen

    Trend and capability analyst

    Six critical quality attributes are trended over 186 batches; five are stable and capable. Dissolution at 30 minutes shifted down from February 2026 — the batch mean fell from 94.1 % to 89.6 %, and capability since the change is Cpk 1.08 against the 1.33 target in SOP-QA-118 §7.3. Every batch except CV25-1188 still met the Q = 80 % limit; the control chart marks the day it started: “Feb 9 · new cellulose supplier”.

  5. 05One click

    Any number, back to its records

    Priya Raman · Product quality lead

    She clicks 89.6 %. The evidence pane shows how it was counted — the mean of batch-mean dissolution at 30 min for the 95 batches made from February 2026 — which agent counted it and when, the system it was counted in, and all 95 batch records behind it.

    “Every number in this review is counted from records.”

  6. 06Decided

    Finding F1: the evidence, a recommendation, her decision

    Priya Raman · Product quality lead

    The shift starts with the first batches made with cellulose from the second supplier, Halvern Cellulose, under change CC-26-0412. Halvern’s certificates of analysis show a d50 of 128–141 µm, against 104–112 µm for lots from the original supplier. The trend analyst recommends a CAPA: particle size at the incoming test, dissolution on every batch for 6 months, and MSAT to assess a supplier-specific granulation water amount. Priya chooses “Raise CAPA as recommended” — CAPA-26-041.

    The change control’s own risk assessment, cited: “Particle size distribution is comparable (d50 within ±10 %); no impact on dissolution expected.”

  7. 07Chapter 10

    Two systems disagree — and the record that explains it

    Reconciliation checker

    The complaint system counts 58 complaints; the QMS product link counts 57. The checker found the difference: CMP-26-0311 (discolouration, May 2026) is linked to Corventa 40 mg in the QMS, but the batch on the complaint photo, CV26-1058, is a 20 mg batch. Priya relinks it — 58 in both systems.

    A count that differs between two systems blocks sign-off until a person resolves it.

  8. 08Findings F3 and F2

    A stability pull on watch, and a complaint cluster

    Priya Raman · Product quality lead

    Impurity B at 18 months, 0.31 %, is above the trend of earlier pulls, but the projection to the 36-month shelf-life is 0.42 % (upper bound 0.47 %), inside the 0.5 % limit: Priya keeps it on watch with a 21-month pull. Five broken-tablet complaints from April to June all came from batches packed on blister line 2 after its sealing temperature was lowered to 185 °C — she raises CAPA-26-042 to verify forming depth and add a start-up check.

    “Keep on watch: add a 21-month pull and review again at 24 months. No change to shelf-life.”

  9. 09All decided

    The conclusion, written from her decisions

    Review writer

    With the three findings decided, the writer drafts the conclusion in chapter 1, naming each finding with the decision and the CAPA it raised, and noting that both corrective actions will be checked in next year’s review.

    “The manufacturing process for Corventa 20 mg and its controls remain in a state of control: every released batch met its specification, and the specifications remain appropriate.”

  10. 10Signed · 22 days to spare

    Three signatures, in order

    Priya Raman · Product quality lead

    Before signing, the solution checks that the findings are decided (3 of 3), the counts are reconciled and chapters 2–13 are ready. Priya signs as author with her user ID and password, and the meaning recorded with it: “I prepared this review; its content and conclusions are accurate.” The review goes to Dr. Omar Haddad as Qualified Person, then to Dana Okafor, Head of Quality.

Who it’s for

Built for everyone who writes, checks and signs a product review.

The same review, seen by the five people who carry it — what their year looked like, and what it looks like now.

PR
Priya RamanProduct quality lead · Plant 2 — Shannon
Author
Before
Spends most of a review’s hours pulling exports and counting records before the first chapter is written.
Now
Opens a drafted review the morning after period close, decides the findings, resolves the counts and signs as author.
OH
Dr. Omar HaddadQualified Person
Second signature
Before
Checks a long report by hand to see that it supports continued certification of the product’s batches.
Now
Signs after the author, with every number one click from its records and the meaning of his signature recorded.
DO
Dana OkaforHead of Quality
Final approval
Before
Finds out which reviews will miss the 90-day clock from the late list.
Now
Sees every review’s stage and clock, author hours and capability across products, and gives the final approval.
MC
Dr. Maya ChenCPV statistician · MSAT
Contributor — CPV
Before
Works out Cpk and run rules for each product’s critical quality attributes in spreadsheets.
Now
Starts from capability for every attribute, run rules applied and the shift marked on the control chart.
SP
Sam PatelQC stability lead
Contributor — stability
Before
Trends each stability study’s pulls by hand to see whether a result is out of trend.
Now
Sees every pull against the 95 % prediction interval of earlier pulls, projected to the end of shelf-life.
Built on the engine

7 agents. Each with one job, and hard limits.

Specialist agents collect, trend, reconcile and write every review; the product quality lead decides each finding and signs.

Batch collector

Pulls production orders, usage decisions, yields and batch-record exceptions for the review period from ERP and MES.

  • Read-only on every source system
  • Period filter must match the review record
  • Never estimates — a batch missing from either system is reported, not filled
Quality events collector

Collects deviations, OOS/OOT investigations, CAPA, change controls, complaints, returns and recalls linked to the product, with the links between them.

  • Read-only
  • Keeps the original classification and status
  • Safety-relevant complaints are flagged, never summarised away
Lab and stability collector

Pulls release results for every critical quality attribute and all stability pulls, with condition and time point, from LIMS.

  • Units carried with every value
  • Invalidated results kept and labelled
Regulatory and agreements collector

Lists the variations filed, approved or refused in the period, open post-approval commitments, and the technical and quality agreements in force for each site.

  • Reports only what the source records show
  • Flags expired agreements, never assumes renewal
Trend and capability analyst

Computes capability (Cpk), run rules, a Pareto of deviations, stability regressions to shelf-life and complaint clusters, and raises each adverse trend as a finding with a recommended action.

  • Every statistic shows its inputs
  • Findings are proposals — a person decides
Reconciliation checker

Counts every number in the review from at least two systems — ERP against QMS disposition, complaint system against QMS link, MES against LIMS lots — and opens an item listing the records that explain any difference.

  • A mismatch blocks sign-off until a person resolves it
Review writer

Fills the 14-chapter template with plain statements, charts and a citation behind every number, and drafts the conclusions from the decisions taken.

  • No statement without a source
  • Marks anything it could not verify
  • Conclusions stay draft until the author signs
Product quality lead

Decides each finding and signs. The agents propose; a named person decides.

Ask in plain words

Ask about any review, in plain words

Ask about any product review, trend or number — every answer cites the record it came from. It can also add a trending rule or link findings across products.

Why did dissolution drop after February?

The drop lines up with the second cellulose supplier. Batch-mean dissolution at 30 min fell from 94.1 % (91 batches, Aug–Jan) to 89.6 % (95 batches, Feb–Jul). The first lower batches are the first made with Halvern cellulose under CC-26-0412, whose particle size is larger — d50 128–141 µm against 104–112 µm. Every batch still passed except CV25-1188, which failed for a different reason (over-wetted granulation).

Which other products use the new cellulose supplier?

Two products use Halvern cellulose: Corventa 40 mg — the same shift, dissolution Cpk 1.17 since February, raised as F-020-1 in its draft review — and Corventa 20 mg, finding F1, Cpk 1.08. The contract-made Corventa 20 mg at Bracken uses only the original supplier, and its dissolution Cpk is 1.41 — no shift. I have linked F-020-1 to F1, so one CAPA can cover both strengths.

Add a rule: flag complaint clusters of 3 or more in 60 days

Added for your approval as a trending rule: complaint cluster — 3 or more complaints with the same failure within 60 days, applied to every product from the next agent run. With it, the broken-tablet cluster on Corventa 20 mg would have been flagged on May 21, six weeks before the period closed.

Who signs, and in what order?

Three electronic signatures, in order: you as author, then Dr. Omar Haddad as Qualified Person, then Dana Okafor, Head of Quality. Your signature is held until every finding is decided and the complaint count is reconciled.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

The review yearEvery product review on its due date, the 90-day clocks still running, what needs the product quality lead and what the agents did overnight.
A review being builtAt period close, four collectors pull the records in parallel, then the trend analyst, the reconciliation checker and the writer — each step shown as it runs.
Summary and conclusionsThe period against the last one, the findings waiting for a decision, and every number in the chapter listed beside it.
Trends and capabilityA control chart of every batch and Cpk for each critical quality attribute, with the shift marked where it starts.
Where a number comes fromHow it was counted, which agent counted it, the systems it was counted in and every record behind it.
Deciding a findingThe evidence with its citations, the trend analyst’s recommendation, and the decision recorded with the CAPA it raised.
Counts reconciledWhen two systems disagree, the record that explains the difference, and the choice to relink, keep or ask the owning unit.
The stability programmeEvery study’s pulls with the 95 % projection to shelf-life, and the out-of-trend pull raised as a finding to watch.
The conclusionWritten in chapter 1 from the decisions taken: each finding, its decision and the CAPA that answers it.
Sign-offThe three signatures in order, each with its meaning, and the review history from the audit trail.
Findings and actionsEvery adverse trend found across the portfolio, the decision a person took and the CAPA it raised, ready to export for management review.
The dashboardReviews approved on time, author hours per review, numbers traced, and process capability across products.
Your rulesThe template, the review period, the capability target and the trending rules — all settings.
Governance

Built for regulated work: cited, counted twice, signed.

Every number cites its recordsClick any underlined number to see how it was counted, the systems that agree on it and every record behind it; click a citation to open the source passage.
Counted twice, or not signedEach number is counted in two systems. A count that differs blocks sign-off until a person resolves it, and the resolution is recorded.
Source systems are read, never changedERP, MES, LIMS, QMS and the complaint, regulatory, engineering and contract systems are read-only connections. Nothing is written back.
Findings are proposalsThe trend analyst recommends; the product quality lead decides — raise a CAPA, watch, or no action with a reason that goes into the conclusions.
Three signatures, in orderAuthor, Qualified Person, Head of Quality — each an electronic signature with its meaning, date and time. A signed review is locked; a change needs a new version.
Every step on the recordEach agent run, decision, reconciliation, signature and settings change is recorded in the audit trail, and the review history shows it on the sign-off page.
Configuration

Your quality system’s rules, not ours

The template, the trending rules, the clocks and the signers are settings. A new trending rule can be described in plain words.

SettingDefaultChoose from
Review templateCombined US annual review + EU quality review (14 chapters)Combined · EU product quality review only (13 chapters) · US annual product review only (9 chapters)
Review periodRolling 12 months per productRolling 12 months per product · Calendar year for all products
Capability target (Cpk)1.331.00 · 1.33 · 1.67
Stability out of trendA pull outside the 95 % prediction interval of earlier pullsOn · Off
Draft built after the period closesNext morning at 06:00Next morning at 06:00 · Within 3 days · On request only
Due date90 days after period end90 · 60 days after period end
Qualified Person — EU-released productsDr. Omar HaddadDr. Omar Haddad · Lena Ortiz
Final approvalDana Okafor — Head of QualityDana Okafor — Head of Quality · Dr. Maya Chen
Connections

Works with the systems you already run

ERP and MESproduction orders, usage decisions, yields, batch records and exceptions
LIMSrelease results and stability pulls
Your quality systemdeviations, OOS/OOT, CAPA and change control
Complaint systemcomplaints, returns and recalls
Regulatory systemvariations and commitments by market
Engineering and contract systemsqualification status, quality and technical agreements
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
41hours
of author time per review, median, down from 122 by hand
By hand122 h
With agents41 h
target
94%
of reviews approved inside the 90-day clock, up from 63% last year
approved on time
target
6,840
numbers this year traced to their records, each counted in two systems

“demo” = seen in the working solution, on its sample product data · “target” = the design goal, measured in the live solution · “estimated” = our estimate · Sources: 21 CFR 211.180(e) · EU GMP Chapter 1 (product quality review) · ICH Q10. People, companies and products named on this page are fictional — characters and sample data in the working solution.

Questions

What product quality teams ask us.

What is an annual product quality review?

A yearly review of each product: batches made and their disposition, results and trends, deviations, OOS, changes, variations, stability, complaints, returns and recalls, last year’s actions, qualification status and agreements. The US calls it the annual product review (21 CFR 211.180(e)); the EU calls it the product quality review (EU GMP Chapter 1). The default template covers both in one 14-chapter report.

How does it write the APR/PQR?

When a product’s review period closes, four collectors pull the period’s records from ERP, MES, LIMS, the QMS and the complaint, regulatory, engineering and contract systems. The trend analyst computes capability, run rules and stability regressions, the reconciliation checker counts every number in two systems, and the writer fills the template with charts and a citation behind every number.

How do we know the numbers are right?

Every number links to the records it was counted from, and is counted in at least two systems. If two systems disagree — 58 complaints in one, 57 in the other — the checker lists the record that explains it, and sign-off is blocked until a person resolves it.

Does it change our ERP, LIMS or QMS records?

No. Every connection is read-only and nothing is written back to the source systems. A change to the report after signature needs a new version.

Do people stay in control of the findings?

Yes. The trend analyst raises each adverse trend with its evidence and a recommended action, but only the product quality lead decides: raise a CAPA, watch, or no action with a reason. The conclusion is written from those decisions.

Who signs the review?

Three electronic signatures, in order: the author, the Qualified Person for EU-released products, and the Head of Quality for final approval. Each is recorded with its meaning, date and time, and the signed review is locked.

Can we use our own template and trending rules?

Yes. The template, the review period, the capability target, run rules, the stability out-of-trend rule, when the draft is built, the due date and the signers are all settings, and a new trending rule can be described in plain words.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements — your review SOP, your template, your trending rules and a sample of a product’s records — and it goes live once every quality gate has passed. We will walk you through it on one of your own products first.

See it on
your products.

We’ll build a product quality review for one of your products, from a sample of its own records.