All blueprints

Oral solid dose MES. The material balance kept as the batch runs.

Oral solid dose MES and electronic batch records in which each intermediate is a controlled object, so dispensing, granulation, compression, coating and packaging build the material balance as they happen.

Illustration of a seal beside a production line of sealed vials.
Batch OSD-1042 / live material ledger
Every transformation posts quantity and state.
01
Dispense
02
Granulate
03
Blend
04
Compress
05
Coat
06
Pack
Issued to batch
100.00 kg
API, excipients and coating solids
Good output
98.42 kg
Samples
0.34 kg
Documented loss
0.81 kg
Rejects
0.43 kg
Reconciliation closed
100.00 kg accounted for / no unexplained difference
100.00 kg

Figure 1. Batch OSD-1042 as a live material ledger from dispensing to packing. Of 100.00 kg issued, 98.42 kg is good output, 0.34 kg samples, 0.81 kg documented loss and 0.43 kg rejects, so the reconciliation closes.

Summary

The problem
Paper records document each intermediate form on a separate page, and inventory systems often see only the issue and the finished receipt. When the material balance does not close, the gap is found at the end, after the physical context has gone.
Seal’s approach
Each intermediate is a controlled batch object, so dispensing, transformations, samples, losses and packaging are recorded as they occur. The reconciliation is the sum of those events, checked against the approved tolerance.
What changes
A discrepancy is investigated while the containers and equipment are still available, and QA reviews unresolved evidence rather than reading every normal entry.
Where to start
One product family: one master record, exercised with wrong-material, failed-IPC, hold-time and reconciliation exceptions. Book a demo.

Oral solid dose manufacturing turns weighed materials into tablets or capsules through a sequence of transformations. At every stage, the site must know what entered, what happened, what was measured, what moved forward and where the remainder went.

Seal keeps dispensing, processing, in-process testing, packaging, QC and release in one batch genealogy, together with the material, equipment and cleaning state each step depended on. The reconciliation is computed from every movement and transformation recorded against the batch when it occurs.

1Material balance is the operating truth.

A batch may begin with drums and bags, become dispensed components, wet or dry granules, milled material, a blend, cores, coated tablets, bulk product and packaged units. Paper records document those forms on separate pages. Inventory systems often see only the issue and the finished receipt.

Seal treats each intermediate state as a controlled batch object. Quantity, unit, status, location, container, process stage, samples and losses remain explicit.

The reconciliation is not a calculation typed at the end. It is the sum of recorded events:

Issued material = acceptable output + samples + documented loss + scrap + accountable returns

If the equation does not close within the approved tolerance, the batch cannot move through normal review. The missing quantity is investigated while the physical context still exists.

1.1Why teams choose Seal for oral solid dose

A material balance that does not close is usually found at the end of an OSD batch, because the batch is recorded on paper or in a document-style eBR and the inventory system sees only the issue and the finished receipt. Seal records each intermediate on one platform with the batch, the in-process tests and the quality events, and sums the reconciliation from what was recorded. A revised tolerance, IPC or hold time becomes a new master version for the batches that follow, so the product family can improve from its own batch history.

2Identity is established at receipt and verified at dispense.

APIs, excipients, capsules and packaging components arrive with different storage, sampling and testing requirements. Seal creates received lots and containers in quarantine, assigns eligible locations and generates sampling work from the approved material and supplier plan. Each laboratory sample stays linked to the containers it represents, and QC disposition changes a lot’s availability without anyone copying the decision into another system. Retest and expiry dates stay with the lot.

The dispensing order derives from the approved master record and batch size. The operator scans the material and container, and Seal checks identity, status, expiry or retest, allocation and whether the lot is permitted for the product. The balance reading can enter directly, so target, tolerance, tare, net weight, balance, operator and verifier are one event rather than a transcription. Partial containers keep their remaining quantity.

Scan → six checks → hard stop / block, don’t warn
Scan / material barcode
Cat# SC-ACS-500 / LOT-8811
✓
Material
Sodium Chloride / matches step
✓
Lot released
LOT-8811 / QA-released 2026-03-17
✓
Not expired
Exp 2027-09 / within date
✓
Not quarantined
Status available
✗
Grade
Cat# SC-ACS-500 / expected SC-USP-500
Hard stop / workflow halted
Expected: Sodium Chloride USP (Cat# SC-USP-500)
Scanned: Sodium Chloride ACS (Cat# SC-ACS-500)—return to shelf
Each scan is checked before the dispense step continues.
Figure 2. A material barcode scan is checked for identity, lot status, expiry and other conditions before weighing; a mismatch stops the dispense step

A wrong material or unacceptable weight stops the step before the component reaches the process; any permitted exception follows an approved path. Independent verification can be electronic and risk-based. When a supplier or lot issue appears later, genealogy traces forward through every dispensed quantity and batch that consumed it.

3The master record becomes the run.

The approved master manufacturing record defines the sequence, materials, equipment classes, instructions, parameters, ranges, hold times, samples, calculations, signatures and conditional paths.

Seal instantiates that version for the batch. Operators see the current instruction and capture the required evidence in context. The system checks what can be checked: correct equipment, material identity, parameter ranges, required sequence, elapsed time, yield tolerance and completion of prerequisites.

Granulation, drying, milling, blending, compression or encapsulation, coating and packaging each keep their own parameters and checks rather than being flattened into generic steps. Reusable operation templates reduce configuration work, while product-specific parameters remain under controlled approval.

4In-process controls belong to the operation.

Controls run at different stages and frequencies: moisture and blend uniformity before compression, weight, hardness and friability during it, dissolution and appearance later.¹ Seal creates the required checks from the process definition. Results can enter from a connected device, an at-line instrument, the QC laboratory or controlled manual observation. The batch step knows whether the result permits continuation, requires adjustment within an approved range, or triggers a hold and investigation.

Adjustments remain visible. If compression weight trends and the operator changes fill depth, the record connects the observation, approved adjustment, new parameter, affected time or unit range, and follow-up result. Reviewers see control, not a final average that hides the process response.

5Material and equipment carry their own eligibility.

Intermediates wait between steps: granules for milling, blend for compression, cores for coating, bulk for packaging. Seal starts each hold clock when the defined event occurs and carries the deadline with the container. Scheduling sees what must run next, and material past its normal hold cannot be issued without the approved assessment. A storage excursion identifies the containers and batches inside the affected interval.

A blender is not available merely because the schedule is empty. Its cleaning status, prior product, maintenance, calibration, qualification and line clearance decide whether it may be used, and Seal checks the selected equipment against the batch requirement. Cleaning execution records its agents, parameters, inspection and release.² Dirty and clean hold times stay live. Changeover rules can add controls based on the previous and next product. The asset state that permitted execution is kept with the batch, closing the gap between the equipment register and the batch record.

6Packaging continues the genealogy.

Packaging is part of the batch history, not an inventory transaction after manufacturing. Labels, cartons, leaflets and other printed components must be the correct ones for the batch.³ Each also has identity, version, quantity and reconciliation requirements.

Seal verifies component issue and line clearance, records code setup and checks, links inspection or vision results, and accounts for issued, used, rejected, destroyed and returned quantities. Finished units inherit the bulk batch and packaging-lot genealogy.

Batch production and control records must show that each significant step was accomplished.⁴ A connected genealogy makes that history retrievable from one place rather than distributed across records.

7Review follows exceptions and transformations.

QA can review completed sections while the batch proceeds. Material verification, parameters, IPCs, yields, hold times, cleaning, samples and deviations surface against the stage where they occurred.

At completion, the release record joins manufacturing with finished-product testing, open quality events, packaging reconciliation, stability commitments and required approvals. The reviewer moves through unresolved evidence rather than reading every normal entry as if each carried equal risk.

After: review, not compilation1 screen
Unified batch view
Execution
Steps with timestamps
Operators identified
Materials linked
Progress tracked
Test results
Results inline
Specs checked
OOS flagged
CoA follows results
Deviations
Linked to step
Full context shown
Resolution status
Impact assessed
Equipment
Calibration status
Usage logged
Quals verified
Training current
One review record
Focus on judgement, not assembly
Figure 3. Batch release requirements for execution, testing, eligibility and data resolve against versioned source records before QA signs a scoped disposition

When disposition is approved, finished goods change status and the Certificate of Analysis renders from the same approved dataset.

8Start with one product family.

An effective implementation begins with a representative family rather than every SKU. Model shared materials, equipment classes, unit operations, tests and packaging patterns. Configure one master record and exercise normal execution plus the exceptions that define real operations: wrong material, out-of-tolerance weight, failed IPC, hold-time risk, yield discrepancy, equipment alarm, cleaning failure and packaging reconciliation difference.

The second product should inherit approved reusable components. The implementation scales when adding a strength or presentation is a controlled delta review—not another document-conversion project.

References

  1. 121 CFR 211.110, Sampling and testing of in-process materials and drug products: written procedures must describe the in-process controls, tests or examinations to be conducted on samples of each batch. eCFR
  2. 221 CFR 211.67, Equipment cleaning and maintenance: equipment and utensils must be cleaned, maintained and, as appropriate, sanitised or sterilised at appropriate intervals under written procedures. eCFR
  3. 321 CFR 211.130, Packaging and labeling operations: written procedures must assure that correct labels, labelling and packaging materials are used. eCFR
  4. 421 CFR 211.188, Batch production and control records: batch production and control records must be prepared for each batch with complete information, documenting that each significant step was accomplished. eCFR

AOperating model

Included in this blueprint

  • GMP material control
  • Weigh and dispense
  • Electronic batch records
  • In-process and release testing
  • Equipment and cleaning state
  • Deviation and CAPA
  • Packaging and labelling
  • Batch disposition

Connected across Seal

BCapabilities

Table B.1. What the Oral Solid Dose MES and Electronic Batch Records blueprint covers. Linked capabilities are blueprints of their own.
CapabilityWhat it covers
GMP material controlReceipt, container identity, quarantine, sampling, release, retest, storage, allocation and genealogy.
Weigh and dispenseFormula-derived orders, scan verification, connected balances, tolerance checks, labels, partial containers and accountability.
Electronic batch recordsGranulation, drying, milling, blending, compression, encapsulation, coating and packaging as guided execution.
In-process and release testingAt-line and laboratory results are checked against current requirements and returned to the batch step that requested them.
Equipment and cleaning stateQualification, calibration, maintenance, product-contact history, cleaning and hold-time eligibility at selection.
Deviation and CAPAProcess exceptions open with stage, values, equipment, material genealogy, operator and affected quantity attached.
Packaging and labellingControlled components, artwork versions, coding, inspection, reconciliation, genealogy and market presentation.
Batch dispositionExecution, IPCs, yields, hold times, packaging, QC, deviations and approvals mature into one release record.

CConnected records

Entity hierarchy
What it records
Kind
Material Container
Specific API, excipient or component container with lot, status, location and remaining quantity.
entity
Dispensed Component
Verified quantity prepared for one batch and linked to source container and balance.
entity
OSD Batch
Parent genealogy across all intermediates, samples, losses, packaging and release.
entity
Intermediate
Granule, blend, core, coated tablet or bulk capsule with quantity, container, status and hold state.
entity
BLD-1042
Released final blend awaiting compression within its approved hold time.
record
Unit Operation
Approved transformation with equipment, parameters, IPCs, yields and signatures.
entity
Tablet Process
Dispense, granulate, dry, mill, blend, compress, coat and package.
template
In-Process Control
Observation or test used to control the current manufacturing stage.
entity
Process Equipment
Eligible asset with cleaning, maintenance, calibration, qualification and product-contact state.
entity
Material Difference
Sample, documented loss, scrap, dust, reject, return or unexplained reconciliation difference.
entity
Packaged Lot
Finished units inheriting bulk product and packaging-component genealogy.
entity
Disposition
QA decision supported by execution, reconciliation, QC, packaging and exception evidence.
entity
Figure C.1. Record types, templates and the relationships between them in this blueprint.

DQuestions and answers

What processes should oral solid dose manufacturing software support?

It should support material receipt and sampling, dispensing, granulation, drying, milling, blending, compression or encapsulation, coating, in-process controls, holds and transfers, cleaning, packaging, reconciliation, QC testing, deviations and final disposition.

Can one electronic batch record cover tablets and capsules?

The platform is shared, while approved unit-operation templates and master records reflect each process. Tablet and capsule products can reuse dispensing, blending, equipment, laboratory, quality and release patterns while maintaining their specific compression, encapsulation, coating and packaging controls.

How does material reconciliation work?

Each issue, dispense, transformation, sample, loss, scrap, reject, return and finished output records its quantity against the batch and stage. Seal calculates the reconciliation from those events and compares it with the approved tolerance. An unexplained difference can be configured to block progression to review or release.

Can Seal connect to balances and at-line instruments?

Yes. Device integration can capture weight and in-process values with instrument identity, timestamp, unit and operator context. The implementation method depends on the device interface and the site’s control architecture.

How are in-process adjustments controlled?

The master record defines which parameters may be adjusted, by whom, within what range and what follow-up measurement is required. The observation, adjustment, affected interval or quantity, rationale and confirmation remain one traceable sequence.

How are intermediate hold times managed?

The configured start event begins the hold clock for a specific intermediate and container, and due times appear in scheduling and execution. Material beyond the normal limit can be made unavailable until the approved assessment and exception path is completed.

How does cleaning status control equipment selection?

Equipment carries its product-contact history, prior product, cleaning execution, verification, clean and dirty hold times and release state. Batch execution checks that state and the applicable changeover rule before the asset can be selected.

Can Seal manage packaging-component reconciliation?

Yes. Issued, used, rejected, destroyed, sampled and returned quantities are recorded for controlled printed and unprinted components. Coding and inspection results link to the packaging run, and finished units inherit the bulk and component genealogy.

How does QC connect to the manufacturing batch?

The process and product definitions create in-process and release samples with batch, stage, priority, tests and specification attached. Approved results update the batch record directly and become part of the disposition dataset and Certificate of Analysis.

How should an existing paper master batch record be migrated?

Model the process behind the document: materials, operations, parameters, decisions, equipment requirements, IPCs, calculations, signatures and exception paths. Execute representative batches and failures with operators and reviewers before approving the electronic master for routine use.

See your process in Seal.

Bring a procedure or a recurring problem. See how your team can use Neil to build the workflow, investigate the results and improve the next version.

Book a demo