When one person performs every production step, memory can appear to be a system. The founder remembers which fragrance behaved differently, which supplier lot arrived late, and why one batch yielded fewer units. As the studio hires, adds products, or produces more often, those details stop being reliably available.
Production logs for small manufacturers preserve what actually happened. They connect the approved plan with materials, people, process conditions, checks, output, and decisions. A useful batch log is not paperwork added after production; it is part of making and releasing the product.
A formula tells you what should happen; a log tells you what did
A formula, recipe, or bill of materials defines the approved inputs and quantities. A work instruction defines the method. A batch production record captures execution: the exact version used, actual quantities, lot identities, times, results, exceptions, and output.
Do not combine these concepts in a document that operators overwrite each run. If someone edits the master formula to record an actual weight, the business loses both the controlled standard and a trustworthy history.
Each batch should have a unique identifier. The lot or batch code on finished goods should lead back to its production record. If codes are reused or recorded only on a carton later discarded, traceability breaks when it matters most.
Record the evidence needed to answer real questions
A practical batch log usually includes:
- product name, SKU, batch ID, and planned quantity;
- approved formula and work-instruction version;
- production date, location, and responsible operators;
- each material or component, supplier lot, planned amount, and actual amount;
- equipment or work center when relevant;
- key times, temperatures, settings, or process observations;
- in-process and finished quality results;
- actual yield, scrap, rework, and retained samples;
- deviations, corrections, and attachments;
- review, disposition, and release authorization.
Not every product needs every field. A jewelry assembly record may emphasize component lots, dimensions, finish, and stone count. A sauce record may require cook time, temperature, pH, fill, and allergen controls. Regulatory obligations differ by product and market, so use qualified advice where required.
The U.S. Food and Drug Administration’s current good manufacturing practice rules illustrate the core principle: records should document production and control for each batch and be reviewed for compliance before release. Even businesses outside FDA-regulated categories can learn from the separation between execution, review, and disposition.
Make entries at the time work occurs
Backfilled logs are vulnerable to forgotten details and reconstructed numbers. Put the record where the action happens and design it for contemporaneous entries.
Use permanent, legible records. On paper, define how corrections are made without obscuring the original entry. In a digital system, preserve who changed what and when. Never share accounts if an electronic signature or user identity is meant to show responsibility.
Pre-number pages or generate controlled batch IDs so missing records are visible. Require units beside quantities. A bare “10” cannot tell the reviewer whether the operator used grams, ounces, or containers.
Avoid checkboxes that invite thoughtless completion. “Verify material” is weaker than fields for item identity, lot, expiry or status, actual quantity, initials, and time. The form should collect evidence of the control, not merely a claim that someone was careful.
Build version control into the workflow
Old instructions cause quiet inconsistency. Assign a version and effective date to formulas, specifications, labels, and procedures. Approve changes before use, record why they were made, and remove obsolete copies from the production area.
At the start of a batch, the operator should confirm that the issued record references current versions. If a change is needed during production, treat it as a documented deviation or approved change rather than editing the instructions informally.
This matters for customer experience as well as compliance. A “small improvement” in scent, color, size, or component can create complaints when customers expect the previous product.
Treat deviations as information, not embarrassment
A deviation is a departure from the approved formula, method, limit, or expected result. The log should describe what occurred, affected quantity, immediate action, and escalation. A designated person then decides whether material can be released, reworked, rejected, or needs more evaluation.
Do not normalize recurring exceptions by writing “acceptable as usual.” Three repeated deviations suggest the standard is unrealistic or the process is unstable. Investigate the cause, change the process, or formally revise the standard based on evidence.
Link customer complaints and returns to batch IDs when possible. A cluster tied to one material lot or production date gives the business a narrower, faster investigation than a general product complaint.
Design logs people can complete correctly
Walk through the production process in sequence and place fields in that order. Group pre-start checks, material dispensing, processing, packaging, and final review. Give operators enough writing space and provide clear options for “not applicable.”
Pilot the form during three real batches. Watch for duplicated entries, missing units, fields completed long after the step, and information recorded elsewhere. Ask operators which instructions are ambiguous. Shorten the form where a field has no decision or traceability value; add detail where people repeatedly improvise.
Training should include a simulated error. Have the operator document a wrong material quantity, failed check, or damaged component correctly. Perfect demonstration batches do not prove that the exception process works.
Review and retrieve records
Assign a reviewer who was not simply checking their own entries where staffing allows. Review for completeness, calculations, required checks, unexplained corrections, yield, deviations, and disposition before finished stock becomes available.
Set a retention policy based on legal, customer, insurance, and business needs. Store records so they remain readable and retrievable for the required period. Test retrieval: choose a finished lot and see whether the team can find its complete history promptly.
Digital tools can reduce transcription and connect lots, inventory movements, and quality decisions. Kerno can support production and batch records for growing makers, but software should not turn a weak procedure into a longer form. Start with the questions your business must be able to answer.
Create a minimum viable batch log
For your next run, capture the unique batch ID, approved version, material lots and actual quantities, responsible operator, key process checks, acceptable yield, exceptions, and release decision. Review the record before stock is sold.
Then select one finished unit and trace it backward. Can you identify what went into it, how it was made, what was checked, and who decided it was ready? If not, revise the log while the gaps are still fresh. Reliable production documentation makes growth less dependent on memory and makes problems smaller when they occur.
