A multi-day event needs a daily handoff, not a fresh start
Close each exhibition day with a review of incomplete contacts, promised actions, staff handoffs, and prize records. Treat daily closeout as an operating routine so the next shift can continue the same event with shared context.
When the doors close, the work does not disappear. A visitor may return tomorrow, a colleague may have promised a document, and a prize may still be waiting for collection. If every morning starts from memory, those commitments become difficult to distinguish from new conversations. A daily closeout turns the current state into a short handoff the next team can use.
Keep the same event context across the exhibition where that matches your planned operating period. A daily review does not mean creating a new event or changing the event to its final closed state each evening. Decide the overall operating dates before the show and use a separate team checklist for the nightly review. That avoids confusing the end of a staff shift with the end of the entire visitor journey.
Choose who closes and who accepts the next morning
Name one person to coordinate the evening review and another to receive it before opening. They may be the same person, but the responsibilities should still be explicit. The closeout coordinator does not have to personally correct every record. They ensure that unresolved items have an owner, the next shift knows what is open, and changes to the booth flow have been communicated.
Schedule this review before everyone begins dismantling displays or leaving for transport. Agree on a backup when the coordinator is occupied with a late visitor. A handoff that depends on catching one colleague in the hotel lobby is fragile. The next morning's recipient should have enough time to read the record and ask questions before the first visitors arrive.
Review incomplete records while the right staff are present
Start with records that cannot support the promised follow-up. Check uncertain contact details, unfinished business card processing, missing notes, and commitments without an owner. Ask the employee who spoke to the visitor to clarify the missing context. If they cannot reliably recall it, mark the uncertainty rather than filling the gap with a plausible story. A known unknown is easier to repair than an invented fact.
Do not spend the whole review polishing low-priority notes while an agreed meeting or document remains unassigned. Separate items that can be fixed now from items that need the visitor or a specialist to answer. Give the second group a named owner and a next action. The record should explain what remains open, not merely indicate that the team will look at it tomorrow.
Prepare for visitors returning on a later day
A returning visitor may come with another colleague or ask for a different conversation. Find the existing person or company context before starting another introduction. Keep separate people as separate contacts and add the new conversation to the relevant record. A shared company name helps staff locate the context, but it does not prove that two entries represent the same individual.
Record an expected return as a commitment only when the visitor has agreed on it. A fictional note could read: [Visitor] plans to return with a technical colleague on [day] around [agreed time]. Wants to discuss [question]. [Owner] will meet them at [place]. If the time is only a preference, say that it remains to confirm. The morning team can then prepare the right host without assuming every return is a booked meeting.
Reconcile prize results and actual handoffs
Count the physical stock and compare it with the result and fulfillment records. Separate a recorded win from a completed handoff. Identify prizes waiting for collection, cancelled results, and questions about a prior delivery. A box that looks partly empty does not explain which visitors have received their prizes. The next shift needs that distinction before it can handle a returning winner.
| Closeout item | What the next shift needs |
|---|---|
| Physical stock | Where the remaining prizes are and what was counted. |
| Uncollected results | Which record is waiting, the agreed collection conditions, and the owner. |
| Delivery exception | What happened and which record needs checking before another handoff. |
| Configuration question | Who will review it and whether any change is appropriate for the current stage. |
Apply the event's agreed rules consistently. Do not quietly promise a replacement prize because a different staff member is on duty.
Treat CSV exports as snapshots
A full event export on the second evening includes records already present in the first evening's export. Appending both files to one spreadsheet can therefore double-count the same contacts. The simplest approach is to replace the working snapshot with the latest export. If you need to compare files, use contact details and capture time carefully, checking uncertain matches manually. Keep earlier files only where your team's retention and review process requires them.
BoothCatch exports the entire event regardless of the lead screen's filters. If you need a day-specific working view, select it in your spreadsheet using the available record information after export. Label the file with the export time and explain whether a report is daily or cumulative. Those labels prevent a colleague from mistaking an older file for the latest picture of the event.
Separate work due tonight from work due tomorrow
Some promises are time-sensitive. A visitor expecting a document that evening should not be pushed into tomorrow's queue simply because the exhibition lasts several days. Review the actual agreed timing. Assign delivery to a person who can complete it, and record the outcome. If the promise cannot be met, the owner should communicate a realistic replacement rather than allowing the original deadline to pass silently.
Other tasks may reasonably wait until the next shift: a specialist discussion, a return visit, or an answer needing information that is not yet available. Preserve the question and the reason it remains open. This distinction keeps the nightly review focused and gives the morning team a usable list, instead of a large set of equally urgent notes.
A daily handoff format you can copy
Use this format in your team's shared operating note: Date and review time: [value]. Open visitor commitments: [person, question, owner, due time]. Record corrections: [item and owner]. Prize exceptions: [record and next check]. Tomorrow's appointments: [accepted time and host]. Booth changes: [what will change and who will explain it]. Decisions still required: [question and decision owner]. Keep personal details in the appropriate restricted record rather than copying them into broad announcements.
The handoff should link tasks to their existing records through your team's normal working process. Do not turn it into a second unmaintained contact database. A short summary of changes and open work is enough when the next staff can find the full lead context. Ask the receiving person to confirm which items they have accepted.
Run a morning check before the first visitor
Check the visitor entry route, staff access, equipment, and the current appointment and prize context. Test the booth instructions in the new day's lighting and layout. Confirm that the right host is present for the first accepted meeting. Read the previous evening's unresolved items before welcoming people who may expect a promised answer or collection.
A quick check is more useful when it targets changes. If a table moved, test QR visibility. If a colleague changed, review their inherited tasks. If the team changed its demonstration sequence, explain that change before staff begin. Keep the stable process familiar and focus the morning discussion on what the next shift must do differently.
End the final day with one consolidated picture
The last evening adds a final event handoff to the daily routine. Confirm which promises are complete, which remain with sales, and who owns the next contact. Reconcile the final prize records and the latest CSV snapshot. A final report should explain the cumulative event result without summing overlapping daily snapshots. Keep the open tasks visible after the booth team has dispersed.
- Incomplete contacts and notes have been reviewed.
- Accepted return visits and meetings have hosts.
- Uncollected prizes and delivery exceptions are clear.
- CSV files are labeled as snapshots, not blindly appended.
- Today's promises are completed or explicitly reassigned.
- The next shift has accepted the remaining work.
Frequently asked questions
Should we create a new event for each exhibition day?
Use the planned event structure and operating dates. When the show is one continuing event, keep its context together and use a daily team closeout routine rather than treating each shift as a new event.
Why do totals grow when we combine daily exports?
Later full-event exports contain earlier records. Appending those snapshots can count the same contact repeatedly. Use the latest snapshot, or carefully compare contact details and capture times while reviewing uncertain matches.
What is the priority during a short evening review?
Start with promised actions, missing contact details needed for those actions, returning visitors, and prize exceptions. Assign the remaining corrections instead of leaving them as unnamed work for tomorrow.
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.