What you’ll learn
- Conserve booking quantities across split loads.
- Distinguish proposed, committed and dispatched work.
- Recheck capacity and availability at commitment.
Useful terms
- Split load
- A consignment distributed across multiple movements.
- Reservation
- An allocation that reduces what is available to other work under defined rules.
Step-by-step operating routine
Select the departure and route
Confirm origin, destination or onward hub, departure window and suitable vehicle. Check route and resource readiness. Do not select a hub solely because it has spare space if it breaks the service promise.
Record or confirm- Origin
- Onward hub
- Departure window
- Vehicle
Review available freight
List package IDs or quantities physically available and eligible. Exclude held, already reserved or incompatible goods. Preserve the reason for an exclusion so staff can resolve it rather than manually bypass it.
Record or confirm- Available pieces
- Hold reasons
- Existing allocations
- Handling
Build a reviewable plan
Assign quantity by booking and check relevant capacity dimensions. Show excluded freight and predicted connection risks as estimates. Keep broader multi-stage optimisation clearly distinguished from the current depot planning capability.
Record or confirm- Allocated quantity
- Weight / volume
- Exclusions
- Connection assumptions
Commit with current checks
Recheck quantity, resource and revision state immediately before committing. If another planner changed availability, refresh and resolve the conflict. Do not silently trim a plan or duplicate a reservation.
Record or confirm- Record revisions
- Current availability
- Commit result
- Conflict owner
Confirm actual loading and dispatch
Scan or count actual pieces and reconcile against the plan. Record substitutions or shortages under controlled rules. Dispatch only the actual load, leaving the rest available, held or reserved according to its real state.
Record or confirm- Planned pieces
- Loaded pieces
- Difference
- Dispatch reference
100 cartons on two departures
A booking has 100 available cartons. Departure A commits 60 and departure B commits 40. Another planner must see no unallocated balance. If only 58 load on A, the two missing cartons require a location and resolution; they cannot disappear because the trip was marked dispatched.
- The allocation total never exceeds 100.
- Commit rechecks concurrent changes.
- Actual loading differences remain accountable.
Exceptions and mistakes to avoid
- Completing one departure does not complete the entire booking.
- Do not use illegal overloading to make a plan fit.
- A simulated network scenario must never reserve real freight.
Split-load reconciliation
Use one row per departure and reconcile all rows to the original consignment.
| Booking | Available before plan | Departure allocation | Actual loaded | Remaining state |
|---|---|---|---|---|
| LR 100 | 100 cartons | A: 60 | A: 58 | 2 discrepancy; B: 40 allocated |
Includes the illustrative row and blank rows. This is a planning worksheet, not a HiVAM import format. Keep your completed copy private; do not add credentials.
Check your understanding
Try answering first, then open the explanation. Use the worksheet and source records to practise the task.
Why recheck a plan at commit?
Availability, assignments or records may have changed while it was being reviewed.
Can a planning proposal count as dispatch?
No. Actual loading and controlled departure remain separate steps.
Put it to work with HiVAM
Use these connections to explore the relevant product workflows. Confirm access in your deployed release; API capabilities require an integration or an available interface.
Explainable depot load plans
Inspect proposals and exclusions, then commit selected loads with fresh checks.
Partial loads with complete quantity history
Keep every split quantity linked to its original booking.
Keep your learning moving.
0 chapters marked complete. Reading progress stays in this browser; it is not a qualification or your company’s setup progress.
Try the workflow with your team.
Bring a representative job and an exception to a HiVAM demonstration. Review saved records, permissions and handoffs alongside the interface.