SOPs and their versions
Effective SOP versions read from a quality document system, with major and minor version, lifecycle state and effective date. The quality system stays the SOP record; Trovensa reads and never approves a controlled procedure.
All products
RECORD · Trovensa Review
PreviewCompare records with the procedure version in force, then decide.
Findings with the source, the requirement and the reason.
In preview; not generally available. Status as of 2026-09-15.
Intended forQuality reviewers and the scientists whose records they review.
PillarRECORD · Decisions with a record
Capabilities
What Trovensa Review keeps.
Review is being designed to compare protocols, experiment records, reports and notebook entries with the standard operating procedure version that was effective when the work was done. Each finding names the record, the requirement, the SOP version and an explanation, and waits for a quality reviewer to accept, dismiss or resolve it. Findings are evidence your quality process consumes, never automatic proof of compliance or non-compliance.
Each capability below is a design target for Trovensa Review.
Requirement sets, accepted by QA
An agent proposes coded requirements from each version, with page and paragraph. A quality reviewer edits and accepts the set with a decision signature before any check can use it.
Checks bound to a version
A check names the SOP version effective when the work was done, or a version chosen with a recorded reason. A new effective version triggers an impact review of the open checks and drafts bound to the old one.
Checks on notebook entries
Started from a button inside the electronic lab notebook or from the console. Findings cite the entry passage and the requirement; nothing is written back to the notebook.
Decisions and deviations
Reviewer decisions recorded per finding; suspected deviations carry a proposed classification and are tracked to closure by a person.
OutputsReview check with SOP versionReview finding with decisionRequirement set with acceptanceDeviation record
In the console
Ask, see the plan, decide.
How Trovensa Review is used from the console: one ask, the plan, the proposals an agent may make, and the decision that stays with a person.
Preview In preview; not generally available. Status as of 2026-09-15.
A scientist asks
“Check entry EXP-0417 against the effective SOP.”
The plan card
Read the entry as last modified; bind the check to the SOP version effective at that time; compare against the accepted requirement set; propose findings.
Gated proposals
- Review check with its version binding
- Review findings (open, citing the passage)
- Suspected deviations with a proposed classification
Never proposed
Deciding a finding, closing a deviation or accepting a requirement set.
A person decides
The scientist fixes the entry in the notebook; the quality reviewer decides each finding. A finding is never a verdict.
Every accepted proposal becomes an ordinary Trovensa Review record marked agent-generated, with the run and the decision beside it.Illustrative
Captured 2026-09-15 from build e456d2d.
Stages served
Where Trovensa Review fits in the lifecycle.
Read on