Publish curated MobilityOps source snapshot

This commit is contained in:
Jens committed 2026-09-29 22:03:33 +02:00
commit 7adc072f5e
317 files changed
+48851

No files matched your search

@@ -0,0 +1,21 @@
---
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. Fleet Ops records the reviewed outcome.
## 3. Safety
Do not automatically cancel a customer booking based only on an inferred conflict.