Fleet readiness

Dispatcher needs to know which vehicle is available for the planned movement and why the team considers it ready. The fleet record identifies the vehicle code, equipment class, capacity and external fleet identity. Its active flag and readiness state provide the starting point for the dispatch check.

Vehicle defects retain the reported time, severity, repair evidence and release time. These details let the operating team investigate the condition behind a readiness label. App Administrator maintains the vehicle reference record; Transport Supervisor helps resolve cases where the operating picture and supporting evidence disagree.

• Choose an appropriate vehicle. Dispatcher compares the load’s equipment class with the vehicle details and checks its active state. The vehicle code should remain recognizable to the team using the yard or fleet source. Capacity is available as a vehicle attribute for the planning discussion.
• Read the defect evidence. The team examines Minor, Major and Critical reports with their recorded repair evidence and release time. A recent entry deserves attention when the vehicle is about to move. Keep the supporting explanation clear enough for the next shift to understand what was repaired.
• Resolve readiness before dispatch. Ready, Held and Maintenance identify the current operating position. Dispatcher checks the evidence before assigning a vehicle. App Administrator resolves incorrect vehicle reference information, while Transport Supervisor coordinates the decision when a reported defect creates uncertainty.

Agree how fleet personnel provide repair evidence and who maintains the vehicle readiness record. Set expectations for the meaning of a release time and how the operating team handles a disagreement between that time and the latest defect report. Use the same external fleet identity across any connected source.

Choose the vehicle code convention and the equipment descriptions dispatchers will use. Establish who can maintain defect records within the agreed permissions. A review should consider the reported condition and repair evidence for the selected vehicle, rather than assuming that another vehicle with the same equipment class shares its readiness.

Prepare a rehearsal vehicle called V-204 with a Major defect report and a repair note referring to a brake inspection. Dispatcher is considering V-204 for an afternoon load. Ask the team to inspect the release time and supporting evidence before confirming the vehicle choice.

Now introduce a disagreement: the vehicle record says Ready, but the team cannot reconcile the repair note with the latest report. Transport Supervisor investigates, and Dispatcher keeps the assignment unresolved until the evidence is understood. App Administrator corrects reference information only when the responsible team has established the facts.

Repeat the exercise with a vehicle in Maintenance and a second vehicle that is ready but already committed during the desired window. The handoff needs both the condition check and the assignment check; finishing one still leaves the other to resolve.

• Fleet Readiness Board — Vehicles with their readiness, equipment class and active state.
• Vehicle Defects Default List — Reported severity, repair evidence and release times for inspection.

Use Load to dispatch for the readiness check and Exception reconciliation for disputed operating outcomes.