Conference email communication plan and templates

Segment before you write

Authors, reviewers, registered attendees, speakers and committee members need different messages. Keep them as separate lists and avoid sending the same newsletter to everyone. A reviewer does not need registration reminders, and an attendee does not need review deadlines.

The plan

This sequence covers the main touchpoints. Adjust the timing to your own timeline.

• Save-the-date: announce dates and place to the community, twelve months before.
• Call for papers: open the submission, nine months before, then reminders at half-time and a week before the deadline.
• Submission confirmation: automatic, immediately after submission.
• Reviewer invitation and reminders: as in our reviewer templates.
• Decisions: acceptance, poster offer or rejection, on the announced date.
• Registration open and early-bird reminders: to accepted authors and the wider list.
• Programme published: to all registered, with the link.
• Practical information: one week before, covering venue, times and what to bring.
• Thank-you and survey: within two days after the meeting.

A simple template for practical information

Send it a week before the meeting.

Subject: [Conference name]: what you need to know before you arrive Dear [Name], [Conference name] starts on [date] in [venue]. Registration opens at [time]. Your programme is here: [link]. Getting here: [transport summary and link] What to bring: [badge, ID, poster] Problems on arrival: [name, phone] See you soon, [Organising team]

Write for scanning

One message, one main action. Put the deadline and the action in the subject line or the first sentence, link to the page that holds the details and avoid attachments that will be out of date by the next message.

Save-the-date template

The first message is short. Its only job is to put the dates in people’s calendars and give them a page to bookmark.

Subject: Save the date: [Conference name], [City], [dates] Dear colleagues, [Conference name] will take place in [City] from [dates]. The meeting brings together researchers working on [topics]. The call for abstracts opens on [date]. Details and updates will be on [link]. Please share this message with colleagues who may be interested. [Organising committee]

Submission confirmation template

This message is sent automatically and is read carefully, because it is the author’s proof that the submission arrived. Repeat what was submitted and say what happens next.

Subject: [Conference name]: we have received your abstract Dear [Name], Thank you for submitting “[Title]” (ID [number]). You can view or edit your abstract until [deadline] at [link]. Next steps: abstracts are reviewed between [dates]. You will receive a decision by [date]. If you do not see a message in your inbox, please check your spam folder. Questions: [address]

Programme announcement template

Send this to everyone who registered, and put the link at the top. It should be short, since the programme itself carries the detail.

Subject: The programme for [Conference name] is now online Dear [Name], The programme is published: [link]. It includes [number] sessions across [number] days, with keynotes by [names]. You can filter by track and save the sessions you want to attend. The programme may change, and the latest version is always on the website. We will tell presenters directly if their session moves. See you in [City], [Organising team]

How often to write, and to whom

Frequency should follow need. During the call, a message at opening, at the midpoint and one week before the deadline is enough. In the quiet months between decisions and the meeting, write only when there is news. Send transactional messages, such as confirmations and receipts, when they are triggered, and keep them separate from newsletters. Give recipients a way to say that they no longer want general messages, while still receiving those that concern their own submission or registration. Where the law requires consent for marketing email, obtain it properly and keep the record.

Deliverability basics

A message that lands in spam is a message that did not exist. Send from an address on your own domain, set up the authentication records that your email provider or IT team can supply, and avoid sending a large first mailing from a new address. Keep your list clean: remove addresses that bounce and people who ask to be removed. Write like a person, avoid all-capital subject lines and excessive punctuation, and include a plain-text version. Test each template by sending it to a few addresses at different providers before the main send.

Emails in more than one language

If your community is international, decide whether emails go out in one language or several. A common pattern is English for everyone with the key deadlines repeated in the recipient’s language. When you write in several languages, send the versions together and check that the dates, times and links are identical. Store the recipient’s language preference at registration and use it. A translation that is late or different from the English is worse than none, so agree who checks each version.

What to measure after each send

A small set of measures shows whether the plan works. Look at delivery and bounce rates, opens and clicks, and, most important, the action that followed: submissions after the call reminder, registrations after the early-bird message. Watch replies, too. If several people ask the same question, the message or the web page was unclear. Change one thing at a time so that you know which change worked, and keep a note of results for next year.

A quiet-period calendar

Plan the year on one page. This grid shows a typical pattern for a meeting in October, with the audience for each message.

January Save-the-date All contacts February Call for abstracts opens All contacts March Midpoint reminder; deadline reminder All contacts April Decisions Authors May Registration open; early-bird ends Authors, all contacts June Presenter reminders Accepted authors August Programme published Registered September Practical information Registered October Meeting; thank-you and survey Registered

Keep a single source for dates and links

Emails go out over many months, and each one repeats dates and links. Keep them in one place, such as a shared page or a short list, and copy from it. When a deadline changes, update the source first, then correct any queued messages, and tell the people who received the earlier version. This small habit prevents the most damaging error in conference communication: two different deadlines in two different emails, each looking official.

Watch what works

Review deliverability and replies after each send. If many people reply with the same question, fix the page or the message that caused it, and give the same answer to your attendee support channel so responses stay consistent.