Operations overview

Operations Overview brings load visibility into one place. It presents active loads, on-time deliveries, pending decisions, failed operations, delivered-by-week and late-by-partner charts, and an exception queue. The Dispatcher can use that picture to identify a load needing pickup confirmation or a carrier event needing review. The Operations Reviewer can focus on decisions and receipt discrepancies before the team treats an operation as complete.

The page is an aggregate view of operating records. A chart is useful when it leads back to the load, its partner and the evidence behind the timing. The Operations Analyst should compare the original promised delivery time with actual delivery, then inspect the ordered stops and carrier events when a load is late. A late partner chart should lead to an operational discussion about specific loads rather than a broad judgment based on one status.

• Triage. Dispatcher checks active loads and the exception queue for immediate pickup, transit or delivery action.
• Review. Operations Reviewer checks pending decisions and failed operations against the relevant load revision and receipt.
• Explain. Operations Analyst uses delivered-by-week and late-by-partner views to find the records behind a trend.

The page should support a clear handoff. A Dispatcher seeing an Exception opens the load to find its owner, promised time and transport partner. A reviewer seeing a failed operation opens the receipt to compare its operation key, expected revision and linked effect. When a load is marked Delivered, the team can inspect actual delivery time and recipient proof separately.

Agree which statuses count as active for daily review and who owns each exception. Decide what constitutes an on-time delivery: the load’s actual delivery time compared with its promised delivery time gives a direct basis. Set a routine for checking pending decisions and failed receipts before the next dispatch wave. Assign a person to resolve discrepancies so an item does not sit indefinitely in the queue.

The team should also decide how it reports partner performance. Transport Partners carry the partner identity, while Loads carry the promised and actual delivery times. A provider-reported delay is a different measure from final lateness. Show both where useful and keep the load-level evidence available for a disputed event.

At the start of a shift, the Dispatcher finds a Planned load in Active loads, confirms the assigned driver and vehicle, then records pickup when it occurs. Later, a carrier milestone arrives with a reported delay. The reviewer checks the milestone against the load and records the outcome. If the linked operation receipt is Failed, Operations Overview points the team to a reconciliation task instead of treating the event as settled.

After delivery, the Dispatcher records proof and actual delivery time. Operations Analyst uses the delivered-by-week and late-by-partner charts to locate this load and compare it with the promised time. If the load is late, the team opens its stop windows and carrier milestone history to explain the difference, with the Load Owner responsible for any correction request.

• Active loads — Work in planning, dispatch, transit and exception status with owner and partner.
• Receipts needing review — Failed and review-needed effects linked to their parent loads.
• Delivery exceptions — Loads whose operating status calls for follow-up.

See pickup and transit, carrier event review and corrections and reconciliation.