Write for the person who follows up
A useful trade show note tells the next owner what the visitor needs, what was actually agreed, and who will act next. Record that context beside the contact while the conversation is still fresh.
A business card tells you how to reach someone. It rarely tells you why they stopped, what they asked, or what they expect after the event. A consultation note fills that gap. The best test is simple: could a colleague who missed the conversation send a relevant first message without asking you to explain it again? If the answer is no, another adjective such as interested or promising will not fix the record.
Keep the note short enough to write before the next visitor arrives, but specific enough to preserve the agreement. Separate the visitor's own statements from your interpretation. A clearly recorded request for a comparison sheet is more useful than an unsupported guess about buying intent. Notes should help the recipient recognize the conversation, not make the seller sound more certain than the conversation allowed.
Use five parts, with an explicit unknown where needed
Start with the current problem, the relevant context, the requested information, the next action, and the person responsible. A date belongs to an agreed commitment, not to a deadline you silently invented. If the visitor has not named a buying timetable, record timing unknown. If another colleague handles procurement, keep that distinction rather than assuming the person holding the business card owns the decision.
| Note component | What to record |
|---|---|
| Problem | The task or difficulty the visitor described in their own words. |
| Context | Their current process, relevant team, or condition affecting the request. |
| Request | The specific resource, answer, demonstration, or introduction they wanted. |
| Next action | The agreed deliverable, channel, and date, or an explicit item still to confirm. |
| Owner | One named colleague responsible for completing the next step. |
These parts can live in one compact note. They do not require five extra questions on the visitor form. Collect what the conversation naturally provides and flag the remaining uncertainty for the next contact.
Ask one clarifying question before the visitor leaves
A visitor may say send me more information while meaning something quite specific. Ask which question the information should help them answer. A product overview, a technical compatibility document, and a pricing discussion support different decisions. Confirm whether they want the material themselves or need to share it with another person. This small clarification makes the handoff more useful without turning the conversation into a long qualification interview.
Read back the next action in ordinary language: I will ask our technical colleague to send the integration overview tomorrow; is that the right starting point? If tomorrow is your team's proposal rather than the visitor's request, make that clear. Offer a different timing if needed. The purpose is to check the agreement, not to pressure the visitor into accepting a meeting they did not ask for.
Example: turn a vague note into a workable handoff
The following is a fictional writing example. An equipment supplier visits a booth and asks whether the product can fit an existing approval process. The first note says good lead, wants details. That note leaves the next owner guessing about both the problem and the requested material. A better version preserves the specific question while leaving unresolved points open.
| Weak note | Useful replacement |
|---|---|
| Very interested | Asked whether two reviewers can check the same request before approval; current process is handled in a spreadsheet. |
| Send introduction | Requested an overview of the review workflow, not a general product brochure. |
| Budget probably available | Budget and purchase timing were not discussed. |
| Contact next week | Owner: [name]. Send the agreed overview by [date], then ask whether a technical conversation would help. |
Notice that the replacement does not claim an opportunity exists. It gives the next person an honest starting point and a concrete obligation. That is enough to make the follow-up relevant.
A note format you can copy
Use the following labels as prompts, not as a requirement to fill every line with confident text. Problem: [the visitor's wording]. Current approach: [what they currently do]. Requested next step: [resource or conversation]. Timing: [agreed date or unknown]. Owner: [name]. Open question: [what still needs clarification]. Remove lines that do not apply. A shorter accurate record is better than a complete-looking record built from assumptions.
For a brief encounter, one sentence can work: Asked for the maintenance checklist for a two-site rollout; [owner] will send it by [date]; implementation timing remains unknown. For a longer consultation, add a second paragraph with technical questions and who raised them. Keep the actual agreement near the beginning so the owner does not have to search through an account of everything the booth staff said.
Preserve the speaker and the source of each statement
When two colleagues visit together, identify who asked which question. The operations contact may describe the current workflow while a technical colleague asks about compatibility. Combining both into a single anonymous interested company note loses useful detail. Keep each person's contact record and refer to the shared conversation in their notes. Do not assign a senior title or decision role unless the visitor actually confirmed it.
Distinguish facts, interpretation, and next steps with plain wording. Visitor said the current process takes several handoffs is a fact about the conversation. May need help with coordination is your interpretation. Ask which handoff creates the most delay is a next question. That separation protects the quality of later messages and helps colleagues avoid treating a tentative observation as a confirmed requirement.
Choose a moment to record, even during a rush
Agree on a note-taking moment before the event. One useful choice is immediately after confirming the next step and before welcoming another visitor. If the booth is busy, save a short note with the request and owner first. Add secondary context during the next quiet interval. Leaving every note until the hotel or train ride home makes similar conversations harder to distinguish.
Use a consistent fallback when a handoff interrupts the conversation. Tell the next staff member what remains unresolved and record that fact. A note saying visitor asked about [topic], introduction to [colleague] pending is useful because it identifies unfinished work. Staff should be able to find those records again. A private notebook full of unnamed fragments does not serve the same purpose as context attached to the right lead.
Put the context beside the contact in BoothCatch
After QR registration, business card capture, or staff entry, use the lead's short note, owner, next action, and follow-up status to keep the conversation connected. Put the factual summary in the note and the promised task in the next action. Assign the colleague who will actually deliver it. Use the interest level as a quick orientation, supported by the note rather than as a substitute for it.
When checking records before handoff, search for the person or company and read the contact details together with the context. If you export the event to CSV, review the relevant rows in your team's working process. The export includes the whole event, regardless of the screen filters. Select the records you need after export and keep the original event context attached when moving them into another system.
Review notes by usefulness, not by volume
At closeout, sample records from short visits, longer demos, and staff handoffs. Check whether another person can identify the request and act on it. Look for missing owners, vague promises, and inconsistent language. A note can contain many words and still fail this test. Fix the records with a real commitment before polishing notes from conversations that had no agreed next step.
- Can a colleague identify the visitor's question without asking the booth staff?
- Are the visitor's statements distinguishable from our interpretation?
- Is the requested resource or meeting clear?
- Does one person own the next action?
- Is timing agreed, proposed, or explicitly unknown?
- Are unanswered questions preserved rather than guessed?
Make the first follow-up reflect the note
A good note earns its place when it changes the first contact. Open with the question the visitor asked, deliver the promised item, and propose one relevant next step. If the note records only a request for a document, send that document before asking for a large meeting. If the visitor requested a technical discussion, bring the right colleague and use the open questions as the agenda.
After acting, update the next action and follow-up status so another team member does not repeat the same message. Keep a short record of what was delivered and what remains unresolved. This closes the loop between the booth conversation and sales work. For the next event, adjust the note format around the details your colleagues actually used, rather than adding fields simply because a longer form looks more thorough.
Frequently asked questions
How long should a trade show consultation note be?
Usually a few specific sentences are enough. Cover the visitor's problem, requested next step, owner, and timing. Add detail when it affects the promised action, rather than trying to transcribe the whole conversation.
Should we record a lead score if the budget is unknown?
You can record an interest level based on what happened, but do not invent budget or timing. Keep the supporting observation and the unknowns visible so the next owner knows what to clarify.
What if the note was not written at the booth?
Write down what you can reliably recall, mark uncertain details, and check the next commitment with the colleague who spoke to the visitor. Avoid reconstructing a confident narrative from a business card alone.
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.