Fleet Repair Lifecycle · Shop · Dispatch · Safety
Defect → Shop acknowledged → Repaired → Dispatch Return-to-Service. One trail · three scopes.
Every Fleet defect — DVIR, Weekly Lead, or Weekly Emergency — flows through the same four-step lifecycle. Shop, Dispatch, and Safety see the same record at every step, scoped to what each role actually does.
- Open · the defect is fresh from the driver/inspector. Shop sees it in the unit's queue.
- Shop acknowledged · the mechanic opened the card. Optional — most shops skip this and go straight to repair.
- Repaired · Shop logged the repair drawer (mechanic name · repair notes · photos if applicable · timestamp).
- Returned to service · Dispatch confirmed the unit is safe to roll. Intentional · checkbox-confirmed.
Why this mattersThe four steps are deliberate. Shop owns the wrench. Dispatch owns the operational decision to put the truck back in rotation. Safety reads the trail. No one person closes the loop alone.
- Shop · uses the driver's note and photo to know exactly what to look at
- Dispatch · sees Available / OOS / Repair-in-progress without scanning a list
- Safety · reads the full audit trail · who · when · what changed · before/after status
What happens next
- After Shop marks repaired · unit status becomes 'Repair in progress' (awaiting RTS)
- Dispatch sees the unit on their visibility page with a 'Return to Service' button
- After RTS · unit status returns to Available · audit log stamped with both names
Common mistakes
- Shop marks repaired but Dispatch never confirms — unit sits in 'awaiting RTS' indefinitely
- Repair note shorter than 'replaced part' — Safety has no record of what was inspected
- Skipping the Shop drawer and editing the defect directly · breaks the audit trail