22 lines
645 B
Markdown
22 lines
645 B
Markdown
---
|
|
document_id: booking-conflict-procedure
|
|
title: Booking conflict procedure
|
|
version: "1.2"
|
|
effective_date: 2026-06-20
|
|
department: Operations
|
|
status: 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.
|