DAT-120 · Check completeness gate before booking approval

Travel & housing · master data

Status: Concept – not built yet

Prevents bookings from being created on incomplete personal data and makes the data gap visible before costs and cancellation deadlines start running. The gate is the only transition from the master data world into procurement.

Trigger: Triggered by TRV-080 (booking request created) or HSG-080 (room assignment created); plus a preliminary check {{BUCHUNG_VORLAUF_MIN_TAGE}} before the planned booking time.

Rule (automatable) Judgment (human decides)

Decision rules

• R1 IF all booking-critical fields for the respective booking type are present THEN traffic light green and approval without human intervention.
• R2 IF a non-booking-critical field is missing (for example, a preference) THEN traffic light yellow, booking possible, follow-up request in parallel.
• R3 IF a booking-critical field is missing THEN traffic light red and a hard block. Booking-critical fields are: name as shown on ID for flights, ID validity for international travel, starting point for mileage billing, driving authorization for vehicle assignment, valid consent for passing D5 to HOT.
• R4 IF traffic light red AND first work day − today < 7 days THEN escalation F2, because from this point the alternative is non-arrival, not correction.
• R5 IF PL approves a booking at yellow THEN add a note “booking on an incomplete data basis” naming the missing fields, so the cause remains traceable in CLS-050.
• R6 IF the check was more than 48 hours before the actual booking THEN check again, because DAT-090 may have changed fields in the meantime.

Common pitfalls

1. The gate is implemented as a recommendation instead of a block → bookings continue, and the traffic light becomes a statistic. 2. The check happens once at the request stage, but the booking happens two weeks later with changed data → ticket under the old name. 3. The follow-up request only states “data incomplete” without specifying the field → multiple rounds of queries, deadline passes. 4. Yellow gets waved through across the board because of time pressure → the causes remain invisible and repeat in the next work block.

Impact H × Effort S → Do-first · VOLL · RACI **R** THK · **A** PL · **C** GWL, PBH for billing fields · **I** REI · Manual effort: Estimate: 0 min for green, 5–15 min per yellow case, 30–60 min per red case including follow-up request and escalation

Request this workflow