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
- Fuel review
Fuel review
Give the supervisor a clear purchase to decide and the Dispatcher a recorded reason for the next action.
OverviewFuel correction queue×
Fuel Management System · Fuel review
New
Fuel correction queue
Fuel transactions
| Transaction number | Vehicle | Related load | Card reference | Revision | Decision at | |
|---|---|---|---|---|---|---|
| FT-99542 | VHC-44404 | LDS-95928 | CR-315 | 210 | 08 Oct | |
| FT-43207 | VHC-90363 | LDS-15491 | CR-602 | 620 | 12 Oct | |
| FT-52123 | VHC-53329 | LDS-39623 | CR-201 | 110 | 21 Oct | |
| FT-42305 | VHC-31796 | LDS-77173 | CR-797 | 930 | 11 Oct | |
| FT-64639 | VHC-46679 | LDS-40805 | CR-889 | 860 | 04 Oct |
6 of 6 records
CR-315Fuel transactions · FT-99542
RejectedVehicleVHC-44404
Related loadLDS-95928
Revision210
Decision at08 Oct
What you can do
Record the decision against the purchase under review
A Submitted purchase is ready for the Transport Supervisor to examine under the team’s review procedure. The supervisor checks the purchase details, receipt and relevant operating context before recording Approved, Rejected, Returned or Escalated in the decision record. Identify the purchase and its revision so the next person understands what was considered.
The Dispatcher maintains the fuel transaction’s state after the decision. An approved purchase can move to Approved, while a rejected purchase remains recognizable for correction. A Returned decision keeps the purchase awaiting follow-up until the Dispatcher resolves the request. Agree that handoff before the first review cycle.
How the work is organized
- Review preparation. The Dispatcher checks the quantity, vehicle, card reference and receipt before submitting the entry. The supervisor can then concentrate on the purchase and the operating evidence that explains it.
- Decision ownership. The Transport Supervisor records the outcome with reviewer identity, date and rationale. Keep the source-record reference and revision aligned with the purchase examined so a later correction can be discussed clearly.
- Outcome recording. The Dispatcher checks that the decision names the purchase and its current revision before applying the agreed state update. Keep rejected and returned work visible until the requested investigation or correction has been completed.
What to agree during setup
Agree who prepares purchases and which supervisor decides them. Define the checks needed for approval and what information a returned decision should request. Test the role handoff with the actual people in the pilot, including how the supervisor can examine supporting evidence and how the Dispatcher finds the result.
Decide when a purchase can move from Approved to Completed and what completion means for the team’s operating review. Set the procedure for correcting an already reviewed entry, including how a new decision refers to the revised information. Keep the previous rationale available when explaining why the record was changed. A decision on the earlier revision stays attached to that earlier review; obtain a fresh decision before treating the corrected purchase as accepted.
Check the handoff on an actual case
A diesel purchase is Submitted with a receipt and a linked load, but the vehicle on the purchase differs from the vehicle the supervisor finds in the assignment evidence. The supervisor records Returned and asks the Dispatcher to establish which vehicle received the fuel. The Dispatcher investigates the original receipt and operating records.
After the attribution is corrected, the supervisor reviews the updated entry and records the appropriate new decision. The Dispatcher then updates the purchase state under the agreed procedure. Rehearse a rejected outcome too, and ask another supervisor to identify the purchase, revision and reason from the decision record. The case should remain understandable when the next shift takes over the correction.
What your team sees
- Fuel review inbox — Submitted purchases with the quantity, vehicle, load context and revision ready to examine.
- Fuel correction queue — Rejected purchases that need the Dispatcher to read the decision and resolve the concern.
- Review exceptions — Returned and Escalated decisions whose rationale identifies the follow-up required.
Follow the work through
Rehearse purchase submission and review and receipt correction before using the review process on live purchases.
What it keeps track of
Data model- Fuel transactions
- Fuel and energy purchases recorded per asset
- Review decisions
- Approval, rejection and escalation decisions on records
- Record attachments
- Documents, photos and signature evidence attached to records
- Loads
- Planned and executed transport loads
- Load assignments
- Driver and vehicle assignment for a load
- Vehicles
- Powered units and trailing equipment in the fleet
- Team members
- Dispatch, planning, safety and maintenance staff
Who uses it
Permissions- Transport Supervisor
- , Dispatcher, Auditor.
- The supervisor records the decision, the Dispatcher maintains the purchase outcome, and the Auditor reads the evidence of the handoff.
Set up Fuel Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.