What this is
What is an over short and damaged report?
What is an over short and damaged report?
It records a mismatch between what the purchase order and delivery note say should have arrived and what physically turned up: over-delivered, short, damaged, wrong item, or outside temperature. It's the record a freight claim under the Carmack Amendment is built from, so it's written at the dock, not reconstructed from memory afterwards.
What's the difference between an OS&D report and a receiving inspection record?
The receiving inspection record checks a delivery against the purchase order and specification as a routine gate. This report only exists because that check, or the driver handover, found something wrong. It's the exception record, not the routine one.
Why does the report ask about the delivery note separately from the physical count?
A discrepancy has two independent facts: what the paperwork claims and what's physically present. Recording them separately is what lets a later reviewer tell whether the supplier under-shipped, the carrier lost something in transit, or the paperwork was simply wrong.
Scope
When is an over short and damaged report required?
This report only exists because a receiving check, or the driver handover itself, has already found a mismatch. Raising it for anything else produces a record with no claim behind it.
Use this template when
- A delivery's quantity, condition or temperature doesn't match the purchase order or delivery note, and the driver is still at the dock
- The receiving inspection has flagged a discrepancy that needs its own claim-ready record
- A shortage, overage or damage needs to be assessed for carrier versus supplier liability before a claim is raised
- You are running the Inbound and Receiving or Claims and Carrier Performance programme and this is one of its steps
- A linked record needs this one to exist: feeds Freight Claim Record and Supplier Scorecard
Do not use it for
- Delivery Appointment Record, which books the dock slot and confirms the vehicle arrived on time, with no discrepancy involved.
- Receiving Inspection Record, which is the routine check that this report exists to escalate out of, once something fails it.
- Freight Claim Record, which is what this report feeds once liability and value are established, not where the discrepancy itself is first written down.
- Shortage Investigation Record, which digs into a pattern of repeated shortages after the fact, rather than the single discrepancy at the dock.
- Anything outside KnowLogistics, which belongs in the workspace that owns that process.
Compliance mapping
Which Carmack Amendment requirements does this satisfy?
The Carmack Amendment (49 U.S.C. § 14706) puts the burden on the shipper to show the goods were delivered in a damaged or short condition; 49 CFR Part 370 governs how the resulting claim is processed. The map below shows which section of the report carries each obligation.
| Clause | Requirement | Where it lands |
|---|---|---|
| 49 U.S.C. § 14706(a) | Establish that the discrepancy existed at the point of delivery, not afterwards | Header |
| 49 CFR § 370.3 | Provide the carrier with a written or noted claim within the applicable time limit | At the dock |
| 49 U.S.C. § 14706(a) | Show the condition of goods when tendered to the carrier, to establish liability | Cause |
| 49 CFR § 370.9 | Substantiate the amount of the claim with supporting evidence | Header |
| ISO 9001 cl.10.2.1 | Determine the cause of nonconformity before deciding corrective action | Cause |
| ISO 9001 cl.8.7.1 | Identify and control product that does not conform to requirements | Outcome |
| ISO 9001 cl.8.4.3 | Feed supplier performance data back into supplier evaluation | Related records |
What it does not cover
- Found Before The Driver Left marked No, with Driver Signed The Notation marked Yes, which is a contradiction, since the notation can't be signed by a driver who had already gone.
- Damage marked consistent with both transit and loading, which answers a question the cause section is meant to force a single decision on.
- Claim Being Raised marked Yes with no Claim ID entered, which leaves the claim unreferenced and the discrepancy effectively unresolved.
- Liability Position left as Disputed with no follow-up action recorded, which lets a genuine disagreement quietly close itself out.
- Feeds Vendor Scorecard marked No on a supplier picking error, which keeps a real supplier failure off the record that's supposed to catch it.
Global
Over Short and Damaged Report requirements by country
Carrier liability for freight loss and damage is decided under different regimes depending on where the movement happens, and the report needs to hold the evidence each one actually asks for.
Carmack Amendment, 49 U.S.C. § 14706
Statutory liability framing
A domestic motor carrier is presumptively liable for loss or damage in transit. The shipper's job is to prove condition at tender and condition at delivery, which is exactly what the At the dock and Cause sections capture.
49 CFR Part 370
Claims-processing framing
Sets the carrier's obligation to acknowledge and investigate a claim within fixed timeframes, timeframes that only start once a claim, built from this report, has actually been filed.
ISO 9001:2015 cl.8.7 and cl.10.2
Quality-system framing
Outside the US carriage regime, the same discrepancy still has to be identified as nonconforming product and traced to a cause, which is what keeps the record useful where Carmack doesn't apply.
How to complete it
How to complete an over short and damaged report, step by step
Filling in yes/no answers is mechanical. The judgement sits in four places where the form asks the receiver or reviewer to make a call that determines whether the claim, and the record, will hold up.
Cause allows Yes on more than one of Damage Consistent With Transit, Damage Consistent With Loading and Packaging Inadequate For The Journey, but liability can't sit with more than one party at once. The reviewer has to pick which cause actually explains the defect, not tick every plausible one.
Liability Position includes Disputed for the case where the evidence genuinely doesn't point one way. Used as a default because nobody wants to name the carrier or the supplier, it defeats the reason the Cause section exists.
Claim Being Raised is a cost decision as much as a factual one: Estimated Value and the scale of the shortage matter more than the principle of the thing. A report that files a claim on every discrepancy trains the carrier to expect it, and a report that never does gives away money that was recoverable.
Feeds Vendor Scorecard is a judgement about whether the fault sits with the supplier's picking or packing, not the carrier's handling. Answering it on autopilot either inflates a supplier's failure rate for a carrier's mistake, or lets a real supplier pattern go unrecorded.
What auditors find
Most common over short and damaged report findings
The failure patterns below repeat across sites more than any single bad delivery does.
| Finding | Clause | What fixes it |
|---|---|---|
| The delivery note notation and driver signature are added after the vehicle has already left | 49 U.S.C. § 14706(a) | Treat Found Before The Driver Left as a hard gate: if it's No, route the record to a shortage investigation rather than a claim, since the claim evidence no longer exists. |
| Photographs are attached without being taken in position, undermining the condition-at-tender evidence | 49 CFR § 370.9 | Require Photographs Taken In Position to be answered Yes before the file upload is accepted, or flag the mismatch for review. |
| More than one cause field is marked Yes with no note on which one actually applies | ISO 9001 cl.10.2.1 | Add a required free-text field naming the primary cause whenever two or more cause checks are positive. |
| Claim Being Raised is Yes with Claim ID left blank for weeks | 49 CFR Part 370 | Report open claims without a Claim ID on a standing exception list, since the claims-processing clock is already running whether or not the reference is entered. |
| Supplier Notified is marked Yes with no corresponding date or contact captured | 49 CFR § 370.3 | Add a date field beside Supplier Notified so the notification itself is timestamped, not just asserted. |
| Liability Position is set before the Cause section is fully answered | ISO 9001 cl.10.2.1 | Sequence the form so Liability Position can't be submitted ahead of the cause questions it's supposed to be based on. |
Case in point
Case in point: the claim that had nowhere to stand
A refrigerated load arrived two pallets short. The receiver photographed the gap in the trailer, but the driver had already signed off and left before anyone wrote the shortage onto the delivery note itself. The photograph existed; the notation didn't.
When the freight claim went in three days later, the carrier's response leaned entirely on the fact that the delivery note carried no exception at the time of signing. The shortage was real and the photograph was genuine, but the claim was fighting the paperwork it should have had, not the ambiguity of what happened at the dock.
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.
5 sections
- Reference
- LOG-003
- Archetype
- Record
- Record ID
- OSD-2026-000
- Scoring
- Discrepancies resolved
- Direction
- High is good
- Singleton
- Yes
- Basis
- Carmack Amendment
- Links
- Feeds Freight Claim and Vendor Scorecard
- Tags
- Inbound, Claim, Discrepancy
- Sections
- 5
- Fields
- 45
- Follow up fields
- 4
- Repeating sections
- 0
- Links out
- 6
Header
18 fieldsReport ID*
Auto sequence. Format OSD-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
Carrier*
Vendor ID*
Format VEN-0000.
Links to FDN-005 Vendor ID
Discrepancy Type*
Over, short, damaged, wrong item, or a temperature failure.
- Overnot scored
- Shortnot scored
- Damagednot scored
- Wrong itemnot scored
- Temperature failurenot scored
Delivery Note Reference*
Receipt ID
Links to LOG-002 Receipt ID
Quantity On Paperwork*
Quantity Physically Present*
Quantity Damaged
Photographs
Estimated Value
Found Before The Driver Left*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Signed At The Dock Or Not At All
A claim rests on a notation made before the driver leaves and a photograph taken where the goods stood. Both become impossible the moment the vehicle pulls away.
At the dock
6 fieldsDriver Shown The Discrepancy*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Noted On The Delivery Note*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Driver Signed The Notation*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Photographs Taken In Position*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Seal Number Recorded*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Vehicle Registration Recorded*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Cause
6 fieldsDamage Consistent With Transit*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Damage Consistent With Loading*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Packaging Inadequate For The Journey*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Load Securement Inadequate*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Temperature Excursion Involved*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Supplier Picking Error Suspected*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Related records
1 fieldSupplier Scorecard ID
The scorecard this discrepancy counts against.
Links to QUA-041 Scorecard ID
Outcome
14 fieldsLiability Position*
Carrier, supplier, us, or disputed.
- Carriernot scored
- Suppliernot scored
- Usnot scored
- Disputednot scored
Claim Being Raised*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Claim ID
Links to LOG-025 Claim ID
Supplier Notified*
- Yes3 pts
- Not applicable3 pts
- No0 pts
Replacement Requested*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Feeds Vendor 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
Receiver*
Signature*
Warehouse Manager*
Second Signature*
LOG-003 · record IDs look like OSD-2026-000 · Feeds Freight Claim and Vendor Scorecard
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is the easy part. Getting the notation signed before the vehicle leaves, chasing a claim reference and keeping the vendor scorecard current is the work that actually slips.
Holds the OS&D register against every open receipt, flags a discrepancy that's missing its driver notation, and keeps the receipt, claim and scorecard references linked together.
Tracks which carrier a discrepancy sits against, rolls repeated damage or shortage patterns into that carrier's performance record, and flags a liability position before a claim is filed against the wrong party.
Keeps the claim timeline against the regulatory clock in 49 CFR Part 370, so a claim reference that's gone quiet for too long surfaces before the window closes.

Coordinates the crew across sites, surfaces reports with a missing notation or an unreferenced claim, 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
Over Short and Damaged Report definitions and key terms
- Carmack Amendment
- US federal law, 49 U.S.C. § 14706, that makes an interstate motor carrier presumptively liable for loss or damage to freight, unless it can show the cause was outside its control.
- OS&D
- Over, Short and Damaged, shorthand for any mismatch between ordered, documented and physically received quantity or condition.
- Notation
- A written exception recorded on the delivery note itself, at the time of delivery, describing the shortage or damage found.
- Concession
- A documented decision to accept goods despite a known deviation, distinct from simply not noticing the deviation.
- Liability position
- The report's determination of which party, carrier, supplier or the receiving site itself, bears responsibility for a discrepancy.
FAQ
Frequently asked questions about over short and damaged report
Does the driver have to agree with the discrepancy for the report to be valid?+
No. Driver Shown The Discrepancy and Driver Signed The Notation are recorded separately for exactly this reason: a driver who disagrees can still be shown the damage and asked to sign that it was noted, without agreeing to fault.
What happens if the driver refuses to sign?+
The report still stands on the photographs, the seal number and the notation on the delivery note. A refusal to sign is itself worth recording rather than treated as blocking the report.
Does every OS&D report end in a freight claim?+
No. Claim Being Raised is a separate decision from the discrepancy itself. Small or low-value discrepancies are often recorded and closed without a claim, while the record still feeds the vendor scorecard.
How is this different from a shortage investigation record?+
This report captures a single discrepancy at the point of delivery. A shortage investigation looks at a pattern across multiple deliveries or a supplier, usually triggered once several OS&D reports point the same way.
What's the time limit for filing a claim after an OS&D report?+
It depends on the bill of lading terms and the carrier's tariff, but 49 CFR Part 370 sets the carrier's obligations once a claim is filed. The report itself should be raised immediately, well inside whatever window applies.
Can the liability position be changed after it's submitted?+
Yes, if better evidence comes in. A carrier's own investigation or a supplier's response can shift Disputed to a firmer answer, and the record should be updated rather than left inconsistent with the claim's outcome.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Inbound and Receiving
Vendor and Contractor Register
Holds every supplier, contractor and service provider you work with, including their status and approval level
Delivery Appointment Record
Books an inbound delivery into a dock slot and records whether it arrived when it said it would
Receiving Inspection Record
Checks an inbound delivery against the purchase order and the specification before it is accepted into stock
Container and Trailer Seal Check
Verifies the seal number against the paperwork and records its condition before the doors are opened
Container Devanning Record
Records the unloading of a shipping container, covering condition, contamination, count and the conditions inside
Inbound Quality Gate
Holds a receipt until the checks that must happen before it enters usable stock are complete
More in Inbound
Delivery Appointment Record
Books an inbound delivery into a dock slot and records whether it arrived when it said it would
Receiving Inspection Record
Checks an inbound delivery against the purchase order and the specification before it is accepted into stock
Container and Trailer Seal Check
Verifies the seal number against the paperwork and records its condition before the doors are opened
Container Devanning Record
Records the unloading of a shipping container, covering condition, contamination, count and the conditions inside
Inbound Quality Gate
Holds a receipt until the checks that must happen before it enters usable stock are complete

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 — Reporting of loss and damage claims
- ISO 9001:2015 cl.8.7 — Control of nonconforming outputs
- ISO 9001:2015 cl.10.2 — Nonconformity and corrective action
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.