What to put in an event invitation email
You have the date, the programme outline and a list of people to invite, and now you have to write the email that gets a clear reply.
The short answer
An invitation email needs six parts in this order: who is inviting and why the recipient, what and when, where, what you ask them to do and by when, any cost or conditions, and who to ask. Put the action and deadline where a reader sees them without scrolling.
Keep the programme detail on a linked page. The email's job is to get a decision, not to hold the whole plan.
The parts, in reading order
| Part | What to write | Check |
|---|---|---|
| Subject line | Event name, date and the action, for example reply by a date. | Does it say what the email is, without sounding like bulk mail? |
| Opening | Who is inviting, and why this recipient. | Is the reason true for this segment? |
| Event facts | Format, date, time, venue or platform. | Matches the master document. |
| Your ask | Register or reply, by when, and how. | One action, one deadline. |
| Cost and conditions | Fee if any, what it includes, transfer rule, eligibility. | Link to the transfer policy wording if needed. |
| Contact | A role and channel to ask questions. | Monitored by someone. |
Write for the segment, not the list
A member, a sponsor's contact and a guest speaker need different openings. Take the segment from your audience segmentation and change the first two sentences and the ask for each.
Do not copy text that was approved for a different segment without the owner of that list checking it.
Questions for your data protection contact
Whether you may email this person at all, what you say about how you obtained their details, and what an unsubscribe or opt-out line must contain are questions for your organisation's data protection contact. Registering for the event and agreeing to marketing messages are separate permissions, so do not bundle them into one tick.
Take these questions to that contact before the first send, and record their answer next to the template.
Before you press send
- Check every fact against the master document and have a second person read the email cold.
- Send a test and read it on a phone, since many readers open invitations there.
- Confirm the reply route works and that someone owns the inbox or form.
- Suppress anyone who has opted out or is not eligible, using the rules in your invitation sequence.
Worked example · Fictional example
An email to association members
Fictional organisation and figures, for illustration only.
A fictional building-services association invites 900 members to a half-day seminar. The first email has the subject line Seminar on 12 March: reply by 20 February, a two-sentence opening about why members are invited, and a single Register button.
A second version for non-member guests removes the member fee sentence and adds an approval line, because guest places are approved by the committee secretary. Both link to one programme page so the text only changes in one place.
Use this yourself
Invitation email template
Copy this and replace each bracket. Delete any line that does not apply to the segment.
- Subject: [Event name], [date]: please reply by [date]
- Opening: [Organisation] is inviting [segment] to [event] because [reason that is true for this segment].
- Facts: [format], [date], [time], [venue or platform]. Programme: [link].
- Ask: To take part, please [register / reply] at [route] by [date].
- Cost and conditions: [fee and what it covers, or no fee]. [Transfer and eligibility wording].
- Questions: contact [role] at [channel].
- Footer: [wording on how details were obtained and how to opt out, confirmed by the data protection contact]
- Question for the contact: what permission statement is needed for event updates versus future marketing?
Handle it in-house, or bring in help?
Your team can usually handle this when
- Your team writes to a known, small list and has sent invitations before.
- One approver and one segment.
- The data protection contact has already confirmed the standard footer.
Outside planning help earns its fee when
- Several segments with different wording, approvers and rules.
- You are unsure of the permission basis for part of the list.
- Invitations, reminders and waiting-list messages need to run as one sequence.
Want the invitations drafted and checked as a set?
A conference project lead can draft one email per segment from your master facts, route each to its approver and keep the sequence aligned with registration. Consent and permission wording stays with your data protection contact. Send your segments and the draft you have.
Questions organisers ask
How long should the email be?
Short enough to read on a phone without scrolling past the ask. Put detail on a linked page.
Should the programme be attached?
Link to a programme page instead. An attachment can go out of date and is harder to update once sent.
Can we add everyone who registered last year?
That is a question for your data protection contact. Ask what you told people when you collected their details and what permission covers a new invitation.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.