How to Write a Freight Service Level Agreement That Actually Protects You

Most freight forwarding relationships operate without a written service level agreement. The arrangement is informal: the client sends a booking request, the forwarder quotes and executes, and everyone hopes the other party's expectations match. When something goes wrong — and eventually something always does — the absence of a written SLA means both parties are arguing from memory about what was agreed. An SLA that takes 90 minutes to write prevents disputes that take 90 days to resolve.

What a freight SLA should cover

The service scope is the first section: which services are included (freight forwarding, customs clearance, inland transport, warehousing) and which are explicitly excluded. Many SLA disputes arise not from the service that failed but from the service that was assumed to be included and was not. Be specific — 'customs clearance at port of discharge' and 'customs clearance at destination CFS' are not the same service.

Service standards define what good performance looks like on specific, measurable dimensions. Booking confirmation within four business hours of a request. Pre-alert sent to consignee 48 hours before vessel arrival. Customs documentation filed at least three days before vessel arrival at discharge port. Invoice issued within two business days of cargo delivery. Proactive notification within four hours of any exception that will affect the delivery commitment. These are the standards that clients actually care about — and the standards you can actually meet consistently.

Liability limits are the section most freight forwarders avoid writing because it makes the limitation explicit. But an SLA that does not specify liability limits leaves you exposed to unlimited claims on the goodwill of the client's lawyer. The standard approach: reference the applicable liability convention (CMR for road freight, Hague-Visby Rules or COGSA for ocean) and your own terms and conditions, and specify the cap as the lower of the actual freight charges for the affected shipment or a defined monetary amount. Clients who need broader coverage should take out cargo insurance — and the SLA should recommend they do.

The escalation and dispute resolution clause that actually gets used

Disputes in freight forwarding are almost always about money or timeline — a demurrage charge the client disputes, an invoice discrepancy, a delivery that arrived late and caused a client loss. The escalation clause should specify: first, a 30-day period for the parties to resolve the dispute directly, with a named contact on each side. If not resolved, mediation through a defined body before arbitration or litigation. Specifying the governing law and jurisdiction explicitly — particularly important for India-GCC contracts where the parties are in different jurisdictions — avoids the satellite dispute about where a primary dispute gets heard.

Key Takeaways

1. A freight SLA takes 90 minutes to write and prevents disputes that take 90 days to resolve. The most common SLA disputes are not about service failure — they are about what was assumed to be included but was not written down.

2. Service standards should be specific and measurable: booking confirmation time, pre-alert lead time, filing deadline, invoice turnaround, and exception notification window. Vague standards cannot be enforced.

3. Include the escalation clause with a named contact on each side, a 30-day resolution period, and a defined mediation or arbitration pathway. Specify governing law and jurisdiction — India-GCC contracts must be explicit about this.

Tags:#SLA#FreightContracts