Boulder Creek Info Packet - Contents Outline

One PDF (or one link page), sent personally by the booking owner. The job: after one read, a coordinator can picture their event here and knows exactly what happens next. Short pieces, real photos, no padding.

1 · The property story, one page - NEEDS CREATION

• What this place is: a working farm and retreat campus in north Idaho, forest on three sides, room for 123 to sleep and 175 to gather.
• One paragraph of history (the school years, the farm now), one paragraph of what a stay feels like, one wide photo.
• Raw material exists (site audit, pillar pathways, re•world voice guide); the page itself does not. Load the re•world voice guide before drafting.

2 · Campus map - BASE EXISTS, GUEST VERSION NEEDS CREATION

• The aerial exists (design_handoff_boulder_creek-0717/uploads/BoulderCreek-Total.png).
• The guest one-pager is specced at 26-0717-CAMPUS-MAP-ONE-PAGER.md - a crop-and-annotate job, blocked only by the naming-reconcile decision.

3 · Lodging lineup with photos - PHOTOS EXIST, PAGE NEEDS CREATION

• One row or half-page per unit: name, one warm sentence, sleeps, layout, kitchen note, [photo slot].
• Photos exist: bouldercreekretreat.com /lodging pages plus the building-library refs folders. Choose one hero shot per unit; do not reshoot for v1.
• Uses whichever names win the naming reconcile (see the map spec).

4 · Pricing overview - PRICE SHEET EXISTS, POINT AT IT

• Half a page: how pricing works (per building per night, event spaces by the day, resort fee, deposit rhythm) and who to talk to about a quote.
• Numbers live in the canonical price sheet (26-0616-CURRENT-INVENTORY-AND-RATES.md + 26-0616-RATE-CARD.html). The packet does NOT duplicate rates - one source, no stale copies floating around in old PDFs.
• [CONFIRM whether the packet includes the rate card as an attachment or states "ask us for current rates."]

5 · Food + Timberline Catering feature - NEEDS CREATION

• Half a page on meals, and it should lead with confidence: guests arrive expecting camp food and get Julie's cooking instead. That surprise is one of our best reviews-in-waiting - say it plainly, with one great food photo.
• Cover: catered vs self-cook vs mix, the kitchens that exist in the units, dietary needs handled when we know early.
• Keep internal mechanics (markup, licensing) out of the packet entirely.
• [CONFIRM with Julie: the sentence we use about her kitchen, and a photo she likes.]

6 · Sample schedules - NEEDS CREATION

• Two or three one-page day shapes, so a coordinator can picture the rhythm:
  • A 3-day retreat (seed it from the Amanda Aug 27-30 shape once it runs)
  • A training or corporate offsite day
  • A wedding weekend [CONFIRM we want to feature weddings in v1]
• Each: arrival to departure in ~10 lines. Real times, real spaces.

7 · What to expect one-pager - EXISTS (draft)

• 26-0716-PROPERTY-EXPECTATIONS-ONE-PAGER.md, drafted, Rylie redline pending. Include it as the honesty page: house rules, quiet hours, the pond, the wild.

8 · Next steps, half a page - NEEDS CREATION

• The path, numbered, no mystery:
  1. Answer the questionnaire (or just reply to the email).
  2. We propose a shape and hold a call.
  3. Agreement + deposit holds your dates. Nothing is held until then.
• Who you will be working with: the booking owner by name, one line on the host handoff at arrival.

Assembly notes

• v1 is allowed to be plain: consistent headers, real photos, tight copy. The design system comes later and restyles all of it - do not wait for it.
• Order above is the reading order: story first, map second, money in the middle, honesty near the end, next steps last.
• One file, under 10 pages, small enough to email.

The ledger