---
title: "Creating a group travel proposal with individual choices"
description: "Build a shared group itinerary with household choices, clear dependencies and separate approvals, using a practical template and Nowah planning prompt."
canonical: https://nowah.xyz/blog/travel-agents-creating-a-group-travel-proposal-with-individual-choices
lastModified: "2026-11-20T15:07:04.443Z"
---

# Creating a group travel proposal with individual choices

Build a shared group itinerary with household choices, clear dependencies and separate approvals, using a practical template and Nowah planning prompt.

Create the proposal as **one shared group plan (“the spine”) plus separate, repeatable choice blocks for each decision unit** (usually a household). Use [Nowah](https://app.nowah.xyz) to develop the shared itinerary and test how household variations affect it. Individual choices still require current supplier checks and a clear approval from the person authorised to make each purchase.

## 1) Start by defining the “choice unit” (the key to clarity)

“Individual choices” can mean different things. Decide what counts as a single selection/approval unit, state it once, and keep it consistent throughout the document.

Build the group's shared travel outline in Nowah after identifying each household's decision scope. The [group lead-contact guide](/blog/travel-agents-choosing-a-lead-contact-for-a-group-trip) helps establish the coordination route.

Common choice units:

- **Household unit:** one decision-maker/payer for a couple or family (most common)
- **Rooming unit:** anyone sharing a room, even if they’re not a household
- **True individual:** separate approvals per traveller

Put this near the top:

- **Choice unit for this proposal:** Household unit (each household selects flights/room/add-ons together).

Why it matters: your counts (rooms, transfers, deposits/approvals, deadlines) only stay coherent if the choice unit is explicit.

## 2) Use a two-layer document: shared spine + unit choice blocks

A group proposal succeeds when clients can answer two questions instantly:

Use the Nowah itinerary as the shared route reference, with separate household choices in your document. The [group decision register](/blog/travel-agents-tracking-group-travel-decisions-in-one-place) keeps selections distinguishable.

1) **What are we doing together?** 2) **What can my household choose without breaking the group plan?**

### Layer A: The shared spine (fixed for the group)

Keep the spine short, scannable, and agreed with the group before individual selections. It should include:

- trip length and base location
- shared anchors (e.g., welcome dinner; two shared day trips)
- logistics rules that affect everyone (arrival window for group transfers)

### Layer B: Individual choice blocks (repeat per unit)

Repeat the exact same block for each household. Each block should include:

- **Flights:** two flight *patterns* (A/B) with trade-offs
- **Hotel room category:** two options (or one if fixed)
- **Add-ons:** a small, controlled set (1–2 items max)
- **Requirements:** a single place to capture needs at decision time
- **Dependency acknowledgement:** tick-boxes that make timing consequences obvious

## 3) Build the spine in Nowah, then validate it before you write the proposal

### Copyable Nowah planning prompt (fictional, anonymised)

Paste this into Nowah and replace bracketed fields:

**Prompt: Group spine + individual choice lanes**

“You are assisting a travel adviser. Create a **7-night** group trip plan to **Lisbon, Portugal, checking in 4 June and out 11 June 2027** for **10 travellers (6 adults, 4 children ages 6–14)**. Travellers depart from **London**, **Dublin**, and **Madrid**.

Output required:

1) A **day-by-day itinerary** with an arrival-day welcome dinner, **two shared day trips** (one scenic; one cultural, subject to verified suitability), and **two free-time days**.

2) **Three base-hotel candidates (A/B/C)** described by family suitability and room-category types (standard, upgraded view, suite/family; note connecting rooms as a request).

3) For flights: **two flight patterns per origin** described by trade-offs (duration/connection complexity/arrival-time alignment). **No prices.**

4) A short list of **dependencies** (how split arrivals affect transfers/check-in; what days must remain fixed).

Keep the output structured with headings and simple tables. Label any quantities as planning placeholders.”

### Adviser check: what to verify before anything goes client-facing

- **Pacing:** shared days aren’t stacked too tightly around arrival/departure
- **Geography:** use map/timeline views to confirm travel flow is plausible
- **Choice impact:** each flight pattern’s arrival timing clearly does or doesn’t fit the transfer plan
- **Room realism:** check exact occupancy and bedding. Treat unconfirmed preferences as requests; essential requirements must be resolved before purchase.
- **Governance:** bookings, changes, and refunds are subject to supplier availability and terms; obtain client approval before payment

## 4) Worked example: reunion group, three origin cities, household-level choices

**Scenario (hypothetical):** A 10-person reunion group (6 adults, 4 children ages 6–14) travelling for 7 nights to Lisbon. Household 1 has two adults and two children; Household 2 has two adults and two children; Household 3 has two adults. Three households are departing from three different origin cities. The organiser wants everyone together for a welcome dinner plus two shared day trips, with breathing room for households to self-direct the rest.

Compare the reunion's arrival patterns in Nowah before proposing common activities. The [group arrival coordination guide](/blog/travel-agents-coordinating-arrival-times-for-a-group-itinerary) helps protect shared plans without forcing identical flights.

### Step A: Define the spine (what is fixed)

Your spine can be as compact as a single table:

- **Trip length:** 7 nights
- **Base location:** one area/region
- **Shared anchors:** welcome dinner + two shared day trips
- **Free-time:** two days with no group commitments
- **Transfer rule:** one arrival window for a group transfer plan

### Step B: Offer flight *patterns* (A/B), not sprawling flight lists

For group proposals, patterns are easier for clients to choose and easier for you to operationalise.

Example pattern language (no prices):

- **Pattern A (alignment-first):** arrives early-to-mid afternoon; may include a connection; is a candidate for the proposed transfer and welcome dinner; timings need checking.
- **Pattern B (comfort-first):** fewer connections or better routing; may arrive later; may require separate transfer and could miss the welcome dinner.

Search each origin in Nowah. Offer two patterns only where real search results support them; otherwise explain the available choice. A pattern is an itinerary direction, not approval to buy an unspecified flight.

### Step C: Keep rooms category-based and consistent across households

For each household, show the exact supplier room category, permitted occupancy and bedding terms once priced:

- **Room A:** standard category
- **Room B:** upgraded view category or suite/family category
- **Connecting rooms:** if essential, require actual supplier confirmation; otherwise label the preference unconfirmed

Nowah’s hotel search and booking capabilities (see /features) can support your research and shortlisting internally. In the proposal, keep it decision-oriented: categories, trade-offs, and dependencies.

## 5) Copy/paste template: “Shared Spine + Individual Choices” proposal section

Use this directly in your proposal pack (this is an editorial template to use in your own document tools).

### Group Travel Proposal — Shared Spine + Individual Choices

**Trip name:** \[Group name\]

**Dates / travel window:** \[Dates\]

**Choice unit:** \[Household / Rooming unit / Individual\]

**Organiser:** \[Name\]

**Selections due (time zone):** \[Date \+ time \+ TZ\]

#### A) Shared spine (applies to all units)

| Spine item | Group plan (fixed) | Notes / dependencies |
| --- | --- | --- |
| Trip length | \[7 nights\] |  |
| Base location | \[Area/region\] |  |
| Base hotel approach | \[One selected property, subject to availability\] | Room category varies per unit |
| Welcome moment | \[Arrival\-day dinner / meet\-up\] | Late arrivals may miss |
| Shared day trip #1 | \[Scenic/nature day\] | Fixed day |
| Shared day trip #2 | \[Cultural day\] | Fixed day |
| Free-time days | \[Days\] | No group commitments |

**Transfer rule (one sentence):** Travellers arriving within a **\[X\]\-hour window** use the group transfer plan; arrivals outside this window use a separate transfer arrangement.

#### B) Individual choices (repeat this block per unit)

**Unit label:** \[Household 1\]

**Origin city:** \[City\]

| Choice area | Option A | Option B | Selection |
| --- | --- | --- | --- |
| Flights | Pattern A: \[arrival range \+ trade\-off\] | Pattern B: \[trade\-off \+ timing impact\] | A / B |
| Hotel room | Room A: \[category\] | Room B: \[category\] | A / B |
| Add-on (optional) | \[Add\-on name \+ brief purpose\] | Not taking | Yes / No |
| Special requirements | Bedding/dietary/accessibility |  | \[Write\-in\] |

**Dependency acknowledgement:**

- \[ \] My flight choice fits the group transfer window\.
- \[ \] If my flight choice does not fit, I accept separate transfer arrangements may be required\.

#### C) Unit estimate (confirmed when sourcing live availability)

| Bucket | Basis | Amount |
| --- | --- | --- |
| Flights | Selected pattern | \[ \] |
| Hotel | \[\#\] nights × selected category | \[ \] |
| Transfers | Group vs separate | \[ \] |
| Add-on | Only if selected | \[ \] |
| **Estimated unit total** |  | **\[ \]** |

**Unit approval statement:** I approve the selections above for this unit. I understand bookings, changes and refunds are subject to supplier availability and terms, and I will review final details before payment.

Name: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  Date: \_\_\_\_\_\_\_\_\_\_

## 6) Decision rules that keep freedom without breaking the plan

1) **Shared anchors are fixed** on the days shown.

2) **Arrival timing affects logistics:** flight patterns that don’t fit the transfer window may require separate transfers and could miss the welcome moment.

3) **Room suitability is specific:** check occupancy and bedding for every unit. Connecting rooms required for safe rooming must be confirmed; a request alone is insufficient.

4) **Requirements must be submitted with selections** (dietary/accessibility/bedding) so they can be requested during sourcing.

These rules are exactly what you pressure-test in Nowah: does the itinerary still work when you imagine some households choosing Pattern B?

## 8) Pre-send rubric (specific to group proposals with individual choices)

Run this quick rubric before you send the proposal to the organiser for distribution.

| Check | Pass standard | If it fails |
| --- | --- | --- |
| Spine is scannable | One table; anchors/days are unambiguous | Reduce narrative; rewrite as bullets/table |
| Every unit has the same block | Flights + room + add-on + requirements | Duplicate the block; don’t improvise layouts |
| Dependencies are visible | Transfer/arrival impacts are next to flight options | Add a dependency line/tick-boxes |
| Choices are limited | Two flight patterns; max two room categories | Collapse to A/B; move other ideas out |
| Approvals are actionable | Each unit can approve selections clearly | Add signature/acknowledgement line |

If you used Nowah for itinerary planning, do a final alignment check: the spine in your proposal must match the latest Nowah itinerary and day order.

## Keep the shared plan and household decisions aligned

A group proposal works when it feels like **one trip**—but decisions are still made **per household**. The “shared spine + individual choices” format gives you a record of what the group shares and what each household selected.

Use [Nowah](https://app.nowah.xyz) to build and refine the spine, explore flight patterns by origin, and research hotel candidates and room categories that support your choice lanes (see [Nowah features](/features)). Keep private household prices and requirements within authorised recipients. An organiser’s coordination role does not automatically give them payment authority for every traveller.

## Related guides for travel agents

- [Recording a client's acceptance of a travel proposal](/blog/travel-agents-recording-a-client-s-acceptance-of-a-travel-proposal)
- [Creating a travel itinerary revision log](/blog/travel-agents-creating-a-travel-itinerary-revision-log)
- [Building a hotel shortlist for a travel proposal](/blog/travel-agents-building-a-hotel-shortlist-for-a-travel-proposal)
