These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Manufacturing TMS
- Features
- Load planning
Load planning
Prepare the load, transport partner and stop sequence before committing the trip.
OverviewMy loads×
Manufacturing TMS · Load planning
New
My loads
Loads
| Record number | Subject | Owner | Lane | Planned departure | Promised delivery at | |
|---|---|---|---|---|---|---|
| LDS-78342 | Draft lds-152 | LNE-124 | 08 Oct | 15 Oct | ||
| LDS-41808 | Planned lds-885 | LNE-845 | 24 Oct | 29 Oct | ||
| LDS-56875 | Dispatched lds-792 | LNE-121 | 07 Oct | 11 Oct | ||
| LDS-16867 | Delivered lds-437 | LNE-635 | 26 Oct | 28 Oct | ||
| LDS-96455 | Exception lds-989 | LNE-350 | 17 Oct | 22 Oct |
6 of 6 records
Draft lds-152Loads · LDS-78342
DraftLaneLNE-124
Planned departure08 Oct
Promised delivery at15 Oct
What you can do
Start with the plant's transport requirement
A materials shipment can miss its plant commitment before a truck leaves the yard. The Transport Planner needs the item being moved, the requested units and the destination promise together when deciding whether the trip is ready. Load planning holds that information against an identifiable load and its responsible owner. A lane describes the movement, while the linked transport partner identifies the carrier, broker, shipper or logistics provider involved.
Use Loads Awaiting Approval to review drafts awaiting the planning decision. A load with an unclear quantity needs attention before assignment. A changed delivery promise needs a conversation with the receiving plant. The planner records that decision against the current revision so the Dispatcher can work from an agreed transport requirement.
How the work is organized
- Load scope. Record the item code, requested units, planned departure and promised delivery. Keep the load subject recognizable to the receiving team, and select the organization and owner responsible for the move.
- Stop sequence. Add pickup, delivery and service stops in their intended order. Each stop carries an address, contact and arrival window start. The Dispatcher uses these details to distinguish an intermediate stop from the final delivery.
- Planning decision. The Transport Planner reviews the load before marking it Planned. Keep the review reason associated with the source record and revision. A later change deserves a fresh comparison with the dispatch arrangements already made.
What to agree during setup
Agree how item codes and requested units relate to your production or warehouse system. A load quantity needs a shared unit convention; the receiving plant should understand the same quantity as the dispatch team. Choose recognizable lane names and stable transport partner codes. Review who owns a load when the sending and receiving plants belong to different operating companies.
Set the planning handoff with the Dispatcher. It should identify which requirements must be settled before assignment and who resolves a late change. Standard routes can provide origin, destination, distance and planned duration for reference. Any connection to production demand or warehouse orders needs an agreed mapping and source owner during implementation.
Check the handoff on an actual case
Rehearse a load carrying 18 pallets of components from a supplier to the assembly plant. The Transport Planner records the item code and requested units using the plant’s agreed unit convention, then adds the pickup and delivery stops. The receiving contact asks for an earlier arrival. Review the delivery promise before changing the plan and tell the Dispatcher which revision to use.
Compare that planned load with its assignment and plant appointment. They should identify the same movement and still make sense together. If the truck cannot reach the revised appointment, keep the conflict visible and resolve it before dispatch. Record the planning decision without treating an approved dock reservation as evidence that the truck has departed.
What your team sees
- Loads Awaiting Approval — Draft loads awaiting the planning decision, with quantities and delivery commitments.
- My loads — Loads owned by the signed-in team member, with departure and delivery dates.
Follow the work through
Follow load planning and dispatch, then review the plant appointment decision.
What it keeps track of
Data model- Loads
- Planned and executed transport loads
- Load stops
- Pickup, delivery and service stops on a load
- Routes
- Standard lanes between an origin and destination
- Transport partners
- Carriers, brokers, 3PLs and shippers linked to transport work
- Organizations
- Carrier, broker, shipper and operating companies using the platform
- Team members
- Dispatch, planning, safety and maintenance staff
- Review decisions
- Approval, rejection and escalation decisions on records
Who uses it
Permissions- Transport Planner
- , Dispatcher, Admin.
- The Transport Planner owns the plan; the Dispatcher confirms the operational handoff and Admin maintains the organization and staff context.
Set up Manufacturing TMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.