Dynamic vs. Manual Attendee Lists: Event Attendee Management Without Spreadsheets

Most event teams manage attendee data the same way: export a spreadsheet, filter it in Excel, email the filtered list, and repeat every time someone new registers or cancels. That approach works for a one-time task, but event attendee management isn't a one-time task — registrations, cancellations, and ticket upgrades keep coming in until the event starts. Every export is out of date the moment you save it.

Contact Lists in Sunfish Events solve this by letting you define a segment once and have it stay current on its own, or build a one-off named list by hand when that's genuinely what you need. Here's how the mechanics work, when to use each type, and a few concrete examples of how organizers put them to work.

The two kinds of lists: people already in, and people not yet in

Before getting into dynamic versus manual, it helps to understand the basic split in Sunfish Events. A Contact List is either an Attendee Update list — people who have already registered for the event — or an Invite and Promote list — people who are not in the event yet and who you want to invite or market to.

This distinction matters because the two list types serve different purposes. Attendee Update lists are for segmenting people who are already registered, so you can email check-in instructions to VIP ticket holders, or flag who still owes a balance. Invite and Promote lists are for reaching people outside the event, which is a different problem with different reuse patterns — we cover that side in detail in reusable invite lists for every event. This article focuses on Attendee Update lists: segmenting the people who have already said yes.

How to manage event attendee lists without spreadsheets

Attendee Update lists can be dynamic, manual, or both. Understanding the difference is the key to getting out of the export-filter-email cycle for good.

A dynamic list is built on a rule, not a fixed set of names. You define the parameters — say, "ticket type = VIP" and "status = not checked in" — and Sunfish Events keeps the membership current automatically. As people register, cancel, upgrade, or check in, they move into or out of the list on their own. Nobody has to remember to update it, because there's nothing to update. The list is a live query against your registration data, not a snapshot of it.

A manual list is the opposite: you add specific people by name, and the list only changes when you change it. Nothing about it responds to registration activity.

A hybrid list combines both — a dynamic rule that keeps a core segment current, plus specific individuals added on top who don't necessarily meet the rule. We'll walk through exactly what that looks like a bit further down.

The dimensions you can build a dynamic rule from are:

Any of these can stand alone or combine — a dynamic list can be "ticket type = VIP AND status = not checked in" just as easily as it can be a single condition.

Custom question answers are worth a closer look, because they're the most flexible dimension on the list — you're not limited to whatever questions your ticket types or groups already imply. If your registration form asks "which track are you attending?", a dynamic list filtered to a specific track answer gives session organizers a self-maintaining roster for their room, updated automatically as people change their track selection or register late. The same pattern works for a "how did you hear about us?" question (segment by referral source for a post-event report), a "job title" free-text-turned-dropdown question (segment by seniority for a targeted follow-up), or an opt-in question like "interested in a demo?" (segment for sales follow-up). Any question you build into your form becomes a segmentation dimension the moment responses start coming in — you're not restricted to the built-in fields.

Why "set it once" beats re-exporting every time

The practical case for dynamic lists comes down to what happens between now and event day. Registration data changes constantly — someone cancels, someone upgrades their ticket, someone checks in at the door. A spreadsheet export captures none of that after the moment you make it.

Take the example in the mechanics section above: a dynamic list of everyone who bought the VIP ticket and hasn't checked in yet. On a manual spreadsheet, that list is accurate for about five minutes. The moment your check-in staff scans a badge or a new VIP ticket sells, the export is wrong, and someone has to remember to pull a new one. As a dynamic list in Sunfish Events, that same segment updates itself continuously — pull it up the morning of the event and it reflects exactly who's still expected, with zero manual maintenance.

This matters most for anything you'll reference more than once: a pre-event reminder email, a day-of check-in report, a post-event follow-up to no-shows. Any list you'd otherwise need to re-export is a strong candidate for a dynamic rule instead.

Five ways organizers actually use this

Dietary restrictions from a custom question. If your registration form asks about dietary needs, build a dynamic list filtered to specific answers — "vegetarian," "gluten-free," "no restriction." Hand that segmented list to catering instead of a raw export of every response, and it stays accurate as new people register right up until the day of the event.

Company attendees by email domain. When a sponsor or client company sends a group to your event, a dynamic list filtered by email domain (e.g., everyone registering with an @acmecorp.com address) automatically catches every employee who signs up, including ones who register at the last minute. This is a common pattern for associations tracking member-company delegations or B2B events courting a key account — for more on segmenting by group and member type specifically, see registration for associations in 2026.

Workshop or session attendees by add-on. If your event sells optional add-ons — a pre-conference workshop, a networking dinner, a certification exam — a dynamic list filtered by that add-on gives the workshop facilitator an always-current headcount and roster, without anyone needing to ask you for an updated list the week before.

No-shows and cancellations by status. A dynamic list filtered to "status = cancelled" or "status = registered but not checked in" gives you a live view of who to follow up with after the event, or who to flag for a post-event win-back email, without manually cross-referencing check-in logs against your registration list.

Sponsor-tier attendees by group. If your event assigns registrants to a group based on sponsorship level — platinum, gold, silver — a dynamic list filtered by group gives your sponsorship team an always-current view of who's attending from each tier. That's useful for coordinating a sponsor lounge, sending tier-specific perks, or making sure the platinum sponsor's team gets a personal welcome, without your team manually tracking which registrants belong to which sponsor as new people register under that group.

When a manual list is still the right call

Dynamic lists aren't a replacement for every use case. Some segments genuinely aren't rule-based — they're a specific set of people you know by name. A hand-picked list of VIPs the CEO wants greeted personally, a small group of press contacts, or a set of speakers who need a different day-of communication are all better as manual lists. There's no underlying registration attribute that defines "people the CEO wants to personally greet" — it's a judgment call, not a filter.

What a hybrid list actually looks like

The good news is you don't have to pick one mode and stick with it for the life of the list. A hybrid list keeps a dynamic rule as the backbone while letting you add specific people on top who don't meet that rule but should still be included.

Here's a concrete version: say you're building a list for a VIP dinner. Your dynamic rule is "ticket type = VIP." That rule alone catches everyone who paid for VIP access, and it updates itself automatically as more VIP tickets sell or as VIP registrants cancel. But the event has three other people who need to be at that same dinner even though they didn't buy a VIP ticket — a keynote speaker registered on a complimentary comp ticket, a board member who registered late under general admission, and a sponsor contact who's attending as a guest. None of those three match the dynamic rule, so instead of rewriting the rule to somehow account for three unrelated exceptions, you simply add those three people to the list manually, on top of the dynamic rule.

The result is one list that does both jobs at once: the VIP-ticket segment keeps updating itself with zero effort as ticket sales change, and the three named additions stay on the list permanently regardless of what their ticket type says. This is the practical middle ground — automation for the part of the segment that's genuinely rule-based, manual control for the handful of people who are exceptions to that rule.

Choosing the right approach for your segment

Here's a quick way to decide which mode fits a given list:

As a general default, if you can describe the segment as a sentence using "everyone who…," it's almost always a candidate for a dynamic rule. If you can only describe it as a list of names, it's manual. And if it's mostly one but has a few exceptions, that's exactly what a hybrid list is for.

What to do with a segment once you have it

Building the segment is the first step, not the last one. Once you have a dynamic list of VIP ticket holders, or non-checked-in registrants, or workshop attendees, the natural next step is using it to trigger the right communication automatically — a reminder, a thank-you, a win-back email — instead of manually emailing each segment yourself. That's covered in more depth in using registration data to automate event marketing, which walks through connecting these same segments to email campaigns.

Key takeaways and next step

Attendee Update lists in Sunfish Events can be dynamic (rule-based and self-updating), manual (hand-picked and static), or hybrid (a rule plus manually added exceptions). Dynamic lists can be built from any combination of group, ticket type, registration status, custom question answers, email domain, or add-ons, which covers most of the segments organizers actually need — VIPs who haven't checked in, a company's employees by domain, workshop attendees by add-on, sponsor-tier guests by group, or no-shows by status. Manual lists still have a place for genuinely one-off, hand-picked groups that don't map to a registration attribute, and hybrid lists let you combine both in the same list without compromise.

The underlying goal is the same either way: stop re-exporting spreadsheets every time your registration list changes, and start working from a segment that's already current. If you're managing an upcoming event and want to see how dynamic Contact Lists work with your own registration data, try Sunfish Events or book a quick demo — we're happy to walk through it with your actual attendee list.