A day-of-event execution playbook helps sales teams make good decisions when the schedule changes. Meetings move, buyers arrive late, and an interesting conversation can consume the time reserved for the next account. The plan needs a way to absorb those changes while keeping the team's commercial priorities clear.
Use this playbook after building your rep event itinerary. The itinerary sets the intended route. This guide covers the decisions a rep and team lead make as the day unfolds. The times below are illustrative; adapt them to the organizer's hours, confirmed appointments, and local time zone.
07:30–08:30: Confirm the conditions for the day
Before the first conversation, check badge pickup, venue access, meeting locations, and messages from confirmed contacts. Download the day's essential details so a weak connection does not interrupt the plan. Verify the first meeting's location with enough time to reach it.
Registration time and meeting access can differ. At Yotta 2026, September 28–30 in Las Vegas, the official agenda lists Monday badge pickup from 7:30 a.m. and hosted buyer meetings from 8:30 a.m., with pre-registration required. A badge alone does not establish eligibility for every activity. Check the latest organizer information before relying on a slot.
Hold a short team check-in. Confirm each rep's priority accounts, who can resolve ownership questions, and how to report changes. Pick a fallback meeting point and a contact method everyone can use.
08:30–10:30: Protect confirmed meetings
Review the next account brief before entering the conversation. Know the verified role, one relevant business hypothesis, and the outcome you hope to achieve. Start by confirming how much time the person has and what would make the discussion useful for them.
Leave space between meetings for notes and movement. If a discussion is valuable but time is running out, agree on a follow-up rather than letting the next appointment fail silently. Send a prompt update if you will be late.
For an organizer-managed meeting program, follow its schedule and instructions. Groceryshop 2026, September 22–24 in Las Vegas, uses mutual opt-in and pre-scheduled meetings. An invitation or pending request is not a confirmed appointment. Check the actual meeting record before changing your route.
10:30–12:00: Work the reserve list when time opens
Keep a small set of relevant accounts near the confirmed route. When a slot becomes free, choose the next account by fit, location, and verified availability. Avoid turning a cancellation into an unplanned trip across the venue for someone who may not be there.
Use this decision table during the day:
| Situation | Immediate action | What to record |
|---|---|---|
| Contact is late | Check messages and follow the meeting program's guidance | Updated meeting status |
| Contact cancels | Offer a suitable next step, then review nearby reserve accounts | Cancellation and owner |
| Conversation runs long | Agree whether to continue or schedule a follow-up | The explicit commitment |
| Relevant person is absent | Verify the right contact and a useful way to reconnect | Attendance uncertainty |
| Account already has an owner | Coordinate before starting a competing approach | Owner and handoff |
The reserve list should give the rep options without creating fictional appointments. Scryon's platform can support the account research behind those options; confirm booth details and person availability through current event information and direct contact.
12:00–13:00: Reassess the afternoon
Take a proper break and compare progress with the objective. Look at which conversations were useful, which assumptions proved wrong, and whether the remaining plan is achievable. A count of badge scans will not answer those questions.
Reassign work when a rep is overloaded or a priority account needs another specialist. Keep changes in one shared plan so two people do not independently promise the same follow-up. Preserve fixed appointments and communicate any change to the affected contact.
Choose one adjustment that improves the afternoon: narrow the reserve list, involve a technical colleague, or protect time for an important follow-up. Avoid rebuilding the entire day because one conversation suggested a new direction.
13:00–16:30: Capture useful outcomes
During each conversation, distinguish what the buyer said from your interpretation. A stated operational problem is evidence. A guess about budget or urgency remains a hypothesis until confirmed. Ask questions that help you understand the decision and whether another stakeholder should be involved.
Afterward, capture a short note with five fields:
- Account and person, including the verified role.
- Business problem or objective discussed.
- Relevant qualification information and remaining unknowns.
- Next step actually agreed, if any.
- Owner and date for that next step.
Record “no agreed next step” when appropriate. That is more useful than manufacturing an opportunity from a pleasant conversation. Save the details promptly so the next meeting does not overwrite them in memory.
16:30–17:00: Close commitments before leaving
Review the day's promised actions and assign them in the CRM or working system your team owns. Check that meeting status, contact identity, and account ownership are correct. A Slack acknowledgment or a handwritten note should not be the only place a customer commitment exists.
Separate held meetings, no-shows, new introductions, and research-only observations. Use the post-event CRM hygiene guide to make the handoff usable. If a follow-up needs another person's input, name that dependency and its owner before the team disperses.
Finish with three observations: what worked, what changed, and what tomorrow needs. Measure the day by qualified conversations and clear commitments, with enough context to judge their value. That gives the team a basis for improving its next event instead of repeating the same scheduling mistakes.