travel-trip-contingency-planning

The saved excerpt is a snapshot from review. The external source remains the complete and most current version.

---
name: travel-trip-contingency-planning
description: "Activate when: building a complex/high-value itinerary; multi-supplier or international trip; hurricane/advisory season; client asks 'what if something goes wrong?'; designing a group/FIT trip. Do NOT activate when: single refundable booking with trivial exposure. More: deciqai.com/s/travel-trip-contingency-planning"
---

# Travel Advisor — Trip Contingency Planning

> **Industry front door for [scenario-planning](../scenario-planning/SKILL.md).** Adds domain triggers, example, packs only. Parent Process unchanged.

**Activate when:** building a complex/high-value itinerary; multi-supplier or international trip; hurricane/advisory season; client asks "what if something goes wrong?"; designing a group/FIT trip.
**Do NOT activate when:** single refundable booking with trivial exposure.

## Why this variant
The parent [scenario-planning](../scenario-planning/SKILL.md) builds several plausible futures and a response to each. Travel disruption (weather, strike, supplier default, advisory, illness) is a scenario problem: the advisor's value is having the rebooking/refund path ready *before* it's needed.

## Domain inputs → parent's Process
Build 3–4 scenarios and a pre-staged response:
- Weather/force-majeure cancellation → rebooking + insurance claim path.
- Supplier default/insolvency → protected-booking (ARC/IATA, card chargeback, insurance).
- Travel advisory / entry-rule change → reroute or postpone.
- Medical / missed-connection → assistance line + coverage.
For each: who the advisor calls, what the client is owed, what's documented.

## Worked example
7-night Caribbean, cruise + air + hotel, September.
→ Scenario "named storm diverts sailing": pre-agree with client the rebook window, insurance trigger, and the air-change fee owner. Documented at booking → a 2 a.m. disruption becomes a scripted action, not improvisation.

## Compliance anchors
- Disclose cancellation/refund terms and insurance role at booking; keep the disclosure record (supports E&O defense).

## Packs
- **Solo:** one-page "if X then Y" contingency card attached to each complex trip.
- **Agency:** supplier-default and advisory playbooks shared across advisors.

## Red flags
- No insurance discussion documented on an exposed trip.
- Single points of failure with no rebooking path.
- Advisories ignored at planning time.

## Verification
- [ ] Top 3 disruption scenarios named with a response each
- [ ] Insurance role disclosed & recorded
- [ ] Fee/refund ownership pre-agreed with client
- [ ] Assistance contacts in the trip doc

---
Part of **deciqAI Knowledge Skills**. Core method: [scenario-planning](../scenario-planning/SKILL.md).

---

*Part of **deciqAI Knowledge Skills** — 233 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/s/travel-trip-contingency-planning** · Built by deciqAI · github.com/deciqAI · Contributions welcome.*

*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/travel-trip-contingency-planning.json*