Skip to content
Back to skills

Itinerary Design And Quoting

ASecurity

Turn a travel brief into a structured, bookable, transparently-quoted itinerary: structure before price, itemize net/commissionable cost + service fee + taxes + insurance, attach the per-supplier cancellation/penalty schedule (verify-at-use), and document every element. No traveler PII in the artifact.

  • 7 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
ai-agentsrustgodocumentation

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add mcorbett51090/RavenClaude --skill itinerary-design-and-quoting --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Itinerary Design And Quoting?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Itinerary Design And Quoting
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-itinerary-design-and-quoting/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-itinerary-design-and-quoting)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: itinerary-design-and-quoting
description: "Turn a travel brief into a structured, bookable, transparently-quoted itinerary: structure before price, itemize net/commissionable cost + service fee + taxes + insurance, attach the per-supplier cancellation/penalty schedule (verify-at-use), and document every element. No traveler PII in the artifact."
---

# Itinerary Design & Quoting

An itinerary is a **structured, priced, documented commitment** — not a wish list. Build the structure, then price it honestly, then record it.

## The loop

1. **Structure first.** Fix routing, sequencing, pace, and must-haves before quoting. Sanity-check feasibility (connection times, check-in/out, minimum stays) — see the group-vs-FIT structuring tree in [`../../knowledge/travel-agency-decision-trees.md`](../../knowledge/travel-agency-decision-trees.md).
2. **Quote transparently.** Itemize: net/commissionable supplier cost, your **service/planning fee** (when the work exceeds what commission covers — ask [`travel-agency-operations-lead`](../../agents/travel-agency-operations-lead.md)), taxes/fees, and travel insurance offered. No hidden markups surfacing at final payment.
3. **Attach the penalty schedule.** For every supplier, record the deposit, final-payment date, and cancellation-penalty schedule. Treat each as `[verify-at-use]` against the live supplier at booking.
4. **Document the record.** Confirmation numbers, inclusions/exclusions, and every subsequent change go into the itinerary artifact — see [`../service-recovery-and-disruption/SKILL.md`](../service-recovery-and-disruption/SKILL.md) for change handling.

## Metrics

| Metric | Reads | Note |
|---|---|---|
| Quote-to-book conversion | booked / quoted | Low -> structure or price/trust problem |
| Average booking value | revenue per booking | Feeds the fee-vs-commission call |
| Service-fee capture | % of complex trips carrying a fee | Uncharged expertise is lost margin |
| Documentation completeness | % of elements with confirmations logged | The E&O shield |

## Anti-patterns

- Pricing before the structure is agreed.
- Burying a markup instead of naming a service fee.
- Booking without recording the cancellation-penalty schedule.

## See also

- [`../group-vs-fit-trip-operations/SKILL.md`](../group-vs-fit-trip-operations/SKILL.md), [`../../templates/itinerary-and-quote.md`](../../templates/itinerary-and-quote.md).
- Best practices: [`../../best-practices/charge-a-fee-when-the-commission-wont-cover-the-work.md`](../../best-practices/charge-a-fee-when-the-commission-wont-cover-the-work.md), [`../../best-practices/document-the-itinerary-and-every-change.md`](../../best-practices/document-the-itinerary-and-every-change.md).

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…