The release request starts with the vehicle and load that need the decision. Maintenance staff supply the actual service evidence, the assigned Dispatcher submits the current plan and the Transport Supervisor independently reviews it. Dispatch then checks the release result before using the vehicle for the intended assignment.
The Maintenance Coordinator identifies the service evidence and relevant vehicle defect records. The Dispatcher prepares the plan under the selected load, checking vehicle code, service type, odometer reading and next due date against the source.
The assigned Dispatcher checks the current load and maintenance plan revisions and moves the plan from Draft to Submitted. Preserve the information being presented for review so a later change is distinguishable from the submitted scope.
The Transport Supervisor independently approves, rejects or returns the request with a reason. An approval moves the plan from Submitted to Approved; rejection moves it to Rejected. A returned plan needs correction and another review through the agreed revision practice.
Execute the release action only with the required source evidence confirmed. Inspect the operation receipt and resulting vehicle readiness. If the expected effect remains uncertain, retain the discrepancy for reconciliation before dispatch relies on the release.
And how to keep it from happening.
Start free, then use Proto to change fields, steps and approvals before your team goes live.