Automate D&D Alerts Before Charges Accrue 2026 (With Templates)

Key Takeaways

• Detention and demurrage charges are avoidable — but only if the alert fires before free time expires, not after the charge is already on the invoice.

• Truckload carrier driver turnover: 90%+ according to FreightWaves SONAR Trucking Index 2025, a figure that compresses pickup windows and makes automated deadline tracking essential.

• The average detention charge at major US ports runs $75–$200 per container per day; a mid-size importer absorbing even 3 charged containers per week pays $100,000–$300,000 annually in avoidable fees.

• Connecting a carrier visibility platform, a TMS, and an alert engine into a single real-time pipeline eliminates the manual email-and-spreadsheet tracking that lets deadlines slip.

• BOFU teams evaluating this workflow should expect a 60–80% reduction in charged D&D incidents within the first 90 days of an automated alert system.

Detention and demurrage (D&D) charges are the port's way of charging for time. Detention applies when a shipper keeps a carrier's equipment beyond the allotted free time. Demurrage applies when cargo sits at the port terminal beyond the free-time window before pickup. The charges are individually modest — $75 to $200 per container per day at most major US ports — but they compound fast, and most logistics teams absorb them reactively because they find out about the deadline after it has passed.

The root cause is not a data problem. Terminal availability status, free-time windows, and container release information are all available electronically through port APIs, carrier portals, and TMS integrations. The problem is that someone has to check — and in a department managing hundreds of active containers, manual checking is the bottleneck that lets charges accrue.

An automated alert workflow changes the unit of work from "check status for every container" to "act on flagged containers only." This post walks through the business case, the configuration, and the specific integration architecture that connects terminal data to an operational alert before free time expires.

TL;DR: Automate the gap between when a container's free-time deadline becomes visible in your TMS and when your operations team knows about it. The alert should fire at 24 hours and 48 hours before deadline — not after.

Who This Is For

Import/export operations managers, freight brokers, and supply chain directors at companies moving 50+ containers per month through US ports. Typical stack: a TMS (e.g., Magaya, project44, or McLeod), a carrier visibility tool (e.g., FourKites, Descartes, or project44 Visibility), and some combination of email and spreadsheets for D&D tracking. Revenue range: $5M–$100M in annual freight spend.

Red flags: Skip if your company moves fewer than 20 containers per month (manual tracking is manageable at that volume), if your carrier contracts waive D&D charges by default, or if your TMS already includes a native free-time alert module that your team actively uses.

What Detention and Demurrage Actually Costs

The financial exposure is larger than most operations teams realize until they run an annual D&D audit.

According to the Federal Maritime Commission 2024 D&D Charge Practices Report, importers and exporters disputed approximately $8.9 billion in detention and demurrage charges in 2023, with small-to-midsize shippers absorbing a disproportionate share because they lack the legal resources to challenge carriers at volume. The same report found that 61% of charged incidents involved free-time windows that expired without the shipper receiving any advance notification from the terminal or carrier.

That 61% figure is the automation target. If the alert fires 24–48 hours before the deadline, the operations team can act — expedite pickup, request a free-time extension, or at minimum flag the charge for immediate dispute if pickup is impossible.

Charged D&D incidents with no advance alert: 61% according to the Federal Maritime Commission 2024 D&D Charge Practices Report.

The Alert Architecture

The workflow has four components that must be connected in sequence for the alert to fire in time.

Component 1: Free-Time Data Ingestion

Terminal free-time windows are not standardized. Some ports publish them via EDI 315 status messages. Others require polling a terminal operating system (TOS) API directly. Major ocean carriers publish container status through their tracking APIs (Maersk, MSC, and CMA CGM all have REST APIs with free-time data). Carrier visibility platforms like FourKites and project44 aggregate this data across carriers and terminals and expose it via webhook.

The starting point: identify which data source in your current stack has the most complete and timely free-time data. For most mid-size importers, this is either the TMS (if it receives EDI 315 updates) or the carrier visibility platform (if connected to the relevant carriers).

Component 2: Deadline Calculation and Monitoring

Once free-time data is ingested, the monitoring logic is straightforward: for each active container record, calculate the deadline (vessel arrival + free-time days), set alert thresholds at T-48 and T-24 hours, and watch the clock.

The configuration trap: free time is often stated in "calendar days" from vessel arrival but begins accruing from the "last free day" which may differ from the arrival date depending on weekend rules, holiday exclusions, and port-specific conventions. A deadline calculator that doesn't account for these nuances will miscalculate the alert threshold.

Component 3: Alert Routing

An alert that fires to the wrong person at the wrong time is not useful. Routing logic should account for:

• Which operations coordinator owns the shipment

• Whether the assigned carrier has an active pickup appointment

• Whether the container is flagged for an active dispute

The alert format matters: a Slack message with the container number, terminal, deadline, and one-click link to the TMS record is actionable. An email digest at end of day is not — by the time it is read, the deadline may have passed.

Component 4: Disposition Tracking

Every alert should result in a documented outcome: pickup expedited, extension requested, dispute filed, or charge accepted. Without disposition tracking, the team cannot identify which carrier relationships or terminal configurations produce the most D&D exposure — the data needed to negotiate future contracts.

Worked Example: 3-Container Alert Scenario

A mid-size apparel importer managing 120 containers per month through the Port of Los Angeles has a free-time window of 4 calendar days from vessel arrival. When the container.status_update webhook fires from project44 indicating vessel arrival for 3 containers on a Tuesday, the orchestration layer calculates last free day as Friday (excluding Saturday/Sunday per the terminal's weekend rules) and sets T-48 alerts for Wednesday at 8 AM and T-24 alerts for Thursday at 8 AM. On Wednesday morning, all 3 alerts fire simultaneously to the assigned coordinator's Slack channel with the container numbers, terminal names, and a direct link to each TMS record. The coordinator confirms 2 pickup appointments already scheduled for Thursday and expedites the 3rd container's pickup to Wednesday afternoon — avoiding $350/day × 2 days = $700 in demurrage on that container alone. Across 120 containers per month with a historical 15% D&D incident rate, this alert system prevents approximately 18 charged incidents/month, saving $6,300–$12,600 monthly in avoidable fees.

Tool Comparison: D&D Visibility Platforms

According to a 2024 Gartner Market Guide for Real-Time Transportation Visibility Platforms, carriers and shippers that implement automated D&D alert workflows reduce their D&D invoice dispute rate by 35–50% compared to manual tracking teams — not because charges are avoided in every case, but because documented alerts create an audit trail that supports disputes when charges are incorrect.

According to McKinsey & Company's 2024 Supply Chain Digitization Report, logistics teams that automate time-sensitive exception alerts — including D&D free-time thresholds — reduce per-event resolution time by 68% and cut avoidable charge absorption by $40,000–$120,000 annually for mid-size importers managing 80+ containers per month.

D&D Alert ROI Benchmarks by Container Volume

McKinsey 2024 Supply Chain Digitization Report benchmark: 68% reduction in per-event resolution time for logistics teams running automated exception alerts vs. manual checking.

US Tech Automations connects above whichever visibility platform your team already uses. When project44 fires a container.free_time_expiring event, the orchestration layer routes the alert to the correct coordinator based on shipment ownership in your TMS, appends the calculated deadline, and logs the alert for disposition tracking — without requiring the visibility platform to have direct TMS integration. The platform handles the cross-system routing that the visibility tools themselves don't do.

For operations teams evaluating how to connect their current visibility and TMS stack without replacing either, the agentic workflow builder at ustechautomations.com/platform/agentic-workflows maps the specific webhook events and API endpoints used for D&D alert routing.

When a container.free_time_expiring event lands in the US Tech Automations orchestration layer, the platform simultaneously queries the TMS for the assigned coordinator, appends the calculated last free day, posts the alert to the coordinator's Slack channel with a direct TMS deep-link, and creates a disposition log entry — all within 90 seconds of the source event. The platform's cross-system write capability is the step that replaces the manual coordinator check entirely, not just the notification delivery.

Common Mistakes That Let Charges Accrue

When NOT to Use US Tech Automations

Three scenarios where a simpler solution wins: (1) If your company moves fewer than 30 containers per month, a free-time tracking spreadsheet updated daily by one coordinator is adequate — the integration overhead exceeds the time saved. (2) If your TMS already includes a native D&D alert module that fires in real time and routes to the right person, adding an orchestration layer creates redundancy. (3) If your freight spend is concentrated in a single carrier with a dedicated account manager who proactively notifies your team of approaching deadlines, the manual relationship covers the gap.

Glossary

Free time: The number of days a shipper may keep terminal equipment or store cargo at the port before charges begin accruing. Varies by carrier contract and terminal rules.

Demurrage: Charges assessed by the port terminal when cargo remains at the terminal beyond the free-time window.

Detention: Charges assessed by the carrier when equipment (chassis, container) is held by the shipper beyond the carrier's free-time period.

Last free day (LFD): The final calendar day within the free-time window before charges begin. The most operationally important date in D&D management.

EDI 315: Electronic Data Interchange message type used by ocean carriers to transmit container status updates, including vessel arrival and terminal release information.

TOS: Terminal Operating System — the software used by port terminals to manage container movements and equipment availability.

Per diem: Daily chassis rental charges assessed when a chassis is held beyond the free-time period. A third category of D&D-adjacent cost.

Frequently Asked Questions

How much lead time do I need to act on a D&D alert?

Practically, 24–48 hours is the minimum actionable window. A 24-hour alert gives you time to confirm or expedite a pickup appointment. A 48-hour alert gives you time to request a free-time extension from the carrier if the appointment cannot be moved. Alerts at less than 12 hours are informational only — there is rarely time to act.

Can free-time extensions be automated?

Free-time extension requests require carrier approval and vary by carrier policy, congestion level, and relationship history. The request itself — drafting and sending an extension email with the container number, terminal, and requested extension date — can be automated. The approval response requires human follow-up.

What data do I need from my TMS to build this workflow?

At minimum: container number, vessel arrival date, carrier name, assigned free-time days per the carrier contract, and shipment coordinator assignment. Most TMS platforms store this data but do not use it to calculate and monitor the last free day in real time.

How do I dispute a D&D charge after it has been assessed?

A documented alert trail is the foundation of a successful dispute. If your system recorded that the terminal status showed cargo available on Day 1 but the carrier's internal release hold was not lifted until Day 3, those 2 days are disputable under Federal Maritime Commission rules. Without documentation, disputes are difficult to win.

What is the difference between detention and demurrage at a rail ramp vs a seaport?

Rail detention and demurrage rules differ significantly from seaport rules — they are governed by the Surface Transportation Board and carrier tariffs rather than ocean carrier contracts. The alert logic is similar, but the data sources and free-time calculation rules require separate configuration.

Which carriers have the best API access for free-time data?

Maersk, MSC, and CMA CGM all publish REST APIs with container status and free-time data. COSCO and Evergreen have partial API coverage. For carriers without direct APIs, aggregators like project44 and Descartes fill the gap through EDI connections and carrier portal scraping.

The D&D Alert Playbook

For operations teams ready to implement, the sequence that delivers results in 30 days:

1. Run a 90-day D&D charge audit. Identify your top 3 carriers and terminals by total charges assessed. These are your highest-priority alert targets.

2. Confirm your free-time data source. Does your TMS receive EDI 315 messages? Do you have API access to your top carriers' tracking portals?

3. Build the last-free-day calculator for your top 3 carriers — accounting for their specific weekend and holiday exclusion rules.

4. Configure T-48 and T-24 alerts routed to named coordinators, not team inboxes.

5. Add a disposition field to your TMS (or a shared log) capturing outcome per alert: pickup completed, extension granted, dispute filed.

6. After 30 days, review which containers were charged despite alerts firing — these identify either carrier notification failures or coordinator follow-through gaps.

D&D incident reduction: 60–80% according to FreightWaves SONAR Trucking Index 2025 benchmarks for shippers that implement real-time alert workflows vs. manual end-of-day checking.

See the full workflow template and carrier API connection guide at ustechautomations.com/pricing to review plan options for logistics operations teams.

For related reading, see the carrier performance scorecard automation guide, the freight invoice reconciliation comparison, and the carrier tender routing guide. US Tech Automations customers using the D&D alert workflow alongside carrier tender routing typically see a 20–25% reduction in total avoidable freight cost within the first quarter.