Production Record Management: Scope, Controls, and Software

Production record management is the systematic control of the records that document how a batch, lot, or run was made: their creation at the time of the work, their review, their storage, their retrieval, and their eventual disposal. In the United States the content and retention of these records is set by the regulation that governs the product, so a defensible program begins by identifying that regulation and then building a consistent process around it. This article sets out what the records contain, how they are controlled across their life, which rules illustrate the retention question, and which safeguards matter when production log software is selected.

TL;DR

• Production records are contemporaneous evidence of what was made, by whom, when, with which inputs and at what yield; they differ from controlled documents, which may be revised.
• Entries are made when the work occurs, are attributable to a named individual, and are reviewed by a qualified person before product is released.
• Retention periods are product-specific: low-acid canned food, for example, carries a one-year plant period plus two further years, whereas other sectors set other periods.
• Electronic systems can replace paper only where validated controls, audit trails, and access restrictions are in place and the authoritative format is documented.
• Software selection should be weighed on security maturity and record integrity before convenience.

Table of Contents

• What production records are and which ones they cover
• Records versus controlled documents
• The 5 Ws as a completeness test
• Creating records: contemporaneous, attributable, legible
• Reviewing and releasing
• Retention: how to determine the period
• From paper to a digital production log
• What to require of production record software
• Our perspective
• Support for production records and production teams
• FAQ
• Sources

What production records are and which ones they cover

A production record documents a specific execution of a process. The governing master document describes the intended procedure; the production record describes what actually happened. Federal regulation of medicated feed illustrates the distinction clearly: a master record file states the manufacturing procedure, formulation, theoretical yield, assay requirements, and labeling, while the production record documents the individual batch or run, including drug amounts and the quantity of feed produced.

For each batch or run under that rule, the production record must carry product identification, the production date, the signature or initials of a responsible individual, the name and quantity of the drug component, and both theoretical and actual quantities produced. The same pattern recurs, with sector-specific detail, across food, drug, device, and cannabis manufacturing. A reasonable working inventory of production records therefore includes:

• batch or lot records, with identifiers and dates;
• input and material records, including component quantities and lot codes;
• process parameter logs such as temperatures, times, and equipment settings;
• equipment, calibration, and cleaning records;
• yield reconciliation, deviation, and rework records;
• distribution records that connect finished lots to first recipients.

Quality control logs, equipment maintenance records, and regulatory submissions are typically the first candidates when a company ranks which records carry the greatest risk. Our companion guide on quality control records and logs treats the contents, review, and retention of that adjacent category in detail.

Records versus controlled documents

A frequent source of audit findings is the conflation of two categories. A procedure, work instruction, or specification is a controlled document: it is expected to be revised, and its version history matters. A record is static evidence that an activity occurred, and it must not be altered after the fact. A records process description published by Argonne National Laboratory states that a management system should distinguish between the two, with separate metadata and access controls for each. In practice this means that a person with rights to edit a standard operating procedure should not automatically hold rights to edit a completed batch record.

The 5 Ws as a completeness test

The familiar five questions of documentation (who, what, when, where, and why) are a useful screening device for whether an entry is complete. Practitioner guidance on the five Ws of documentation frames them as the elements that make a record defensible later, and they map onto regulated production logs without difficulty:

The fifth question is the one most often left blank. A temperature excursion with no recorded reason, or a quantity adjustment without a rationale, cannot be assessed by a later reviewer, and the entry is incomplete even where every number is present.

The five Ws are a heuristic and not a regulatory standard. The regulatory standard is the one in the applicable rule, and the Ws are best used to check that the rule’s required fields were captured in context.

Creating records: contemporaneous, attributable, legible

The most consistent requirement across sectors is timing. California’s cannabis manufacturing checklist, for example, states that batch production records must be created concurrently with each documented manufacturing or remediation activity. Retrospective transcription from memory or from scrap paper is the practice that regulators and auditors distrust most.

HACCP recordkeeping guidance prepared at Texas A&M in line with FDA principles gives a compact statement of good practice: records are created accurately and at the time of the activity, identify the facility, date, product, and lot code, carry signatures or initials, are legible and indelible, are regularly reviewed, and are promptly available. Each element corresponds to a control that can be audited:

1. Concurrency. Entry points are located at the work station, so the operator does not rely on later transcription.
2. Attribution. Every entry traces to an individual, through initials on paper or unique credentials in a system.
3. Legibility and permanence. Paper entries are made in indelible ink; electronic entries are protected against overwriting.
4. Correction discipline. Corrections are made by a single line-through, with date, initials, and reason, so that the original entry remains readable.
5. Identification. Facility, date, product, and lot code appear on every page or screen.

Reviewing and releasing

Creation is only half of the control. Under the low-acid canned food inspection guide published by FDA, a qualified plant-management representative reviews the processing and production records for completeness after processing and before shipment or release, then signs or initials and dates them. The principle generalizes: the reviewer is independent of the person who made the entries, has the competence to recognize an out-of-limit value, and acts before product leaves control.

Review also supports traceability. FDA explains that U.S. food-record requirements allow identification of a food’s immediate previous sources and immediate subsequent recipients, which presupposes that lot identifiers in production records are accurate. In the pharmaceutical setting, FDA states that when an internal audit leads to corrective action, the documentation, the affected master production records, and investigations into related batches must be retained and available for inspection. A production record is therefore not an archive item only; it is the basis on which impact assessment after a deviation is performed.

The same logic applies to commercial records that alter production, such as customer-initiated changes. Margin leakage frequently originates in undocumented scope changes, and a disciplined approach to change order tracking applies the same attribution and timing principles to the commercial side of a production job.

Retention: how to determine the period

There is no single U.S. retention period for production records. The period follows from the product category, the regulation that applies, contractual obligations, and the organization’s own risk assessment. Two examples show the range of what a rule can specify.

Under 21 CFR §113.100, low-acid canned food processors record production conditions when observed, including product and code, date, equipment, container size, temperatures, processing time, and other scheduled-process factors, and management reviews the records for completeness and process compliance before release. The same rule requires distribution records that identify where finished lots were first distributed so that lots that may be contaminated can be segregated, and covered records are generally retained for at least one year at the plant and two additional years at the plant or another accessible location. FDA’s inspection guide restates this arrangement and notes that scheduled-process establishment records are excepted.

A records process description should then convert such obligations into practice. The Argonne document describes the generic cycle: businesses classify and index records, store and protect them, make them retrievable, and destroy them through an approved process based on business, legal, and regulatory requirements. A practical retention schedule therefore lists, for each record class, the governing citation, the retention trigger (date of manufacture, date of release, end of shelf life), the period, the storage location, and the disposal method.

Where the company manufactures under more than one regime, the longest applicable period normally governs the combined class, and a legal hold overrides the schedule. Counsel or a regulatory specialist familiar with the product should confirm the schedule, since the examples above apply to their own product categories and not to production generally.

From paper to a digital production log

A move to electronic records changes the evidence, not the obligation. FDA’s guidance on Part 11 explains that the regulation applies when organizations rely on electronic records to perform regulated activities in place of paper, and it recommends that firms document in their standard operating procedures which format is the authoritative record. A hybrid state, in which some data is on paper and some on screen with no declared master, is where many inspection observations arise.

In food processing, FDA’s inspection guide states that computerized control and recordkeeping systems must give accurate, reliable, and consistent results, and that electronic records and signatures can be treated as equivalent to paper and handwritten signatures when Part 11 provisions are followed and validated controls exist. A sound migration sequence is:

1. Inventory the existing paper workflows and identify which records are regulated.
2. Define, in writing, which format is authoritative for each record class.
3. Map every required field in the governing rule to a mandatory field in the electronic form.
4. Validate the system for its intended use before live production data enters it.
5. Pilot on a single line or product family, then train the operators and reviewers.
6. Expand, and review audit-trail and access logs on a defined schedule.

Paper is not always the problem. In low-volume environments a well-designed paper form with disciplined review may satisfy the rule at lower cost, and the decision should rest on volume, risk, and the number of people who must retrieve the data.

What to require of production record software

Searches for the best production log software usually produce feature lists. A more reliable method is to rank requirements by the harm that their absence would cause.

Record integrity. The system should hold a time-stamped audit trail of creation, modification, and deletion, tie each action to a unique user, and keep completed records static. Logging and audit trails are treated as security controls in industrial architecture guidance, which cites IEC 62443 requirement SR 2.8 among the frameworks to consider.

Access control. Role-based permissions should separate those who enter data, those who review, and those who administer the configuration. The same architecture guidance lists role-based access control alongside IEC 62443 and the NIST Cybersecurity Framework as a design consideration.

Documented security maturity. An academic framework for evaluating cloud ERP systems proposes that security maturity be assessed across authentication, encryption, access control, vulnerability management, and compliance, which allows vendors to be compared on the same criteria rather than on marketing claims. Organizations that need to place such an assessment inside a wider program can consult our overview of a NIST CSF implementation.

Validation and regulatory fit. Where Part 11 applies, the vendor should supply the documentation that supports validation, and the buyer remains responsible for validating the configuration it deploys.

Retrieval and retention. The system should support search by lot, date, product, and operator, enforce the retention schedule, and export records in a readable form that outlives the vendor relationship.

Backup and continuity. Manufacturing security guidance from Google recommends keeping an up-to-date inventory of operational technology assets and connections, tracing cloud data flows, and testing backups at least annually; a production log that cannot be restored is not a record system.

Alternatives fall into recognizable types: general-purpose spreadsheets and shared drives, paper binders, document-management platforms, manufacturing execution systems, and lightweight workflow tools for small producers and independent practitioners. The right type depends on the regulated status of the product and the number of sites and users.

Our perspective

Our experience in mission-critical environments is that record failures are rarely failures of intent. They are failures of design: the entry point is far from the work, the reviewer cannot see what changed, or no one has decided which copy is the record.

We therefore approach production record management as a systems question before it is a software question. We map the regulated records, define the authoritative format, and test the controls that protect integrity, including authentication, access, logging, and backup. Only then does the choice of tool become straightforward.

This is the reason we build workflow tools from real production problems, and the reason our technical advisory work treats record integrity and cybersecurity as one subject. Clarity under pressure depends on records that can be trusted at the moment they are needed.

Jesse Hart

Support for production records and production teams

For teams that manage production records and contracts in one place, Project Relay is our tool for production record and contract management, published at $49 per month. Where the question concerns the security or architecture of the system that holds the records, our technical systems and risk review examines the controls described above in the context of a specific environment.

The full range of our advisory, training, and production services is described on the PROJECT-JTH site.

FAQ

What is the difference between a production record and a controlled document?

A controlled document, such as a procedure or specification, may be revised under version control. A production record is static evidence of what occurred in a particular batch or run and should not be altered after the fact. Systems should apply separate access controls and metadata to the two categories.

How long must production records be kept?

The period depends on the product and the governing rule. Low-acid canned food records, for example, are generally kept at the plant for at least one year and for two further years at the plant or another accessible location. Other sectors set different periods, so the retention schedule should cite the specific regulation for each record class.

Can electronic production records replace paper?

In FDA-regulated settings, electronic records and signatures can be treated as equivalent to paper when Part 11 provisions are followed and validated controls are in place. The organization should state in its procedures which format is the authoritative record. Products outside FDA jurisdiction follow their own regulator’s rules.

What makes a production log entry complete?

The entry identifies who made it, what was produced or measured, when and where the work occurred, and why any deviation or adjustment was made. It is recorded at the time of the activity, is legible and permanent, and is reviewed by a qualified person before release.

Sources

• 21 CFR § 225.102, Master record file and production records
• 21 CFR § 113.100, Processing and production records
• FDA, Guide to Inspections of Low Acid Canned Food 42
• Argonne National Laboratory, Documents and Records Process Description
• California Department of Cannabis Control, Batch production record checklist
• Texas A&M, Principle 7: Recordkeeping Procedures
• FDA, Questions and Answers Regarding Establishment and Maintenance of Records
• FDA, Questions and Answers on CGMP Requirements for Records and Reports
• FDA, Part 11, Electronic Records; Electronic Signatures: Scope and Application
• FDA, Computerized Systems in Food Processing Industry
• Security evaluation framework for cloud ERP systems
• TEEPTRAK, MES SCADA IIoT Integration
• Google, Manufacturing OT Security Guidance
• The 5 Ws of Documentation

Recommended

• Protect Production Margin With Change Order Tracking and a 5-Day SLA
• Quality Control Records and Logs: Contents, Review, Retention
• Content Production Workflow: Stages, Gates and Metrics
• 30/90/365 Document Version Control for Teams: Operations First