Reading an attendee list means understanding what the rows can tell you before acting on them. Names, titles, and logos may suggest opportunity, but they do not automatically identify your buyers or prove that a person will be available for a meeting. A useful review turns the list into a smaller set of accounts with clear next steps.

Work through the list in passes. Each pass should resolve a different question, so missing information does not get buried beneath an impressive row count.
First, identify what kind of list you have
Check the event edition, collection date, and source. Is this a registered-attendee list, an exhibitor directory, a speaker program, or last year's roster? Write that description at the top of the working file. Preserve the original source so another teammate can inspect it.
An exhibitor listing establishes a company connection to the show. It does not independently verify every employee attached to that company. Keep “person confirmed” separate from “company listed,” and avoid merging historical attendees into a current list without a clear label.
Scryon's Watch accounts guidance makes the same distinction between account presence and person-level attendance. It is a useful rule even when the list comes from another provider.
Second, resolve companies before ranking people
Normalize company names and domains. Check whether similarly named rows represent the same business, a subsidiary, or an unrelated company. Apply the account structure already used by your CRM rather than inventing a new one for the event.
HubSpot's import documentation explains the use of record identifiers when matching data. Even outside HubSpot, the principle is useful: retain a stable account identifier when moving a list between research and sales tools.
Count unique accounts alongside people. Twelve contacts from one company create a different opportunity from twelve companies with one contact each. The first may support a buying-group strategy; the second may support broader prospect discovery. Neither should be hidden by a single contact total.
Third, qualify the role and business problem
Translate titles into likely responsibilities, then verify them. “Director” alone says little. A director of ecommerce and a director of facilities may work at the same retailer while owning unrelated decisions.
For a list associated with Groceryshop 2026, September 22–24 in Las Vegas, group contacts by the business problem you address: merchandising, digital commerce, operations, payments, or another relevant function. Do not assume that every retailer contact is a buyer for every retail technology product.
The organizer's Meetup description highlights meeting selection and mutual opt-in. That makes a relevant role and a credible reason to meet more useful than a generic request sent to everyone at an attractive logo.
Fourth, give each account an action
Use a short disposition table:
| Disposition | Meaning | Next action |
|---|---|---|
| Ready for owner review | Fit and person evidence are sufficient | Coordinate a meeting approach |
| Account fits, person unclear | Company is relevant | Verify the right role and attendance |
| Existing relationship | Customer or active opportunity | Route to the current owner |
| Weak fit | Limited relevance | Exclude from this campaign |
| Evidence missing | Identity or edition is uncertain | Research before outreach |
These are working categories, not universal CRM lifecycle stages. Avoid changing an account's sales stage simply because it moved through an event-list review.
Add a one-sentence rationale for priority accounts. “Matches our territory and sells through the channel we support” is reviewable. “Looks interesting” makes it difficult for another rep to continue the work.
Finally, test the list against available time
Calculate how many accounts the team can research, contact, and meet before the event. Assign owners and deadlines to that manageable set. Keep a reserve list for cancellations, and use pre-event prospecting planning to sequence the work.
Review the first handful of records together with sales. If the same identity or attendance error recurs, fix the process before scaling. Keep evidence dates visible so late roster changes can be checked without repeating the entire exercise.
An attendee list becomes valuable when it reduces uncertainty about who to approach and why. Try Scryon free and build the account context that makes the next action clear.