Direct answer: before the start of a UK package, regulation 12 of the Package Travel and Linked Travel Arrangements Regulations 2018 lets the traveller terminate at any time, may require only an **appropriate and justifiable termination fee**, forces the organiser to justify that fee on request, and — where unavoidable and extraordinary circumstances at the destination (or its immediate vicinity) significantly affect performance or carriage — gives a **fee-free full refund** with no extra compensation right. Regulation 13 limits when the **organiser** may terminate (minimum numbers with hard notice windows, or UEC preventing performance) and, when it does, requires a **full refund**. Regulation 14 then clocks every reimbursement: without undue delay and **not later than 14 days** after termination. An AI cancel, “self-serve refund”, or ops-disruption agent that voids a booking, withholds money, or invents a cancellation charge **without** that statutory stack is not helpful automation. It is a pre-start package-termination 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 booking and payments state machine before AI is allowed to propose or bind a cancel or refund. It sits beside — and does not replace — our PTR Regulation 15 alternative-arrangements gate (**mid-trip** performance), our PTR insolvency-cover naming gate (**pre-sale** protection disclosure), our AI rebooking prepare-vs-confirm framing, and our UK package-travel 2026 booking-journey changes. This article is narrower: **Regulations 12–14 termination and refund duties must be encoded** before AI may cancel or refund a UK package before it starts.
Why cancel-and-refund agents keep colliding with Regulations 12–14
Most UK organisers already have a human cancellations desk that can quote a sliding scale, open a UEC exception, or push a 14-day refund. The 2026 failure mode is a **generative cancel agent** that can read a PNR, call a payment API, message the guest on WhatsApp, and close the booking — **without** classifying whether the path is traveller-termination under 12(2)–(6), fee-free UEC termination under 12(7)–(8), organiser termination under 13(2)–(3), or a refund clock under 14(2)–(3). Regulations 12–14 are implied into every package travel contract. The model does not get to redefine “appropriate and justifiable”, “unavoidable and extraordinary circumstances”, or “14 days” as prompt tone.
Three statutory facts teams must encode before any auto-cancel or auto-refund tool is armed:
- **Traveller termination is always available before start — fees are constrained** — regulation 12(2)–(6) allows termination at any time before start; fees must be appropriate and justifiable (standardised by time-to-start and expected cost savings / alternative deployment, or otherwise package price minus those savings), and the organiser must justify the amount on request.
- **UEC at destination kills the fee and unlocks a full refund** — regulation 12(7)–(8): unavoidable and extraordinary circumstances at the place of destination or its immediate vicinity that significantly affect package performance or carriage to the destination → terminate with **no termination fee** and a **full refund** of payments made (no additional compensation under that paragraph).
- **Organiser termination and the refund clock are hard rules** — regulation 13 only allows organiser termination for stated minimum-number windows or UEC preventing performance, with a full refund and no extra compensation liability under 13(3); regulation 14 then requires reimbursement (after any lawful fee on 12(2) paths, or full refund on 12(8) / 13(3) paths) without undue delay and **within 14 days** of termination.
Map the duty before the model speaks
Business Companion restates the same ladder for traders: travellers may cancel before departure subject to an appropriate justifiable fee; no fee where UEC significantly affects the package or transport, with a full refund; organisers may terminate only for minimum numbers (with the 20-day / 7-day / 48-hour notice caps by trip length) or UEC, with a full refund; refunds after termination must land within 14 days. Those are **system requirements**, not blog suggestions. Your cancel agent needs structured fields for: who initiated termination, whether UEC evidence is present and destination-scoped, the contractual fee schedule or calculated residual, fee-justification artefact, organiser minimum-number eligibility and notice deadline, refund gross / fee / net, and a payment-execution deadline that cannot exceed 14 days — **sourced from ops and finance systems**, not invented in prose.
The six gates before AI may cancel or refund a UK package
Gate 1 — Classify the path: traveller fee path, traveller UEC path, or organiser termination
Before any generative turn quotes a charge or fires a refund, classify against regulations 12 and 13. Is this traveller-initiated under 12(2)? Does a documented UEC at destination / vicinity trigger 12(7)? Is the organiser terminating under 13(2)(a) minimum numbers or 13(2)(b) UEC? Gate 1 fails if the assistant uses one generic “here’s your cancellation fee” script for a change-of-mind cancel and a destination-wide UEC event alike.
Gate 2 — Termination-fee payload is calculated from contract rules, not model imagination
Build a structured fee object from the package contract and commercial systems: time-to-start band, standard fee table if present, or residual = package price − expected cost savings − income from alternative deployment of the travel services, plus a durable justification string the guest (and later counsel) can read. Regulation 12(6) requires justification on request — so the artefact must exist even if the guest has not asked yet. Gate 2 fails if null commercial fields still allow the agent to invent “non-refundable” or a round-number penalty.
Gate 3 — UEC fee-free full-refund path stays live and evidence-backed
When destination / vicinity UEC significantly affects performance or carriage, regulation 12(7)–(8) forbids a termination fee and requires a full refund of payments made. Encode an evidence object (source, geography scope, significance assessment, human review flag) before the agent can choose the fee path. Gate 3 fails if the model can “keep the deposit because policy says so” while ops has already logged a qualifying UEC.
Gate 4 — Organiser-initiated cancels respect minimum-number windows and UEC-only breadth
Regulation 13 is not a general commercial convenience kill-switch. Minimum-number terminations need the contract’s stated minimum, notification within the contract period, and not later than 20 / 7 / 48-hour caps by trip length. UEC organiser termination needs prevention of performance and notice without undue delay before start. Both paths pay a full refund under 13(3). Gate 4 fails if an AI yield or “low occupancy” tool can cancel guests outside those limbs.
Gate 5 — The 14-day refund clock is a payment-system hard stop
Regulation 14 does not care that the LLM apologised nicely. After termination under 12(2), reimburse payments minus any lawful fee; after 12(8) or 13(3), refund in full; in every case without undue delay and **not later than 14 days** after termination. Encode termination timestamp, refund due-by, payment-rail status, and a block on “case closed” while due-by is unmet. Gate 5 fails if the agent marks the booking cancelled while finance can still sit on funds past day 14.
Gate 6 — Adjacent gates still apply: Reg 15 mid-trip, insolvency naming, ATOL, human confirm
Pre-start termination duties do not replace mid-trip Reg 15 alternative arrangements, pre-sale insolvency-cover naming, ATOL AST-14 disclosure on sales channels, CCR 2013 pre-contract information on new distance sales, or the prepare-vs-human-confirm rule for high-impact money movements. Gate 6 fails if teams treat Regs 12–14 as the only checklist and let the model bind refunds without a human confirm path on disputed UEC or fee-justification cases.
What this is not
- Not a rewrite of PTR Regulation 15 alternative arrangements — that article is the **mid-trip** performance / rebook ladder; this one is **pre-start** termination and refund timing under Regs 12–14.
- Not a substitute for PTR insolvency cover naming — pre-sale insolvency-protection disclosure, not cancel/refund execution.
- Not AI rebooking prepare-vs-confirm — general human confirmation; this encodes the statutory terminate-and-refund stack inside that confirmation.
- Not UK package travel 2026 booking-journey changes — journey design focus, not the Reg 12–14 cancel/refund control plane.
- Not UK261 disruption notifications — flight passenger-rights messaging under UK261 / assimilated Reg 261, which can sit alongside flight legs but does not replace organiser package termination and refund duties.
Operator checklist before go-live
- Cancel taxonomy maps every AI-touchable pre-start event to traveller-fee / traveller-UEC / organiser-minimum / organiser-UEC buckets with counsel sign-off.
- Fee offers are structured objects from contract + commercial systems; justification artefact is mandatory; nulls block bind.
- UEC evidence object required before any fee-free full-refund path is denied or any fee path is forced.
- Organiser cancel tools cannot fire outside regulation 13 limbs and notice windows.
- Refund workflow starts at termination timestamp; due-by ≤ 14 days; case cannot close while funds remain unpaid past due-by.
- Human confirm remains mandatory for disputed UEC, non-standard fees, and organiser-initiated cancels; model may prepare, not silently commit money movement.
- Change control: no new AI cancel/refund channel without repeating Gates 1–6; adjacent Reg 15, insolvency, ATOL, CCR and UK261 gates stay armed.
How Kaize frames the build
Kaize designs travel and hospitality AI so **control planes sit in front of models**. PTR Regulations 12–14 termination and refund duties are one of those gates: the cancel/refund path does not call confirm-and-pay until classification, fee or UEC state, organiser-eligibility and the 14-day reimbursement clock are live on the session — just as we refuse mid-trip rebinds until Reg 15 alternative arrangements are encoded, 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 payments 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 12; regulation 13; regulation 14; PTR 2018 contents; Business Companion — package travel and holidays. Always verify against the consolidated text and your counsel — this page is an operator control framing, not advice.