Capacity and Scheduling for Saunas

A sauna does not sell appointments. It sells a session: one room, a set number of seats, a fixed clock. When the 6:00 session starts, the heat is already up and the door is about to close. The job of your scheduling is to put as many of those seats to work as the room will safely hold, without ever pretending the room is full when it isn't.

That sounds simple. Most booking tools get it wrong because they were built for the hair salon down the street, where one person books one provider for one block of time. A sauna is the opposite. Many people share one room at the same time. Your software has to count seats, not appointments.

Short answer

Every session carries its own seat count, and bookings fill it one seat at a time until the cap is reached. The day is a grid defined by session length, sessions per day, and the turnaround between them, and the turnaround is part of the schedule, not optional padding. One per-seat booking must never mark the whole room as taken.

What to get right first

• Set a capacity per session that matches what the room safely holds.
• Lay out the grid from three numbers: session length, sessions per day, turnaround.
• Bake the cleaning and cooldown gap into the grid so sessions can never overlap on one room.
• Show guests the live seat count: "5 seats open," then "Last seat."
• Track each room or space on its own grid so a sellout in one never blocks another.

A session carries its own seat count

Every session has a capacity: the number of seats the room safely holds for that block. An eight-person room runs eight seats. A two-person barrel runs two. That number belongs to the session, not to the booking.

When a guest reserves, they are buying one seat in a session, not the whole room. The session can hold seven more. So the same 6:00 block stays open to the next guest, and the next, until the eighth seat is taken.

This is the line that separates a shared session, where strangers buy single seats and sit together, from a private buyout, where one group pays to take the whole room. They are different products at different prices. Read more on the buyout side in private rentals and buyouts.

Laying out the day

A schedule is a grid of sessions across the day. Three numbers define it:

• Session length. How long guests are in the room. Forty-five minutes, an hour, ninety.
• Sessions per day. How many blocks you run, set by your hours and the length above.
• Turnaround. The gap between sessions for cleaning, cooldown, wiping benches, resetting the room. This is not optional padding. It is part of the day.

If your sessions run an hour and you need fifteen minutes to reset, the room cycles every seventy-five minutes, not every sixty. Bake the turnaround into the grid so two sessions can never overlap on the same room. The clock should protect your staff, not crowd them.

Operator rule: the room cycles on session length plus turnaround, never on session length alone.

Filling seat by seat

As bookings come in, the session fills one seat at a time. The booking page should show what's left: "5 seats open," then "2 seats open," then "Last seat." Guests booking together can take several seats in one session, and the count drops by that many.

To stop two people from paying for the same last seat, the seat is held the moment checkout begins. The hold is capacity-aware: it counts against the session while the card is being entered, then converts to a confirmed seat on payment or releases if checkout is abandoned. No double-sold seats, no awkward refund email. More on that in booking and checkout.

When the last seat goes, the session sells out and closes itself. The block stays visible as full so guests can pick another time, and so a cancellation can reopen the seat for someone else.

More than one room

Larger sites run several rooms or spaces at once: two saunas, a cold plunge, a steam room. Each space carries its own seat count and its own grid. The 6:00 sauna can be full while the 6:00 plunge has room. Your schedule tracks them separately so a sellout in one never falsely blocks the other.

Why one seat must never lock the room

This is the whole point. If your software treats a single per-seat booking as taking the entire room, one guest blocks seven empty seats and you run a near-empty room marked "sold out." That is revenue left on the bench, night after night. Count seats, hold the right seat during checkout, reset cleanly between sessions, and the room fills the way it was built to. How members and prepaid credits draw against those seats is covered in memberships and credits.