The day runs out of the same system that sold it
Most venues sell in one place and then run the shift somewhere else, on a printed sheet, a whiteboard and a group chat. The gap between the two is where the detail goes missing.
One sheet for the shift, and it is the booking record
The run sheet is not an export of the diary. It is the diary, read for the person standing on the floor: what starts when, who is on it, how many are coming, what they have paid for, what is still outstanding and which of them has told you something you need to know before they arrive.
Because it is the same record, a change made at the counter at four is on the sheet at four and one second. Nobody reprints anything, and nobody works from a version that was true this morning.
Whether the thing starting at seven is a room, a lane, a grid or a table, it is a session with a start, a duration, a party and a set of resources. The sheet does not care which of those you run, and neither does the rest of the system.
Check-in and waivers are one flow, not an add-on you pay for
Waivers sit inside the booking. They are sent with the confirmation, signed before arrival where the guest is willing, and attached to the party rather than to a clipboard by the door. At check-in you can see who has signed and who has not, and the ones who have not can sign on the spot without leaving the flow.
Minors and guardians are handled properly rather than approximately. A guardian signs for the minors they are responsible for, the relationship is recorded, and the signature covers the named children rather than a headcount. When a school or a birthday party arrives with a list that does not match the booking, you can fix the list rather than the paperwork.
None of this is a paid module. A venue that has to buy consent capture separately ends up collecting consent badly, and that is a liability rather than a pricing decision.
The things a new staff member would not know to ask
Each session carries its own prompts: the safety points that must be said out loud, the access needs the party told you about at booking, the allergy on the food order, the fact that this is a corporate group who have asked for no photographs.
They are attached to the session rather than kept in someone's head, so the shift runs the same way on a Tuesday with a new host as it does on a Saturday with the person who has been there three years.
Captured at the end of the session, not reconstructed on Monday
Finished, started late, ran short, one no-show, two walk-ups added, the group that escaped with four minutes left. It takes the host about fifteen seconds at the end of the session, while it is still true.
Reconstructing a week from memory on a Monday produces a version of the week that is roughly right and precisely useless. Everything on the reporting side is only as honest as this step, which is why it is fifteen seconds and not a form.
One screen, one filter, and it stays where you put it
If you run more than one site, the default view is all of them. Set the filter to one venue, or to the three in one state, and it holds across the run sheet, the diary, the reports and the exports until you change it. You are not re-selecting the same venue on every screen you open.
The reverse holds too. A duty manager who only ever needs one site sees one site, and never has to think about the fact that there are others.