What this is
What is a proof of delivery exception?
What is a proof of delivery exception?
It is a record of a delivery that did not complete cleanly: refused outright, short on quantity, damaged, late against the agreed window, wrong product, or accepted with a written notation on the delivery document. It is raised at the point the exception happens, not reconstructed from memory afterwards. In KnowLogistics it is a singleton, run once per workspace and fed by every exception as it occurs.
What counts as an exception under this template?
The Exception Type field lists six categories: refused, short, damaged, late, wrong product, or signed with a notation. The last of these matters most, because it covers deliveries the customer technically accepted but flagged in writing, which is the only version of events that survives a later dispute.
Why does the notation matter more than the signature?
A signature on its own only proves the customer took the goods. It is the words written next to the signature — short two cases, one pallet crushed, seal broken on arrival — that prove the delivery was not clean. Without that notation, the signature reads as unconditional acceptance, and unconditional acceptance is the strongest evidence a carrier has against a claim.
Scope
When is a proof of delivery exception required?
This record is one step in a larger programme. Using it for work that belongs to a neighbouring template produces records that are hard to report on later.
Use this template when
- A delivery has just been refused, come up short, arrived damaged, run late, or been signed with a notation
- A driver has returned with a delivery note that carries any handwritten qualification, however minor it looks
- Customer service needs a single place to hold the evidence before Freight Claim or Complaint is raised
- The workspace is being set up, or the register needs an entry added or retired
- A downstream record needs this one to exist first, since it feeds Freight Claim and Complaint
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, before the vehicle has even been loaded.
- Dispatch Release Check, which is the final check before a load leaves, covering documents, temperature, securement, seal and count, not what happened after arrival.
- Shipping Document Check, which verifies the bill of lading, packing list, certificates and any regulated paperwork before the vehicle moves, not the condition on delivery.
- Customer Delivery Confirmation, which records a delivery that went cleanly, not one that needs an exception on file.
- Anything outside KnowLogistics, which belongs in the workspace that owns that process
Compliance mapping
Which Carmack Amendment requirements does this satisfy?
The Carmack Amendment governs carrier liability for interstate freight loss or damage, and the federal cargo claim regulations set out what a valid claim needs to contain; both depend on evidence fixed at the point of delivery.
| Clause | Requirement | Where it lands |
|---|---|---|
| Carmack Amendment (49 U.S.C. § 14706) | A carrier is liable for loss or damage to freight in interstate transport unless the receiving party's own acceptance documents show otherwise. | Header |
| Carmack Amendment (49 U.S.C. § 14706) | Condition at delivery has to be evidenced at the time of delivery; it cannot be reconstructed convincingly afterwards. | At the point of delivery |
| Carmack Amendment (49 U.S.C. § 14706) | A concealed or later-reported loss carries a materially weaker evidentiary position than one noted and signed at delivery. | At the point of delivery |
| 49 CFR Part 370 (uniform cargo claim rules) | A claim must identify the shipment and specify the facts of the loss or damage; those facts come from what was recorded at the dock. | Cause |
| Carmack Amendment (49 U.S.C. § 14706) | Liability turns on establishing cause: carrier fault, shipper fault, or a constraint at the customer's own site. | Cause |
| 49 CFR Part 370 | The carrier is entitled to inspect damaged or rejected goods before a claim is settled, which depends on the goods being held rather than restocked. | Outcome |
| 49 CFR Part 370 | The minimum period a carrier must allow for filing a claim runs from the point the exception is documented, not from when it is later escalated. | Outcome |
What it does not cover
- Noted On The Delivery Document, which is left blank or marked No whenever the driver rings the office instead of writing the exception on the note itself.
- Customer Signed The Notation, which cannot honestly be Yes if the customer already signed a clean receipt before the exception was raised with them.
- Photographs Taken, which stays No because nobody thought to photograph the pallet before it was moved off the dock and restacked.
- Our Picking Or Loading Error, which gets marked No by default because nobody has actually checked the pick list against what was loaded onto the vehicle.
- Claim Being Raised, which is left as Yes with no Claim ID ever entered, so the linked Freight Claim Record never actually gets opened.
Global
Proof of Delivery Exception requirements by country
The Carmack Amendment gives this template its statutory anchor, but the underlying discipline, getting the exception onto the document before the vehicle leaves, holds regardless of which regime is in force on a given lane.
Carmack Amendment, 49 U.S.C. § 14706
Federal law preempts state-level claims against an interstate common carrier for loss or damage to freight.
A signed-clean delivery receipt is the carrier's strongest defence; this record only carries weight if the notation exists on the document itself, not in a follow-up email.
CMR Convention (Convention on the Contract for the International Carriage of Goods by Road)
Governs international road haulage across borders, with its own requirement that damage or loss be reserved at the point of delivery.
A consignee who accepts goods without a written reservation is presumed to have received them exactly as stated on the consignment note, the same signed-clean trap under a different instrument.
Common law bailment and the carrier's own contract of carriage
Without a Carmack-equivalent statute, liability rests on ordinary bailment principles and whatever terms the carrier has printed on its own note.
The delivery note notation is often the only evidence a shipper has in these lanes, which is exactly why the habit is worth keeping even where no Carmack Amendment applies.
How to complete it
How to complete a proof of delivery exception, step by step
Filling in every field is the mechanical part. The judgement calls below are what decide whether the record actually stands up when a claim is disputed.
A driver who calls the office to describe a problem has raised an internal alert, not evidence. The judgement call is whether customer service treats that call as sufficient to open this record, or insists on the written notation before anything downstream is built on it.
Our Picking Or Loading Error, Transit Damage, Temperature Failure and Customer Site Constraint are mutually exclusive in practice even though the form allows any combination. Someone has to make a real attribution call, often under time pressure, and that call decides who ends up paying.
A photograph taken after the pallet has been moved, restacked or partially unloaded proves very little. The record only reflects reality if Photographs Taken means photographed in place, before anyone touched the load further.
Credit Issued can be Yes, No or Pending independent of whether Claim Being Raised is Yes. Issuing a goodwill credit before the carrier claim resolves is a commercial judgement call, not a form rule, and it changes what the business actually recovers.
What auditors find
Most common proof of delivery exception findings
These are the specific ways this record fails to hold up later, tied to the fields that let the failure happen.
| Finding | Clause | What fixes it |
|---|---|---|
| A delivery is signed clean, then the exception is reported by phone after the driver has left the customer. | Carmack Amendment (49 U.S.C. § 14706) | Require the notation on the document itself before the driver leaves; a call made afterwards has no evidentiary value against a signed-clean receipt. |
| Photographs Taken is marked Yes for images taken after the pallet has already been moved or restacked. | 49 CFR Part 370 | Photograph in place before anything is touched, and only mark this field Yes once that has actually happened. |
| Our Picking Or Loading Error defaults to No without anyone checking the pick list against what was actually loaded. | Carmack Amendment (49 U.S.C. § 14706) | Cross-check the pick and load record before attributing cause; a wrong default here misroutes the entire claim. |
| Claim Being Raised is set to Yes but Claim ID is never populated, so the linked Freight Claim Record is never opened. | 49 CFR Part 370 | Treat Claim ID as mandatory the moment Claim Being Raised is Yes, not a task left for later in the week. |
| Temperature Recorded is marked No on a chilled or frozen load with no reason given for skipping it. | Carmack Amendment (49 U.S.C. § 14706) | Make a temperature reading mandatory on any load flagged as temperature-controlled, rather than optional per driver habit. |
| Returned Stock Inspected Before Restock is skipped and the returned product goes straight back onto a pick face. | 49 CFR Part 370 | Block restock of returned exception stock until this field is answered, tying the record to the goods-inward process rather than leaving it advisory. |
Case in point
Case in point: a signed-clean note beat a genuine transit damage claim
A chilled load arrived with two pallets visibly crushed against the tail door, plainly caused in transit rather than at picking. The driver, already running late on the next drop, apologised, helped the customer clear the damaged stock to one side, and got the delivery note signed so he could move on. Nothing was written on the note itself; the plan was to log it properly back at the depot.
By the time customer service opened this record the next morning, Noted On The Delivery Document and Customer Signed The Notation both had to be answered No. Transit Damage was obviously the true cause, but the carrier's defence needed only the signed-clean receipt: the customer had accepted the delivery without reservation. The claim was declined on paperwork, not on the facts of what actually happened at the tail lift.
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.
4 sections
- Reference
- LOG-010
- Archetype
- Record
- Record ID
- POD-2026-000
- Scoring
- Clean delivery rate
- Direction
- High is good
- Singleton
- Yes
- Basis
- Carmack Amendment
- Links
- Feeds Freight Claim and Complaint
- Tags
- Outbound, Exception, POD
- Sections
- 4
- Fields
- 42
- Follow up fields
- 4
- Repeating sections
- 0
- Links out
- 6
Header
13 fieldsException ID*
Auto sequence. Format POD-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*
Customer
Delivery Attempted*
Exception Type*
Refused, short, damaged, late, wrong product, or signed with a notation.
- Refusednot scored
- Shortnot scored
- Damagednot scored
- Latenot scored
- Wrong productnot scored
- Signed with a notationnot scored
Units Affected
Estimated Value
The Notation Is The Claim
Signed clean means you have accepted the delivery was perfect. Everything you might later want to recover depends on what the driver wrote on the note before leaving the customer.
At the point of delivery
6 fieldsNoted On The Delivery Document*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Customer Signed The Notation*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Photographs Taken*
- Yes3 pts
- No0 pts
Driver Reported Immediately*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Temperature Recorded*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Seal Number Recorded*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Cause
6 fieldsOur Picking Or Loading Error*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Transit Damage*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Temperature Failure*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Late Beyond The Agreed Window*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Customer Site Constraint*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Documentation Error*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Outcome
17 fieldsProduct Returned*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Credit Issued*
Value Credited
Claim Being Raised*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Claim ID
Links to LOG-025 Claim ID
Complaint Case ID
Links to QUA-023 Case ID
Returned Stock Inspected Before Restock*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Return Record ID
Links to LOG-029 Return ID
Feeds Carrier Scorecard*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
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
Customer Service*
Signature*
Logistics Manager*
Second Signature*
LOG-010 · record IDs look like POD-2026-000 · Feeds Freight Claim and Complaint
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is the easy part. Keeping it current, routing it to the right owner and holding the evidence together is the work that actually slips.
Holds the proof of delivery exception register against your load references, routes each exception to customer service, and keeps the photographs and notation on the same record as the claim they support.
Connects the driver, vehicle and load involved in the exception back to the wider fleet record, so a pattern of exceptions on one route or one vehicle is visible rather than buried in separate reports.
Picks up the linked Complaint and CAPA references when an exception points to a systemic cause, so a picking error or a recurring temperature failure gets a corrective action rather than just a credit.
Coordinates the crew, rolls exceptions and their causes into one view across sites, 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
Proof of Delivery Exception definitions and key terms
- POD
- Proof of Delivery. The document or record confirming that goods were delivered, and in what condition, at the point the customer took receipt.
- Carmack Amendment
- United States federal law, codified at 49 U.S.C. § 14706, that sets carrier liability for loss or damage to freight moved in interstate commerce.
- Notation
- A handwritten qualification added to a delivery document at the point of delivery, describing exactly what was wrong with the shipment before it is signed for.
- Concealed damage
- Damage discovered after the delivery has been signed for clean, with no notation made at the time; far harder to attach to the carrier than damage noted on arrival.
- CAPA
- Corrective and Preventive Action. The linked record raised when an exception points to a systemic cause that needs fixing rather than a one-off write-off.
FAQ
Frequently asked questions about proof of delivery exception
Does every late delivery need one of these records?+
Yes, if it falls outside the agreed delivery window. The Exception Type field treats late as one of six categories alongside refused, short, damaged, wrong product and signed with a notation, and Late Beyond The Agreed Window is asked directly in the Cause section.
What happens if the customer refuses to sign anything at all?+
Customer Signed The Notation can be answered No or N/A depending on the situation, but Driver Reported Immediately still needs answering. A refusal to sign is itself evidence worth recording, even without a signature to attach it to.
Who decides whether a claim should be raised?+
Claim Being Raised sits in the Outcome section and is a judgement call for customer service based on value, cause and the strength of the evidence gathered, not an automatic outcome of logging an exception.
Why does the template ask about seal numbers and temperature on every exception?+
Because Exception Type is not always damage-related; a refused or short delivery still benefits from a clean audit trail of what condition the vehicle was in, which supports or undermines whatever cause is later assigned.
Does raising this record automatically create a Freight Claim?+
No. Claim ID only appears once Claim Being Raised is answered Yes, and it has to be entered manually once the Freight Claim Record itself has been raised elsewhere.
Is this the same record as a complaint?+
No, though the two are linked. This record captures the physical delivery exception; Complaint Case ID links across to a separate customer complaint record if the customer raises one on top of the delivery problem itself.
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
Dispatch Release Check
The final check before a load leaves, covering documents, temperature, securement, seal and count
Shipping Document Check
Verifies the bill of lading, packing list, certificates and any regulated documentation before the vehicle moves
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
Dispatch Release Check
The final check before a load leaves, covering documents, temperature, securement, seal and count
Shipping Document Check
Verifies the bill of lading, packing list, certificates and any regulated documentation before the vehicle moves
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:
- Carmack Amendment — 49 U.S.C. § 14706
- 49 CFR Part 370 — Uniform rules for cargo loss and damage claims
- CMR Convention — Convention on the Contract for the International Carriage of Goods by Road
- MAC — HSE Manual Handling Assessment Charts
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.