Follow the handling unit beyond the first trailer
A regional network needs more than a shipment marked in transit. Freight moves across pickup, dock, linehaul, transfer and delivery, while documents, charges and driver pay must retain the same operating context. EXSPEEDITE's baseline includes city cartage, crossdock-floor workflows, office transfer, pallet tracking and OS&D alongside dispatch, rating and settlement.
Bring a handling unit that splits from its original shipment, arrives short or changes its outbound plan. The evaluation should demonstrate how its identity and discrepancy history follow the work. A clean manifest total is useful only when the team can explain the physical units behind it.
Connect the floor to the office record
Pallet barcode tracking should be evaluated with your label format, scanner behavior, duplicate-read handling and relabeling process. A successful scan and a confirmed custody event are related but distinct. Ask what evidence a scan supplies and what additional review is needed when a label is unreadable or the count disagrees.
For a drag-and-drop floor interaction, require a demonstration of the actual supported interface and permission behavior before making it a rollout commitment. The important acceptance condition is that moving a unit in the interface does not create an unexplained second assignment or erase the previous custody record.
Rehearse one difficult terminal transfer
- Receive the shipment and identify the expected handling units. Retain the source expectation even if the count is later corrected.
- Record the relevant pallet or label observations and actual dock location. Resolve unreadable or conflicting identifiers through an owned exception.
- Associate OS&D evidence, photos or documents with the affected units. Preserve the review and communication path.
- Build the outbound manifest and review capacity and routing requirements through your operating process. Prevent an unresolved duplicate assignment from becoming an accepted plan.
- Transfer the operating record to the next terminal or office and demonstrate how a delayed event or split manifest is reconciled.
- Apply the approved customer rating and driver-pay rules, then carry the supporting evidence into billing and settlement review.
Rating and settlement must understand the operating path
A shipment can produce several physical legs without becoming several unrelated commercial orders. The evaluation should show how the proposed configuration relates those legs to the customer's agreement and the driver's work. Bring a rate example and a multi-leg pay example that your finance team has already calculated.
For EDI, the baseline suite includes 204, 990, 214, 997 and 322 workflows. Confirm the actual partner mapping and message direction you need. A transport acknowledgment is not proof that every business condition was accepted. Include duplicates and revisions in the demonstration rather than testing only a single clean message.
Measure handling clarity, not an invented throughput claim
A useful pilot records time to locate a unit, unresolved discrepancies, duplicate assignments, missing-document work and the effort required to reconcile a transfer. Those measures belong to your operation. Do not assume a published pallet-per-hour improvement without a representative test.
Request a regional crossdock review with Scott Elliott. Bring a redacted manifest, label example, discrepancy and driver-pay agreement. We will focus the demonstration on the point where the physical freight and office record most often separate.
Questions from LTL and crossdock teams
Does the scope include pallet tracking and OS&D?
Yes, those functions are part of the owner-supplied product baseline. Validate the actual label, scanner, discrepancy and document workflow for your operation rather than assuming every device and label format is already configured.
Is a drag-and-drop floor interface guaranteed for every setup?
Confirm the exact supported interface and configuration in the demonstration. Test permissions, duplicate assignment, reversal and the relationship between an on-screen movement and the actual custody event.
Can a manifest split retain the shipment relationship?
Make that an explicit acceptance scenario. Ask the team to follow the unit, commercial order, physical leg and financial record through the split and subsequent correction.
How should an unreadable pallet label be handled?
The workflow should preserve the discrepancy and an authorized reconciliation path. Creating a second identity simply to clear a screen can hide the original unit rather than resolve it.
Can we evaluate interterminal driver pay?
Bring the actual leg and pay agreement. Test loaded/empty distinctions, stop items, relevant deductions and the correction path with the controller's approved expected result.
What should we test with EDI partners?
Test message identity, partner mapping, acknowledgment meaning, duplicate handling, revisions and failed delivery. The demonstration should show the source record and the owned exception, not just a successful file transfer.