cost-estimation

name	cost-estimation
description	Use when constructing the Estimated cost ballpark section of a trip plan. Encodes bucket structure (flights+pass+lodging+food+extras), 2026 family-of-N anchors, and the re-verify-at-booking marker. Invoked by trip-planner.
type	reference

cost-estimation

A ballpark that gives the family enough information to decide go/no-go without pretending to be a quote. Always frame as "planning estimate, re-verify at booking."

The bucket structure

Always render as a Markdown table with bucket | per-person | family total columns. Don't skip buckets — visibility is the point.

| Bucket | Per person | Family of N |
|---|---:|---:|
| Flights / fuel | $X | $Y |
| Transit pass / car rental | $X | $Y |
| Scenic-train supplements / paid attractions | $X | $Y |
| Lodging — <base 1>, N nights | — | $Y |
| Lodging — <base 2>, N nights | — | $Y |
| Food | — | $Y |
| Local cable cars / tours / extras / tips | — | $Y |
| **Trip total** | — | **$lo – $hi** |

Why ranges, not point estimates

A point estimate ("$8,500") feels precise but is wrong. Always render as a range ($8,300 – $13,000) so the family understands the swing. Communicate which buckets drive the swing — usually flights and lodging-tier.

2026 family-of-4 anchors (re-verify at booking)

These are calibration anchors, not quotes. Use them to sanity-check estimates; always state "re-verify at booking."