The batch record that writes itself.
Release day should not start with a records hunt. Batches run against an approved master and capture every lot, signature, reading, and deviation as the work happens, so the record reaches QA already complete. Review the exceptions, sign, release.
Batches started · 14 days
per dayDisposition outcomes
Paper batch records fail at the worst possible moment: the audit.
Approve the master once. Every batch is issued as an exact copy of it and fills in as the work happens: lots dispensed, steps performed and verified, readings, deviations, yield. By the time it reaches QA there is nothing left to chase down. The review is a read, not a reconstruction.
Follow a batch from issue to release.
Scroll one batch through. Every screen is the product.
- 1Issue the batchBR-2043 is stamped from master v3.1 as an exact, frozen copy. Later revisions cannot touch it.
- 2Dispense by scanScan the lot, weigh it, and a witness signs. The debit and the genealogy link land in one transaction.
- 3Perform and verifySteps run in enforced order. The performer signs, a second person verifies, no password mid-run.
- 4An exception, on the recordA reading lands out of tolerance. The line keeps moving; the exception waits for QA at review.
- 5Release with one signatureThe gate has checked steps, dispenses, exceptions, and yield. QA signs; the record locks, a PDF copy freezes.
From approved recipe to released batch, on one record.
Approve the recipe once. It stays approved.
A master is approved with a password and a reason, then frozen. Revising it creates the next version and supersedes the old one, so no batch ever runs against a draft or a stale copy.
MMR-011 · Vitamin C 500 mg
master recordAny batch, traced to every input.
Dispensing debits the lot and writes the genealogy link in the same transaction. When a supplier calls about a suspect lot, the batches it touched are one query, not an afternoon of binder archaeology.
Genealogy · FG-0107
one queryThe gate does the arithmetic. QA does the judgment.
The release gate has already checked step completion, dispense tolerances, exceptions, and yield. What lands on the QA desk is the part that needs a human: each exception, with who, what, and why attached. Sign to release, and a hashed PDF copy freezes with the record.
Release gate · BR-2043
QA disposition-
Every batch matches its master
Issuing a batch freezes the full master into it. A recipe revision can never reach back into a batch already on the floor.
-
One gloved hand on the line
Steps run in enforced order, performer and verifier sign as they go, and dispensing is a scan. No password prompts mid-run.
-
Exceptions surface themselves
An out-of-tolerance reading or a missed yield raises an exception on its own. The line keeps moving, and QA sees everything at review.
-
A record you can hand over
Signatures carry name, time, and meaning. The released record is hashed, with a frozen PDF copy an inspector can take away.
Runs beside quality, the warehouse, and the lab.
Fluid QMS
A batch exception escalates into a deviation and CAPA without retyping a word.
Warehouse & Dispatch
Dispense from released stock only. Finished goods land on the ledger, ready to ship.
Vapor LIMS
Run both and release can wait on the lab: finished-goods testing gates the disposition.
Retire the paper batch record.
Batch records run standalone, or beside quality and the lab on the same login. Tell us what you make and we will set up a master recipe to walk through.