Sequencing member outreach for an event
Your member list is ready, and you need to decide who hears about the event first, second and last.
The short answer
Send invitations in waves, not all at once: people who shape the event first, people most likely to attend next, then the wider list. Each wave has its own message, owner, date and a rule for who is removed before the next one goes.
The order matters because early replies change what you say later, and a member who has already registered or declined should never receive the next reminder.
Decide the waves from your own member data
Start with the segments you can already name from your records: committee and past speakers, members who attended before, members in the target profile who have not, and lapsed or associate members. Use labels, not names, at planning stage.
Do not copy another association's wave sizes. Your own last-event registration list tells you which segments responded and how early.
A four-wave sequence and what each wave does
| Wave | Who | Message focus | Owner | Remove before next wave |
|---|---|---|---|---|
| 1. Shapers | Committee, past speakers, chapter heads | Ask for feedback on programme and request they invite colleagues | Event owner | Anyone who has replied or registered |
| 2. Likely attendees | Members who attended recently | Date, theme, registration link, what is new this year | Secretariat | Registered, declined, opted out |
| 3. Target profile | Members who fit the audience but did not attend before | Why this edition is relevant to their role; one clear action | Secretariat with a committee name on the message | Registered, declined, opted out |
| 4. Wider list and partners | Remaining members, partner bodies | Shorter note, ask partners to forward under their own approval | Event owner | Anyone ineligible or already contacted twice |
Spacing and wording rules
- Set each send as a dated decision with a named sender, using an invitation sequence planner or a spreadsheet.
- Write the gap between waves from your registration deadline backwards, then check it against member calendars and public holidays.
- Change the message in each wave. A repeated identical email is a reminder, not a new reason to attend.
- Hold a short review point after wave 2 to decide whether wave 3 wording needs to change.
Suppression comes before sending
Before every send, filter out registered members, declines, opt-outs and anyone flagged as ineligible, such as a speaker already confirmed. Ask your data owner how opt-outs are recorded and who checks the list on send day.
The sending decision stays with your organisation. A tool can hold the sheet, but a person approves each wave.
Worked example · Fictional example
A professional association's wave plan
Fictional organisation and figures, for illustration only.
Persatuan Fiktif Jurutera Logistik has a list of about 900 members for a one-day forum. The secretariat labels four segments and sets wave 1 to the committee, asking each to bring one non-member colleague.
After wave 1 the committee suggests moving the registration deadline by one week because of a school holiday. The secretariat updates the dates for waves 2 to 4 and records the change in the sequence sheet, so every later send uses the new deadline.
Use this yourself
Member outreach sequence sheet
Copy one block per wave and complete it before anything is sent.
- Wave number and segment label:
- Who is in it (source list and date pulled):
- Message focus and the one action requested:
- Sender name and approver:
- Send date and time:
- Suppress: registered / declined / opted out / ineligible, checked by:
- Review point and what would change the next wave:
- Stop rule for this segment (see outreach stop conditions):
Handle it in-house, or bring in help?
Your team can usually handle this when
- You have one clean member list and one person who owns sending.
- The same segments were used at the last event and you have its registration record.
- The committee agrees who approves wording.
Outside planning help earns its fee when
- Lists sit with several chapters or partner bodies and no one holds the combined suppression list.
- Invitations depend on committee members who each send in their own way.
- The timeline is tight and every wave needs a named owner and a dated decision.
Need someone to run the sequence decisions?
A conference project lead can hold the wave plan, chase the named owners for each send, keep the suppression checks on the calendar and bring the review point to your committee. Message wording and final approval stay with your organisation.
Questions organisers ask
How many waves should an association use?
There is no standard number. Use as many as you have distinct segments with a different reason to attend, and no more. Three or four is common to describe, but your own segments decide.
Should committee members be contacted before the general list?
Usually yes, because their replies shape the message and many members respond to a colleague they know. Record what you ask of them so they are not left guessing.
Who owns the suppression list?
Name one person for each send. Ask whether registrations, declines and opt-outs sit in one place or several, and check them again on send day.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.