The short answer
Event-day rehearsal checklist: a 30-minute dry run is not mainly about adding another tool. It is about deciding who records what, at which moment, and how that context reaches the next owner. Run one complete journey on real devices, from the first visitor interaction to giveaway and CSV review.
Run one complete journey on real devices, from the first visitor interaction to giveaway and CSV review.
Why this decision belongs before event day
Event-day rehearsal checklist: a 30-minute dry run is difficult to improvise once the aisle fills up. One extra field, an unclear owner, or an untested result screen can change wait time and record quality. Put the criteria below into a rehearsal and run one visitor journey from beginning to end on the devices the team will actually use.
What to diagnose first
The purpose of rehearsal is to find handoff breaks between people, devices, network paths, and printed material—not to glance at each screen once. A happy-path test does not reveal the correction and retry work that consumes time in the field. Alongside success, deliberately reproduce a bad email, blurred card, duplicate participant, permission-limited action, and delayed connection.
A concrete field example
Divide 30 minutes into QR submission, card capture and correction, staff entry, draw and fulfillment, and CSV closeout. Let the same visitor enter through two routes and use a restricted staff account for part of the run. At the end of each segment, inspect both the visible result and what the next owner received; a saved screen is not enough if context disappeared in the handoff.
Failure patterns to watch
- One administrator clicks quickly on a familiar device and declares the rehearsal complete.
- A problem is fixed on the spot without recording its reproduction conditions, owner, or retest.
- Testing stops at a winner screen and skips physical fulfillment, inventory change, and no-show handling.
How to know the work is complete
Every scenario has a starting condition, expected result, observed result, owner, and repair deadline. After a change, the same scenario is rerun on the intended device. The rehearsal passes when no critical item remains at “it should work.”
Put the decision on one page
Do not compare feature names alone. Write down how each choice changes staff and visitor behavior in the booth.
| Decision | Field test |
|---|---|
| 01 | Time one complete visitor submission through the QR form. |
| 02 | Capture a reflective card and a card with small print, then review both. |
| 03 | Create a staff-entered lead and edit its note and owner. |
A practical workflow
Give every step an owner and a deadline. A checklist without ownership is usually the first thing to fail during a rush.
- Time one complete visitor submission through the QR form.
- Capture a reflective card and a card with small print, then review both.
- Create a staff-entered lead and edit its note and owner.
- Run instant and scheduled result checks plus prize fulfillment.
- Export all test leads and open the CSV outside BoothCatch.
1. Time one complete visitor submission through the QR form.
Turn “Time one complete visitor submission through the QR form.” into an observable field procedure. Write its completion condition, owner, backup, and review point, then reproduce one important exception on the actual device. At close, pass unfinished work to a named person so follow-up can understand the result without oral reconstruction.
- Write the completion condition and owner for: Time one complete visitor submission through the QR form.
- Verify one exception and its handoff on the real device.
2. Capture a reflective card and a card with small print, then review both.
Turn “Capture a reflective card and a card with small print, then review both.” into an observable field procedure. Write its completion condition, owner, backup, and review point, then reproduce one important exception on the actual device. At close, pass unfinished work to a named person so follow-up can understand the result without oral reconstruction.
- Write the completion condition and owner for: Capture a reflective card and a card with small print, then review both.
- Verify one exception and its handoff on the real device.
3. Create a staff-entered lead and edit its note and owner.
Turn “Create a staff-entered lead and edit its note and owner.” into an observable field procedure. Write its completion condition, owner, backup, and review point, then reproduce one important exception on the actual device. At close, pass unfinished work to a named person so follow-up can understand the result without oral reconstruction.
- Write the completion condition and owner for: Create a staff-entered lead and edit its note and owner.
- Verify one exception and its handoff on the real device.
4. Run instant and scheduled result checks plus prize fulfillment.
Turn “Run instant and scheduled result checks plus prize fulfillment.” into an observable field procedure. Write its completion condition, owner, backup, and review point, then reproduce one important exception on the actual device. At close, pass unfinished work to a named person so follow-up can understand the result without oral reconstruction.
- Write the completion condition and owner for: Run instant and scheduled result checks plus prize fulfillment.
- Verify one exception and its handoff on the real device.
5. Export all test leads and open the CSV outside BoothCatch.
Turn “Export all test leads and open the CSV outside BoothCatch.” into an observable field procedure. Write its completion condition, owner, backup, and review point, then reproduce one important exception on the actual device. At close, pass unfinished work to a named person so follow-up can understand the result without oral reconstruction.
- Write the completion condition and owner for: Export all test leads and open the CSV outside BoothCatch.
- Verify one exception and its handoff on the real device.
Adapt the method to real field conditions
There is no single event planning setup for every event. Conversation length, booth traffic, staffing, prize handoff location, and the team responsible for first contact all change the right design. Convert the guidance below into questions your team can verify in rehearsal. Remove a field or move a role when the observed result is clearer than the original plan.
| Metric | How to read it |
|---|---|
| Rehearsal pass rate | Scenarios completed on real devices without a blocker |
| Median intake time | Whether the flow stays usable during the rush |
| Question usefulness | Captured questions that sales actually uses later |
Event-day checklist
Before the doors open, pretend one real visitor has arrived and test the full path below.
- Time one complete visitor submission through the QR form.
- Capture a reflective card and a card with small print, then review both.
- Create a staff-entered lead and edit its note and owner.
- Run instant and scheduled result checks plus prize fulfillment.
- Export all test leads and open the CSV outside BoothCatch.
- Visitor QR forms, business card OCR, and staff entry
- Per-lead field notes, ownership, and follow-up status
Measure output and quality together
Lead count alone can make a fast form look successful. If the resulting records cannot support a relevant follow-up, that speed did not create pipeline.
| Metric | How to read it |
|---|---|
| Rehearsal pass rate | Scenarios completed on real devices without a blocker |
| Median intake time | Whether the flow stays usable during the rush |
| Question usefulness | Captured questions that sales actually uses later |
How this maps to BoothCatch today
BoothCatch connects the currently available capture, giveaway, and handoff functions in one event workflow.
- Visitor QR forms, business card OCR, and staff entry
- Per-lead field notes, ownership, and follow-up status
- Instant and scheduled giveaways with inventory and fulfillment records
- Event lead CSV export
BoothCatch does not currently present automatic CRM sync, a complete offline mode, badge scanning, or a specific international compliance certification as available features. A network plan should pause intake safely and verify the same request after connectivity returns.
A 20-minute closeout review
Review delays and bad records while the event is still fresh. The goal is not to blame an individual. Find the form, signage, role, or physical path that the team can change next time.
- Records missing information needed for first contact
- Duplicates and leads without a clear owner
- The step with the longest visitor wait
- Differences between winner and physical fulfillment records
- Questions to remove or add before the next event
Frequently asked questions
When should a team start preparing for event-day rehearsal checklist: a 30-minute dry run?
Finalize the operating method no later than the day before and rehearse it on real devices. Start earlier for questions, privacy text, and internal approvals that require review.
Is one field owner enough?
Keep one final decision owner, but assign backups for capture, giveaway, fulfillment, and closeout so breaks and rush periods do not stop the workflow.
What can we test in BoothCatch?
After creating an event draft, purchase an Event Pass to operate QR, card, staff entry, complete lead management, and giveaway flows. Contact BoothCatch to confirm whether the scope matches your event.
Start the operating flow for your next event
Create an event and purchase an Event Pass to operate QR, card, lead management, and giveaway flows.