Batch record types

Fiddle works with two related kinds of batch record. Knowing which is which keeps your templates clean and your production history accurate.

Master vs. issued

Type	What it is	When you use it
Master batch record	The approved, reusable template for a product	Defining and controlling the standard process
Issued batch record	A working copy of a master for one specific run	Recording what actually happened during production

The relationship is one-to-many: a single master produces many issued records, one per batch.

Choosing a structure

How you structure a master depends on the product and regulatory needs:

• Simple checklist — an ordered procedure with sign-offs, for low-risk products.
• Data-capture heavy — many in-process measurements and checks, for tightly controlled products like supplements or pharmaceuticals.
• Multi-stage — separate procedure sections for sub-assemblies or intermediates that feed a final build (see assemblies and sub-assemblies).

Build one well-structured master per product or product family rather than many one-off records. Versioning the master, not duplicating it, keeps your history traceable.

Keep types distinct

Never run production directly off a master, and never reuse an issued record for a second batch. Each run gets its own issued record so that quantities, lots, and sign-offs belong to exactly one batch.

Next steps

Read the batch records overview for how these pieces fit into a compliant production workflow.