Initial MobilityOps build pack (docs, contracts, scaffold)
This commit is contained in:
@@ -0,0 +1,21 @@
|
||||
---
|
||||
document_id: damage-procedure
|
||||
title: Damage handling procedure
|
||||
version: "1.3"
|
||||
effective_date: 2026-06-15
|
||||
department: Operations
|
||||
status: active
|
||||
---
|
||||
# Damage handling procedure
|
||||
|
||||
## 1. Immediate actions
|
||||
|
||||
When a vehicle returns with visible or reported damage, mark damage in the return inspection, add a concise factual description and keep the vehicle blocked. Do not promise the customer a repair cost or liability decision.
|
||||
|
||||
## 2. Evidence
|
||||
|
||||
Record at least four photographs in the source inspection system: full affected side, close view, wider context and vehicle registration. MobilityOps may store only the evidence reference in this PoC.
|
||||
|
||||
## 3. Escalation
|
||||
|
||||
Create an Operations review before any new rental. A vehicle with unresolved damage may not be marked available even when a future booking exists.
|
||||
Reference in New Issue
Block a user