Peak Amazon Relay Volumes: Ops Playbook for Q4

Scenario
Amazon Relay released its peak surge schedule two weeks early, increasing overnight live loads by 22%. FreightWaves’ Sep 12 update highlighted lane congestion in Dallas, Houston, and Memphis.
Risks
- Unbuffered tender windows causing dock conflicts.
- Overlapping vendor tickets delaying outbound dispatch.
- Leadership visibility gaps on exception trends.
Checklist
- Reconcile Relay board updates against ROC dashboards every two hours.
- Stage a surge roster in Coda and tag on-call dispatchers by shift.
- Run n8n automation to notify Amerit when trucks exceed two open tickets.
- Drop a nightly Telegram digest summarising misses and recoveries.
- Log vendor escalations and pass-through costs for the weekly operations pulse.
Tools we use
- Coda surge roster with live exception views.
- n8n to push automated load status changes to Telegram.
- NetraDyne to monitor driver behaviour during back-to-back loads.
- Amerit portal for realtime maintenance ticket status.
Outcome to measure
Hold 98% on-time departures, keep vendor acknowledgements under 15 minutes, and surface exceptions in the exec dashboard by 08:30 ET daily.
Operator next steps
- Assign a surge captain for each shift and confirm relief coverage.
- Update escalation sheets with vendor contact tiers.
- Publish a midpoint review during the Friday operations huddle.
Source: FreightWaves prime update



