In cold-chain logistics the deliverable is not movement. Anyone can move a pallet. What the shipper is paying for is a defensible record that the right thing stayed in the right state through every handoff — and when a claim arrives, that record is the product, retroactively and expensively. Custody and condition are one evidence problem, and the handoff is where both records break today.
The claim you're actually paid for
Read your own cold-chain contracts as an operator and the structure is plain: the service is temperature-integrity plus proof. A load delivered in perfect condition with an indefensible record loses a claims dispute to a load delivered warm with a good one. The site that wins claims, passes client audits, and gets named in the solutions team's bids is the site whose record survives hostile reading. That is an operations capability, and it is built at the dock, not in the claims office.
The worked sequence: reefer, dock, cooler
One inbound handoff at a cold storage site, recorded as events. Three custody-relevant moments (illustrative throughout):
| # | Event | What today's systems capture | What goes silent |
|---|---|---|---|
| 1 | Reefer arrives, doors opened | Carrier's telematics: trailer temp trace, arrival time, stop number | Whose observation opened the record — carrier's device, under whose warrant |
| 2 | Freight received at dock, custody changes hands | WMS receipt: facility code, timestamp, quantities; a signature image | Who accepted custody — the receiving worker, plausibly agency labor, appears nowhere the record can carry |
| 3 | Pallets in the cooler, put-away complete | Location scan; cooler's own temp log, in a separate system | The join — which person or agent moved which pallet through the ambient gap, and for how long |
EPCIS 2.0 gives this sequence a proper shape: each moment is a conformant event, and condition rides on the event itself through the standard's native sensor data (sensorElementList — temperature on the custody record, not in a logger file joined by hand after a claim). What, when, where, why, how: all five of the standard's dimensions are answerable, and with sensor data on the events, condition is continuous across all three rows.
Two questions remain structurally unanswerable in the standard alone, and they are the two a claims adjuster asks first. Who accepted custody at row 2? And under whose warrant was each observation recorded? EPCIS 2.0 §7.2.2 defines five event dimensions and no performer among them; the party fields are organisation-grain (CBV 2.0 §8.7.1) — a company, never a person, an agent, or a device acting for one. Ten minutes, the specs are public, don't take our word for it.
Condition without custody is a thermometer log; custody without condition is a signature
The industry's two partial answers fail in mirrored ways. A temperature trace with no attributed custody tells you the trailer was cold — it cannot tell you your site's exposure, because it cannot say when your people's responsibility began and whose hands the freight was in through the gap. A signed receipt with no condition tells you custody transferred — it cannot tell you the state of what transferred. Claims live precisely in the seam between the two, which is why they take months: each party holds half a record and argues about the missing half.
The complete record closes the seam with two grains the standard omits, carried on every event and never merged. who is the attested observer — the dock worker whose identity is verified at the scan, the agent, or the embodied agent, since on an automated dock the observer may be a machine; the grain itself, agent-human-thing, is the problem id.org.ai names. capturedBy is the warrantor account — who stands behind the capture. On a dock running agency labor the distinction is not pedantry: the temp worker observes; the site's account warrants. A claims conversation needs both answers, and a record with one field for the two parties can support neither attribution nor accountability.
What the claims conversation looks like with the chain in hand
A shipper alleges heat exposure on a delivered load. With the complete chain: the trailer trace closes at door-open with an attested observation; the receiving event names its observer and its warrantor and carries the dock temperature; the put-away event bounds the ambient gap to eleven minutes, attributed. Each event's identity is its CBV 2.0 §8.9 content hash, so the shipper verifies every record independently — without joining anything of yours. The conversation is one meeting with exhibits, not a season of discovery. And the same chain is the demonstrable answer your solutions team needs the next time an RFP's traceability clause asks who handled the freight.
Pilot it where the evidence burden is already highest — one cooler, one dispute-prone lane. Get started: the interview branches for 3PL and cold-chain operators, and the site-operations questions are in it.