Skip to content
Back to skills

Group Vs Fit Trip Operations

ASecurity

Decide and run group vs FIT trips: FIT (individual custom) flexibility vs group-block economics (room block, deposit, cutoff date, attrition, tour-conductor benefit). Build the block before you sell against it, and manage the deposit/cutoff/attrition liabilities. Contract terms are verify-at-use per supplier.

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

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add mcorbett51090/RavenClaude --skill group-vs-fit-trip-operations --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Group Vs Fit Trip Operations?

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

Security grade badge for Group Vs Fit Trip Operations
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-group-vs-fit-trip-operations/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-group-vs-fit-trip-operations)

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: group-vs-fit-trip-operations
description: "Decide and run group vs FIT trips: FIT (individual custom) flexibility vs group-block economics (room block, deposit, cutoff date, attrition, tour-conductor benefit). Build the block before you sell against it, and manage the deposit/cutoff/attrition liabilities. Contract terms are verify-at-use per supplier."
---

# Group vs FIT Trip Operations

**FIT** (individual, custom) and **group** (a contracted block) are different economic instruments with different risk. Choose deliberately, then operate the one you chose.

## The loop

1. **Classify the trip.** Party size, price sensitivity, need for shared inclusions, and flexibility drive FIT vs group — traverse the group-vs-FIT tree in [`../../knowledge/travel-agency-decision-trees.md`](../../knowledge/travel-agency-decision-trees.md).
2. **FIT path — flexibility over leverage.** Book each element individually; each carries its own penalty schedule (see [`../itinerary-design-and-quoting/SKILL.md`](../itinerary-design-and-quoting/SKILL.md)). Best when travelers want custom pacing and there's no block economics to capture.
3. **Group path — build the block first.** Contract the room/seat block: deposit, **cutoff date** (when unsold rooms release), and **attrition** (the % you owe even if unsold). Understand the **tour-conductor (TC) / comp** benefit (e.g. one comp per N paid — `[verify-at-use]`). Build and hold the block *before* selling against it (§ best practice below).
4. **Manage the liabilities.** Track pickup vs the block, watch the cutoff, and reduce attrition exposure before the penalty date. Group payment cadence differs from FIT — deposits and name lists on a schedule.

## Metrics

| Metric | Reads | Note |
|---|---|---|
| Block pickup rate | rooms sold / rooms blocked | Low near cutoff -> attrition risk |
| Attrition exposure | unsold block × attrition penalty | The liability to manage down |
| TC / comp earned | comps earned vs threshold | A group's margin sweetener |
| Group deposit adherence | on-schedule deposits collected | Protects against traveler melt |

## Anti-patterns

- Selling a group before the block is contracted (overselling or attrition surprise).
- Ignoring the cutoff date until it passes.
- Running a group as N separate FIT bookings and losing the block benefit.

## See also

- [`../itinerary-design-and-quoting/SKILL.md`](../itinerary-design-and-quoting/SKILL.md), [`../service-recovery-and-disruption/SKILL.md`](../service-recovery-and-disruption/SKILL.md).
- Best practice: [`../../best-practices/build-the-group-block-before-you-sell-it.md`](../../best-practices/build-the-group-block-before-you-sell-it.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…