What this is
What is a label verification record?
What is a label verification record?
It is a line-side checklist confirming that the label currently being applied matches the approved specification for the product running, including the ingredient list, allergen declaration, claims, date coding and barcode. It is not the artwork sign-off, which happens once before print; it is the repeated check that the right, already-approved label is the one actually on the pack.
Why does this need two checkers rather than one?
A single checker verifying their own changeover is checking their own work, which is exactly the condition under which a wrong label survives to run. The second, independent signature exists to catch what fatigue, familiarity or time pressure hide from the first person, and it is the control BRCGS expects at this point.
What counts as a reference sample here?
A reference sample is a current, signed-off master label kept at the line for direct visual comparison, not a memory of what last week's pack looked like or a photo on a phone. Comparing against a stale or missing master is the most common reason a correct-looking verification still misses a change.
Scope
When is a label verification record required?
This is the line-side check that a label matches spec, run repeatedly through production. It is not artwork sign-off, not the changeover clean, and not the date-code check on its own — using it for those blurs the record trail each one is meant to produce.
Use this template when
- A changeover has just happened, or is about to happen, and the new label needs checking before the run starts
- The run is in progress and a periodic label check is due
- A previous verification found an issue and the line needs re-checking before it can be released
- The workspace is being set up and this register needs an entry added or retired
- A linked record needs this one to exist, such as the product register or the changeover log
Do not use it for
- Artwork Approval Record, which signs off new or amended artwork before it is ever printed, with each checker named — this record checks the printed label already on the line.
- Allergen Changeover Check, which manages segregation and cleaning at changeover — this record checks what ends up printed on the pack, not what is on the line surfaces.
- Date Coding Verification, which is the deeper check on date and batch coding alone — use it when coding itself, not the whole label, is in question.
- Packaging Material Inspection, which inspects incoming packaging stock for damage and print quality before it ever reaches the line.
- Anything outside KnowQuality, which belongs in the workspace that owns that process.
Compliance mapping
Which BRCGS cl.5.2 requirements does this satisfy?
BRCGS cl.5.2 sets the expectation that label content is checked against specification at the point it is applied, not only when artwork is first approved. The clauses below map that expectation onto this template's sections.
| Clause | Requirement | Where it lands |
|---|---|---|
| BRCGS cl.5.2 | The applied label matches the approved specification for the product running | Label content |
| BRCGS cl.5.2 | Allergens are declared as used in the current recipe, not the specification on file | Label content |
| BRCGS cl.5.2 | Date and batch coding are present, legible and correctly positioned | Codes and print |
| BRCGS cl.5.2 | The barcode scans correctly against the product record | Codes and print |
| BRCGS cl.5.2 | Verification is carried out independently by two people, not one signing twice | Control |
| BRCGS cl.5.2 | Labels from the previous product are removed from the line before the new run starts | Control |
| BRCGS cl.5.2 | Label reconciliation is completed and the line is formally released for labelling | Control |
| BRCGS cl.5.2 | Any nonconformance is scored, held and actioned rather than left open | Result |
What it does not cover
- Verified Independently By Two People, which shows One person only, is the single-checker gap this record exists to close.
- Previous Product Labels Removed From Line, which shows Partly, leaves the last product's allergen declaration within reach of the next run.
- Reference Sample Used For Comparison, which shows No, means the check was made against memory rather than a signed-off master label.
- Allergen Declaration Correct, which fails against the current recipe rather than an outdated specification, is the finding a recall investigation looks for first.
- Incorrect Label Reached Product, which shows Yes with no Hold ID entered, leaves affected stock unlocated while it is still moving through the site.
Global
Label Verification Record requirements by country
Label verification sits under BRCGS globally, but what a wrong label actually triggers downstream depends on where the product ships.
Natasha's Law (Food Information Amendment 2019) and FIC retained regulation
Full ingredient and allergen labelling is mandatory on prepacked-for-direct-sale food, closing the loop this record is meant to protect on the line.
A missed allergen emphasis here is not a paperwork gap in the UK; it is the direct precursor to the incident the law was written after.
Regulation (EU) No 1169/2011, the Food Information to Consumers Regulation
Sets the mandatory particulars — allergens, nutrition, claims, country of origin — that this template checks field by field.
Country of origin and claims checks in the Label content section exist because FIC makes both enforceable, not optional, on most prepacked product.
FALCPA and the FASTER Act (sesame as the ninth major allergen)
Defines which allergens must be declared and how; a specification that has not caught up with a recipe change is an FALCPA gap, not a formatting error.
Where sesame or another of the nine major allergens is present, checking against the current recipe rather than a stale specification is the control this law actually requires.
How to complete it
How to complete a label verification record, step by step
Filling in every field is the easy part. The judgement calls below decide whether a completed record would hold up if a mislabelled pack were ever traced back to it.
Minor difference is scored above a flat No, which is right for a font-weight variance and wrong for anything touching allergens, claims or net quantity. Whoever completes this needs a shared, written line on which differences are minor before the option is used as a way to avoid a fail.
A master label at the line is only useful if it was updated the last time the specification changed. A verification that compares against a superseded master will pass cleanly while checking against the wrong target, which is worse than not comparing at all.
Independence means the second checker looks at the pack themselves, separately, not that they countersign the first checker's opinion. A second signature obtained by walking a form around the office after the run has already started does not meet this bar even though the field reads Yes.
Quantity Affected and Product Location only appear once Incorrect Label Reached Product is Yes, and both need an honest, not optimistic, answer. Understating either is how a hold that should cover a full pallet ends up covering a shelf.
What auditors find
Most common label verification record findings
These are the patterns that recur across sites running this template, not a list of every possible answer.
| Finding | Clause | What fixes it |
|---|---|---|
| Verified Independently By Two People is marked One person only at changeover more often than at any other verification point. | BRCGS cl.5.2 | Roster the second checker before the changeover starts, not after the run is already underway. |
| Allergen Emphasis Present is regularly left at Partly rather than escalated. | BRCGS cl.5.2 | Treat Partly as a hold condition on allergen fields specifically, even though the option itself scores above zero. |
| Reference Sample Used For Comparison is answered No on changeovers where no master label was mounted at the line. | BRCGS cl.5.2 | Make a current master label a changeover prerequisite, checked before the first pack runs, not during verification. |
| Country Of Origin Correct is frequently left blank, since the field is not marked required. | BRCGS cl.5.2 | Make the field mandatory for any product shipping into a market where origin marking is enforced. |
| Label Reconciliation Done is left at Deferred across multiple records for the same batch. | BRCGS cl.5.2 | Close reconciliation within the same shift; a batch should not carry more than one deferred reconciliation forward. |
| Incorrect Label Reached Product is marked Yes with the Hold ID field left empty. | BRCGS cl.5.2 | Require a Hold ID before the record can be submitted whenever this field is Yes. |
Case in point
Case in point: the master label nobody updated
A specification changed to add a new stabiliser, and the allergen declaration moved with it. The master label at the line, however, was the version printed before the change — nobody had swapped it when the new spec went live. Every verification for two shifts compared the new label against that old master and passed, because the two matched each other perfectly. They just no longer matched the product actually being made.
The gap only surfaced when a customer complaint referenced an ingredient that wasn't on the pack. The verification records for both shifts read Yes, Yes, Yes down the column — a paper trail that looked exactly like the system working, because the check was comparing the label to the wrong thing rather than not comparing it at all.
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-089
- Archetype
- Checklist
- Record ID
- LVR-2026-000
- Scoring
- Verification pass rate
- Direction
- High is good
- Singleton
- Yes
- Basis
- BRCGS cl.5.2
- Links
- Links Product register, Changeover
- Tags
- Labelling
- Sections
- 6
- Fields
- 59
- Follow up fields
- 6
- Repeating sections
- 0
- Links out
- 6
Header
16 fieldsVerification ID*
Auto sequence. Format LVR-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*
The Leading Recall Cause
More product is recalled for the wrong label than for anything else. Two people check, independently, and both sign. One person checking their own changeover is how it goes wrong.
Verification Point*
Start up, changeover, periodic during run, or end of run.
Product Code*
Product ID*
Links to FDN-022 Product Code
Label content
12 fieldsLabel Matches Specification*
- Yes3 pts
- Minor difference1 pt
- No0 pts
Product Name Correct*
- Yes3 pts
- No0 pts
Pack Size Correct*
- Yes3 pts
- No0 pts
Ingredient List Correct*
- Yes3 pts
- No0 pts
Allergen Declaration Correct*
Checked against the actual recipe in use today, not against what the specification said last year.
- Yes3 pts
- No0 pts
Allergen Emphasis Present*
- Yes3 pts
- Partly1 pt
- No0 pts
Nutritional Panel Correct*
- Yes3 pts
- No0 pts
Claims Correct And Supported*
- Yes3 pts
- Unsupported claim0 pts
Country Of Origin Correct
- Yes3 pts
- No0 pts
Storage Instructions Correct*
- Yes3 pts
- No0 pts
Cooking Instructions Correct
- Yes3 pts
- No0 pts
Legal Marks Present*
- Yes3 pts
- Partly1 pt
- No0 pts
Codes and print
6 fieldsDate Code Correct*
- Yes3 pts
- No0 pts
Batch Code Correct*
- Yes3 pts
- No0 pts
Barcode Scans Correctly*
- Yes3 pts
- Intermittent1 pt
- No0 pts
Print Legible*
- Yes3 pts
- Marginal1 pt
- No0 pts
Label Position Correct*
- Yes3 pts
- Marginal1 pt
- No0 pts
Label Adhesion Adequate
- Yes3 pts
- Marginal1 pt
- No0 pts
Control
10 fieldsReference Sample Used For Comparison*
A signed off master label at the line removes the argument about what correct looks like.
- Yes3 pts
- No0 pts
Previous Product Labels Removed From Line*
- Yes3 pts
- Partly1 pt
- No0 pts
Label Reconciliation Done*
- Yes3 pts
- Deferred1 pt
- No0 pts
Verified Independently By Two People*
- Yes3 pts
- One person only0 pts
Second Checker*
Line Released For Labelling*
- Yes3 pts
- Held0 pts
Incorrect Label Reached Product*
- No3 pts
- Yes0 pts
Quantity Affected
Hold ID
Raise the hold record, then enter its reference.
Links to QUA-003 Hold ID
Product Location
Where the affected product physically is right now.
Related records
2 fieldsArtwork Approval ID
The approved artwork this label was checked against.
Links to QUA-090 Approval ID
Coding Verification ID
The date code check for the same run.
Links to QUA-091 Verification ID
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
Operator*
Signature*
Second Checker*
Second Signature*
QUA-089 · record IDs look like LVR-2026-000 · Links Product register, Changeover
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form itself is not where this breaks. It breaks when the master label goes stale, the second signature is a formality, or a hold never gets a location — none of which a static checklist catches on its own.
Flags when a reference sample hasn't been updated against the latest specification, and keeps changeover verification linked to the product register so a stale master can't quietly pass a check.
Traces where affected stock physically sits once a hold is raised from this record, so Quantity Affected and Product Location reflect what is on the floor, not what is remembered.
Confirms the named second checker was rostered and on shift at the time of the changeover, so independence is verifiable rather than assumed from a signature alone.

Rolls verification pass rate and open holds from this template into one view across sites, and holds every write for your approval before it touches a live record.
This template lives in KnowQuality — quality and food safety. HACCP, nonconformance, traceability, laboratory and customer complaints.
Meet KnowQuality→Glossary
Label Verification Record definitions and key terms
- Label verification
- The line-side check that the label actually applied to a running product matches its approved specification, repeated at defined points through a run.
- Reference sample
- A current, signed-off master label kept at the line for direct comparison, distinct from the artwork file or the specification document.
- Changeover
- The point at which a line switches from one product or pack format to another, and the highest-risk moment for the wrong label to be applied.
- Allergen emphasis
- The typographic distinction — bold, capitals or underline — required to make allergens stand out within an ingredient list rather than simply be present in it.
- Reconciliation
- Accounting for labels issued against labels used and destroyed, so that a discrepancy in count flags a possible mislabelling before it is found any other way.
FAQ
Frequently asked questions about label verification record
Is this the same check as artwork approval?+
No. Artwork approval happens once, before a label design is ever printed. This record checks the printed label actually on the line, every time the line changes over or at defined intervals through a run.
What happens if the label only has a minor difference from specification?+
Minor Difference is scored above a flat fail, but it should not be used as a way to wave through anything touching allergens, claims, net quantity or legal marks. Those differences are never minor.
Why does the allergen check reference the recipe rather than the specification?+
Specifications can lag a recipe change by days or weeks. Checking against what is actually being made today, rather than what was on file when the specification was last issued, is what catches an undeclared allergen before it reaches a customer.
Who can be the second checker?+
Anyone competent to assess the label who was not the person who set up or ran the changeover. The requirement is independence, not seniority.
What triggers a hold under this record?+
Incorrect Label Reached Product being answered Yes. That opens Quantity Affected, Hold ID and Product Location, and the line cannot be released for labelling until those are resolved.
Does this record replace the date coding check?+
No. Date and batch code fields here confirm coding is correct as part of the overall label check; a dedicated date coding verification exists for a deeper check on coding alone.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Allergen Management
Product and SKU Register
Holds every product and pack format you make, with its specification, allergens, shelf life and customer
Certificate of Analysis Review
Checks the certificate supplied with a material against the agreed specification
Allergen Changeover Check
Confirms the line is clear of the previous allergen before the next product runs
Glass and Brittle Plastic Register
Lists every item of glass or hard plastic in production areas, with its location and condition
Artwork Approval Record
Records approval of new or amended artwork before it is printed, with each checker named
Rework Instruction Record
Sets out how a specific batch is to be reworked, what checks apply and who authorised it
More in Packaging and Labelling
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
Seal Integrity Test Record
Records seal strength, burst or dye testing on packs, with the result against specification
Pack Weight Control Record
Records average and individual pack weights against legal and specification limits

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, cl.5.2 (Labelling)
- Regulation (EU) No 1169/2011, Food Information to Consumers Regulation
- Food Information (Amendment) (England) Regulations 2019, Natasha's Law
- FALCPA (2004) as amended by the FASTER Act (2021)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.