Productionthe MMR is locked, the BMR fills itself in.
On work-order release, V5 snapshots the approved master formula into the WO so the batch record is, in the regulator’s words, an “accurate reproduction” of the master. Operators then walk the steps; the BMR writes itself.
What changes once Production & MMR/BMR execution with locked formulas is live.
Indicative ranges from V5 pilot deployments. Your numbers will land near these once the workflow is operator-led and e-signed at the step.
What changes the day you switch this on.
Wet-ink signatures collected hours after the work happened.
Master records edited in place — provenance lost between revisions.
Operators jump between paper SOPs, scales and a back-office PC.
Variances and overcharges discovered at month-end COGS.
Two e-signatures to approve a master
MMR snapshot is immutable per 211.188
Operators can’t skip a step
In-process checks roll up live
What you actually get
Operator-led, e-signed, immutable. Engineered for regulated manufacturers — not retrofitted.
Two e-signatures to approve a master
Preparer + independent reviewer per 211.186 / 111.205. Approved formulas are immutable; edits create v+1.
MMR snapshot is immutable per 211.188
Reports always render from the snapshot, never from live data that has moved on.
Operators can’t skip a step
The kiosk gates step N+1 until step N is signed. Skipping is impossible, not just discouraged.
In-process checks roll up live
Temperature, hold time, AQL — captured at the kiosk and surfaced to QC by exception.
Curious how this lands in your environment?
Where AI actually earns its place.
AI works from the same locked MMR snapshot that drives the batch, watching in-process checks as operators sign them and drafting the narrative work that used to happen after the fact.
- 01
In-process exceptions rolled up as they happen
Temperature, hold time and AQL readings captured at the kiosk are watched live; anything drifting toward an out-of-tolerance result is surfaced to a supervisor while the batch is still running, not after the eBMR is closed.
- 02
New MMR drafted from an existing procedure
When engineering drops in a paper SOP for a new or revised master, AI proposes the step sequence, tolerance bands and signature/witness points from the document text, ready for the required two-signature approval.
Cuts first-recipe build time from days to an afternoon.
- 03
Step-level 'what does this mean' answers
Operators asking the kiosk to explain a step get an answer sourced from the effective, version-locked MMR snapshot for that specific work order — never from a superseded or draft version.
- 04
Batch-level anomaly summary at hand-off
As the batch nears completion, AI writes a short summary of anything that varied from a routine run — a re-weigh, a delayed step, a witness sign-off — so the next reviewer isn't reading every timestamp cold.
AI never signs a step on an operator's behalf, never advances the kiosk past a gate, and never edits the locked MMR snapshot. Step sequencing and signatures remain entirely human actions.
One operator action — a complete, signed record.
What it leaves behind
- Live eBMR rendering
- Step-by-step gating on the kiosk
- Operator can’t sign for someone else
The clauses this satisfies
What buyers ask before they switch on Production.
The rest of the platform this plugs into.
V5 isn't a bolt-on. Every module shares the same data, the same audit trail, the same operator. Pick where to look next.
Receiving
Scan-gated goods-in: matches PO, captures vendor CoA + lot, auto-quarantines, and prints a GS1-128 license plate before putaway. Built for 21 CFR 211 and FSMA 204.
Dispense
Live-scale dispense with tolerance bands and lot-genealogy capture at the gram. Wrong lot? The kiosk says no. Engineered for 21 CFR 211.101 and 111.40.
QC release
QC sees only what failed. In-process checks roll up; out-of-spec routes to deviation. Two-signature release where the regulator demands it.
Got questions, or want to see it on your shop floor?
Ask V5 — our code-aware assistant — or spin up a workspace. Both are free.