At a glance
Treat every badge scan as context, not consent or qualification. Capture why the person stopped, what they need and the next step they welcomed; then route sales requests, learning interest, customer issues and irrelevant records differently.
A crowded stand can make a scanner look like evidence of success. In reality, it proves only that contact details changed hands. Sales still needs to know whether there was a problem worth solving, a credible next step or simply a polite conversation.
Good event lead qualification protects both sides. It gives sales enough context to respond usefully, while keeping curious visitors and existing customers out of an artificial pipeline. The badge scan starts the record. The conversation determines what it means.
Agree what a good conversation looks like
Before the event, define the audience and the problems your team can credibly help with. Give staff a short description of a suitable opportunity, including cases where your offer is a poor fit.
Then agree what information is worth capturing. Start with the person’s situation, the question they asked and the next step they actually welcomed. A forced interrogation about budget and authority can ruin a useful conversation before it develops.
GOV.UK’s guidance on in-depth interviews recommends understanding people’s circumstances and experiences through conversation. An event stand is not a research interview, but the listening principle transfers well: ask about the person’s reality before delivering your prepared explanation.
Use three questions that create context
- What brought you to this session or stand?
- How are you handling that problem at the moment?
- What would be useful from us after today?
The answers should guide the next question. Someone replacing a system next quarter needs a different conversation from someone gathering ideas for next year.
If the person describes a relevant project, ask who else is involved and what they need to decide. If they are learning, offer useful material without pretending they requested a sales call.
Record enough to make the follow-up personal
| Weak note | Useful note |
|---|---|
| Interested in platform | Comparing ways to connect event attendance with CRM records |
| Hot lead | Asked for a technical discussion next week; replacement planned this quarter |
| Send information | Requested the integration checklist and no call for now |
Keep the note short enough to write while the conversation is fresh. Separate what the person said from your interpretation. If the next step was not agreed, record that rather than inventing enthusiasm.
Use the approved collection process and make follow-up choices clear. Scanning a badge should not become a reason to disregard the person’s stated preference.
Create distinct routes after the event
Route explicit sales requests to a named owner. Send requested educational material promptly. Pass existing customer issues to the right service team. Exclude irrelevant or duplicate records from the opportunity count.
For digital events, apply the same logic to questions, resource requests and meeting bookings. Attendance duration alone does not explain intent. Our webinar follow-up guide shows how to respond to different kinds of engagement.
Measure quality after the stand comes down
Track agreed next steps, completed conversations, qualified opportunities and eventual commercial outcomes. Keep the original event interaction visible so later reporting does not lose the context.
Review the result against the event’s actual purpose. A customer education session may create value without new opportunities. A prospecting event should not be celebrated solely for registrations. Use the event ROI guide to include the full cost and a sensible follow-up period.
Afterwards, read a sample of the notes with the people who worked the stand. Which questions produced useful answers? Which fields were consistently empty? What did visitors ask that the team could not answer?
The best qualification process makes the conversation better while it is happening. If it only makes the spreadsheet longer afterwards, redesign it.
