Your Team Attends Multiple Trade Shows: How to Organise Contacts by Event and Priority
A tag scheme your whole team agrees before the season, clear priority definitions, a quarterly clean-up and a simple way to see which shows actually produce booked meetings.
To organise contacts from several trade shows, agree one tag scheme before the season starts: an event tag with the year, a priority tag with written definitions, an interest tag and an owner tag. Apply it to every contact, clean it up each quarter and compare bookings by event tag, and you will know which shows earn their stand fee.
This page is about the system across a whole season, not about capturing cards at the stand. It is for teams that attend four, eight or a dozen shows a year and end up with contacts tagged "Expo", "expo 2026", "Brisbane" and "hot" by different people. If you need the basics of capture first, see our guide to business card scanning.
What does a good event-and-priority scheme look like?
A good scheme is small, predictable and written down. Anyone on the team should be able to tag a contact the same way without asking, and anyone should be able to find "all high-priority contacts from the Mackay show interested in maintenance contracts" in a few seconds.
Four tag families
- Event: one tag per show, with the year, such as evt-26-mackay-mining. The prefix keeps event tags together; the year stops this year's show merging with last year's.
- Priority: exactly three, p1, p2 and p3, defined below.
- Interest: a short, fixed list of what they want, such as int-maintenance, int-shutdowns or int-coatings. Five to eight interests is plenty.
- Owner: one per team member, such as own-kl, so every contact has someone responsible.
Naming conventions, agreed before the season
Write the conventions on one page and share it before the first show. Lower case only, hyphens not spaces, two-digit year, short place or show name. Publish the full list of event tags for the season in advance so nobody invents a new one at the stand. If a show is added mid-season, the person who books it adds the tag to the list.
Priority definitions that mean the same thing to everyone
"Hot" means different things to different people. Write definitions based on facts you can learn in a two-minute conversation:
- p1: a named need, a rough timeframe within six months, and they influence the decision.
- p2: a relevant need, but no timing or not the decision-maker.
- p3: general interest, a peer, a supplier or a student. Worth keeping, not worth chasing.
Pair each priority with an expected action, for example p1 gets a personal email and a booking link within two working days, p2 gets a personal email within a week, and p3 gets nothing unless they opt in to updates.
Notes still matter
Tags are for sorting; notes are for context. Calenix contacts hold both, so keep the note short and specific, and let the tags do the filtering. Our guide to keeping meeting notes organised by contact covers note structure in more detail.
Exports per event
Contacts can be exported with their notes and tags. To report on a single show, export your contacts and filter the event tag column in a spreadsheet, or check whether your plan lets you export a filtered list directly. Calenix is not a CRM, so if your pipeline lives elsewhere, use the same event tags there; HubSpot, Salesforce and Zapier connections are available where enabled, so check what your account supports.
Why a shared scheme matters more as the season grows
One show's contacts can be managed in anyone's head. Five shows' contacts cannot. By the third event, the team is working from a list where the same show has four spellings, half the contacts have no priority and nobody can say which event produced last month's best client.
That last question is the expensive one. Trade shows cost stand fees, travel, accommodation and days away from paying work. If you cannot connect contacts to outcomes by event, you decide next year's calendar on gut feel and whoever enjoyed which show. A consistent event tag, carried through to bookings, gives you something firmer.
Priorities protect your time after the show. Without agreed definitions, everyone's contacts look urgent and the genuinely promising ones wait in the same queue as students and suppliers. With them, the p1 list is short enough to finish in two days.
Finally, a written scheme survives staff changes. A new starter can tag correctly on day one, and a leaver's contacts can be reassigned by owner tag. For measuring the step from contact to booking, see our guide to booking funnel analytics.
What an agreed scheme gives your team
One spelling per show: a published list of event tags stops duplicates like 'Expo' and 'expo-2026'.
Priorities that mean something: written definitions make p1 a short, real list rather than everyone's favourites.
Fast filtering: event, priority, interest and owner combine to answer most questions in seconds.
Event-level reporting: contacts and bookings by event tag show which shows are worth repeating.
Cleaner exports: tags travel with contacts into spreadsheets or your CRM.
Easy onboarding: a one-page convention lets new staff tag correctly from the first show.
How to organise contacts by event and priority in 7 steps
List the season's shows — Write down every show you plan to attend this season and create its event tag in advance, using the agreed format.
Write the one-page convention — Cover the four tag families, lower case and hyphens, the two-digit year, the priority definitions and the expected action for each priority.
Fix the interest list — Agree five to eight interest tags that match what you sell. Resist adding new ones mid-season unless the team agrees.
Tag every contact on four axes — Each contact gets one event tag, one priority, at least one interest and one owner. A contact missing any of them is unfinished.
Track bookings by event — Add a custom booking question such as 'Where did we meet?' with each show as an option, or use a separately tagged booking link for each show, so bookings can be traced back.
Review each show two weeks later — Count contacts, p1s, follow-ups sent and meetings booked for that event tag, and write two lines on what to change next time.
Clean up every quarter — Merge spelling variants, fix contacts with missing tags, retire tags for shows you dropped and check owner tags for anyone who has left.
The four tag families at a glance
| Feature | Format | How many per contact | Who sets it |
|---|---|---|---|
| Event | evt-26-showname | Exactly one (first meeting) | Whoever captured the contact |
| Priority | p1, p2 or p3 | Exactly one | Whoever had the conversation |
| Interest | int-topic | One or two | Whoever had the conversation |
| Owner | own-initials | Exactly one | Agreed ownership rule; manager settles disputes |
| Status after review | Written in the note, not a tag | Updated as needed | The owner |
Best practices for event and priority tagging
Agree the scheme before the first show of the season, never during it.
Publish every event tag in advance so nobody invents spellings at the stand.
Keep priorities to three, with definitions based on facts rather than feelings.
Record the event where you first met someone; add a note if you meet them again elsewhere.
Keep interests few and stable so filters stay useful across seasons.
Review each show two weeks after it ends, while people still remember it.
Clean up quarterly, including leavers' owner tags.
Common mistakes when organising contacts across shows
Event tags without a year, so this year's contacts merge with last year's.
Letting each person invent tags, which multiplies spellings and breaks filters.
Using 'hot', 'warm' and 'cold' without definitions, so every rep's scale differs.
Putting status updates into tags instead of notes, until the tag list becomes unreadable.
Judging shows by contacts collected rather than meetings booked.
Never cleaning up, so the tag list grows every season until nobody trusts it.
Example: an industrial maintenance firm in Gladstone
Take a fictional industrial maintenance and corrosion protection firm based in Gladstone, Queensland, with four people who work shows: the managing director, two business development managers and an estimator. In the 2026 season they attend five events: a Gladstone regional industry show, a mining expo in Mackay, a Brisbane engineering expo, a resources conference in Perth and a smaller ports and logistics event in Townsville.
The convention. Before the first show, the managing director, Kerry, writes a one-page guide. Event tags: evt-26-gladstone, evt-26-mackay, evt-26-brisbane, evt-26-perth and evt-26-townsville. Priorities p1 to p3 with the definitions above. Six interest tags: int-coatings, int-shutdowns, int-structural, int-blasting, int-inspections and int-contract. Owner tags own-kc, own-dm, own-sj and own-ta. The team uses the Calenix Professionals plan with shared contacts, so everyone works from one list, and a custom booking question, "Where did we meet?", lists each show.
The season. Across five shows they collect 410 contacts. After the Townsville event, Kerry runs a review on Monday 16 November:
- Gladstone: 120 contacts, 18 p1, 9 meetings booked.
- Mackay: 95 contacts, 14 p1, 7 meetings booked.
- Brisbane: 110 contacts, 6 p1, 3 meetings booked.
- Perth: 55 contacts, 8 p1, 4 meetings booked.
- Townsville: 30 contacts, 5 p1, 3 meetings booked.
Illustrative maths. Meetings per 100 contacts: Gladstone 7.5, Mackay about 7.4, Brisbane about 2.7, Perth about 7.3 and Townsville 10. Brisbane produced the second-largest pile of contacts but the fewest meetings; most of its contacts were p3 students and other suppliers. Townsville was small but efficient. The team decides to keep Gladstone, Mackay and Townsville, take a smaller stand in Perth and reconsider Brisbane. These figures are illustrative, and the team also weighs the cost of each show, as in our guide to cost per booked appointment.
The clean-up. At the end of the quarter, the estimator merges six contacts tagged "evt-mackay" without the year into evt-26-mackay, adds missing priorities to 14 contacts and removes an interest tag nobody used. For the wider numbers to track between shows, the team uses our list of booking metrics worth tracking.
FAQ
Frequently asked questions
Trade show season
Tag once, report on every show
Start free with card scanning, contact notes, tags and export. Move to Professionals for shared contacts across your show team and team analytics. No card needed.