Managing participant expectations before an event
Delegates arrive with an idea of the day that you never gave them, and the gap shows up in feedback.
The short answer
Expectations are set by what delegates read before they arrive: the invitation, the programme page, the confirmation email and the joining instructions. Write down the five or six things people most often assume, then state each plainly in those messages.
Say what the event is for, who it suits, what is included, what is not and what you ask of attendees. Plain statements early prevent disappointment later.
Where expectations come from
Delegates form a picture from the title, the speaker list, last year's event and what colleagues tell them. Each of these can promise more than the programme delivers.
Your job is not to lower interest. It is to make the picture match the day.
The assumptions to check
| Assumption delegates may hold | What to state instead | Where to say it |
|---|---|---|
| Every session suits every role | Who each session is aimed at, and the level of knowledge assumed. | Programme page, session descriptions. |
| Slides and recordings will be shared | What will be shared, when and with whom, as agreed with speakers. | Confirmation email, closing session. |
| Networking will be introduced for them | What structured connection is offered and what is left open. | Programme, joining instructions. |
| Meals suit every dietary need | What the registration form asks and what the caterer can confirm in writing. | Registration form, confirmation email. |
| Certificates or points will be issued | Only what the awarding body has confirmed. Otherwise write that it is being confirmed. | Programme page, with the confirmed date. |
| Start and finish times are fixed | Which times are firm and which may shift, and how changes are announced. | Joining instructions, on-the-day signage. |
Sequence the messages
- Invitation: purpose, audience, format and date. Keep claims modest.
- Programme release: session aims, who each suits, what is optional.
- Confirmation: what is included, what is not, how to ask for support.
- Week-before message: practical details, how to arrive, what to bring, what to expect on the day.
- On the day: a short welcome that restates the plan and how to raise a problem.
When the plan changes
Changes are easier to accept when people already know which parts were firm. Tell delegates what changed, why and what it means for them, in one short message.
Keep a record of what was promised in the decision log so replacements match the original commitments.
Measuring the gap
Ask delegates in the feedback questionnaire whether the event matched what they expected and, if not, what differed. Treat answers as a list of messages to rewrite, not as a score to report.
Use the objective-to-measure planner to link each expectation message to an observable result.
Worked example · Fictional example
A seminar organiser rewrites its confirmation email
Fictional organisation and figures, written to show the level of detail that is useful.
The secretariat of a fictional logistics association hosts a half-day seminar for about 120 members. Last year, several attendees expected a full lunch and recordings; the event offered light refreshments and live sessions only.
This year the confirmation email lists what is included (two refreshment breaks, printed notes), what is not (lunch, recordings) and when slides will be shared after speakers confirm. A short note explains how to tell the secretariat about dietary needs before a closing date.
Use this yourself
Pre-event expectation message plan
Copy the list and fill in the owner, message and date for each item.
- Purpose and audience statement used in every message:
- Five assumptions delegates may hold, as found in past feedback:
- For each: the plain statement and the channel it appears in:
- Included in registration, in one sentence:
- Not included, in one sentence:
- What attendees are asked to do before and on the day:
- Items still being confirmed, with confirm-by date:
- Message dates: invitation, programme, confirmation, week-before, on the day:
- Message approver and sender:
- Who updates all channels when something changes:
Handle it in-house, or bring in help?
Your team can usually handle this when
- The event is familiar and past feedback already names the main gaps.
- One person owns all communications.
- The programme is stable and few items are still being confirmed.
Outside planning help earns its fee when
- Several departments send their own messages and they no longer agree.
- The programme is changing and approvals take time.
- Sponsors, speakers or partners make promises that the organiser does not control.
Need one consistent message across every channel?
An Event Blueprint can list what is promised, by whom and where, then set out one set of delegate messages with owners and dates. A planning pack also marks which items are still unconfirmed, so nothing is announced before the supplier or speaker has agreed to it.
Questions organisers ask
How much should we promise in the invitation?
Only what is confirmed. Describe the purpose and audience, and state clearly what is still being arranged. Add detail when each item is confirmed.
Should we mention what is not included?
Yes, briefly and early. A short list of exclusions in the confirmation email prevents more complaints than any apology afterwards.
What if speakers or sessions change?
Tell delegates what changed, why and what replaces it, in one message. Keep a record of the original promise so the replacement is comparable.
Can we use past feedback to find the assumptions?
Yes. Read open comments for words such as expected, assumed or thought, and group them. They point to the messages that need rewriting.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.