Work breakdown and scheduling
Planning an event invitation release schedule
The event date is set, and now the order and timing of invitations will decide whether the right people can plan to come.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Release invitations in waves, starting with the people whose attendance shapes the event: speakers, chairs and key stakeholders. Then invite your core audience, then wider lists, with a reminder after each wave.
Each wave has prerequisites that must be ready first: confirmed date and venue, a programme outline, registration open, and approved wording. Back-plan from the date you want registrations in.
Who goes in which wave
| Wave | Who | Why first or later |
|---|---|---|
| Hold-the-date | Speakers, chairs, committee, key partners | Their availability shapes the programme and they need the longest notice. |
| Core invitation | Members, past attendees, named delegates | The audience the event is for; they need a clear programme and registration route. |
| Wider invitation | Partner organisations, wider mailing lists, public channels | Sent once the programme is firm and you know how many places remain. |
| Reminders | Anyone who has not responded | Timed to a real deadline, such as an early registration close or a hotel block release. |
What must be ready before each wave
- Date and venue confirmed in writing, or clearly worded as provisional.
- Programme outline at the level of detail the audience needs to decide.
- Registration route tested end to end, with the person who answers questions named.
- Wording approved at the gate described in approval milestones.
- A plan for what happens when places run out, such as a waiting list.
Set the spacing between waves and reminders
Leave enough time between waves for responses to arrive and for you to learn something, for example how many places the first wave filled. Without that gap, the second wave goes out blind.
Tie each reminder to a reason: a deadline, a new speaker, a programme release. Reminders with nothing new to say are the ones people mute.
Lists and consent
Whether you may use a given list for event invitations depends on how the contacts were collected and what they were told. Ask your data protection contact, or an adviser, to confirm which lists are usable and what each message must include.
Record the answer in the schedule so the sender is not left to decide on the day.
Pitfalls
- Inviting delegates before the speaker line-up is firm, then changing it.
- Opening registration before the cancellation and substitution terms are agreed.
- A single sender with no deputy when the replies arrive.
- Not counting replies, so the next wave is sized by guess.
Worked example · Fictional example
A seminar invitation plan
Fictional organisation and figures. Weeks and numbers are hypothetical and show only the structure.
A fictional trade association plans a half-day seminar for about 180 people. The secretariat sets the registration target date and works backwards, holding a decision point after the first wave to size the next.
| Release | Timing (weeks before event) | Ready first | Check after |
|---|---|---|---|
| Hold-the-date to speakers and chairs | 10 | Date approved, venue provisional | All confirmed or declined within 1 week |
| Core invitation to members | 8 | Programme outline, registration tested | Count registrations after 2 weeks |
| Reminder with new speaker named | 6 | Speaker confirmed in writing | Count again |
| Wider invitation to partner organisations | 5 | Places remaining known | Decide whether to open a waiting list |
| Final reminder before early registration closes | 3 | Closing date stated in first message | Prepare attendee information |
Use this yourself
Invitation release schedule
Copy this into a sheet. Fill in the wave, list, send date and owner. Do not mark a row ready until every prerequisite is ticked.
- Tick prerequisites before the send date, not on it.
- Add a check after each wave: replies, registrations, bounced addresses.
- Name a deputy sender for each row.
| Wave | List and size | Send date | Message and approver | Prerequisites ready | Owner and deputy | Check after send |
|---|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- One list, one sender and a registration route your team already uses.
- The programme is firm before the first invitation goes out.
- Someone can monitor replies daily.
Outside planning help earns its fee when
- Several lists belong to different departments or partner bodies, each with its own rules and owner.
- Invitations depend on decisions still open, such as venue, speakers or fees.
- Replies need a person to manage substitutions, special requests and a waiting list.
Want the invitation plan built into your event timeline?
An Event Blueprint can set the invitation waves alongside the milestones they depend on, with owners, approvals and the checks after each release. A project lead can also coordinate lists, approvers and registration queries so the schedule keeps its dates.
Questions organisers ask
How many invitation waves should I plan?
Two or three is usual: a hold-the-date message to speakers and key people, a core invitation, and a wider one if places remain. Add reminders tied to real deadlines.
Should I send a save-the-date before the programme is ready?
Yes, if the date and place are confirmed, and say clearly what is still to come. Use the programme release as the reason for the next message.
When can I use my member list for invitations?
That depends on how the contacts were collected and what they were told. Ask your data protection contact or adviser to confirm before the first send, and record the answer.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.