Who owns the outstanding load work?
Use Load workload by owner to examine the operating organization, assigned person and lifecycle state alongside the original delivery promise.
Explain parcel movement, delivery performance and unresolved actions from their underlying evidence.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 30 | ||
| Planned | 17 | 57% | |
| Dispatched | 9 | 53% | |
| In transit | 6 | 67% |
Sample totals per stage
Use Load workload by owner to examine the operating organization, assigned person and lifecycle state alongside the original delivery promise.
Read Assignment window register and Driver eligibility register, then examine Critical vehicle defect history where readiness needs investigation.
Follow Parcel milestone history by load and tracking number, keeping physical event type separate from the record's review status.
Use Independent scan decision history to trace the source revision, reviewer and decision reason.
Read Delivery timeliness against the original promise, then use Stop evidence register to inspect the actual service and proof reference.
Use Operation discrepancy register to find uncertain effects and the revision each action expected.
Group Loads by Organization, Owner and Status with promised delivery at and freight amount USD to distinguish operational work from recorded freight value.
List load assignments with Load, Driver, Vehicle, starts at, ends at and Status to inspect overlapping commitments.
List Drivers with driver code, Active, eligibility until and external authority for the assignment interval under review.
Group vehicle defects by Vehicle and show reported at, Severity, repair evidence and released at without treating every historical Critical entry as currently open.
Group parcel scans by Parent and tracking number with scan type, scanned at, package weight LB, Status and Revision, retaining repeated milestones without summing their weight as separate parcels.
Compare actual delivery at with promised delivery at on Delivered Loads and group by actual delivery week, retaining late deliveries against the original promise.
Group load stops by Parent and stop sequence with window start, window end, actual arrival at, actual departure at and proof reference.
Group review decisions by Parent and source revision with Reviewer, Decision, Reason, decided at and operation key.
List operation receipts with result state Pending, Failed or needs review alongside expected revision, effect references and failure reason.
Start free, then use Proto to change fields, steps and approvals before your team goes live.