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.
- Fuel Management System
- Features
- Load context
Load context
Connect a purchase to the load, assignment and stop information that explains the transport work.
OverviewLoads Awaiting Approval×
Fuel Management System · Load context
New
Loads Awaiting Approval
Submission waits for the dispatcher
| Record number | Subject | Organization | Counterparty | Requested units | Revision | |
|---|---|---|---|---|---|---|
| LDS-35197 | Draft lds-405 | ORG-6522 | TP-4176 | 450 | 490 | |
| LDS-62642 | Draft lds-746 | ORG-5372 | TP-7212 | 530 | 710 | |
| LDS-93841 | Draft lds-736 | ORG-4951 | TP-6506 | 280 | 300 | |
| LDS-43763 | Draft lds-867 | ORG-3197 | TP-7138 | 510 | 450 | |
| LDS-37752 | Draft lds-708 | ORG-2751 | TP-2340 | 660 | 810 |
6 of 6 records
Draft lds-405Loads · LDS-35197
DraftOrganizationORG-6522
CounterpartyTP-4176
Requested units450
Revision490
What you can do
Keep the operating job recognizable
A fuel purchase can refer to the load it supported. The Dispatcher checks the load’s subject, lane, organization and owner before adding that relationship. The link gives the Transport Supervisor a route from the purchase into the operating work when a receipt or vehicle attribution needs explanation.
The load has its own planned departure, promised delivery time and delivery state. Driver and vehicle assignments and stop records provide further context for the review. Read those records together when asking why a purchase was made at a particular site or which asset was serving the job.
How the work is organized
- Load ownership. Keep the subject and record number recognizable to the Dispatcher responsible for follow-through. The load owner helps the next shift find the person who can explain the work behind a purchase.
- Assignment context. The Transport Supervisor checks the recorded driver and vehicle assignment when establishing whether the purchase attribution is consistent with the operating job. Resolve differences with the people responsible for the records.
- Stop context. Stop sequence, location and appointment information help the team discuss where the work was expected to occur. Actual arrival, departure and proof references can add detail when examining an entry after the job.
What to agree during setup
Agree when a purchase should be attributed to a particular load and when it should remain part of the vehicle’s general purchase history. Decide how the Dispatcher identifies the load from the receipt or operating evidence. A recognizable lane or subject helps the discussion, but the selected record must still be the intended job.
Define who owns changes to transport assignments and stop evidence, then test the authorized operating path before using it in the pilot. For fuel review, the Dispatcher maintains the purchase and the supervisor examines the available context. Agree how the team handles a disputed attribution when the underlying transport work also needs correction.
Check the handoff on an actual case
A truck makes a fuel purchase while serving a multi-stop delivery. The Dispatcher links the purchase to the load and attaches the receipt. The supervisor opens the assignment and checks that the vehicle agrees, then reads the stop information to understand the operating context around the purchase date.
A second purchase has been linked to another load with a similar lane name. Ask the Dispatcher to identify the correct job from the record number, organization and supporting evidence. Record the correction under the review procedure and retain the supervisor’s rationale. During the rehearsal, include a purchase that cannot be attributed confidently to a load and agree how it will remain identifiable in the vehicle history while the team investigates.
What your team sees
- Active Loads — Planned and active transport work with owner, lane and timing information available for context.
- My load follow-up — Loads owned by the current team member, providing a starting point for purchase questions.
- Loads Awaiting Approval — Draft load records available for the supervisor’s agreed review procedure.
Follow the work through
Follow purchase attribution to operating work, then return to fuel review when the context is ready for a decision.
What it keeps track of
Data model- Loads
- Planned and executed transport loads
- Fuel transactions
- Fuel and energy purchases recorded per asset
- Load assignments
- Driver and vehicle assignment for a load
- Load stops
- Pickup, delivery and service stops on a load
- Drivers
- Licensed drivers available for load assignment
- Vehicles
- Powered units and trailing equipment in the fleet
- Transport partners
- Carriers, brokers, 3PLs and shippers linked to transport work
- Team members
- Dispatch, planning, safety and maintenance staff
Who uses it
Permissions- Dispatcher
- , Transport Supervisor, Auditor.
- The Dispatcher maintains purchase attribution and related load records, while the supervisor and Auditor examine the recorded operating context.
Set up Fuel Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.