Return-to-Service · Dispatch confirmation
Shop fixed the truck. Dispatch confirms it can roll. Intentional · timestamped · audit-logged.
Return-to-Service is the moment Dispatch tells the system 'this truck is back in rotation.' It happens only after Shop has logged a repair · never automatically · never as a side effect of closing something else.
- Open the Fleet view from the Dispatch portal
- Find the unit · it shows 'Awaiting RTS' alongside the Shop's repair record
- Tap 'Return to Service' on the defect
- Review the Shop repair note (and photos, if Shop attached any)
- Enter your name · add an optional Dispatch note
- Check the confirmation box — 'I have reviewed the Shop repair record and confirm this unit is safe to return to service'
- Tap Return to Service
Why this mattersThe Shop owns the wrench but Dispatch owns the operational decision. Dispatch is the role that knows whether the load is realistic, whether the route makes sense for a freshly repaired unit, and whether anyone needs a heads-up. The intentional checkbox is not red tape · it is the moment the platform records that a human made a decision, not that a button got tapped on the way to somewhere else.
What happens next
- Unit status flips to Available · drivers can pick it up
- Audit log captures: who · when · status_before · status_after · Shop note · Dispatch note
- Safety can read the full trail · DVIR → Shop repair → Dispatch RTS
Common mistakes
- Confirming RTS without reading the Shop note · you lose the operational context
- Skipping the confirmation note when something is unusual · brief context helps Safety later
- Trying to RTS a unit Shop hasn't repaired yet · system blocks this · for good reason