A Group Trip to the Calgary Stampede: Rodeo Days, the Midway, and Eight People Who All Owe Different Amounts

A Calgary Stampede group trip is a specific kind of planning problem. It's not one event — it's ten days of overlapping ones, in a city most of the crew doesn't live in, with a schedule that runs from a 7am pancake breakfast to a 1am exit from Nashville North. Get the coordination wrong and you spend the trip texting "where is everyone?" instead of being somewhere.

This is the Stampede-specific layer on top of the summer group hangouts playbook — the daily schedule, the map of the grounds, and the cross-border money math, all run from one hangout link.

Decide: which days, and who's actually in

Stampede is ten days, but your crew isn't doing ten days. The first decision is which days — and that's a poll, not a thread.

Drop the options in: the first Saturday (rodeo afternoon plus the evening Grandstand Show), a Friday built around the midway and Nashville North, a Sunday recovery brunch downtown. Let people vote on what they'll actually commit to, with a deadline. You'll find out fast whether you've got a four-day crew or a one-big-Saturday crew before anyone books a flight.

Set the RSVP-by date two weeks before grandstand tickets go on the group card. Once it passes, nobody can quietly flip from "yes" to "actually can't" after you've bought their seat — the headcount you're spending against is the real one. (Plans genuinely change; as host you can still adjust someone's RSVP, but the deadline stops the silent drift.)

Personal note — the poll does something sneaky and useful: it surfaces the one friend who wants the rodeo and the three who only care about the concert. Better to know that Tuesday than at the gate.

Coordinate: a day that runs 7am to 1am, on a map

This is where a Stampede trip lives or dies. A single day can have a pancake breakfast downtown, a rodeo in the afternoon, a grandstand show in the evening, and a late night at Nashville North — and those overlap with people splitting off. Brunchie's itinerary is built for exactly that: items can overlap in time, and each one carries its own location.

So your Saturday reads honestly:

• 7:30am — Pancake breakfast (downtown lot)
• 1:00pm — Rodeo (Stampede Park grandstand)
• 4:00pm — Midway + free stages (Stampede Park) — overlaps; this is the split-off crew
• 7:45pm — Grandstand Show (Stampede Park)
• 11:00pm — Nashville North (Stampede Park)

Every stop you pick from address autocomplete drops a pin on the map, color-coded by schedule, with the rental marked too. New-to-Calgary friends see the whole day laid out geographically — the park, the breakfast spot, the rental, the airport — instead of asking the one local where everything is.

Keep the logistics off the guest view with a host-only itinerary: the rental door code, the "everyone's gift for the bride" cue, the backup rideshare plan. Guests see the fun schedule; you keep the runbook.

Match your attendee cap to the rental's beds — if it sleeps eight, cap it at eight — and turn on the waitlist so the two maybes queue up instead of bouncing. And invite your Calgary-local friend as an external guest by email; they'll never download an app, but they'll see the plan on the link and meet you at the gate.

Spend: passes, the rental, and the friends paying in USD

Stampede money gets messy because it arrives in pieces — gate passes here, grandstand tickets there, the rental on one card, rideshares on four different phones. Log each shared cost as it's booked and mark who paid:

• Rental — 3 nights (whole crew)
• Grandstand Show ×8
• Rodeo grandstand seats ×8
• Airport + grounds rideshares

When it's time to settle, Brunchie collapses the tangle into the fewest payments — not eight people sending eight transfers in eight directions. You record the payments as they happen; it's a clean ledger, not an auto-charge.

The cross-border part is the quiet win. Your friends flying in from the US paid for some things in USD and owe their share of CAD costs. Log everything in the currency you actually paid; when the US crew opens settle-up, their share converts to USD at the day's exchange rate, labelled approximate. Nobody's doing exchange math at the airport. (The full mechanics are in the expense splitting guide, and the broader trip-money pattern is the same one in the summer playbook.)

Personal note — the rule that saves the friendship: log the expense the second you book it, not "later." Later is where the $340 rideshare night quietly disappears.

Remember: ten days of photos in one place

By day three everyone's camera roll is a mess and the good midway-at-dusk shot is on someone's phone who left early. The shared album fixes that — everyone uploads straight from their phone in the hangout, so the rodeo afternoon, the ferris wheel, and the Nashville North chaos all land in one place. No "can you AirDrop me that."

The feed keeps the running commentary — photo posts, videos, reactions — as the trip happens. And the guestbook catches the stuff photos miss: the breathless "we actually made it to the front" voice note or clip, the inside joke nobody will be able to re-explain by August.

If you're also running a friendly competition — a cornhole bracket at the rental, say — Brunchie does that too; here's the bracket walkthrough.

The Stampede trip on one hangout

A Stampede crew trip is too many moving parts for a group chat: ten days, a city nobody knows, a schedule that overlaps itself, and money in two currencies. Putting it in one hangout means the schedule is on a map, the headcount is real, the split is settled, and the photos are in one place — so the planning stops being one person's full-time job and everyone just shows up.

Start with the summer group hangouts playbook for the full four-phase workflow, or if your crew's summer is more festival than fairground, here's planning a music festival trip. Either way, it's one link and the whole crew's on it.