What this is
What is a production trial in food manufacturing?
What is a production trial in food manufacturing?
A production trial is a controlled run of a new or changed product on the actual manufacturing line, at normal speed and with normal operators, used to confirm the product and the line perform as expected before committing to full production. It differs from a development kitchen or pilot-scale test because it exposes the product to real changeovers, real cleaning cycles and real shift conditions.
What is a production trial record?
It is the record used in KnowQuality that captures a trial run of a new or changed product on the real line, covering planning, the run itself, results and the conclusion reached. It is built against BRCGS cl.5.1 and forms part of the Labelling and Packaging and Change Control programmes.
Why does a trial need success criteria agreed before it runs?
Criteria written after the trial are criteria the trial passed by definition, because they were chosen with the result already known. Agreeing what counts as success beforehand is what makes the trial's Approved To Proceed decision defensible rather than retrospective.
Scope
When is a production trial record required?
This record documents one trial run. Using it to record the gate decision that authorised the trial, or the shelf life and sensory work that ran alongside it, produces a trial record that duplicates other templates and references that go nowhere.
Use this template when
- A new product, recipe, process, equipment or supplier change is about to run on the real line for the first time
- The gate review recorded Trial Completed as Planned and now needs the Trial Record ID it referenced to exist
- Production and technical need a documented basis for the Approved To Proceed decision before full production starts
- The trial reveals a need for a specification, artwork or process change that has to be picked up in change control
- A linked record needs this one to exist: NPD gate, change control
Do not use it for
- New Product Development Gate Review, which records the wider go or no-go decision the trial is one input into, not the trial run itself
- Shelf Life Study Record, which records the study that establishes or extends a shelf life, covering storage conditions, test points and criteria
- Challenge Test Record, which records a deliberate inoculation study to confirm the product controls the organism of concern across its life
- Sensory Evaluation Record, which records a structured taste, smell and appearance assessment against a reference standard, referenced here only by its record ID
- Anything outside KnowQuality, which belongs in the workspace that owns that process
Compliance mapping
Which BRCGS cl.5.1 requirements does this satisfy?
The clause references below anchor the record to BRCGS cl.5.1; the trial is treated as evidence feeding the gate decision rather than a separate certification requirement in its own right.
| Clause | Requirement | Where it lands |
|---|---|---|
| BRCGS cl.5.1 | A new or changed product is trialled under representative conditions before full production begins | Running the trial |
| BRCGS cl.5.1 | Success criteria and food safety clearance are agreed before the trial runs, not fitted to the result afterwards | Planning |
| BRCGS cl.5.1 | Trial material is segregated, labelled and its disposition decided before the run so it cannot be released undecided | Planning |
| BRCGS cl.5.1 | Process parameters, yield and downtime are recorded during the run so the trial produces evidence rather than an impression | Running the trial |
| BRCGS cl.5.1 | The product is checked against specification and the line's rate and yield performance assessed | Results |
| BRCGS cl.5.1 | A documented conclusion is reached — approved, approved with conditions, or not approved — with any specification update captured | Conclusion |
| BRCGS cl.5.1 | Any change identified by the trial is picked up under change control before implementation rather than carried informally into full production | Conclusion |
| BRCGS cl.5.1 | Site, line and batch identity are captured against the trial so it can be traced back to a specific run | Header |
What it does not cover
- Success Criteria Agreed Beforehand answered After, which means the criteria the trial was judged against were chosen once the result was already known.
- Trial Product Disposition left as Sellable with Trial Product Status Decided answered Decided after, which lets stock leave the trial before anyone had committed to what should happen to it.
- Run By Normal Operators answered Technical staff while Approved To Proceed is marked Yes unconditionally, which treats a trial run by the people best equipped to make it succeed as proof an ordinary shift can repeat it.
- Further Trial Required answered Yes with no second Trial ID anywhere in the register, which leaves the acknowledged gap with nothing tracking it closed.
- Hold ID left blank when Trial Product Disposition is Destroy or Rework, which removes the record's link to the hold that should have controlled that material until disposition was confirmed.
Global
Production Trial Record requirements by country
A production trial has no standalone statutory trigger; its consequence runs through the certification and customer relationships the product is destined for.
BRCGS Global Standard for Food Safety
Auditors treat the trial record as the physical-evidence half of a gate decision that showed Trial Completed as Yes; a gate that references a trial ID which does not exist, or which shows a reduced-rate run, is treated as an open finding.
The trial record is what turns a paper gate decision into something a certification body will accept as tested.
FDA Food Safety Modernization Act — Preventive Controls for Human Food, 21 CFR Part 117
Where a trial changes a process step that is a preventive control, the trial's results feed the site's hazard analysis and process preventive controls rather than sitting only in a quality file.
A trial that surfaces a new hazard or control point failure needs to reach the HACCP or food safety plan, not stop at Problems Encountered as free text.
Individual retailer technical and new-product-introduction standards
Major retailers often require documented production trial evidence, including yield and rate data, before accepting a new SKU into their supply chain, independent of certification scheme.
A thin trial record — no parameters, no yield, no downtime — can stall a listing even when the gate review itself shows Proceed.
How to complete it
How to complete a production trial record, step by step
Every field can be filled in without the trial having actually proven anything. These are the judgement calls that decide whether it did.
Run At Normal Line Speed marked Reduced does not block Approved To Proceed from being Yes. Deciding whether a below-rate trial is still sufficient evidence, or whether it only supports a conditional approval pending a second trial at rate, is a judgement the template surfaces but leaves to the signatories.
Operator Feedback Captured accepts Informally as an answer with the same downstream weight as a formal capture. Whether an informal conversation after the shift is enough evidence for a launch decision, versus a documented debrief, is a call the trial's authors have to make deliberately.
Specification Updated can be answered Yes without a linked MOC or change record anywhere on the form. Deciding whether a specification change discovered mid-trial needs formal change control before it is applied, or can be folded into this record's conclusion, changes who else needs to sign off.
Trial Product Disposition and Approved To Proceed are recorded independently. A trial that disposes its output as Destroy while still recording Approved To Proceed as Yes needs the disposition explained in the narrative, or the record reads as contradictory to anyone auditing it later.
What auditors find
Most common production trial record findings
These are the patterns that recur when trial records are audited against what actually happened on the floor.
| Finding | Clause | What fixes it |
|---|---|---|
| Trials recorded as run at normal line speed and by normal operators when shift logs show the trial ran on an overtime shift staffed by technical and engineering. | BRCGS cl.5.1 | Cross-check Run By Normal Operators and Run At Normal Line Speed against the shift roster before the trial record is signed off. |
| Success Criteria Agreed Beforehand answered Yes with the criteria text added to the record on the same date as the trial results. | BRCGS cl.5.1 | Timestamp the Planning section separately from Results so the sequence is visible rather than inferred. |
| Downtime Recorded left blank on trials that other line records show stopped for over an hour. | BRCGS cl.5.1 | Make Downtime Recorded required whenever the line's own stoppage log shows an event during the trial window. |
| Trial Product Disposition marked Sellable on batches where Product Met Specification is Partly. | BRCGS cl.5.1 | Block a Sellable disposition unless Product Met Specification is Yes, forcing Partly results to Sample only or Rework. |
| Sensory Record ID left blank when Sensory Evaluation Done is marked Yes. | BRCGS cl.5.1 | Require Sensory Record ID whenever Sensory Evaluation Done is Yes so the linked assessment can be checked. |
| Further Trial Required answered Yes with no follow-up Trial ID raised within the same development project inside three months. | BRCGS cl.5.1 | Report open Further Trial Required flags against the project register on a fixed review cycle rather than leaving them to be found. |
Case in point
Case in point: the trial that proved the recipe, not the line
A dairy site trialled a new cultured milk formulation using technical staff on an off-shift, running well below normal rate to keep close control over the process. Product Met Specification was recorded Yes, and Approved To Proceed was signed as Yes on the strength of that result.
Full production three weeks later used normal operators at normal rate, and the product's texture failed specification at the first changeover — a condition the trial never tested, because it never ran a changeover and never used the operators who would actually run the line day to day.
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.
6 sections
- Reference
- QUA-100
- Archetype
- Record
- Record ID
- TRL-2026-000
- Scoring
- Trials successful
- Direction
- High is good
- Singleton
- Yes
- Basis
- BRCGS cl.5.1
- Links
- Links NPD gate, Change control
- Tags
- Development, Trials
- Sections
- 6
- Fields
- 56
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 4
Header
16 fieldsTrial ID*
Auto sequence. Format TRL-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Raised By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Line*
Shift*
Line Lead
Batch Number*
Numeric key joining to your ERP batch record.
Links to External system reference
Product*
Production Date*
Pilot Scale Tells You Almost Nothing
A product that works in a development kitchen behaves differently on a line running at rate, with real changeovers, real temperature and real people.
Product Or Change Trialled*
Trial Purpose*
Trial Quantity*
Planning
6 fieldsTrial Protocol Written*
- Yes3 pts
- Verbal only1 pt
- No0 pts
Success Criteria Agreed Beforehand*
Criteria written after the trial are criteria the trial passed.
- Yes3 pts
- After0 pts
Food Safety Cleared For Trial*
- Yes3 pts
- No0 pts
Trial Product Status Decided*
Sellable, sample only, or destroy. Decided before the run, not after somebody sees how much there is.
- Decided beforehand3 pts
- Decided after0 pts
Trial Material Segregated And Labelled*
- Yes3 pts
- Partly1 pt
- No0 pts
Line And Time Agreed With Production*
- Yes3 pts
- No0 pts
Running the trial
9 fieldsRun At Normal Line Speed*
- Yes3 pts
- Reduced1 pt
- Much reduced0 pts
Run By Normal Operators*
- Yes3 pts
- Mixed1 pt
- Technical staff0 pts
Duration Long Enough To Be Meaningful*
- Yes3 pts
- Marginal1 pt
- No0 pts
Process Parameters Recorded*
- Yes3 pts
- Partly1 pt
- No0 pts
Yield Measured*
- Yes3 pts
- Estimated1 pt
- No0 pts
Downtime Recorded*
- Yes3 pts
- No0 pts
Changeover Tested
- Yes3 pts
- No0 pts
Cleaning Tested
- Yes3 pts
- No0 pts
Operator Feedback Captured*
- Yes3 pts
- Informally1 pt
- No0 pts
Results
6 fieldsProduct Met Specification*
- Yes3 pts
- Partly1 pt
- No0 pts
Rate Achieved*
- Yes3 pts
- Marginal1 pt
- No0 pts
Yield Acceptable*
- Yes3 pts
- Marginal1 pt
- No0 pts
Problems Encountered
Sensory Evaluation Done
Sensory Record ID
Links to QUA-098 Record ID
Conclusion
6 fieldsSuccess Criteria Met*
- All3 pts
- Most1 pt
- Few0 pts
Further Trial Required*
- No3 pts
- Yes1 pt
Approved To Proceed*
- Yes3 pts
- With conditions2 pts
- No0 pts
Trial Product Disposition*
Hold ID
Links to QUA-003 Hold ID
Specification Updated*
- Yes3 pts
- Not needed3 pts
- No0 pts
Result
13 fieldsItems Assessed*
Excludes anything marked N/A.
Items Failed*
Score Percent*
Calculated on submission. High is good. N/A items leave the denominator.
Result Band*
- Pass3 pts
- Caution1 pt
- Fail0 pts
Completeness Percent*
How much of the template was actually answered. A high score on a half completed form is not a high score.
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Technical*
Signature*
Production Manager*
Second Signature*
QUA-100 · record IDs look like TRL-2026-000 · Links NPD gate, Change control
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form captures what happened on the line. Checking that it actually reflects normal conditions, chasing the linked change record, and catching a disposition that contradicts its own specification result is the work that actually slips.
Holds the trial register against the gate review and change control records it links to, and flags a trial marked Approved To Proceed with no matching specification or MOC update.
Cross-checks Run At Normal Line Speed and Downtime Recorded against the line's own maintenance and stoppage logs, so a trial can't quietly under-report how the equipment actually behaved.
Flags a trial run by technical staff rather than normal operators, and tracks the operator training gap that a Mixed or Technical staff answer is usually pointing at.
Coordinates production, technical and the line before the trial starts, rolls the planning checklist into one view, and holds every write for your approval before it touches the record.
This template lives in KnowQuality — quality and food safety. HACCP, nonconformance, traceability, laboratory and customer complaints.
Meet KnowQuality→Glossary
Production Trial Record definitions and key terms
- Rate
- The speed at which a line is designed to run in normal production, as distinct from a slower speed used to make a trial easier to control.
- Changeover
- The transition between products or configurations on a line, often the point where contamination, allergen carryover or setup errors occur.
- Disposition
- The decision on what happens to material produced during a trial — released as sellable stock, kept as a sample, reworked, or destroyed.
- Yield
- The proportion of usable finished product obtained from the input material run through the trial, used to judge whether the process is commercially viable at scale.
- Hold
- A status placed on material to prevent its release or use while its disposition is decided, referenced here by the linked hold record.
FAQ
Frequently asked questions about production trial record
What is the production trial record template based on?+
It is built against BRCGS cl.5.1, the clause governing product development, formulation and reformulation, of which the production trial is the physical evidence stage.
What sections does the production trial record contain?+
There are 6 sections: Header, Planning, Running the trial, Results, Conclusion, Result. Together they hold 56 fields, 45 of which are required.
When should a production trial be run?+
Before first production of a new or changed product, recipe, process, equipment or supplier change — not reconstructed afterwards from memory once the run has already happened.
Which programme does the production trial record belong to?+
It sits in both Labelling and Packaging and Change Control, because a trial commonly triggers a specification, artwork or process change that needs its own change record.
How is a production trial record scored?+
Scoring is trials successful, where high is good. It rolls up planning discipline, run conditions and results into one figure, but Approved To Proceed is the decision that actually matters.
Can the production trial record template be changed?+
Yes. Every field, option, score and conditional rule is editable, and the links to the gate review and change control come with it. Most teams run it as supplied for a cycle before adjusting which fields are required at which trial type.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Labelling and Packaging
Product and SKU Register
Holds every product and pack format you make, with its specification, allergens, shelf life and customer
Label Verification Record
Verifies that the label on the line matches the specification for that product, covering allergens, claims, dates and barcodes
Artwork Approval Record
Records approval of new or amended artwork before it is printed, with each checker named
Date Coding Verification
Verifies date and batch coding is present, legible, correct and in the right position
Packaging Material Inspection
Inspects incoming packaging for damage, contamination, correct print and food contact compliance
Packaging Reconciliation Record
Reconciles packaging and label quantities issued, used and returned at the end of a run
More in Shelf Life
Shelf Life Study Record
Records the study that establishes or extends a shelf life, covering storage conditions, test points and criteria
Challenge Test Record
Records a deliberate inoculation study to confirm the product controls the organism of concern across its life
Sensory Evaluation Record
Records a structured taste, smell and appearance assessment against a reference standard
New Product Development Gate Review
Reviews a product at each development gate for food safety, legality, capability and shelf life before it moves on
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
Sources and last review. Reviewed 16 August 2026 against:
- BRCGS Global Standard for Food Safety, Issue 9 — Clause 5.1, Product Development, Formulation and Reformulation
- FDA Food Safety Modernization Act — Preventive Controls for Human Food, 21 CFR Part 117
- GFSI Benchmarking Requirements, Version 2020.1
- Codex Alimentarius CXC 1-1969 — General Principles of Food Hygiene
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.