BoothCatch event operations guide: plan, run, close

The short answer

BoothCatch event operations guide: plan, run, close 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. Use BoothCatch's current QR, card OCR, staff entry, lead notes, giveaways, fulfillment, and CSV features in operating order.

Why this decision belongs before event day

BoothCatch event operations guide: plan, run, close 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

If BoothCatch is learned feature by feature, QR, card capture, staff entry, lead notes, draws, fulfillment, and CSV become disconnected tasks in the field. Start with the event objective and definition of a complete lead, place each intake method in the visitor path, and fix draw rules and physical inventory responsibility. Customer-authored event names, questions, and prize names remain original when the interface language changes.

A concrete field example

An administrator creates the event and form and reviews every public phrase. Entrance QR, consultation card OCR, and staff entry for exceptions feed the same lead list. After a conversation, staff save an owner and next action. Prize quantity and phase are frozen before drawing. At close, the team reviews incomplete, duplicate, and unfulfilled records before giving the CSV and ownership plan to follow-up.

Failure patterns to watch

1. The team relies on a legacy translated-content workflow and customer-authored source text differs across views.
2. Draw settings are finished but nobody assigns physical stock location and fulfillment responsibility.
3. The operating rehearsal covers only happy screens and excludes permissions, duplicates, errors, and shift changes.

How to know the work is complete

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.

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.

1. Create the event and visitor form, then review every public word before publishing.
2. Place QR, card OCR, and staff entry according to each booth zone.
3. Add a conversation note, owner, and follow-up status to each useful lead.
4. Freeze draw rules and prize quantities, then record wins and fulfillment separately.
5. After close, export CSV and review incomplete, duplicate, and ownerless records.

1. Create the event and visitor form, then review every public word before publishing.

Turn “Create the event and visitor form, then review every public word before publishing.” 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 the event and visitor form, then review every public word before publishing.
• Verify one exception and its handoff on the real device.

2. Place QR, card OCR, and staff entry according to each booth zone.

Turn “Place QR, card OCR, and staff entry according to each booth zone.” 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: Place QR, card OCR, and staff entry according to each booth zone.
• Verify one exception and its handoff on the real device.

3. Add a conversation note, owner, and follow-up status to each useful lead.

Turn “Add a conversation note, owner, and follow-up status to each useful lead.” 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: Add a conversation note, owner, and follow-up status to each useful lead.
• Verify one exception and its handoff on the real device.

4. Freeze draw rules and prize quantities, then record wins and fulfillment separately.

Turn “Freeze draw rules and prize quantities, then record wins and fulfillment separately.” 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: Freeze draw rules and prize quantities, then record wins and fulfillment separately.
• Verify one exception and its handoff on the real device.

5. After close, export CSV and review incomplete, duplicate, and ownerless records.

Turn “After close, export CSV and review incomplete, duplicate, and ownerless records.” 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: After close, export CSV and review incomplete, duplicate, and ownerless records.
• Verify one exception and its handoff on the real device.

Adapt the method to real field conditions

There is no single field operations 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.

Event-day checklist

Before the doors open, pretend one real visitor has arrived and test the full path below.

• Create the event and visitor form, then review every public word before publishing.
• Place QR, card OCR, and staff entry according to each booth zone.
• Add a conversation note, owner, and follow-up status to each useful lead.
• Freeze draw rules and prize quantities, then record wins and fulfillment separately.
• After close, export CSV and review incomplete, duplicate, and ownerless records.
• 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.

How this maps to BoothCatch today

1. Visitor QR forms, business card OCR, and staff entry
2. Per-lead field notes, ownership, and follow-up status
3. Instant and scheduled giveaways with inventory and fulfillment records
4. Event lead CSV export

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