Most demurrage is not a mystery. It comes from a handful of predictable handoffs where teams watch the wrong timestamp or notify the wrong person. One core pitfall is semantic. Arrival is not the same as available for pick up. Getting that distinction right changes outcomes.
The five leak scenarios you can prevent
1) Friday night ATA, Monday appointment scarcity
What happens: Discharge or ATA posts late Friday. “Available for pick up” flips over the weekend. Monday slots are already tight. Day one burns.
Why it leaks: Alerts are tied to arrival timestamps instead of the available milestone. Event names and timing differ by carrier and terminal. Standardization exists, but adoption varies.
- Do this: Alert on Available for pick up across carriers. Maintain terminal-specific booking lead times. Pre-stage chassis for weekend flips at high-risk terminals.
- Measure: Availability-to-appointment hours, LFD minus pickup hours, first-attempt pickup rate.
- Assumption to question: Do your target terminals show weekend availability flips, or is your leak actually a notify-party routing issue.
2) Arrival is not availability
What happens: Team celebrates ATA. “Available” posts hours later. Dray was not pre-booked. Free time burns.
Why it leaks: Arrival can mean first line ashore, not yard release. Arrival notices are customer documents, not release signals. The broker or dray dispatcher may not be in that chain.
- Do this: Subscribe to Available for pick up and Customs released. Route alerts to the person who books the truck. Escalate if no appointment within six hours of availability.
- Measure: Share of pickups executed within 24 hours of availability.
- Assumption to question: Are alerts landing in generic inboxes. Track time to first action, not time to email sent.
3) Customs hold releases after hours
What happens: Hold lifts at 19:00. Terminal is closed. The next viable slot is a day later.
Why it leaks: Customs and carrier events live in different systems. Alert rules ignore terminal hours, so no one secures the first morning slot.
- Do this: Merge Customs released with terminal-hours logic in alerts. If release occurs after close, auto-escalate to secure the first slot next day. When invoices look wrong, reference the U.S. billing rule for required fields and timelines.
- Measure: Release-to-appointment time, after-hours release capture rate.
- Assumption to question: Are you modeling terminal operating hours and cutoffs in alert logic, or treating releases as 24×7 events.
4) Chassis and yard constraints kill a confirmed slot
What happens: You get a slot, but there is no chassis or the yard cannot move it. Pickup slips. Charges start.
Why it leaks: Status tools focus on vessel and yard timestamps, not on chassis pools or appointment capacity dynamics.
- Do this: Pair appointment confirmation with chassis pre-booking where markets are tight. Keep a terminal-cluster playbook listing chassis providers, hours, and lead times.
- Measure: Appointment-kept rate, cancellations due to chassis unavailability.
- Assumption to question: Is the real constraint data freshness, or is it chassis procurement. Fix the right bottleneck.
5) Notify-party gaps delay downstream steps
What happens: Arrival notice goes to consignee and a stale notify. The broker or dray dispatch does not see it in time.
Why it leaks: BL master data is not maintained. The wrong actors receive the message and the clock runs.
- Do this: Quarterly audit of consignee and notify contacts by lane. Auto-CC the actioning party, for example the broker or dray dispatcher.
- Measure: Share of arrival notices with the correct actioning party, response time to arrival notices.
- Assumption to question: Is notify treated as FYI. Make it operational and measurable.
The money side: plan with a conservative band, then swap in your tariff
Demurrage and detention are per-container, per-day charges. Schedules are often progressive after the first few days. For planning, use a conservative U.S. band and replace it with your local tariff as soon as you have it.
| Input | Your value |
|---|---|
| Containers affected this week | |
| Days past free time per container | |
| Daily D or D rate (USD) | Use your tariff. If unknown, model with a low-hundreds baseline, then update. |
| Estimated charge = containers × days × rate |
Tip: Carrier and terminal documents publish exact schedules. Review those for your lanes and replace the band with real numbers before you brief finance.
Before you run this playbook: confirm two local facts
- Which event equals “available” at your terminals. Look up the exact label in the carrier or terminal feed that signals yard release. Examples you will see in standards or feeds include “Available for pick up” and “Customs released.” Wire alerts to that event. Not to ATA or discharge.
- Your actual demurrage or detention tariff. Note free time, the daily rate, and any escalation after a certain day. Replace the planning band in the calculator with these local values before you estimate savings or set targets.
Quick worksheet
| Lane or terminal | Exact availability event label | Free time | Daily rate (USD) | Escalation after day |
|---|---|---|---|---|
| Example: LA Pier XXX | “Cargo available” | 4 days | 225 | Day 4 to 375 |
| Example: NY/NJ Term Y | “Available for pick up” | 3 days | 180 | None |
Why it matters: If you alert on ATA when your terminal posts availability later, you miss the first bookable slot. If your tariff escalates after day 4 and the plan assumes a flat rate, the calculator will understate risk.
The fix: standardize events, route actions, enforce lead times
- Standards first: Map carrier and terminal data to a common vocabulary so “arrival,” “available,” “customs released,” and “gate-out” are unambiguous across carriers.
- Minimal alert set: Turn on three alerts only. Available for pick up. Customs released. Last Free Day minus N hours.
- Lead times by terminal: Maintain appointment lead-time rules per terminal cluster. Slot scarcity and yard capacity create real constraints, so book accordingly.
- Chassis pairing: In constrained markets, pair appointment confirmation with chassis pre-booking. Track appointment-kept rate, not just appointment-made.
- Dispute readiness: In the U.S., detention and demurrage invoices must include required fields and meet timelines. Missing fields strengthen your dispute posture. Use the federal rule as your checklist.
What to measure
- Availability-to-appointment hours
- First-attempt pickup success rate
- LFD minus one day pickup rate
- After-hours release capture rate
- Appointment-kept rate
Sources
- Standards and event vocabulary: DCSA Track and Trace; DCSA Glossary
- Arrival notice is a document to consignee and notify, not yard release: Maersk FAQ; Maersk explainer
- U.S. interpretive rule and billing requirements for D and D: FMC Interpretive Rule 2020; Final Rule 2024; FMC notice on effective date
- Slot scarcity and appointment dynamics: Queue and quota capacity study; Truck appointment system modeling
- Chassis and empties as systemic bottlenecks: FMC Fact Finding 29 Final Report and Executive summary
- Planning references for D and D ranges and definitions. Use local tariffs for exact numbers: DHL glossary; example carrier schedules MSC USA and CMA CGM D and D
Leave a Reply