Client
Regional air-freight forwarder
Industry
Air Freight
Timeline
Visibility first, then documents and release work
Key takeaway
The team stopped chasing status and started working the shipment, the paperwork, and the exception in the same place.
Air freight does not stall only because a flight is late. It stalls because the status is in one place, the paperwork is in another, and the release check is waiting on someone who has not seen either. This forwarder's operations team was assembling that picture by hand while cargo sat. We built a control point for the people who move shipments: cargo status, operational documents, release and duty checks, receipts, inbound requests, and the internal work sitting behind them.
The challenge
A status update meant checking more than one handler. Documents and receipts were prepared beside the shipment instead of with it, so a missing paper showed up as a delay. Release, duty, and inbound requests had no shared queue, which meant the person who noticed a problem was often not the person who could clear it. Volume made the gaps more expensive, not more visible.
Status in pieces
Progress across carriers and cargo handlers had to be assembled before anyone could say where a shipment actually was.
Paperwork off to the side
Operational documents and receipts were easy to lose track of, and a missing one held freight that was otherwise ready.
Exceptions without an owner
Release checks, inbound requests, and follow-up sat in separate handoffs, so they waited until someone went looking.
What we built
Operations watches active shipments, prepares the documents those shipments need, and reviews release and duty work from the same desk. Receipts and inbound requests sit with the shipment they belong to. Managers see activity, staffing, and the health of the book without asking the floor to compile a report.
- A live view of shipment and cargo-handling status across the sources the team already uses
- Batch monitoring for the freight that is actually in motion
- Operational document preparation kept with the shipment
- A workspace for duty and release checks
- Inbound requests and payment receipts in the same operational picture
- Role-based views for operations, activity, and management reporting
Before & after
Before
- Staff rebuilt shipment status from separate handler updates
- Documents, receipts, and release checks moved on their own timelines
- A straight answer on the active book meant asking the floor
After
- Shipment and cargo-handling status are reviewed from one workspace
- Documents, receipts, inbound requests, and release work sit with the shipment
- Managers see activity and the state of the operation without a compiled report
Built with
Our approach
01
Audit
We mapped the points where a shipment changed hands: tracking, documents, release, receipts, and internal follow-up.
02
Build
We built the desk around the tasks the floor repeats every day, then opened reporting for the people managing it.
03
Pilot
The team ran daily shipment monitoring and the work around it in the new desk before it became the default.
04
Support
We extend the operational views as lanes, handlers, and reporting needs change.
Frequently asked questions
More engagements