Photo Booth Event Checklist: Booking to Strike
Every step of running a booth at an event, from the week-before checks to post-event file delivery — built for open-air, enclosed, mirror, and 360 setups alike. Copy it, adapt it to your booth, and brief your attendant straight from it. Everything here is free to read and use — no signup.
Booth failures are almost never mysterious. The printer that dies mid-event was low on media at load-in; the artwork with last year's date was never re-approved; the 360 platform that wobbled was on carpet nobody asked about. This checklist front-loads all of it. Run the pre-event section in the week before, the setup section on site, and the strike section before you pull out of the parking lot.
Pre-event: the week before
Everything that can be verified from your desk gets verified from your desk. Show-day problems you could have caught a week early are the most expensive kind.
Load-in and setup
The order matters: place, level, power, light, test. A booth tested in the actual spot under the actual lighting is the only booth that is actually ready.
During the event
A running booth is not a finished job. The attendant's checklist is short but continuous — consumables, queue, quality, power.
Strike and after
The event ends twice: once when the last guest leaves the booth, and once when the files are delivered and the gear is counted back in. Only the second one closes the job.
Running this without the paper
In OpsVue, each booking is a work record that already holds most of this checklist's answers: the package and add-ons are the quote lines, the artwork lives in the job's files — with version families, so "final_v3_ACTUAL" chaos becomes one file with a current version — and the week-before items become tasks with due dates and owners. Availability is date-scoped with turnaround buffers, so when a second event tries to claim the same booth for the same Saturday, the conflict surfaces while you are quoting, not while you are loading the van. Gear check-out and check-in runs against the job, and anything missing is computed from what went out versus what came back.
Your client confirms the booking through a no-login link — they view the document and accept with a typed name, recorded with evidence — OpsVue calls this exactly what it is, a recorded acceptance — and they can send files back through that same link, which is a clean way to collect the artwork approval in writing. OpsVue is in early access; the checklist above works on a clipboard today, and the software version is the same list wired to the booking, the booth, and the money.
OpsVue is operations software for rental, sales, and service teams — quotes, inventory, workflows, files, and payments in one connected system. Start a free trial →