Direct answer: once a UK package is underway, regulation 15 of the Package Travel and Linked Travel Arrangements Regulations 2018 makes the **organiser liable for performance** of every travel service in the package — whether the organiser or another provider delivers it — and sets hard duties when services fail. If the organiser cannot provide a **significant proportion** of the travel services as agreed, regulation 15(8) requires an offer of **suitable alternative arrangements**, at **no extra cost**, of **equivalent or higher quality where possible**, for continuation of the package (including return). Lower-quality alternatives trigger an **appropriate price reduction** under 15(9). The traveller may reject only if the offer is **not comparable** or the reduction is **inadequate** (15(10)). Failure paths trigger price reduction and/or compensation under regulation 16, and — where carriage of passengers is included — **repatriation with equivalent transport** without undue delay and at no extra cost (15(13)). An AI ops, disruption or “auto-rebook” agent that swaps hotels, flights or tours and treats the guest as bound **without** that statutory stack is not helpful automation. It is a mid-trip package-performance control failure.
That is the operator question Kaize is answering here. We are a UK AI product studio for travel and hospitality. This is **not legal advice** and not a substitute for the live SI text, Business Companion package-travel guidance, CAA / ATOL rules, or counsel for your product mix. It is a **control-stack** article: what must already be true in the ops state machine before AI is allowed to propose or bind a mid-trip package change. It sits beside — and does not replace — our PTR insolvency-cover naming gate (a **pre-sale** gate), our AI rebooking prepare-vs-confirm framing (general human confirmation), our UK package-travel 2026 booking-journey changes (mostly **pre-start** journey design), and our UK261 disruption notifications (flight passenger-rights messaging). This article is narrower: **Regulation 15 alternative-arrangement duties must be encoded** before AI may rebook a UK package mid-trip.
Why AI rebooking agents keep colliding with Regulation 15
Most UK organisers already have a human ops playbook for hotel overbooks, supplier failures and weather closures. The 2026 failure mode is a **generative ops agent** that can call supplier APIs, invent a “similar” hotel, message the guest on WhatsApp, and write a new PNR — **without** classifying whether the change is a minor remedy under 15(4), a **significant-proportion** alternative under 15(8), a lower-quality offer needing a priced reduction under 15(9), or a path that must keep **rejection and repatriation** rights live under 15(10)–(13). Regulation 15 is implied into every package travel contract. The model does not get to redefine “suitable”, “comparable” or “no extra cost” as prompt tone.
Three statutory facts teams must encode before any auto-rebook tool is armed:
- **Organiser liability is not optional** — regulation 15(2) makes the organiser liable for performance of the travel services in the package irrespective of who performs them. An AI that blames “the hotel partner” in guest chat does not move the duty.
- **Significant-proportion failure has a specific remedy ladder** — offer suitable alternatives at no extra cost (15(8)); price-reduce if quality drops (15(9)); honour lawful rejection (15(10)); then compensation / repatriation paths (15(12)–(13)). Skipping to “we’ve moved you — enjoy” is not a ladder.
- **Unavoidable and extraordinary circumstances still leave accommodation duties** — where return cannot be ensured as agreed, regulation 15(14) requires the organiser to bear necessary accommodation costs (generally up to three nights, with listed exceptions for PRM travellers and others who gave 48-hour notice). An AI that says “force majeure, you’re on your own for hotels” is wrong on the face of 15(14)–(16).
Map the duty before the model speaks
Business Companion restates the same ladder for traders: remedy lack of conformity within a reasonable period unless impossible or disproportionately costly; where a significant proportion cannot be performed, offer suitable alternatives at no extra cost and of equivalent or higher quality where possible; grant an appropriate price reduction for lower quality; allow rejection only for non-comparable offers or inadequate reductions; arrange repatriation with equivalent transport when carriage is included and alternatives fail. Those are **system requirements**, not blog suggestions. Your disruption agent needs structured fields for: affected services, whether the proportion is significant, proposed alternative inventory with quality/comparability scores, price-reduction amount, traveller decision window, and repatriation eligibility — **sourced from ops systems**, not invented in prose.
The six gates before AI may rebook a UK package mid-trip
Gate 1 — Classify the event: remedy, significant-proportion alternative, or termination path
Before any generative turn offers a new hotel or flight, classify against regulation 15: can the lack of conformity be remedied under 15(4)? Is a significant proportion of services unavailable so 15(8) applies? Has lack of conformity substantially affected performance so the traveller may terminate under 15(11)? Gate 1 fails if the assistant uses one generic “sorry for the inconvenience, here’s another room” script for a late housekeeping issue and a closed resort alike.
Gate 2 — Alternative payload is assembled from inventory systems, not model imagination
Build a structured alternative object from CRS/PMS/GDS/NDC and contracting data: property or service identity, category/star or contracted quality markers, location relative to the original, dates, board basis, transfer implications, total guest cost delta (must be **zero extra cost** to the traveller for a compliant 15(8) offer), and a documented quality comparison. The LLM may explain the offer; it must not invent a “4-star equivalent” when the PMS says 3-star with no pool. Gate 2 fails if null inventory fields still allow confirm.
Gate 3 — Price reduction is calculated and shown when quality drops
If the proposed alternative is lower quality than the contract, regulation 15(9) requires an **appropriate price reduction** granted to the traveller — not a silent downgrade. Encode the reduction as a priced artefact the guest can see before accepting. Gate 3 fails if the agent “upgrades messaging” while the commercial record is a downgrade with no credit.
Gate 4 — Traveller rejection rights stay live in the channel
Regulation 15(10) limits rejection to non-comparable arrangements or inadequate price reduction — but those rights must still be **presented and operable** on the channel the AI uses. A WhatsApp bot that only offers “Accept new hotel” without a path to reject for non-comparability, escalate to a human, or trigger the 15(12) compensation/repatriation branch is not implementing the Regulation. Gate 4 fails on forced-choice UX.
Gate 5 — Repatriation and extraordinary-circumstances accommodation are hard stops
Where carriage of passengers is in the package and alternatives fail or are lawfully rejected, regulation 15(13) requires repatriation with equivalent transport without undue delay at no extra cost. Where return cannot be ensured because of unavoidable and extraordinary circumstances, 15(14) still puts necessary accommodation cost on the organiser (with the stated night cap and PRM/pregnancy/unaccompanied-minor/medical exceptions). Gate 5 fails if the agent can close the ticket as “weather — guest to rebook home flights themselves” without those duties firing.
Gate 6 — Adjacent gates still apply: insolvency naming, UK261, ATOL, human confirm
Regulation 15 performance duties do not replace pre-sale insolvency-cover naming, UK261 passenger-rights notifications where flights are disrupted, ATOL AST-14 disclosure on sales channels, or the prepare-vs-human-confirm rule for high-impact rebooks. Gate 6 fails if teams treat Reg 15 as the only checklist and let the model bind guests without a human confirm path on significant-proportion changes.
What this is not
- Not a rewrite of PTR insolvency cover naming — that article is the **pre-sale** insolvency-protection disclosure gate; this one is **mid-performance** alternative arrangements under Reg 15.
- Not a substitute for AI rebooking prepare-vs-confirm — that piece frames human confirmation generally; this encodes the statutory Reg 15 ladder inside that confirmation.
- Not UK package travel 2026 booking-journey changes — focused on journey design and pre-start rules, not the Reg 15 mid-trip alternative stack.
- Not UK261 disruption notifications — flight passenger-rights messaging under UK261 / assimilated Reg 261, which can sit alongside but does not replace organiser package duties.
- Not permission to skip CCR 2013 pre-contract information on new distance sales the AI might create while “helping” mid-trip.
Operator checklist before go-live
- Disruption taxonomy maps every AI-touchable mid-trip event to remedy / significant-proportion alternative / termination / repatriation buckets with counsel sign-off.
- Alternative offers are structured objects from inventory systems; quality comparison and guest cost delta are mandatory fields; nulls block bind.
- Price-reduction artefact required whenever quality is lower than contracted; shown before accept.
- Channel UX implements accept, reject-for-non-comparability, reject-for-inadequate-reduction, and human escalate — not a single forced accept.
- Repatriation and 15(14) accommodation duties are coded paths, including PRM and related exceptions with 48-hour notice flags.
- Human confirm remains mandatory for significant-proportion rebinds; model may prepare, not silently commit.
- Change control: no new AI disruption channel without repeating Gates 1–6; adjacent insolvency, UK261, ATOL and CCR gates stay armed.
How Kaize frames the build
Kaize designs travel and hospitality AI so **control planes sit in front of models**. PTR Regulation 15 alternative arrangements are one of those gates: the mid-trip rebook path does not call confirm-and-commit until classification, suitable-alternative payload, price-reduction state and rejection/repatriation rights are live on the session — just as we refuse package sale completion until insolvency cover is named or distance sale completion until CCR Schedule 2 / Reg 14 is satisfied. If you want that control stack designed around your DMC, tour-ops, CRS and messaging stack, discuss a project or see what we build and how travel companies should control AI agents.
Sources for operators to read next: PTR 2018 (SI 2018/634) regulation 15; PTR 2018 contents; Business Companion — package travel and holidays; BEIS/DBT package-travel business guidance on GOV.UK where still published. Always verify against the consolidated text and your counsel — this page is an operator control framing, not advice.