Half past seven on a Saturday. The building is open because somebody unlocked it, the heating is not on, and the guest wifi is asking for a code that was emailed to a colleague who is not in until Monday. Your first guest is in ninety minutes.
Nothing about this event is harder than the one you ran on Wednesday. The difference is that on Wednesday, roughly forty people in that building could have solved the wifi in under a minute. Today there are four, and none of them are the ones who set it up.
Weekend and out-of-hours events get planned as if they are weekday events with a different date on them. They are not. The event is the same size, the door is the same door, and everything behind it is thinner.
What actually gets thinner
Worth being specific, because it is not the obvious things.
The venue's duty manager on a Saturday is often not the person you did the site visit with. They are competent and they are covering, which means they know where the fire panel is and not where the registration desk power comes from. Anything you agreed verbally in June is now a story you are telling a stranger.
Technical support goes from a person in the building to a number that rings out. Same for the AV contractor, the furniture hire, and whoever supplied the printers. Most of those companies staff their weekends for shows they are already on site for, not for phone calls.
Deliveries and couriers largely stop. A forgotten box on a Saturday is not a box that arrives at eleven, it is a box you do without.
And your own crew is different. Weekend work is the part of this industry that people opt out of first. In the ESSA member survey reported at the end of last year, 73% of member companies had faced recruitment difficulties in the previous twelve months, with 88% of those citing a shortage of skilled candidates, and 87% named work-life balance as the biggest single obstacle to retaining the staff they have (New ESSA survey exposes persistent UK events industry pressures, Event Industry News, December 2025). The practical version of that number is the one you already know: the Saturday roster is the hardest one to fill, and the people who do say yes are more likely to be new.
So plan for a door staffed by fewer people, some of whom are on their first shift with you, in a building where nobody can help you. That is the actual brief.
Move every dependency to Friday afternoon
The single highest-value habit here is to stop treating the morning of the event as a time when anything can be obtained.
By close of business on the last working day before, you want to be holding, in your own hands and not in somebody's inbox:
- The wifi network name and password, tested from a device you will actually be using, not read off a laminated card.
- Door codes, key collection arrangements, and the name of the person who will physically be in the building at your access time.
- A mobile number for that person, and their manager's, and confirmation that both are on duty rather than on call.
- Loading access times and whether the bay is locked at weekends.
- Power. Which sockets by the desk are live, and whether they are on a circuit that the building switches off out of hours.
- Any printed material, badge stock and signage, on site or in your vehicle.
None of that is new advice, and all of it is advice people skip on a weekday because they can improvise. On a Saturday you cannot. If you have not done a site visit that walks the front door properly, the weekend event is the one where that shows.
Test the check-in itself the same way. A full rehearsal of the check-in before the day, on the devices and the network you will use, catches the problems that have a supplier-shaped fix while suppliers are still answering.
Make the door survive the building
The reason we keep coming back to this is that the front door is the one part of an event that cannot wait. A session can start ten minutes late. Arrivals cannot pause.
Two failures cause almost all of it: the network and the power.
For the network, assume it will drop and check what happens when it does. Scanning should keep working from the device, queueing the results, rather than stalling on a server it cannot reach. That is the whole argument for scanning that survives the venue wifi dropping, and it matters twice as much when there is nobody to reset the access point. If you are running self service, check that your kiosks fall back gracefully rather than showing a guest an error message they cannot act on.
A signed QR pass helps here for the same reason. The pass carries its own proof, so a scanner can verify it without asking a server for permission first.
For power, carry your own. Battery packs, charged the night before, a four-way you own, and a plan for where the tablets sit between waves. The front-of-house kit list is not a weekend-specific document, but the weekend is when the missing item stays missing.
Fewer people, so make each one independent
A thin crew fails differently from a full one. It is not that the work is too much, it is that everything routes through the one person who knows how the system works, and that person spends the morning being interrupted.
The fix is to hand out capability rather than instructions. Every person on the door gets their own login and their own lane, so they can search the list, check a guest in, and register a walk-up without asking. Somebody who has to fetch you to look up a name is not staffing a lane, they are queueing at one.
Then be explicit about the three or four exceptions that will actually happen: the guest who is not on the list, the pass that has already been used, the person who wants to bring a colleague, and the one who is upset. Say who decides, in a sentence, before doors open. On a weekday you can defer that decision to whoever is in the office. Today you are the office.
Keep the briefing to five minutes and do it standing at the desk rather than in a back room, because half of it is pointing at things. If your crew are volunteers or new casuals, the same brief plus one practice scan each is the difference between a nervous door and a calm one, which is most of keeping volunteers confident on the day.
Write down who you call, and what happens if nobody answers
One side of one page, printed, at the desk. Not a group chat, not a shared document behind a login.
Names and mobile numbers for the venue contact, the duty manager, your own event lead, the AV or technical contact, and the first aider. Then, next to each, the answer to the question nobody writes down: what you do if that number rings out. Fire alarm goes off and the duty manager is not answering means everyone out to the assembly point you identified this morning, and you have the list of who is in the building on the tablet in your hand.
That last part is the piece that matters most on a quiet day. A live count of who is checked in and has not departed is the only version of the truth that exists when the building's own staff are minimal, and it is precisely what a duty manager or a responding officer will ask you for. It is the same reasoning behind Martyn's Law and knowing who is in the building, applied on the day of the week when the fewest people can answer it for you.
The rest is ordinary
Weekend events are not a special discipline. They are the ordinary discipline with the safety net taken away, which is why they reward the things that were always worth doing: the dependency list closed on Friday, the check-in tested on the real network, the crew who can each work independently, the count that is right and visible, and one printed page of numbers.
A door that only works because somebody in the building can be summoned is not really working. It is being rescued, quietly, every time, by people who happen to be there on a Tuesday.
