Electronic batch records. Execution, not paper on a screen.

Electronic batch record software should change how manufacturing runs, not only where operators type. A PDF displayed on a tablet is still a document-driven process: people interpret instructions, transcribe values, calculate results, discover missing evidence during review, and reconcile materials and equipment after the batch is complete.

Seal turns the approved master manufacturing record into an executable workflow. The live record knows which product, batch, process version, materials, equipment, people, parameters, samples, calculations, signatures, and exception rules apply. Evidence is checked as it is created, and release review begins while the batch is still running.

The batch record must prove that the approved process was followed and that departures were visible, assessed, and resolved. That requires more than digitized fields.

An executable EBR should:

FDA's Part 11 scope and application guidance explains that electronic-record controls operate alongside the underlying predicate-rule requirements. An electronic signature does not make an incomplete manufacturing process compliant. The system must first create and retain the record the operation requires.

A master manufacturing record contains approved process knowledge. Seal represents that knowledge as reusable stages and steps with explicit behavior:

Authors can reuse approved patterns for dispensing, setup, line clearance, sampling, cleaning, reconciliation, or review without copying uncontrolled text between records. Product-specific differences remain explicit. The displayed instruction is generated from structured requirements and governed content, so the executable logic and readable record cannot silently diverge.

Authoring is itself controlled. Draft, review, approval, effective, superseded, and retired states have defined permissions. Comments, changes, comparison, approval signatures, and validation evidence remain attached to the version.

The latest version is not always the correct version. A batch may need the process, specification, label, method, or material rule approved for its product, site, market, campaign, and start date.

Seal resolves effectivity when the batch is instantiated and records the versions selected. A later change does not rewrite work in progress. Change control identifies open orders, active batches, material populations, training assignments, interfaces, and validation evidence affected by a proposed revision.

If an urgent change must apply to live work, the decision is explicit. Authorized users assess current state, define the transition point, approve additional instructions, and preserve both the original and changed course. There is no invisible replacement of a page in an issued packet.

An approved order creates a live batch with product, site, process version, planned quantity, units, campaign, market, due state, and external references. It does not create an empty copy of a document.

The instance accumulates actual genealogy and execution:

This is why an EBR is not simply a document-management feature. It is the as-executed state of the physical batch.

Material requirements resolve from the effective process and product definition. When an operator scans a container, Seal checks identity, lot, status, expiry or retest, storage or exposure state, supplier restrictions, reservation, quantity, and eligibility for the batch.

Dispensing can integrate balances and barcode printers. The record retains the scale, calibration state, gross, tare, net, units, tolerance, source container, destination, operator, verifier, timestamps, and label. Partial use updates the source container rather than creating an unexplained inventory adjustment.

A wrong material, rejected lot, expired container, duplicate scan, or quantity outside tolerance does not become a red note discovered later. The normal transition is blocked and the approved resolution path begins immediately. Substitution, overage, reconciliation difference, or returned material requires its own accountable rule.

The instruction requests an equipment class; execution selects a physical asset. Seal checks qualification, calibration, maintenance, cleaning, sterilization where applicable, current allocation, status, and product-changeover rules before the step can begin.

The same principle applies to people. A user account alone does not establish eligibility. Effective procedure training, role assignment, practical qualification, aseptic qualification, method authorization, or independent-verifier rules can be evaluated at the action.

The record stores the state that allowed the work at that time. If an equipment calibration or personnel qualification is later found invalid, impact assessment can identify every affected batch action without reconstructing schedules and sign-in sheets.

Not every value should be typed, and not every automation signal belongs in the EBR. The design decision is which evidence supports the accountable manufacturing action.

Manual entries retain user, time, unit, range, instruction, and correction history. Calculated values retain formula version, source inputs, precision, rounding, result, and review. Barcode and device readings retain the physical source. DCS, PLC, SCADA, historian, and equipment interfaces can provide phase events, critical values, alarms, summaries, or source references while remaining authoritative for process control.

Every interface defines ownership and failure behavior. Seal records message identity, source, acknowledgement, status, and retry so a network interruption cannot silently duplicate or drop the evidence. Operators can see when expected data is pending or unavailable; an integration fault cannot masquerade as a completed step.

A field with a red border is not an exception strategy. Each controlled value needs its units, source, expected range, action range, precision, formula, and response.

Seal evaluates values as they arrive. The configured result can allow continuation, require verification, repeat an observation, request an approved adjustment, create a sample, place the batch on hold, or open a deviation. The original value and system evaluation remain visible even when the authorized process continues.

Calculations are versioned process logic. Yield, potency adjustment, concentration, addition quantity, activity, material balance, and time-window calculations retain inputs and outputs. A changed formula becomes a controlled revision and can be tested against representative cases before effectivity.

Paper records encourage users to write around problems: annotations, arrows, blank fields, attached forms, and retrospective explanations. A strong EBR makes abnormal paths first-class.

Seal distinguishes correction, comment, variance, alarm, intervention, deviation, rework, repeat, abort, and skipped or not-applicable work. Each path has permission, rationale, required evidence, impact, and approval rules. The original planned path remains visible.

A deviation opened from a step inherits the batch, product, process version, phase, materials, equipment, values, users, samples, and time window. Containment and product impact begin with a defined population. Authorized rework or reprocessing creates additional executable work without altering the original course.

The record therefore answers both what happened and how the quality system responded.

A signature should identify the record, signer, time, and meaning of the act. Review, verification, performance, approval, and disposition are different decisions.

Seal binds the signature to the current record and displayed context. Authentication, role, signer eligibility, and separation-of-duty rules can be enforced. A verifier can be required to be different from the performer. Reauthentication can be required for critical actions. Changes after signature trigger the configured invalidation or additional review behavior.

Audit history is readable as part of the record. It preserves creation, modification, original and changed values, reason, user, time, and relevant system action. Administrative configuration and privileged access also require governance; data integrity is not limited to operator fields.

FDA's drug CGMP data-integrity guidance frames integrity around complete, consistent, and accurate data and its associated metadata across the lifecycle. EBR design should make those properties the normal output of execution.

Traditional review starts after the packet reaches QA. Reviewers search every page for missing entries, unchecked boxes, arithmetic, late signatures, unexpected values, and unexplained changes.

Seal evaluates completeness and exceptions continuously. Reviewers can see completed stages and focus on:

Review by exception does not hide the batch. Every instruction, value, action, signature, and attachment remains available. It directs attention to risk and change while preserving complete review evidence.

The completed EBR contributes to disposition with material genealogy, execution, equipment state, process values, in-process and release results, yields, packaging, labels, deviations, and required approvals connected.

QA can disposition the batch only when the effective release requirements are resolved. Approved, rejected, restricted, rework, pending, and other authorized states remain distinguishable. The decision updates eligible containers, inventory, downstream use, and CoA without a second manual status change.

The final human-readable batch record is generated from governed data and history. It is useful for inspection and archival, but it is an output—not the only representation of the batch. The underlying objects remain searchable and traceable for investigations, annual review, continued process verification, complaints, and recalls.

Electronic execution changes the failure model. The implementation must define what happens during application, network, device, identity-provider, interface, printer, or facility outages.

Seal's operating design identifies critical steps, safe hold points, expected service, monitoring, backup, recovery, queued interfaces, and approved contingency records. When service returns, reconciliation determines which actions occurred, which data arrived, and how the official record is completed without duplication or silent transcription.

Contingency is not permission to run a shadow paper system indefinitely. It is a controlled, tested procedure for maintaining product and patient protection during a defined failure and returning to the authoritative electronic state.

Copying every line of a legacy batch record into fields reproduces its ambiguity and review burden. Migration should begin by classifying each element:

Duplicate prompts, retrospective entries, manual calculations, and data already available from another source should be redesigned. The resulting executable process is then reviewed by manufacturing, QC, engineering, and quality against intended use and representative risks.

Historical migration is selective. Active master data, open batches, current inventory, equipment state, and records required for ongoing decisions need controlled transfer and reconciliation. Closed paper packets can often remain in a validated archive rather than being re-keyed into a new execution system.

Validation should demonstrate intended use and risk controls, not only confirm that buttons work. The European Commission's GMP Annex 11 states that the application should be validated, infrastructure qualified, and replacement of a manual operation should not reduce product quality, process control, or quality assurance.

Start with one representative product and execute:

The EBR is ready when operators can run the real process, QA can understand abnormal execution without reconstructing it, and the organization can recover from failure without losing the authoritative record.