Check reports and methods against LIMS, specifications and templates, then sign the review
- Numbers already traced to their rows
- Citations judged on the result date
- A read they can steer mid-run
GMP document review for API plants and CDMOs: agents read a controlled document against its template, check each citation on the date its results were made, and trace each number to LIMS before the technical reviewer and the QA approver sign. They then find the other approved documents that still cite a superseded revision.
See one stability report checked screen by screen ↓The technical reviewer prints the LIMS export, ticks numbers against the report, and opens each cited specification and method at the revision the document system shows today. Copied from the row above, a value looks right on paper. A citation that changed halfway through the study gets checked against the wrong date, and a template section that asks for a regression receives one sentence saying the trend is slight.
QA then signs a document whose errors nobody went looking for. When the client lowers a limit, the report under review may get fixed, while the protocol, the test worksheet and the disposition checklist that cite the same specification wait for the next periodic review or an inspector.
Built forQC technical reviewersQA document approversDocument control specialistsStability coordinators
Reviewers tick numbers against a printout and open citations at today's revision, so a superseded limit or a pasted row gets signed.
Checked by hand, page by page
Built-in controls
Documents reach clients and inspectors with each number and citation traced, and a specification change reaches the documents that cite it.
The technical reviewer runs the read, the author fixes from each source, the lab head rules on a data question, and the QA approver signs and writes to the client.
demoEverything you see here is sample data: the stability study, its batches, the plant, its client, the people and every figure.
Four jobs share one controlled document, and nobody holds two of them on the same draft.
Check reports and methods against LIMS, specifications and templates, then sign the review
Approve controlled documents and own the approval queue and its clocks
Keep templates and review profiles, and raise document change requests
Write stability protocols and reports and fix what review finds
demoSample data, from the working solution.
Past the one report: where the old revision still sits, what the client answered, the queue and its sampled approval, the profiles and the record of it all.
demoSample data, from the working solution.
The report printed 0.32% where LIMS holds 0.34%: the value of the batch printed above it, pasted one row off.
A client specification and a test method had both changed during the study, and the report cited one revision for every time point.
With no regression, ICH Q1E allows 18 months from 12; computed, the tighter market's limit is reached at 17.1 months.
The agents' first fix moved earlier results to the new limit; the challenger caught it before the author applied it.
demoSample data, from the working solution.
Six agents read in view, in order, each handing on to the next; reviewers sign.
Picks the approved review profile for the document type and draws samples for bulk approval.
Lays the template over the document, section by section.
Judges each citation by the revision that applied on its result's date, and reads client change notices when told to.
Traces each result to LIMS at the reported precision and recomputes computed values.
Works out a missing evaluation: regression, poolability and the confidence bound against each market's limit.
Reads the document as the client's regulatory reviewer and attacks it, along with the agents' own fixes.
GMP document review is the check a controlled document gets before QA approves it: does it follow its template, are its citations right, and do its numbers match the records they came from. Here agents do that reading in three layers, and the technical reviewer and the QA approver sign.
The one that applied on the day each result was made. Earlier results stay judged against the old limit, while later results and the conclusion use the new one. The reference checker applies that rule date by date, and the challenger tests the agents' own fixes against it.
When long-term data show change and no statistical analysis is done, extrapolation is limited to one and a half times the period covered and no more than six months beyond it. With a regression and a confidence bound, the period can go further. Where a report leaves the evaluation out, the agents compute it and show what each market's limit supports.
No. The agents read the document management system, LIMS, the chromatography data system and the quality system, and write nothing back to them. What this adds is the read before anyone signs, with each mark opening the record behind it.
Each type gets a review profile built from its template and governing procedure, proposed by document control and approved by QA. Procedures, work instructions, protocols, validation reports and specifications each run on their own profile, and a type without one is read for references and numbers only.
People. The QA approver signs the report and the note, and the client's regulatory lead replies in fields on how its market will be handled. The agents compute what the data support and never pick the retest period.
PPQ starts on its planned date: the protocol was proven on the plant batches first.
1-min demoBatch Record SearchAny batch-record question answered in seconds, cited to the page and step.
1-min demoValidation Document AutomationProtocols drafted in minutes, every value traced to its source.
1-min demoSend one stability or validation report with its template, the documents it cites and its LIMS results; we will read it in three layers and show what review missed.