What this is
What is a dispatch release check?
What is a dispatch release check?
It is the last gate before a loaded vehicle leaves the site — a structured check of product, vehicle condition, paperwork and seal, closed out with two independent signatures. It exists because every error it catches costs minutes; the same error caught by the customer costs a rejection, a return trip and a credit note. It is completed once per load, at the point of dispatch, not reconstructed afterwards.
What does 'loads released clean' actually measure?
It is the proportion of dispatch checks completed with no failed item and no N/A used to avoid answering. A high score built on heavy use of N/A is not the same as a genuinely clean load, which is why Completeness Percent is tracked alongside the pass score rather than instead of it.
Why does the form need two signatures for one check?
The loader who builds and checks a load has already decided, in their own head, that it's correct — a second, independent person is the control that catches what the first person is structurally unlikely to see. Collapsing both signatures onto one person removes the control while leaving the form looking complete.
Scope
When is a dispatch release check required?
This is the release gate for a single load at the point of dispatch — not a place to record how the load was planned, how it was tendered, or what happened after it arrived. Each of those has its own template upstream or downstream of this one.
Use this template when
- A load is built and ready to leave, and needs product, vehicle, paperwork and seal verified before departure
- A second person is available to independently verify the load, not just countersign the first person's check
- The workspace is being set up, or the dispatch register needs an entry added or retired
- You are running the Outbound and Despatch programme and this is the release step in it
- A linked record needs this one to exist: Proof of Delivery Exception and Load Securement both reference it
Do not use it for
- Load Tender Record, which records a load offered to a carrier, the rate agreed and whether it was accepted or refused, long before the load is built.
- Shipping Document Check, which verifies the bill of lading, packing list and certificates as a standalone check, on sites that run it separately from the physical release.
- Proof of Delivery Exception, which records a delivery that didn't complete cleanly, well after this check has already passed the load out of the yard.
- Load Securement Check, which focuses specifically on how the load is restrained and can run as its own record where securement is a specialist sign-off separate from general release.
- Anything outside KnowLogistics, such as the vehicle's own roadworthiness inspection, which belongs to fleet maintenance rather than the load being released.
Compliance mapping
Which ISO 9001 cl.8.5 requirements does this satisfy?
This checklist is built against ISO 9001 clause 8.5, Control of Production and Service Provision, which covers verifying an output before release. The sub-clauses below map onto specific sections of the form, alongside the release and nonconformity clauses either side of 8.5.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.8.5.1 — Control of production and service provision | Verify product identity and quantity against the order before it is treated as ready to load | Product |
| ISO 9001 cl.8.5.2 — Identification and traceability | Record batch codes and remaining shelf life so the load can be traced back if a problem surfaces later | Product |
| ISO 9001 cl.8.5.4 — Preservation | Confirm trailer cleanliness, no residue from a previous load, and temperature pulled down before loading begins | Vehicle |
| ISO 9001 cl.7.5.3 — Control of documented information | Delivery notes, certificates and dangerous goods documentation must be present and correct before departure | Paperwork and seal |
| ISO 9001 cl.8.6 — Release of products and services | Release only after an independent second person verifies the load and signs alongside the loader | Outcome |
| ISO 9001 cl.8.7 — Control of nonconforming outputs | Route any failed item to a case reference rather than releasing the load anyway | Outcome |
| ISO 9001 cl.9.1.3 — Analysis and evaluation | Convert the individual checks into a score and a completeness percentage that feeds the wider release-quality trend | Outcome |
What it does not cover
- Second Person Verified The Load, which is marked Yes without a second name entered against Despatch Supervisor — a single-person check has been recorded as a two-person control.
- Any Item Failed, which is marked Yes with no Case ID recorded — a failed release check has nothing tying it to the corrective action it should have triggered.
- Temperature Pulled Down Before Loading, which is marked No with Released For Despatch marked Yes — a cold-chain failure has been waved through rather than held.
- Seal Applied And Number Recorded, which is answered Yes with no seal number captured in the Outcome section — the seal meant to prove the trailer wasn't opened in transit can't be checked against anything.
- Allergen Segregation Maintained, which is marked No while Correct Product And Quantity is marked Yes — the count is right but the load is not safe to release as built.
Global
Dispatch Release Check requirements by country
ISO 9001 cl.8.5 sets the release principle, but food, dangerous goods and cross-border movements each add their own binding requirements on top of it. The three below are the ones most likely to decide whether a dispatch actually complies.
21 CFR Part 1, Subpart O (FDA Sanitary Transportation Rule, under FSMA)
Sets sanitary requirements for vehicles and equipment transporting food, including cleaning between loads and temperature control.
Trailer Clean And Odour Free, No Previous Load Residue, and Temperature Pulled Down Before Loading are this checklist's answer to the rule, not paperwork for its own sake.
ADR (European Agreement concerning the International Carriage of Dangerous Goods by Road)
Sets documentation, marking and segregation rules whenever a load includes dangerous goods.
Dangerous Goods Documentation Where Required only satisfies ADR if the correct document set is actually attached, not merely ticked as present.
Codex Alimentarius General Principles of Food Hygiene (CXC 1-1969, HACCP annex)
Treats dispatch as a control point where allergen segregation and product identity must be verified before product leaves controlled conditions.
Allergen Segregation Maintained and Nothing On Hold Included are this checklist's version of a HACCP control point, evidenced on paper rather than assumed.
How to complete it
How to complete a dispatch release check, step by step
Filling in every field correctly doesn't automatically make the release defensible, because the form doesn't decide these four calls for you.
Several fields allow N/A, and Score Percent excludes them from the denominator. Decide, in writing, which fields can legitimately be N/A on a given load type versus which N/A answers are actually a skipped check dressed up as an exemption.
Second Person Verified The Load is meant to be an independent check, not a rubber stamp. Decide whether the same shift's supervisor, who trusts the loader by default, can genuinely provide that independence, or whether the control needs someone outside that reporting line.
Result Band allows Pass, Caution and Fail, but only Any Item Failed drives the Case ID field. Decide whether a Caution result also needs a case opened, or whether it is allowed to release with no trail at all.
Seal Applied And Number Recorded and Departed are captured independently of the shipping document check. Decide who is responsible for reconciling the two before the load is treated as fully released, and when that reconciliation has to happen.
What auditors find
Most common dispatch release check findings
These are the patterns that show up when a dispatch register is reviewed after the fact, not while the load is still on the dock.
| Finding | Clause | What fixes it |
|---|---|---|
| Second Person Verified The Load is ticked Yes by the same loader who signs first | ISO 9001 cl.8.6 — Release of products and services | Require the Despatch Supervisor name to differ from the Loader name before the load can be marked released |
| Temperature Pulled Down Before Loading is answered Yes before Recorder Running And Set is confirmed | ISO 9001 cl.8.5.4 — Preservation | Sequence the form so the recorder is confirmed running before the temperature question can be answered |
| Dangerous Goods Documentation Where Required is marked N/A on loads that carry a DG line item | ISO 9001 cl.7.5.3 — Control of documented information | Cross-check the N/A answer against the load's own product codes rather than trusting the checkbox alone |
| Any Item Failed is marked Yes with Released For Despatch also marked Yes | ISO 9001 cl.8.7 — Control of nonconforming outputs | Block Released For Despatch = Yes whenever Any Item Failed = Yes without a documented concession |
| Score Percent looks clean because every uncertain item is marked N/A rather than No | ISO 9001 cl.9.1.3 — Analysis and evaluation | Cap the proportion of items allowed as N/A before Completeness Percent forces a review |
| Seal Number is recorded in the Outcome section but never checked against the Shipping Document Check | ISO 9001 cl.8.5.2 — Identification and traceability | Reconcile Seal Number against Document Check ID before the load is treated as fully released |
Case in point
Case in point: the seal that didn't match
A load was released clean — every product, vehicle and paperwork check ticked Yes, seal applied, number recorded. Three hours later the shipping document check on the same load recorded a different seal number for the same trailer.
Nobody had reconciled the two records against each other, because nothing in either template required it. The trailer had almost certainly not been opened in between; but 'almost certainly' is not what a seal number exists to provide.
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
- LOG-008
- Archetype
- Checklist
- Record ID
- DISP-2026-000
- Scoring
- Loads released clean
- Direction
- High is good
- Singleton
- Yes
- Basis
- ISO 9001 cl.8.5
- Links
- Feeds Proof of Delivery Exception and Load Securement
- Tags
- Outbound, Dispatch
- Sections
- 6
- Fields
- 51
- Follow up fields
- 4
- Repeating sections
- 0
- Links out
- 5
Header
13 fieldsCheck ID*
Auto sequence. Format DISP-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*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Load Reference*
Vehicle Registration*
Carrier
Pallets Loaded*
Drops On This Load
Loader*
Ten Times More Expensive After This Point
Every error caught here costs a few minutes. The same error caught at the customer costs a rejection, a return journey, a credit and a conversation about your reliability.
Product
6 fieldsCorrect Product And Quantity*
- Yes3 pts
- No0 pts
Batch Codes Recorded*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Within Remaining Shelf Life*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Nothing On Hold Included*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Allergen Segregation Maintained*
- Yes3 pts
- No0 pts
Pallets Stable And Wrapped*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Vehicle
6 fieldsTrailer Clean And Odour Free*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
No Previous Load Residue*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Temperature Pulled Down Before Loading*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Recorder Running And Set*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Load Secured*
- Yes3 pts
- No0 pts
Weight Within Axle Limits*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Paperwork and seal
6 fieldsDelivery Notes Present And Correct*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Certificates Attached Where Required*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Dangerous Goods Documentation Where Required*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Seal Applied And Number Recorded*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Driver Briefed On Delivery Points*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Second Person Verified The Load*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Related records
1 fieldPOD Exception ID
Where the load did not deliver cleanly.
Links to LOG-010 Exception ID
Outcome
19 fieldsReleased For Despatch*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Departed
Seal Number
Any Item Failed*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Case ID
Thread key
Document Check ID
Links to LOG-009 Check ID
Items 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
Loader*
Signature*
Despatch Supervisor*
Second Signature*
LOG-008 · record IDs look like DISP-2026-000 · Feeds Proof of Delivery Exception and Load Securement
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The checklist catches what's wrong with one load. What decides whether the pattern behind repeated failures gets seen is whether the second signature is real and whether failures get linked to a case every time.
Holds the dispatch release register against every load, and keeps the case and CAPA trail attached the moment Any Item Failed switches to Yes.
Tracks the product-side requirements this check enforces — batch traceability, shelf life and allergen segregation — against the wider quality system they sit inside.
Confirms the vehicle side of the check — trailer condition and temperature recorder status — against the asset record the check assumes is already current.
Coordinates the crew, rolls completion and failed items into one view, and holds every write for your approval before it touches a record.
This template lives in KnowLogistics — supply chain execution. Inbound, outbound, inventory, yard, claims, supplier lifecycle and customs.
Glossary
Dispatch Release Check definitions and key terms
- Release
- The formal decision, evidenced by two signatures, that a load meets every requirement checked here and may leave the site — distinct from simply finishing the loading.
- Traceability
- The ability to trace a specific pallet back to a batch code and shelf-life date after it has left, using what was recorded at the point of release.
- Preservation
- Keeping product in the condition it needs to be in through handling and transport — here, trailer cleanliness, temperature and load security together, not any one of them alone.
- Seal
- A single-use, numbered fastener applied to the trailer doors at release, whose recorded number is the only evidence the trailer wasn't opened before the next check.
- Concession
- A documented decision to release a load despite a failed item, made deliberately rather than by leaving Any Item Failed unanswered.
FAQ
Frequently asked questions about dispatch release check
What is the dispatch release check template based on?+
ISO 9001 clause 8.5, Control of Production and Service Provision, alongside the adjoining release clause 8.6 and the nonconformity clause 8.7 for anything that fails.
Can this check be completed by one person?+
The form allows it, but doing so removes the independent verification the second signature exists to provide. Most sites treat the Despatch Supervisor field as a genuine second look, not a formality.
What happens when an item fails?+
Any Item Failed switches to Yes, which is meant to open a Case ID and, where the fault is systemic rather than one-off, a linked CAPA. A failed item with neither is a fault with no trail.
Why track Completeness Percent alongside the score?+
Because a high score built from a form half-answered with N/A isn't evidence of a clean load — it's evidence the check wasn't actually run. The two numbers are meant to be read together.
Which programme does the dispatch release check belong to?+
Outbound and Despatch, as the release step between load building and departure, feeding Proof of Delivery Exception and Load Securement downstream.
Can the checklist items or their scoring be changed?+
Yes — every field, option, score and conditional rule is editable. Most sites install it as supplied, run it for a cycle, and adjust which items are genuinely eligible for N/A based on what the completeness figure shows.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Outbound and Despatch
Load Securement Check
Confirms the load is secured correctly for its type, weight and journey
Weight and Axle Check
Records gross weight and axle loading against legal limits
Load Tender Record
Records a load offered to a carrier, the rate agreed and whether it was accepted or refused
Shipping Document Check
Verifies the bill of lading, packing list, certificates and any regulated documentation before the vehicle moves
Proof of Delivery Exception
Records a delivery that did not complete cleanly: refused, short, damaged, late or signed with a notation
Load Plan and Build Record
Sets out how a vehicle will be loaded before loading starts, covering weight distribution, stop sequence and segregation
More in Outbound
Load Tender Record
Records a load offered to a carrier, the rate agreed and whether it was accepted or refused
Shipping Document Check
Verifies the bill of lading, packing list, certificates and any regulated documentation before the vehicle moves
Proof of Delivery Exception
Records a delivery that did not complete cleanly: refused, short, damaged, late or signed with a notation
Load Plan and Build Record
Sets out how a vehicle will be loaded before loading starts, covering weight distribution, stop sequence and segregation
Customer Delivery Confirmation
Confirms what the customer actually received against what was despatched
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 cl.8.5 — Control of production and service provision
- ISO 9001:2015 cl.8.6 — Release of products and services
- ISO 9001:2015 cl.8.7 — Control of nonconforming outputs
- 21 CFR Part 1, Subpart O — Sanitary Transportation of Human and Animal Food
- ADR — European Agreement concerning the International Carriage of Dangerous Goods by Road
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.