Cargo contracts and custody: questions to ask before accepting freight responsibility

A transportation agreement can assign operational responsibility long before a loss reveals how the policy responds.

By Aditya Bhatt · Freight operations and cargo records. Originally published by Embarcadero Risk.

Spot the contractual trigger

A new shipper agreement, broker arrangement, warehouse contract, or subcontracted-haul relationship should prompt a review before service begins. The contract may use words such as custody, control, indemnity, limitation, or responsibility that do not by themselves describe the insurance available.

Do not limit the review to the master agreement. A rate confirmation, shipper instruction, warehouse receipt, bill of lading, or email change can alter the practical handoff. The business should be able to show which document governs the particular move and whether its operating staff follows the process written into the agreement.

Collect the document chain

Assemble the executed agreement, bills of lading, rate confirmations, warehouse receipts, shipper instructions, delivery records, and subcontractor documents. Create a simple handoff map showing who has possession, who signs, and where goods can wait at each stage.

The handoff map should identify more than names. Note who loads, seals, scans, signs, inspects, stores, and has authority to redirect the shipment. A clear map also surfaces cases where a carrier has physical possession but another party controls instructions or where freight is held after an attempted delivery.

Compare assumed responsibility with terms

Review the cargo form’s covered-property definition, valuation, exclusions, limits, deductibles, territory, and conditions against the actual handoff process. Also compare contract insurance requirements with the relevant policy and endorsements; a certificate is evidence of insurance and does not amend the policy.

Read limits and valuation alongside the contract’s damage, delay, indemnity, and notification language. An agreement may require a response or proof that is operationally difficult to produce if drivers do not retain photographs, exception notes, seals, or delivery records. Flag that process issue before it becomes a loss-file issue.

Keep the answer usable

Record clauses that require a business decision, follow-up, or contractual revision. Retain the final contract packet and coverage-review questions with the account record, especially when a shipper changes commodities or routes. Policy wording, declarations, and endorsements control.

After accepting a new account, test the record against the first completed shipment. Confirm that the documents, custody map, and actual dispatch practice agree. If a new shipper’s process is different from the standard workflow, place that distinction in the account file and raise it in the next coverage review.

  • Who has possession at every handoff?
  • Which documents establish shipment value?
  • Can freight be stored before final delivery?
  • What does the agreement actually require?

Test the agreement against the handoff on the floor

A contract can describe a clean transfer of responsibility while the actual operation uses a different sequence of drivers, docks, temporary storage, and exception calls. Ask an operations lead to walk through a routine pickup and a delayed delivery, then compare that account with the documents the contract says should govern.

Pay particular attention to a refused delivery, a consignee request to redirect freight, an overnight hold, or a substituted carrier. These are ordinary operational events that can change who has possession, what documentation is created, and which contract terms the team relies on. The review should identify the record expected at each point.

If a shipper requires a special process, add it to the account instructions and confirm that dispatch, drivers, and warehouse staff can follow it. Retain the final workflow with the agreement so the insurance review uses the same facts the operation is expected to follow.

Follow a refused shipment through the contract file

A refused delivery is a useful stress test because freight may remain in a trailer, move to a terminal, return to the shipper, or be redirected to another consignee. Write down who can give those instructions and which document records each choice. Preserve the original delivery attempt, exception code, customer communication, seal record, and any new rate confirmation. Do not assume the original pickup-to-delivery description still captures the whole custody period.

Compare the shipper agreement, bill of lading, warehouse receipt, and subcontractor terms for the delayed interval. Ask who has possession, who bears responsibility under each document, how value is measured, and whether a deadline or notice requirement applies. If the documents disagree, record the conflict for operational and contract review before treating it as an insurance conclusion. A certificate cannot resolve that conflict by itself.

Use the resulting timeline to ask precise policy questions about transit, storage, unattended vehicles, valuation, and subcontracted carriage. Confirm how dispatch will handle the next refusal: who contacts the shipper, where the load may wait, who authorizes a transfer, and how the condition of the goods is documented. The point is to make the process repeatable and the coverage question answerable.

Get Help With Insurance Buying and Renewals.

Get help buying coverage and managing renewals, with less paperwork for your team. Create your account and submit an insurance request online.

Talk to Spot