Initial MobilityOps build pack (docs, contracts, scaffold)
This commit is contained in:
@@ -0,0 +1,25 @@
|
||||
---
|
||||
document_id: vehicle-return-procedure
|
||||
title: Vehicle return procedure
|
||||
version: "2.0"
|
||||
effective_date: 2026-07-01
|
||||
department: Rental Operations
|
||||
status: active
|
||||
---
|
||||
# Vehicle return procedure
|
||||
|
||||
## 1. Register the return
|
||||
|
||||
Open the active booking and record the ending odometer, fuel level, cleanliness, visible damage, technical warnings and relevant notes.
|
||||
|
||||
## 2. Validate the reading
|
||||
|
||||
A submitted odometer below the previous canonical reading must never replace the canonical value. Register the inspection, create a data-quality issue and request human review.
|
||||
|
||||
## 3. Determine next state
|
||||
|
||||
Damage or a technical warning requires a blocked state. A reached service threshold requires maintenance. Otherwise the vehicle moves to cleaning before it can become available.
|
||||
|
||||
## 4. Follow-up
|
||||
|
||||
The return automation may create a cleaning or maintenance follow-up, but MobilityOps remains the source of truth for the vehicle state.
|
||||
Reference in New Issue
Block a user