Jens/MobilityOps-Public
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Publish curated MobilityOps source snapshot

Browse Source
This commit is contained in:
Jens committed 2026-09-29 22:03:33 +02:00
commit 7adc072f5e
317 files changed
+48851
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

knowledge/procedures/en-GB/11-vehicle-availability.md
+21
View File
@@ -0,0 +1,21 @@
---
document_id: vehicle-availability-procedure
title: Vehicle availability procedure
version: "1.0"
effective_date: 2026-07-01
department: Rental Operations
status: active
---
# Vehicle availability procedure
## 1. Conditions
A vehicle may be set to available only when no blocking condition remains: no open damage, no unresolved technical warning, no pending maintenance block and no open critical data-quality issue against the vehicle.
## 2. Cleaning is not sufficient
Completing the cleaning checklist alone does not make a vehicle available. Availability is derived from the combined state of cleaning, maintenance and data-quality checks, not from any single step.
## 3. Confirmation
An authorised employee confirms the final check and the vehicle status changes to available. The change is recorded in the audit trail with the checks that were confirmed clear.