Reservation & Booking Management › Booking Disruption & Rebooking Operations

Booking Disruption & Rebooking Operations

BC-4020.70 Level 2 Travel & Hospitality 1 providers 1 API surfaces

Reaccommodation of bookings affected by schedule changes, cancellations, and mass disruptions, including communications and compensation eligibility.

Booking Disruption & Rebooking Operations (BC-4020.70) is a level-2 business capability under Reservation & Booking Management in the Travel & Hospitality model. The catalog holds 1 API surface(s) from 1 provider(s) that can perform some part of it. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Sub-capabilities

Schedule-Change Reaccommodation BC-4020.70.10

Reaccommodation of bookings impacted by published schedule changes including options offered to travellers.

no catalog coverage

Mass Disruption Reaccommodation BC-4020.70.20

Reaccommodation of large numbers of bookings during weather, IROPS, or force-majeure events.

no catalog coverage

Compensation Eligibility Determination BC-4020.70.30

Determination of compensation eligibility under carrier policy and applicable passenger-rights rules.

no catalog coverage

Reaccommodation Communications BC-4020.70.40

Outbound communications to affected travellers and agents throughout reaccommodation events.

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Developing 1 Usable, with meaningful gaps to close
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Booking Disruption & Rebooking Operations. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →