Electronic batch record software — the EBR writes itself as the line runs.
V5 builds the electronic batch record one scan at a time, from dispense to release. By the time the batch is packed, the BMR is already e-signed, reviewable by exception, and ready for QA — no transcription, no missing weights, no chasing operators after the fact.
What breaks without this.
Paper batch records lose weeks per release
QA finds the gaps after the line has moved on. Operators don't remember. The investigation costs more than the deviation.
Transcription errors are the #1 deviation source
Operators write weights on paper, supervisors key them into a spreadsheet, QA re-keys into the BMR. Three chances to be wrong on every line.
Review-by-page doesn't scale
If QA has to read every page of every batch, throughput is gated by headcount. Review-by-exception is the only way out.
eBR systems that just digitize paper miss the point
If your eBR is a PDF form on a tablet, you've made paper electronic — not records-by-execution. Real eBR captures from the scale, the scanner, the sensor.
Records-by-execution. Compliance, by design.
Records-by-execution — captured at the source
Scale weights, barcode scans, sensor readings, e-signatures — all written to the EBR at the moment they happen. There is no separate 'data entry' step.
Scan-gated steps the operator can't skip
The kiosk drives the recipe step by step. Wrong lot, out-of-tolerance weight, missing signature — the system says no. The deviation is prevented, not documented.
Review-by-exception
QA sees only the steps that fell outside spec, ran late, or required overrides. Compliant batches release in minutes, not days.
21 CFR Part 11 e-signatures end-to-end
Every dispense, every charge-in, every line clearance, every release — e-signed and witnessed where the SOP demands. The audit trail is the system, not an export.
Full forward and reverse genealogy
Every gram of every lot, every operator, every instrument, every environmental reading — linked to the finished batch. Recall drills in seconds.
What to look for when you're buying.
eBR vendors all promise paperless batch records. The gap between a real records-by-execution system and a PDF form on a tablet is enormous. These are the criteria that separate them.
Records-by-execution, not paper-on-glass
What it tests: Does data enter the EBR from the scale, the scanner, the sensor — or does the operator still type weights into a form?
Why it matters: If the operator types the weight, you've digitized paper. Transcription errors remain the #1 deviation source.
V5: Scale weights, barcode scans, sensor readings, and e-signatures write directly to the EBR at the moment they happen. There is no separate data-entry step.
Scan-gated steps
What it tests: Can the system block a step when the lot is wrong, the weight is out of tolerance, or the operator isn't trained?
Why it matters: Documenting the deviation after the fact is paper compliance. Preventing it is GMP.
V5: Wrong lot, out-of-tolerance weight, missing signature, untrained operator — the kiosk refuses to advance.
Review by exception
What it tests: Does QA see only the steps that fell outside spec, ran late, or required an override — or do they read every page?
Why it matters: If QA reads every page, throughput is gated by QA headcount. Review-by-exception is the only way to scale.
V5: Compliant batches release in minutes with one e-signature. Only exceptions surface for focused review.
Master recipe authoring without engineering
What it tests: Who builds the EBR template — your quality SMEs, or the vendor's professional services team at $300/hour?
Why it matters: If only the vendor can change a recipe, every product launch waits on a service ticket.
V5: Recipes are built in the no-code designer by quality SMEs. The vendor doesn't gate your roadmap.
Instrument and equipment integration
What it tests: Does the system support Bluetooth and serial scales, Zebra printers, OPC-UA equipment, Hach/Mettler/Sartorius instruments out of the box?
Why it matters: An eBR that can't talk to your scales is just paper on a tablet.
V5: Bluetooth and serial scales, Zebra printers, Hach/Mettler/Sartorius instruments, and OPC-UA equipment are all supported.
Forward and reverse genealogy
What it tests: From a finished batch, can you trace every component lot, every operator, every instrument, every reading — and from a recalled component, every batch that used it?
Why it matters: Recall scope is computed from genealogy. If it's a spreadsheet, the recall is bigger than it needed to be.
V5: Full bidirectional genealogy chain — drill from finished pack to component lot in one click, and vice versa.
21 CFR Part 11 + Annex 11 in one architecture
What it tests: Are e-signatures, audit trails, and validation evidence the same set of records — or do you maintain Part 11 for FDA and Annex 11 for EMA separately?
Why it matters: Maintaining two compliance footprints doubles your validation cost and surface area.
V5: One architecture passes Part 11, Annex 11, GAMP 5, ICH Q7 and ICH Q10 simultaneously.
Validation pack and re-validation cost
What it tests: Does the vendor ship URS, FRS, IQ/OQ/PQ scripts and a regression pack on every release — or do you pay six figures per release?
Why it matters: The validation tail is where most QMS implementations bleed budget for years after go-live.
V5: Validation pack ships with the platform and is re-issued on every release. Minor releases are a regression delta; majors are a full PQ against the supplied scripts.
Spreadsheet vs legacy QMS vs V5.
How V5 eBR compares to the two systems most pharma manufacturers run on today — paper batch records, and a legacy eBR like Werum PAS-X or Rockwell PharmaSuite.
| Capability | Spreadsheet | Legacy QMS | V5 Ultimate |
|---|---|---|---|
| Data capture source | Operator handwrites, supervisor keys | Operator types into PDF form | Scale, scanner, sensor write directly to EBR |
| Scan-gated steps | None | Configurable, often disabled | Default-on, recipe-driven, blocks deviation at the source |
| Review by exception | No — QA reads every page | Possible, complex to configure | Default behaviour — compliant batches one-click release |
| Recipe authoring | Word template | Vendor professional services | No-code designer, your SMEs own it |
| Time to first batch | Day 1 | 12-24 months | 7 days for first product line |
| Validation pack | N/A | Six-figure consultancy | Included; regenerated each release |
| Genealogy chain | Manual | Module add-on | Native, bidirectional, real-time |
| Part 11 + Annex 11 coverage | Fails both | Two configurations | One architecture, both regimes |
The clauses, verbatim — and how V5 answers each.
The clauses that govern electronic batch records — pulled verbatim — and how V5 answers each.
Batch production and control records shall be prepared for each batch of drug product produced and shall include complete information relating to the production and control of each batch.
V5: Every batch in V5 carries a complete EBR assembled at execution — dispense weights, charge-ins, line clearance, environmental readings, in-process tests, label reconciliation, packaging counts and release signatures. Nothing is back-filled after the run.
A record of all calculations performed in connection with the test, including units of measure, conversion factors, and equivalency factors.
V5: All calculations are performed by V5 with units, conversion factors, and equivalency factors stored as part of the record. The operator sees the result; the auditor sees the full chain.
The ability to generate accurate and complete copies of records in both human readable and electronic form suitable for inspection, review, and copying by the agency.
V5: V5 produces a signed, human-readable PDF of any batch on demand, and the underlying electronic record is exportable in both XML and a regulator-friendly format. Both are byte-identical to the source.
Use of secure, computer-generated, time-stamped audit trails to independently record the date and time of operator entries and actions that create, modify, or delete electronic records.
V5: Append-only, tamper-evident audit trail across every action. No admin override exists — even platform owners are subject to the trail.
Consideration should be given, based on a risk assessment, to building into the system the creation of a record of all GMP-relevant changes and deletions (a system generated 'audit trail').
V5: V5's audit trail is the system, not a configurable feature. Every GMP-relevant change is captured with attribution, timestamp, and reason. No risk assessment can turn it off.
Production records should be reviewed and approved by the quality unit(s) before an API batch is released or distributed.
V5: Release in V5 requires quality-unit e-signature with attribution. The system enforces ICH Q7 §6.50 by gate — the batch cannot move to distributable status without the signature.
Step by step on the floor.
What an electronic batch record looks like in V5, from dispense to release.
- 1Pre-batch · Setup
Master recipe drives the run
QA authors the master recipe in the no-code designer — steps, tolerances, signatures, instrument bindings. On batch creation, V5 instantiates the EBR template and reserves materials and equipment.
- 2Hour 0 · Dispense
Scale writes the weight
The operator scans the component lot license plate at the dispense booth. The scale writes the weight directly to the EBR. Out-of-tolerance? The system refuses to accept and routes to QA.
- 3Hour 1 · Charge-in
Two-person verification at the kiosk
Each charge-in requires the dispensing operator's signature plus a witness — both authenticated, both trained on the current SOP. Scan-gated against the master batch sheet.
- 4Hour 2-6 · Process
Sensors stream to the EBR
Mixer temperature, blend time, vacuum, mass — sensors write directly. Out-of-band readings trigger a deviation in real time, link to the batch, and quarantine if criticality demands.
- 5Hour 6 · In-process testing
Lab QC linked to the batch
Hach/Mettler/Sartorius instruments push results straight to the EBR with method, calibration, and operator attribution. No re-keying. OOS opens deviation + CAPA in one action.
- 6Hour 8 · Packaging & reconciliation
Label and pack count match the math
Label issue, packaging output, and reconciliation are scan-counted; the math is the system, not a spreadsheet. Variances must be explained and signed before close.
- 7Hour 9 · Review by exception
QA sees only what needs attention
V5 surfaces the steps that fell outside spec, ran late, or required overrides. Compliant batches release with one quality-unit signature; non-compliant get focused investigation.
- 8Hour 10 · Release
Signed, time-stamped, distributable
Quality-unit e-signature releases the batch under §820.80 / §211.165 / ICH Q7 §6.50. The PDF is generated, the electronic record is sealed, and the genealogy chain is locked.
The math, with the assumptions visible.
eBR ROI is dominated by review-by-exception throughput and the cost of paper-driven deviations. Both compound quarterly.
Batch release cycle
Review-by-exception is the dominant factor. QA reviews only the exceptions, not every page; compliant batches release with one signature.
Transcription deviations
Operators don't transcribe weights — the scale writes them. The deviation source is structurally eliminated.
QA review labor
Headcount no longer caps throughput. QA spends time on exceptions, not on reading compliant pages.
Recall scope
Forward and reverse genealogy drills give the exact list of affected lots — recall scope is the data, not a spreadsheet guess.
For a site running 30 batches a month, the throughput gain alone often justifies V5 in the first quarter. The deviation reduction and recall-scope precision are operationally larger but harder to quantify until they happen.
What changed on the floor.
Setting
A CDMO running solid-dose and semi-solid pharmaceuticals across two sites, using paper BMRs reviewed by QA page-by-page.
Before
Average batch release took 14 days. About 18% of batches generated a transcription-driven deviation. Two QA reviewers were the throughput bottleneck — adding a third was on the budget every year and kept getting cut.
After
First product line live on V5 eBR in 9 days. Within 60 days the line's batch release median was under 4 hours and the transcription deviation rate fell below 1%. The QA team reallocated to investigation and trend analysis instead of page-turning.
Proof points
- Batch release in hours, not weeks — review-by-exception by default
- Zero transcription steps between scale and EBR
- GS1-128 license plates drive scan-gated dispense, blend, fill, label
- Bluetooth + serial scales, Zebra printers, Hach/Mettler instruments — supported out of the box
- FSMA 204 KDEs captured for food; Annex 11 + Part 11 for pharma
Built to satisfy
- 21 CFR 211 Subpart J (records & reports — pharma)
- 21 CFR 211.188 (batch production & control records)
- 21 CFR Part 11 (electronic records & signatures)
- EU GMP Annex 11 (computerised systems)
- ICH Q7 §6 (documentation & records — API)
Frequently asked questions
What is electronic batch record software?+
Electronic batch record (eBR or eBMR) software replaces paper batch manufacturing records with a system that captures every step of production electronically — dispense weights from the scale, lot scans, e-signatures, environmental readings — as the work happens. For medical devices it's called eDHR (electronic device history record).
Is V5's eBR system 21 CFR Part 11 compliant?+
Yes. Every record V5 creates is attributable, legible, contemporaneous, original and accurate. Audit trails are tamper-evident, e-signatures meet §11.50 and §11.70, and access is role-based with biometric or PIN options. The validation pack (URS, FRS, IQ/OQ/PQ templates) ships with the platform.
How is this different from a PDF form on a tablet?+
A PDF form is paper-on-glass — operators still type weights, still skip fields, still write the wrong lot number. V5 captures data at the source: the scale writes the weight, the scanner writes the lot, the sensor writes the temperature. There is no 'enter the data' step to skip.
What does 'review by exception' mean?+
Instead of QA reading every page of every batch, V5 surfaces only the steps that fell outside spec, ran late, required an override, or generated a deviation. Compliant batches release with a single e-signature; non-compliant ones get focused investigation. Throughput is no longer headcount-gated.
Can V5 connect to our existing scales and instruments?+
Yes — Bluetooth and serial scales, Zebra printers, Hach/Mettler/Sartorius instruments, and OPC-UA equipment are supported out of the box. Custom integrations are handled in the V5 hardware layer without rip-and-replace.
How long does eBR implementation take?+
The standard V5 onboarding is 7 days for the first product line. eBMR templates are built in the no-code recipe designer — you don't wait on engineering.
See V5 on your own line.
Free trial, no card. Live in 7 days with guided onboarding.