645 B
645 B
document_id, title, version, effective_date, department, status
| document_id | title | version | effective_date | department | status |
|---|---|---|---|---|---|
| booking-conflict-procedure | Booking conflict procedure | 1.2 | 2026-06-20 | Operations | active |
Booking conflict procedure
1. Detection
Two reserved or active bookings for the same vehicle may not overlap. Imported legacy conflicts must be flagged as data-quality issues.
2. Resolution
Operations reviews both bookings, confirms source-system ownership and reassigns or cancels one booking in the authoritative booking system. MobilityOps records the reviewed outcome.
3. Safety
Do not automatically cancel a customer booking based only on an inferred conflict.