Knowella

Production Order Record

A production order record is the account of what actually happened on one order: which batches went in, what the process did, what came out, and where it went. Its recurring failure is timing, not content. The fields are the right ones, but they get filled in at the end of the shift from memory rather than as the order runs, so a batch code gets transposed, a deviation gets forgotten, and the record that traceability depends on turns out to describe what somebody thinks happened rather than what did.

KnowOpsRecordOPS-008Pinned in navigation58 fields across 6 sectionsFull researchSee the form

Reviewed by Siddarth SinghCSPLast reviewed 16 August 2026

Basis
ISO 9001 cl.8.5.1
Workspace
KnowOps
Form type
Record
Completed by
Line lead, per order
Feeds
Traceability, scrap record, daily production report

The short version

  • The record's real purpose is traceability: one step back to every batch that went in, one step forward to where every unit of output went. Quantities and yield matter, but they are not what a recall depends on.
  • ISO 9001 cl.8.5.1 requires production to be carried out under controlled conditions, including monitoring, verification at appropriate stages, and the retention of documented information demonstrating the results.
  • A record completed at the end of the shift from memory is a different document from one completed as the order runs, even when the same fields end up filled in the same way. Timing is the difference between an account and a reconstruction.
  • Reconciliation within tolerance is not a formality. It is the check that everything issued is accounted for, as good product, as scrap, or as unused material returned, and a reconciliation that does not close is the first sign that something left the process unrecorded.
  • Deviations recorded at the time they happen are recoverable. Deviations reconstructed afterwards are frequently missing altogether, because nobody wrote down the parameter excursion that got corrected and the line kept running.
  • This record connects to Traceability, Scrap Record and the Daily Production Report by ID. Break the link at any point and a batch problem stops being traceable to the order it came from.

What this is

What is a production order record?

What is a production order record?

A production order record is the order-level account of execution: the materials and batch codes consumed, the process parameters and checks performed while it ran, the quantity and quality of what came out, and where that output went. It is the record a traceability exercise pulls first, because it is the one that names both what went in and what left.

Who should complete a production order record?

The line lead, in real time as the order runs, because they are the only person present for the actual events: the batch change, the deviation, the moment output starts going to a different destination. A record built at shift end from a supervisor's notes is a reconstruction, not an account, and reconstructions lose exactly the detail a recall depends on.

How does a production order record differ from a daily production report?

The daily production report aggregates across all orders and lines for the shift, for rate and output reporting. The production order record is the single order's own account, with the batch codes, deviations and reconciliation that a traceability query needs and a daily total cannot supply.

Scope

When is a production order record required?

This record is one step in the Production Control programme, the account of one order's execution. Using it to check a line is ready before it starts, or to log a stoppage, belongs to a neighbouring template.

Use this template when

  • An order has started running, or is about to, and its execution needs to be recorded as it happens
  • Materials and batch codes are being issued to a specific order and need recording against it
  • In-process checks, deviations or parameter excursions occur during the order and need capturing at the time
  • The order has finished and the output, yield and reconciliation need to be closed out
  • A linked record needs this one to exist: traceability, scrap, or the daily production report reference this order

Do not use it for

  • Line Clearance Record, which confirms the line is clear of the previous product, packaging and paperwork before this order can safely start
  • Changeover Record, which times and documents the changeover itself, from last good piece of the previous order to first good piece of this one
  • Downtime Log, which records a stoppage during the order by reason code, rather than the order's own material, process and output account
  • Scrap and Waste Record, which itemises waste by reason once it has been generated, feeding into rather than replacing this order's own scrap figure
  • Daily Production Report, which aggregates every order and line for the shift; it needs this record's figures, it does not substitute for them

Compliance mapping

Which ISO 9001 cl.8.5.1 requirements does this satisfy?

Production control is one of the most directly specified areas in ISO 9001. The standard names the conditions, monitoring, verification and documented information required; what it leaves to the organisation is when, in practice, the record gets written.

ClauseRequirementWhere it lands
ISO 9001 cl.8.5.1(a)Availability of documented information defining the characteristics of the products and the results to be achievedProcess
ISO 9001 cl.8.5.1(f)Implementation of monitoring and measurement activities at appropriate stages to verify criteria for control of processes have been metProcess
ISO 9001 cl.8.5.1(g)Use of suitable infrastructure and environment for the operation of processesOutput
ISO 9001 cl.8.5.2Use of suitable means to identify outputs when traceability is a requirement, and retention of the unique identificationOutput
ISO 9001 cl.7.5.3.2Control of documented information, including retention and legibility of records generated as objective evidenceMaterials
ISO 22000 cl.8.5.2Traceability system enabling identification of product lots and their relation to batches of raw materials and processing recordsRelated records
ISO 9001 cl.8.7Control of nonconforming outputs, including identification and segregation of product that does not meet requirementsOutput
ISO 9001 cl.9.1.3Analysis and evaluation of data from monitoring and measurement, including product conformity and process performanceOutcome

What it does not cover

  • Line clearance, which confirms the previous product and its paperwork are cleared before this order starts, and is a precondition this record assumes rather than performs.
  • Changeover timing, which is captured on the Changeover Record between the last good piece of the previous order and the first good piece of this one.
  • Downtime by reason, which belongs on the Downtime Log; this record's Started and Finished timestamps show the order's span, not what stopped it in between.
  • Allergen and label control, which are named checks on the Allergen Changeover Check and Label Verification Record, not general fields on this order's account.
  • Shift-level aggregation, which is the Daily Production Report's job, rolling this order's figures together with every other order and line for the shift.

Global

Production Order Record requirements by country

Production records are a near-universal requirement wherever a quality or safety management system applies, but the level of prescription over what has to be captured, and for how long, varies by sector and regime.

United States

FDA 21 CFR Part 117 (food); FDA 21 CFR Part 820 (medical devices); FSMA traceability rule for high-risk foods

Sector-specific regulations require production and process records with batch identification; the FSMA traceability rule adds specific data elements for designated high-risk foods.

A production order record that lacks the specific traceability lot code or the key data elements the FSMA rule names will fail a traceability exercise even if it satisfies a general ISO 9001 audit.

United Kingdom

General Food Law Regulation (EC) 178/2002 as retained in UK law, article 18; BRCGS Food Safety

One-step-back, one-step-forward traceability is a legal requirement for food business operators; BRCGS adds specific mass balance and traceability testing expectations.

A reconciliation figure that does not close, or a batch code that cannot be traced to a specific input lot, is a direct nonconformance against both the regulation and a BRCGS audit's traceability test.

European Union

Regulation (EC) 178/2002, article 18

General food law requires traceability at all stages of production, processing and distribution, with records identifying suppliers and immediate customers.

The order record is the internal link in that chain; without batch codes tying input to output, the external traceability the regulation requires cannot be reconstructed.

Canada

Safe Food for Canadians Regulations, traceability requirements

Requires lot identification and the ability to trace product one step back and one step forward through the supply chain.

The order record's batch and lot fields are the evidence a CFIA inspector will ask to see traced through in a mock recall.

Australia

Food Standards Code Standard 3.2.2; AS/NZS ISO 22000

Traceability systems are required under the code, commonly implemented through the ISO 22000 traceability clause referenced in certification schemes.

The order record supplies the batch-to-batch linkage a mock recall exercise under either the code or a certification audit will test directly.

International

ISO 9001; ISO 22000

ISO 9001 cl.8.5.1 and 8.5.2 require controlled conditions and identification enabling traceability; ISO 22000 cl.8.5.2 requires a traceability system linking product lots to raw material batches.

Certification auditors run mock traceability exercises against exactly this record, following one batch code forward and one output lot backward, and a record that cannot support that trace is a direct finding regardless of how complete it looks.

How to complete it

How to complete a production order record, step by step

The fields ask whether materials, process and output were recorded. They do not settle the judgement calls that decide whether the record can actually support a trace afterwards.

Record batch codes at the point of issue, not at reconciliation

The code is only genuinely captured if recorded when the material is issued, with the pallet or drum in front of the person doing it. Reconstructing codes at shift end from a goods-in register produces a plausible record that may not match what was actually consumed, especially where more than one batch of an input was open at once.

Decide what reconciliation within tolerance actually means for this product

A generic tolerance applied to every product hides genuine variance on yield-critical processes and false-alarms on ones with normal trim loss. The field has to be answered against a tolerance set for the specific product, or it either misses a real material loss or manufactures a finding out of ordinary variation.

Capture a deviation at the moment it happens, with the correction, not just the fact

A deviation written up hours later usually states that something happened, without the parameter values, the duration, or what correction was applied. That detail is what a root cause investigation actually needs, and it is why the field asks for it at the time rather than in retrospect.

Treat the reconciliation gap between issued and consumed as a finding, not a rounding error

Material issued but neither consumed nor returned has gone somewhere unaccounted for. Closing the order without resolving that gap, on the assumption it will average out over the week, is how a genuine loss or diversion stays invisible until a stock count finds it much later.

What auditors find

Most common production order record findings

Production order record findings are rarely about a missing field. They are about a field completed after the fact, in a way that cannot be told apart from one completed at the time.

FindingClauseWhat fixes it
Batch codes recorded from the goods-in register rather than from what was actually issued to the order.ISO 9001 cl.8.5.2Capture the batch code at the point of issue to the order, from the material in hand.
Reconciliation marked within tolerance against a single tolerance applied to every product.ISO 9001 cl.8.5.1(f)Set a tolerance per product or process family, and record which one was applied.
A process parameter excursion was corrected and the line kept running, with no deviation recorded.ISO 9001 cl.8.5.1(f)Record every excursion at the time, with the value, duration and correction applied.
Material issued to the order was neither consumed, scrapped nor returned, and the gap was not investigated.ISO 9001 cl.8.5.1(a)Close every issued quantity to a destination before the order is marked complete.
Output batch codes applied inconsistently, so two pallets from the same run carry different lot identifiers.ISO 9001 cl.8.5.2Apply the output batch code at a single defined point in the process, consistently.
Retained samples not linked to the specific output batch code they represent.ISO 9001 cl.7.5.3.2Record the output batch code against the retained sample at the time it is taken.
Order record completed after the shift ended, from a supervisor's verbal account.ISO 9001 cl.8.5.1(f)Complete the record as the order runs; a written account after the fact is a reconstruction.
Scrap recorded as a single total figure rather than by reason.ISO 9001 cl.8.7Record scrap by reason at the point it is generated, feeding the dedicated scrap record.
Yield calculated from planned quantities rather than the actual materials issued and consumed.ISO 9001 cl.9.1.3Calculate yield from what was actually issued and actually produced, not from the plan.
Despatch or storage location not recorded, so finished output cannot be traced forward from the order.ISO 9001 cl.8.5.2Record the destination at the point output leaves the line, not from a later stock system query.

Case in point

Case in point: the batch code that was one shift late

A dairy processor ran a cultured product across two orders on consecutive days, using two different lots of the same starter culture. The line lead on day one recorded the culture batch code correctly, at the point it was added. On day two, the starter culture delivery was late, the order started anyway on the remaining stock of the previous lot, and when the new lot arrived partway through, nobody updated the record. The order was closed showing a single batch code for the whole run.

A complaint arrived three weeks later about an off-flavour in product from day two. The recall team needed to isolate which portion of the day-two run used which culture lot, because only one of the two lots was implicated by the supplier's own investigation. The order record showed one code, not two, and the only way to narrow the affected quantity was to interview the line lead about when, approximately, the delivery had arrived and been added.

The recall that should have isolated a few hours of production instead covered the entire day-two run, because the record could not make the distinction the actual event required. The corrective action was not a new field; the field for batch code already existed. It was a rule that a mid-order material change gets a new line in the record at the time it happens, not a single code chosen at reconciliation to represent the whole order.

The template

The template, field by field

The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.

58fields
6 sections
Reference
OPS-008
Archetype
Record
Record ID
PORD-2026-000
Scoring
Orders reconciled
Direction
High is good
Singleton
Yes
Basis
ISO 9001 cl.8.5.1
Links
Links Traceability, Scrap Record, Daily Production Report
Tags
Production, Order, Traceability
Sections
6
Fields
58
Follow up fields
3
Repeating sections
0
Links out
6
Field typesOwn ID, generated on saveCase thread and parentPick list from a registryLinked to another templateFollow up, dashed outlineScored

Header

18 fields
Text

Order ID*

Generated on save

Auto sequence. Format PORD-2026-000.

The record's own ID. Other templates point at this value.

Single Choice

Status*

Scored

Drives who this goes to next.

  • Planned2 pts
  • In progress2 pts
  • Complete3 pts
  • Deferred0 pts
  • Open0 pts
  • Closed3 pts
  • Overdue0 pts
Date & Time

Date and Time*

Users

Completed By*

Pick List

Site*

From FDN-001 Site NameFilter: Status is Active
Text

Site ID*

Linked

Format SITE-000.

Links to FDN-001 Site ID

Single Choice

Area

Optional

The area within the site.

Cutting roomBoning hallPackingChill storeFreezerPasteurisingFillingCulture roomDespatchYardWorkshopPlant roomOffices
Location

Exact Location

Optional

Drop a pin for anything hard to find.

Text

Production Order Number*

Text

Product

Optional
Numeric Answer

Quantity Ordered*

Date & Time

Started*

Date & Time

Finished

Optional
Text

Batch Or Lot Number*

Single Choice

Line*

Line 1Line 2Line 3Line 4Line 5
Users

Line Lead*

Numeric Answer

Quantity Produced

OptionalScored
Info

Reconstructed Afterwards From Memory

Traceability depends on this record, and it is the one most often written up at the end of the shift from what somebody remembers. Recording it as it happens is the whole point.

Materials

6 fields
Single Choice

All Materials Verified Against The Order*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Batch Codes Of Every Input Recorded*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Rework Or Carry Over Recorded*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Quantities Issued Recorded*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Unused Material Returned And Recorded*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Reconciliation Within Tolerance*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator

Process

6 fields
Single Choice

Recipe Or Specification Version Recorded*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Process Parameters Within Range*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Critical Control Records Complete*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

In Process Checks Completed*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Deviations Recorded At The Time*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Equipment Used Recorded*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator

Output

6 fields
Single Choice

Good Quantity Recorded*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Scrap Recorded By Reason*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Yield Calculated*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Output Batch Codes Applied*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Despatch Or Storage Location Recorded*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Samples Retained*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator

Related records

3 fields
Text

Daily Report ID

OptionalLinked

The report this order feeds.

Links to OPS-012 Report ID

Text

Scrap Record ID

OptionalLinked

Waste generated on this order.

Links to OPS-011 Record ID

Text

Quality Scrap Record ID

OptionalLinked

Where scrap was raised as a quality record.

Links to QUA-005 Scrap ID

Outcome

19 fields
Numeric Answer

Yield Percent

OptionalScored
Numeric Answer

Material Variance

OptionalScored
Single Choice

Reconciliation Acceptable*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Order Complete*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Text

Scrap Record ID

OptionalLinked

Links to OPS-011 Record ID

Text

Traceability Reference

OptionalLinked

Links to QUA-073 Trace ID

Numeric Answer

Items Assessed*

Excludes anything marked N/A.

Numeric Answer

Items Failed*

Numeric Answer

Score Percent*

Scored

Calculated on submission. High is good. N/A items leave the denominator.

Single Choice

Result Band*

Scored
  • Pass3 pts
  • Caution1 pt
  • Fail0 pts
Numeric Answer

Completeness Percent*

How much of the template was actually answered. A high score on a half completed form is not a high score.

Single Choice

Action Required*

Scored

Raise the action record, then enter its reference here.

  • No2 pts
  • Yes0 pts
Single Choice

Priority

OptionalScoredShows if Action Required equals Yes
  • High0 pts
  • Medium1 pt
  • Low3 pts
Text

CAPA ID

OptionalLinkedShows if Action Required equals Yes

Format CAPA-2026-00000.

Links to FDN-014 CAPA ID

Users

Action Owner

OptionalShows if Action Required equals Yes
Users

Line Lead*

Signature

Signature*

Users

Production Manager*

Signature

Second Signature*

OPS-008 · record IDs look like PORD-2026-000 · Links Traceability, Scrap Record, Daily Production Report

Open in Knowella

Run it with agents

From a document you fill in to a programme that runs itself

The record is one order's account. What actually fails is the same account being reconstructed too late to be trustworthy, and the links to scrap and traceability going stale.

KnowOps

Holds the production order library against the schedule, flags a record still open after its expected finish time, and routes it to the line lead.

KnowQuality

Runs the mock traceability exercise against this record's batch codes, one step back and one step forward, before an auditor asks for it.

KnowMaintain

Correlates recorded process deviations against the equipment used, so a recurring excursion on the same line gets investigated as equipment, not operator, cause.

Ella
Ella

Flags a reconciliation that has not closed and a deviation logged well after the order's Started time, before the order is marked complete.

This template lives in KnowOps — frontline execution. Shift handover, production control, daily management, worker lifecycle and improvement.

Meet KnowOps→

Glossary

Production Order Record definitions and key terms

Batch or lot number
The unique identifier applied to a defined quantity of material, input or output, that allows it to be traced to its origin and its destination.
Reconciliation
Accounting for everything issued to an order as good product, scrap, or returned unused material, so nothing is left unexplained.
Yield
The ratio of good output to material input, calculated from actual issued and produced quantities rather than planned ones.
Deviation
A departure from the specified process, recipe or parameter range during the order, recorded with what happened and what was done about it.
In-process check
A verification performed while the order runs, confirming a parameter or characteristic is within range before production continues.
One step back, one step forward
The traceability principle that a business must identify its immediate supplier and immediate customer for any batch, the minimum most food law requires.
Nonconforming output
Product that does not meet requirements, which must be identified and controlled to prevent unintended use, per ISO 9001 cl.8.7.
Mass balance
The audit technique of tracing a quantity of raw material through to finished product and waste, used to test whether a traceability system actually reconciles.

FAQ

Frequently asked questions about production order record

Can the production order record be completed at the end of the shift?+

It can be, but it should not be treated as equivalent to one completed as the order runs. Batch codes, deviations and parameter excursions are the details a shift-end reconstruction loses first, and they are exactly the details a traceability or root cause exercise needs most.

What if reconciliation does not come within tolerance?+

Investigate before closing the order, not after. A reconciliation gap is the first visible sign of material going somewhere unaccounted for, whether that is measurement error, unrecorded scrap, or a genuine loss, and closing the order regardless converts a finding into a fact nobody looked at.

How does this record relate to the Daily Production Report?+

The daily report aggregates every order and line into a shift total. It depends on this record's figures being correct; a wrong order record produces a wrong daily total downstream.

What happens if the input material lot changes partway through an order?+

The change needs its own entry at the time it happens, with both lot codes and the point of changeover, rather than the order being closed under a single batch code chosen afterwards. Otherwise a recall cannot isolate which part of the run used which input.

Should scrap be recorded here or on the Scrap and Waste Record?+

Both, at different levels. This record needs the order's own scrap figure and reason to support reconciliation and yield; the Scrap and Waste Record itemises waste in more detail and feeds trend reporting across orders.

Does traceability require a batch code on the output as well as the inputs?+

Yes. One step back is the input batch codes; one step forward is the output batch code and where it went. A record with input codes but no consistent output code can trace backward from a complaint but cannot trace forward from a supplier recall of a raw material.

Keep going

Related templates and programmes

Industries this is written for

Siddarth Singh

Written and reviewed by

Siddarth Singh

Founder & Chief Executive Officer, Knowella

Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.

  • Certified Safety Professional (CSP), Board of Certified Safety Professionals
  • MBA, University of Chicago Booth School of Business
  • MS and BS, The Ohio State University, Industrial and Systems Engineering
  • Six Sigma Black Belt
Verify with BCSP →

Sources and last review. Reviewed 16 August 2026 against:

  • ISO 9001:2015 clauses 8.5.1, 8.5.2, 8.7 and 9.1.3
  • ISO 22000:2018 clause 8.5.2, traceability system
  • Regulation (EC) 178/2002, article 18, general food law traceability
  • FDA FSMA rule for food traceability, 21 CFR Part 1, Subpart S
  • FDA 21 CFR Part 117, current good manufacturing practice
  • Safe Food for Canadians Regulations, traceability requirements
  • BRCGS Global Standard for Food Safety, traceability requirements

This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.

Start in Minutes, Not Weeks

Launch a Ready-Made Template and Customize It Your Way

Every template is fully editable. Adjust fields, workflows, and branding to match your processes, then deploy to your team instantly.