When expenses are off: here's what a plus-ones hangout CAN do

Something that trips people up: you set up a hangout, you turn on plus-ones, and the expenses tab disappears. Not greyed out — gone.

This is intentional. Here's why, and here's everything you actually have in its place.

Why expenses turn off with plus-ones

Expense splitting is built on a known headcount. When you split a $400 dinner 8 ways, you get $50 each. The math works because you know the denominator.

Plus-ones break the denominator. If you allow plus-ones, the headcount is fluid. Guest A is coming alone. Guest B is bringing a partner. Guest C RSVPs with two extras after the initial invite goes out. Guest D still hasn't answered. The actual number of people attending — and by extension the per-person share of any shared cost — isn't knowable until the last RSVP closes. And even then, day-of numbers often don't match.

Brunchie auto-disables expenses when allows_plus_ones is on. Not as a limitation — as a correctness guarantee. Split math on a fluid headcount produces numbers that are wrong by design. We don't want to show you wrong numbers.

This is also why the wedding hangout specifically doesn't use the expense splitter: your 150-person wedding is the ultimate fluid-headcount event, and the budget is host-private anyway. Your guests should never see vendor invoices. The expense tab being off isn't something your guests notice — because they were never supposed to have it.

For more context on the headcount-certainty tradeoff, our post on attendee limits and recurring hangouts covers the related case: attendee limits and plus-ones can't be used at the same time for the same underlying reason — they're both about headcount certainty, and you can only enforce one model at a time.

What a plus-ones hangout does have

The expenses tab being off doesn't leave you with an empty hangout. Here's the full feature surface:

Multi-itinerary

Run multiple itineraries from a single hangout, each with its own audience. A public guest schedule so everyone knows where to be and when. A host-only runbook with vendor cues, timing notes, and the things guests shouldn't see — your cohost team plus any vendors you've added as external cohosts (photographer, coordinator) share that runbook view; regular guests don't.

This is especially useful for weddings: the ceremony timeline your guests see is different from the run-of-show your planner is executing. Same hangout, different views. See the itinerary guide for how the audience model works.

Live event feed and photobooth

Guests post photos, videos, boomerangs, and voice memos in real time. The feed is the shared album — no QR code, no separate link, no Google Photos permissions to manage. Voice memos display with pre-computed waveforms so they look polished in the feed, not like a sad gray audio blob. Everything is preserved post-event; guests can reopen the hangout a year later and the photos are still there.

See your shared wedding photo album is already built in for the full breakdown.

Docs tab

Every PDF uploaded to the hangout surfaces automatically in the Docs tab. Venue contracts, DJ agreements, floor plans, photographer shot lists — all in one place. Hosts, cohosts, and external cohosts (the trusted-vendor tier) see all guest-visible plus host-only documents; plain guests and external guests see only the guest-visible ones (anything not marked host-only).

See every wedding contract in one place for how this works in practice.

Polls

Dietary preferences. Song requests. Shuttle timing. Menu choices. Polls in a plus-ones hangout work the same as in any hangout — run them before the event to collect info, during to keep people engaged, or after to gather feedback. Headcount fluidity doesn't affect polls at all.

Host-only spreadsheets

The wedding budget. Vendor comparisons. The seating chart source data before it gets loaded into the visual chart. Spreadsheets inside the hangout are visible only to hosts and cohosts. Your guests see the hangout; they don't see the host-only layer.

External guests (view-only vendor access)

Invite your photographer, DJ, coordinator, or florist as an external guest (read-only) or as an external cohost if you trust them with the host-only runbook. External guests see all guest-visible content; external cohosts additionally see anything you've marked host-only. Neither tier can RSVP, post to the feed, or see the host-private expense data. It's a window into the parts of your hangout that vendors need to do their job — without a backstage pass to everything else.

The trip-vs-event distinction

If you're coming from our pieces on bachelorette trip planning or group trip expense splitting, you may have noticed those posts lean heavily on the expense splitter. That's because trips are a different product.

A bach trip has a fixed headcount. You know exactly who's going, you book for that number, and the per-person splits are real numbers. The expense splitter works because the denominator is stable. Same with any small fixed-attendance event where everyone knows what they owe: rehearsal dinners, group trips, small friend getaways.

Plus-ones hangouts — weddings, large birthday parties, family reunions, holiday parties with open invites — optimize for fluid headcount. The tradeoff is intentional: you get scale and flexibility, and the feature surface reflects that.

The rule of thumb:

• Fixed headcount, peer settle-up (bach, rehearsal dinner, group trip): make a separate hangout, use expenses, enjoy the math.
• Fluid headcount, scale over certainty (wedding, big birthday, open invite): plus-ones hangout, use the tools above.

Plus-ones hangouts aren't trips with worse math. They're a different product for a different problem.

Setting up a plus-ones hangout

There's nothing special to configure beyond the standard hangout setup:

1. Create a new hangout. Toggle on Additional guests in the RSVP section.
2. Build your itinerary — at minimum a public schedule. Add a host-only runbook if you're running a complex event.
3. Upload your key documents to the Docs tab as you finalize them.
4. Create any pre-event polls (dietary preferences, song requests, menu choices).
5. Share the hangout link with your guests.

The photobooth and live feed are on by default. No configuration needed.

The expenses tab being off is the only thing that changes. Everything else is there.

Get started at brunchie.app.