What this is
What is a hold and release record?
What is a hold and release record?
The record placing product under control so it cannot be used or despatched, defining the boundary of what is affected, documenting the investigation and the disposition decision, and evidencing the authorised release.
How is the boundary determined?
By running back to the last point at which the condition was demonstrably good: the last passed check, the last verified calibration, the last confirmed clean. That is usually further back than the immediate batch, and drawing it at the batch in front of you is the most common way product escapes.
Scope
When is a hold and release record required?
This controls product pending a decision. The investigation and the corrective action sit alongside.
Use this template when
- Product suspected or confirmed as not meeting requirements
- Product affected by a process deviation, equipment failure, or failed check
- Material affected by a supplier notification or a customer complaint
- Product pending test results where release cannot proceed without them
- Any situation where the affected boundary needs defining before disposition
Do not use it for
- Root cause analysis, which investigates why rather than controls what
- The corrective action record, tracking actions to prevent recurrence
- Customer complaint handling, which may trigger a hold
- The recall process, which applies once product has left your control
- Rework instructions, which follow a disposition decision
Compliance mapping
Which ISO 9001 cl.8.7 requirements does this satisfy?
Control of nonconforming output is a core requirement across quality and food safety standards.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.8.7.1 | Nonconforming outputs identified and controlled to prevent unintended use or delivery | What is held |
| ISO 9001 cl.8.7.2 | Documented information on the nonconformity, actions taken, concessions and the authority deciding | Release |
| 21 CFR 117.150 | Corrective actions including evaluating product for safety and preventing affected food entering commerce | Disposition |
| ISO 22000 cl.8.9.4 | Withdrawal and recall, and handling of potentially unsafe products | Disposition |
| BRCGS Issue 9 cl.3.8 | Control of nonconforming product with identification, quarantine and disposition | What is held |
| 21 CFR 211.87 | Retesting of approved components subject to deterioration (pharmaceutical parallel) | Investigation |
| IATF 16949 cl.8.7.1.1 | Customer authorisation for concession before further processing | Release |
| ISO 9001 cl.10.2 | Corrective action following nonconformity, including determining causes | Related records |
What it does not cover
- Root cause analysis, investigating why rather than controlling what.
- The corrective action record, tracking prevention of recurrence.
- Complaint handling, which may trigger a hold.
- The recall process, applying once product has left your control.
- Rework instructions, following a disposition decision.
How to complete it
How to complete a hold and release record, step by step
Define the boundary properly, control the product physically, and name who released it.
Not the current batch, but back to the last occasion the condition was demonstrated acceptable. For a failed detector check that is the last passed check; for an out-of-tolerance instrument it is the last confirmed calibration; for a cleaning failure it is the last validated changeover. Record the reasoning as well as the boundary.
A status flag prevents transactions and does not prevent a person picking a pallet from a normal location. Physical segregation, or at minimum unambiguous marking and a location that signals held, is what stops product moving. Systems fail open when someone is in a hurry and the pallet is where it always is.
The person deciding product is acceptable should not be the person accountable for shipping it on time. The conflict is real, it operates strongest when the hold is expensive, and separating the roles costs nothing beyond deciding to.
Product held for months because nobody wants to write it off is being written off slowly by inaction, while occupying space and creating the risk that someone eventually releases it to clear the area. Ageing the hold list and requiring a decision at defined intervals turns a drift into a choice.
What auditors find
Most common hold and release record findings
Hold findings concentrate on the boundary and on how the release happened.
| Finding | Clause | What fixes it |
|---|---|---|
| Boundary drawn at the current batch rather than the last known good point. | 21 CFR 117.150 | Run back to the last demonstrated good condition; that is what defines the affected population. |
| Product held in the system but not physically segregated. | ISO 9001 cl.8.7.1 | Physical control; a status flag does not stop a pallet being picked. |
| Release authorised by the person accountable for despatch. | ISO 9001 cl.8.7.2 | Separate the roles; the conflict peaks when the hold is expensive. |
| Concession granted without customer authorisation where the specification is theirs. | IATF 16949 cl.8.7.1.1 | Customer authorisation is required before further processing. |
| Holds ageing indefinitely with no forced decision point. | ISO 9001 cl.8.7.1 | Age the list; indefinite hold is a write-off decided by inaction. |
| Boundary reasoning not recorded, only the conclusion. | ISO 9001 cl.8.7.2 | Record why the boundary sits where it does; it will be examined. |
| Affected boundary could not be established from records. | BRCGS 3.9 | That is a traceability finding as well as a quality one. |
| Partial release of a held population without re-examining the boundary. | ISO 9001 cl.8.7.1 | Releasing part of a batch requires the same reasoning as holding it. |
| Concessions frequent and not trended. | ISO 9001 cl.10.2 | Repeated concession is a specification or capability finding, not a disposition one. |
| Held product in a normal storage location. | BRCGS 3.8 | Location should signal status; ambiguity is resolved in favour of shipping. |
Case in point
Case in point: the boundary that moved
A metal detector failed its check at the end of a four-hour run. The immediate decision was to hold the product made in the preceding hour, on the basis that the detector had been working earlier and the failure was probably recent.
The verification regime was hourly, and the last passed check had been three hours earlier because two intermediate checks had been missed during a changeover. The defensible boundary was therefore three hours of production, not one.
The distinction was not academic. Holding one hour meant releasing two hours of product that could not be shown to have passed through a functioning detector, and no amount of reasoning about when the failure probably began changes what could be demonstrated.
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-003
- Archetype
- Record
- Record ID
- HOLD-2026-000
- Scoring
- Not scored
- Direction
- n/a
- Singleton
- No
- Basis
- ISO 9001 cl.8.7
- Links
- Links Case; feeds Traceability
- Tags
- Quality, Control
- Sections
- 6
- Fields
- 47
- Follow up fields
- 6
- Repeating sections
- 0
- Links out
- 5
Header
17 fieldsHold ID*
Auto sequence. Format HOLD-2026-00000.
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*
Case ID
The nonconformance or deviation that caused this hold.
Thread key. Every record in this chain carries this value
Parent Type
What kind of record this follows.
Parent ID
The reference of that record.
Immediate predecessor record
Raised Date*
Nothing Leaves Without A Decision
Held product cannot ship, be reworked or be scrapped until a named person records a disposition. Quality approves, never production alone.
What is held
10 fieldsQuantity Held*
Unit Of Measure*
Value
Reason For Hold*
Reason Detail*
Hold Location*
Physically segregated, not just labelled in place.
Physically Segregated*
- Yes3 pts
- Partly1 pt
- No0 pts
Hold Labels Applied*
- Yes3 pts
- No0 pts
System Status Changed To Hold*
Physical and system hold must both happen or somebody will ship it.
- Yes3 pts
- No0 pts
Despatch Notified*
- Yes3 pts
- No0 pts
Investigation
4 fieldsTesting Required*
Test Type
Test Results
Result Acceptable
- Yes3 pts
- Marginal1 pt
- No0 pts
Disposition
6 fieldsDisposition*
- Release3 pts
- Release under concession1 pt
- Rework1 pt
- Downgrade1 pt
- Concession1 pt
- Return to supplier1 pt
- Scrap0 pts
- Destroy0 pts
Disposition Rationale*
Rework Authorization ID
Links to QUA-004 Authorization ID
Scrap Record ID
Links to QUA-005 Scrap ID
Concession ID
Links to QUA-006 Concession ID
Customer Approval Required
Related records
1 fieldWork Order ID
The order raised to correct the cause of the hold.
Links to MNT-002 Work Order ID
Release
9 fieldsApproved By Quality*
Approval Date*
Physical Labels Removed*
- Yes3 pts
- No0 pts
System Status Released*
- Yes3 pts
- No0 pts
Quantity Released*
Quality Approver*
Signature*
Production*
Second Signature*
QUA-003 · record IDs look like HOLD-2026-000 · Links Case; feeds Traceability
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The record controls product pending a decision. What fails is a boundary drawn at the current batch and a hold that aged for a year.
Sets the boundary from the last passed check or verified condition, records the reasoning, and requires named release authority.
Applies physical segregation and location control so held product cannot be picked, rather than relying on a status flag.
Ages held product and forces a decision point, and trends concessions as a specification finding rather than a disposition.
Links equipment failures and calibration results to the affected production window, so the boundary is retrieved rather than reconstructed.
This template lives in KnowQuality — quality and food safety. HACCP, nonconformance, traceability, laboratory and customer complaints.
Meet KnowQuality→Glossary
Hold and Release Record definitions and key terms
- Hold
- Control preventing product being used or despatched pending a disposition decision.
- Last known good point
- The most recent occasion the condition was demonstrated acceptable, which defines the affected boundary.
- Disposition
- The decision on held product: release, rework, downgrade, concession, return or destruction.
- Concession
- Acceptance of product not meeting specification, requiring customer authorisation where the specification is theirs.
- Physical segregation
- Locating held product so it cannot be picked in error, distinct from a system status flag.
- Release authority
- The named person empowered to release held product, separated from despatch accountability.
- Hold ageing
- Tracking how long product has been held, which converts drift into a decision.
- Extent of condition
- The population affected, determined by the boundary rather than by the batch that triggered the hold.
FAQ
Frequently asked questions about hold and release record
How far back should a hold extend?+
To the last point at which the relevant condition was demonstrably good: the last passed check, the last verified calibration, the last validated clean. Everything after that point is unknown. Reasoning about when the failure probably began is frequently correct and is not evidence, and the disposition has to rest on what can be shown.
Is a system hold sufficient?+
No. A status flag prevents transactions and does not prevent someone picking a pallet from its usual location when they are in a hurry. Physical segregation, or at minimum a location and marking that unambiguously signal held status, is what actually stops product moving. Ambiguity gets resolved in favour of shipping.
Who should authorise release?+
Someone with the authority to say no, and not the person accountable for shipping on time. The conflict is real and operates most strongly when the hold is large and the customer is waiting, which is precisely when the decision matters. Separating the roles requires nothing but a decision to do so.
What is the risk of an ageing hold?+
Two things. Product held for months is being written off slowly by nobody deciding, which is worse than deciding to write it off. And it occupies space and creates pressure, so eventually someone releases or disposes of it to clear the area, under conditions where the decision receives less scrutiny than it would have at the outset.
What if we cannot establish the boundary?+
Then you have a traceability finding as well as a quality one, and the boundary has to be drawn conservatively by definition. Being unable to determine what was affected is a more serious finding than the original nonconformity, because it means the same limitation will apply to every future event including a recall.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in HACCP and Food Safety
Unannounced Audit Readiness Check
Checks whether the site would pass an audit arriving today, covering records, standards and area condition
Product Nonconformance Report
Records product that does not meet specification
HACCP Plan
The hazard analysis and critical control point plan for a product or process
HACCP Verification Record
Confirms the HACCP plan is being followed and still works
CCP Monitoring Log
Records readings at a critical control point, such as cook temperature, chill time or metal detection
Prerequisite Programme Plan
Sets out the basic conditions that must be in place for HACCP to work, covering hygiene, maintenance, pest control and training
More in Nonconformance
Product Nonconformance Report
Records product that does not meet specification
Process Deviation Report
Records a process that ran outside its set limits, even where the product still passed
Rework Authorization
Authorises rework on nonconforming product and sets out exactly what will be done
Scrap Record
Records product written off, with quantity, reason and cost
Concession Request
Requests permission to use or ship product that does not fully meet specification
Material Rejection Report
Rejects incoming material that fails inspection
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:
- ISO 9001:2015 clause 8.7, control of nonconforming outputs
- 21 CFR 117.150, corrective actions, FDA
- BRCGS Food Safety Issue 9 clause 3.8, control of nonconforming product
- IATF 16949:2016 clause 8.7.1.1, customer authorisation for concession
- ISO 22000:2018 clause 8.9, control of product and process nonconformities
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.