Guide

How to run an unstaffed studio

An unstaffed studio works when every booking gets access that opens only for its own time, clients know the house rules before they arrive, and each booking leaves time to reset the room. Automate the routine messages and keep a person reachable for the things that go wrong.

When self-service makes sense

Rehearsal rooms, podcast booths, small photo studios and meeting rooms are often booked by people who know what they are doing and don't need a host. Being there for every booking ties you to the building and limits your opening hours. Without it you can open early mornings and late evenings, and your time goes to the studio instead of the door.

It works less well when sessions need an engineer, when the equipment is fragile and expensive, or when most clients are first-timers. You can mix the two: self-service for regulars and simple rooms, staffed sessions for the rest.

1. Access per booking, not per person

Keys and shared codes are the weak point. A key gets copied, a code shared once is passed on, and you can't tell who was in the room. Give each booking its own access instead:

  • A code (or a phone key) that works only from shortly before the start to shortly after the end
  • Sent automatically with the confirmation and again in the reminder, so nobody has to ask for it
  • Cancelled with the booking, so a cancelled client can't come in anyway
  • A log of which door opened when, so you know who was in the room before a problem was found
  • A way to open the door remotely when a code fails

2. House rules and check-in, check-out

Without a host, the rules have to be read before the session, not on a sign by the door. Keep them short and specific: what's included, what isn't allowed (food near the desk, moving the lights, guests beyond the room's capacity), how to leave the room, who to call.

  • Put the rules on your website and link them in the booking confirmation
  • Ask the client to confirm they've read them when they book
  • Check-in: a short list on the wall (lights on, check the equipment, report anything broken before you start)
  • Check-out: chairs back, cables coiled, windows shut, door closed. A photo of the room as it should look helps more than a paragraph
  • Ask clients to report damage they find at the start, so it isn't blamed on them

3. Buffers for reset

Back-to-back bookings leave no time for the next client to find the room ready. Keep a buffer between bookings, long enough to air the room and put things back: often 15 to 30 minutes, more if the room is cleaned between sessions. The buffer is time you don't sell, so include it in your price calculations.

4. Cameras and insurance

A camera at the entrance or in the corridor helps you see who came in and when. If you record people, data protection rules apply: tell them about it on the website and with a sign, keep recordings only as long as you need them, and never put cameras where people expect privacy. In the EU this falls under the GDPR; check what your local data protection authority requires.

Tell your insurer that the studio runs without staff on site. Some policies cover theft or damage differently when nobody is present, or require an alarm or certain locks. Ask before you open, not after the first claim.

5. Damage: deposits or charging after

There are two common approaches, and each has its cost:

  • A deposit held before the session and released afterwards puts off careless clients but adds friction for everyone, and holding and releasing money takes work.
  • Charging after the fact keeps booking simple, but needs written terms the client accepted at booking, evidence (the check-in report, photos, the access log) and a client willing to pay.
  • A practical start is clear terms and charging after, with deposits only for the rooms with the most expensive equipment or for first-time clients.
  • Whichever you choose, write it down in the terms shown at booking, and check what your local consumer rules allow.

6. What to automate, and what still needs a person

Keep a person for what still needs judgement: a phone number for when the code doesn't work or something breaks mid-session, regular checks and deep cleaning, restocking, and decisions on damage, complaints and exceptions. Decide who answers and when, and put that in the confirmation.

Everything that happens the same way every time can run on its own:

  • Booking and payment online, with the price and cancellation policy shown up front
  • Confirmation with the address, the rules and a calendar file
  • A reminder before the session with the door code
  • Cancellations and refunds by your policy
  • Access that opens and closes with the booking

Doing this in Ruumio

With the door codes add-on, Ruumio creates a visitor PIN in UniFi Access for every booking, valid for the booking's time plus the margins you set before and after. The code goes to the client in its own e-mail and again in the reminder, it is revoked when the booking is cancelled, and you choose which doors each room opens. From the admin you can test the connection, create a new code for a booking and open a door remotely.

Each room has a buffer before and after every booking that members and guests can't book over. Booking confirmations carry a calendar file, reminders go out the number of hours before the session that you choose, and cancellations and refunds follow each room's cancellation policy. Your instructions appear on the members' booking page, and on Pro you can edit the member e-mails to include your house rules. Booking questions (all plans) let you ask what you need to know before the session, and a room's capacity limits the number of people.

When something does need a person, admins get phone notifications for new bookings and cancellations, and on Standard and Pro staff accounts can be assigned to the sessions that need someone on site.

Questions

What happens if the code doesn't work?

Have a number clients can call and a way to open the door remotely or send a new code. Put the number in the confirmation and the reminder, not only on your website.

How early should the code start working?

A few minutes before the start is usually enough for people to get in and set up. If your buffer is long, you can let the code start earlier, but not into the previous client's session.

Do I need cameras?

No. Per-booking access with a log already tells you who was in the room and when. Cameras add evidence but also data protection obligations.

Can I run some rooms staffed and others self-service?

Yes. Treat it as a setting per room or per booking type: self-service for simple rooms and regulars, a host or engineer where the session needs one.

Updated 21 October 2026

Try Ruumio free for 14 days

No credit card needed. Your own website and booking calendar in a few minutes.

Create your studio
How to run an unstaffed, self-service studio | Ruumio