OS&D stands for over, short, and damaged: the three exceptions a receiver records when freight arrives with more pieces than ordered, fewer pieces than ordered, or visible damage. An OS&D report is the intake event that opens the freight claims process.
In a broker or forwarder operation, OS&D lands in the shared inbox as urgent, unhappy email: a warehouse notes two pallets short on the delivery receipt, a consignee sends photos of crushed cartons, a driver reports an overage nobody can explain. Each one starts a clock. Concealed damage has short reporting windows, carriers require notations on the POD to honor claims, and the evidence is freshest in the first exchange. Industry research puts exceptions at 8–25% of shipments, at two to five email touches each, which makes OS&D one of the most labor-dense intents in the queue.
The popular shortcut is to point the reporter at a claims portal or a PDF form and consider the ticket deflected. That is where claims go to die. The party reporting OS&D is often a receiver or third party with no login, the form asks for documentation they were never told to capture, and by the time a human re-reads the thread the notation window has passed. Deflection is exactly the wrong instinct for an intent where the first reply decides whether the claim is recoverable.
Ad hoc OS&D intake vs structured intake at a glance
| Dimension | Ad hoc intake | Structured intake |
|---|---|---|
| First reply | generic acknowledgment, days later | documentation checklist for the exception type, immediately |
| Evidence | photos and notations chased across follow-ups | requested while the freight is still on the dock |
| Claim deadlines | discovered when a human finally triages | tracked from the moment the exception is reported |
| Case file | rebuilt manually from a long thread | assembled as the thread unfolds |
Aide, the agentic AI platform for customer experience, treats OS&D as its own intent, not general correspondence. It recognizes an exception report on arrival, replies with the documentation checklist that matches the exception type, requests the delivery receipt notation and photos while they still exist, and builds the case file as evidence lands, with every automated step logged. What it never does is improvise on liability: claims language follows approved text, and anything conceding fault stays with a human. See Aide for logistics and freight for how exception intake fits the rest of a live freight inbox.
Frequently asked questions
- What does OS&D stand for in freight?
- OS&D stands for over, short, and damaged. Over is more freight than the paperwork shows, short is less, and damaged is visible or concealed harm to the goods. Together they cover the delivery exceptions that trigger claims.
- Is an OS&D report the same as a freight claim?
- No. The OS&D report is the exception record made at or shortly after delivery, usually noted on the delivery receipt. The freight claim is the formal demand for compensation filed against the carrier later, and it depends on the OS&D documentation to succeed.