Event communication plan: template and worked example

An event communication plan records who needs each message, what they need to do, when they need it, which channel you'll use, and who's responsible for getting it to them. For a paid event, it should also show how you'll confirm important instructions reached the people who must act on them.

Start with the information people need to attend or deliver your event. Then work backwards to the moment they need it. A buyer booking a train needs the finish time early. A supplier needs an agreed delivery window. A member of your door team needs today's arrival instructions before they start answering questions.

Here's where events get messy. You've updated the website, but the reminder email still has the old entrance. The venue knows the room changed, but the speaker doesn't. Everyone has communicated. They're just saying different things.

This guide gives you a copyable event communication plan, explains how to fill it in, and works through a paid conference example. You'll see how to handle routine messages, a last-minute room change, and follow-up without creating a document nobody has time to maintain.

What belongs in your event communication plan?

Include any message that helps someone make a decision, arrive prepared, or carry out their part of the event. That means ticket holders, your team, the venue, suppliers, speakers or artists, and commercial partners where relevant.

A social campaign calendar answers a different question: how will you persuade people to buy? Your communication plan follows the people who have already bought or agreed to deliver something. The two plans meet when a public promise changes, such as a start time or advertised session.

For each audience, think about the consequence of missing the information. A late reminder about finding a ticket creates support work. An unconfirmed delivery time can leave paid crew waiting around. A sponsor who learns about a changed session from an attendee will reasonably wonder who's managing their agreement.

You don't need every conversation in the plan. Capture messages with a deadline, a dependency, or a meaningful consequence if someone misses them. Everyday chatter can stay in the channels where it already happens.

Keep this alongside your event operations plan. The operations plan decides what will happen; this document tells the affected people what they need to know. If a decision hasn't been made, give it an owner and a decision deadline before scheduling a confident announcement about it.

A copyable event communication plan template

Use this in a shared document or spreadsheet your team already opens. Copy the message entry for each communication. The labels are prompts to make a decision, so delete any that genuinely don't apply.

Event details

• Event name and date: [Name, date and local time zone].

• Plan owner and backup: [Named people and contact details].

• Current event information: [Link to the maintained schedule, arrival information and operational brief].

• Last reviewed: [Date, time and reviewer].

• Where urgent issues go: [Named role, contact method and agreed backup].

Message entry

• Audience: [Exactly who needs this, including ticket type or team where relevant].

• Purpose and action: [What they need to know or do].

• Message: [Approved wording or a link to the draft].

• Timing or trigger: [Send time, deadline, or the decision that starts the communication].

• Channel and fallback: [Primary route and what happens if it fails].

• Sender and backup: [Named people responsible for sending and following up].

• Fact check or approval: [Who verifies the details, and who approves a consequential change].

• Reply and confirmation: [Where questions go; whether a reply or completed action is required].

• Status: [Draft, awaiting facts, ready, scheduled, sent, or confirmed where confirmation is required].

Add the audience before you write the message. "Everyone" feels efficient until you put an equipment delivery instruction into a ticket-holder email. Separate entries when people need different actions, even if one decision starts all the messages.

Be specific about timing. "Before the event" gives nobody a deadline. "Once the venue confirms access, send the supplier brief by Tuesday afternoon" tells your team what they're waiting for and when to chase it.

For routine reminders, the fact check might simply mean the event manager checking the date and entrance. Reserve additional approval for changes with consequences, such as cancellations, revised commercial terms, or statements about an incident. If every routine email waits for your personal approval, you'll become the delay the plan was meant to remove.

The final field matters more than it looks. "Sent" is a useful status for a routine information email. For a supplier agreeing to a different arrival time, you still need confirmation. Decide which finish line applies before you send.

Fill the plan in the order people need information

The first thing you want to do is walk through the event as each audience will experience it. Start when they buy a ticket or accept the job, and continue until you've delivered what you promised afterwards.

Start with decisions people must make early

Your buyer may need to arrange travel, childcare, an overnight stay, or time away from work. Tell them the confirmed start and finish times, location, ticket inclusions, and anything they need to prepare while they can still act on the information.

An arrival guide sent the evening before can't fix a venue detail that should have been available when someone booked. Put stable information on the event page, then use the plan to decide when a direct reminder adds value.

For your team and suppliers, work backwards from their preparation deadlines. A captioner needs materials in advance. A caterer needs the agreed final requirements by the date in your arrangement. An artist's representative needs arrival and technical information early enough to raise a problem. Ask each delivery partner what they need from you and by when, then put those commitments into the plan.

Watch the difference between a buyer and an attendee, too. One person may buy several tickets. Check which contact details you actually hold and how essential information will reach the rest of that party. Don't assume your mailing list contains an individual address for every person walking through the door.

Separate audiences when their next action differs

You can start with ticket holders, delivery teams, and partners, then split only where necessary. A ticket with an earlier admission time needs different instructions. Staff on the later shift need a handover. A supplier using a loading entrance needs a route the audience should never follow.

For a conference, speakers need session timings and presentation requirements. For a music event, performers need the agreed arrival, soundcheck, and stage arrangements. Use the words and deadlines that belong to your event, rather than keeping template rows for people who aren't involved.

Avoid collecting personal information just because the template has somewhere to put it. The caterer may need meal requirements and quantities; that doesn't mean they need the attendee's entire booking record. Give people the information needed for their job and control who can see the full plan.

Choose channels around the action

Email works well when people need details they can return to. A maintained web page gives attendees one place to check current information. A call is useful when a supplier must agree to a change. Your staff briefing gives people a chance to ask questions before they take their positions.

Choose the channel according to the situation, then decide what backs it up. If attendees are already travelling, an email may be one part of your response, alongside updated public information and staff at the affected arrival point. A social post can help spread a correction, but your ticket holders shouldn't have to happen across it in their feed.

For the on-site team, agree which channel carries operational instructions and which carries ordinary discussion. Tell people where a question goes and who can make a decision. Otherwise a busy group chat becomes a pile of suggestions that looks like an instruction.

Give replies somewhere to go

You can write a lovely arrival email and still leave someone stuck if nobody reads the replies. Name the person covering questions before the event, the person covering them on the day, and the hours when each is available. Publish a contact route your team can actually support.

Decide which questions the inbox owner can answer and which need someone else. They might resolve a missing-ticket query using the booking information available to them. A request to change a contracted sponsor benefit goes to the person managing that agreement. A venue access question goes to somebody who can verify the route, rather than a teammate guessing from an old photo.

When you pass a question on, keep an owner until the person receives an answer. Forwarding it to the venue and forgetting it leaves the buyer waiting between two businesses. Record who is getting the answer and when you'll update the person who asked, even if the final answer isn't ready yet.

You also need a fallback that still works when your main channel fails. If mobile reception is poor on site, agree a staffed contact point and the team's alternative communication arrangements beforehand. Keep the essential contact and instruction details available to the people who need them. Test that access in the conditions they'll actually work in.

Make the message usable

Put the required action near the start. "Use the east entrance on River Street" is easier to act on than a paragraph about your venue arrangements. Include the full date where there could be doubt and label times clearly, particularly for remote participants or people travelling between time zones.

Keep important information in readable text. An image of a schedule is awkward to search and can exclude people using assistive technology. Describe routes and meeting points in words as well as showing them visually. For a changed room, give its name and location, then explain where someone can get assistance.

The W3C's accessible events guidance recommends asking participants and speakers about accessibility requirements and making materials available in accessible formats. Build those conversations into the plan early enough to arrange support, then confirm the details directly with the person concerned.

Be honest about what you've checked. "Step-free access through the east entrance" is useful when you've verified that route. "Fully accessible venue" leaves too much unexplained. Our event accessibility checklist helps you work through the wider arrangements behind the message.

Keep event information separate from promotion

A message explaining how to attend an event someone bought is doing a different job from an offer for your next event. Keep that distinction visible in your plan and in the copy.

For example, an entrance change should lead with the new entrance. Adding a discount for another event gives the message a second purpose and may change which marketing rules apply. Don't treat an earlier ticket purchase as blanket permission for every future campaign.

The rules depend on where you operate and who receives the message. In the UK, the ICO's guidance on identifying direct marketing distinguishes administrative service messages from promotion, and explains that adding marketing content can make a service message count as direct marketing. In the US, the FTC's CAN-SPAM business guidance explains the narrower categories of transactional or relationship messages and how it assesses mixed content.

Those are different tests. Your plan should record the purpose and intended audience, while your sending process follows the rules that apply to your business. Don't turn the label "event update" into a substitute for checking the actual content.

In Loopyah's attendee email tools, you can target relevant recipients, send a test, and schedule a message with a time zone. We send event updates to the relevant ticket holders and promotions to people who agreed to receive them, with opt-outs and dead addresses removed from promotional sends. That helps you keep ticket-holder information connected to the event instead of rebuilding recipient lists for every send.

You still decide what the message says, whether the facts are correct, and what must happen outside email. Keep the staff briefing, supplier confirmation, and urgent on-site communication arrangements in your plan.

Before a scheduled send, give someone responsibility for checking that it still makes sense. A reminder prepared weeks ago can contain a speaker, entrance or ticket inclusion that has since changed. The software can send the message at the time you chose; the event team needs to keep the information current.

Write the approved facts once in the maintained event information, then adapt the wording for each audience. Keep internal phone numbers and private operational detail in the team version. Your public page should be a useful destination for attendees without exposing the working document behind it.

For a small event, one person may do all of this. That's fine. The plan still helps you see the jobs and choose a backup for the period when you're greeting attendees or running a session. It should reflect the team you actually have, rather than inventing departments to make the document look complete.

Worked example: a paid one-day conference

Let's make this concrete. The following is an illustrative event, with invented timings and roles to show how the template works. These aren't benchmark recommendations or a real customer result.

You're running a conference with 240 paid attendees. Check-in opens at 9:15 am, the programme starts at 10 am, and the final session ends at 4 pm. There are two session rooms, a catering supplier, a technical supplier, visiting speakers, and a sponsor with an agreed afternoon session.

Maya is the event manager. Omar runs attendee communication and the support inbox. Leah coordinates the venue and suppliers. Dan looks after the programme and speakers. Each has a named backup in the internal contact list.

The public event information page holds the current attendee schedule and arrival details. The internal event brief holds operational timings and contacts. Maya owns confirmed changes, while the relevant lead checks the facts in their area. Here's how their plan develops.

At booking: make the commitment clear

• Audience: Each ticket buyer.

• Message and action: Confirm the event, date, ticket purchased, arrival information, and where to ask a question or raise an access requirement.

• Timing and channel: Booking confirmation, followed by a link to maintained event information.

• Owner and fact check: Omar checks the buyer experience against Maya's confirmed event details.

• Confirmation: Check that the purchase and ticket information are correct in the booking process; monitor delivery problems and questions.

Before sales open, Omar reviews the booking journey using the preview or checking process his ticketing setup supports. He checks the ticket wording, time zone, event address, and help route, including what a buyer with multiple tickets sees.

This is also the time to identify any promised follow-up. If your event page says presentation materials will arrive after the conference, somebody needs to own that delivery. Put it in the plan now so it survives the busy week before the event.

Before partner deadlines: get delivery details agreed

Leah sends each supplier its own brief. The caterer and technical crew need different arrival arrangements, so she doesn't send a combined message and expect them to extract their part.

For the technical supplier, the plan entry looks like this:

• Audience: Supplier's named on-site lead.

• Message and action: Confirm the agreed 7:45 am arrival, loading entrance, equipment requirements, and Leah as the receiving contact.

• Timing and channel: Written brief by the agreed planning deadline, with a call if questions remain unresolved.

• Owner and fact check: Leah verifies access with the venue and checks the brief against the supplier agreement.

• Confirmation: The lead replies to confirm the arrival arrangements; Leah records any unresolved requirement and its decision deadline.

Meanwhile, Dan confirms session times, presentation requirements, and arrival details with speakers. He separately confirms the sponsor's agreed session arrangements with its contact. If the contract sets an approval requirement, he includes it rather than inventing a new one after a change occurs.

Here, "we emailed them" would be an incomplete handover. The technical supplier's acceptance of the arrival arrangement is what allows Leah to organise the people meeting them.

One week before: help attendees prepare

• Audience: Current ticket holders, with separate instructions where ticket types differ.

• Message and action: Explain arrival, check-in, the programme, what to bring, access arrangements, and the support contact.

• Timing and channel: Email one week before, linking to the event information page.

• Owner and fact check: Omar prepares the message; Leah checks the route and Dan checks the programme.

• Confirmation: Send a test, check the recipient selection, monitor delivery problems, and answer questions through the shared support inbox.

The opening can be simple: "Your conference starts at 10 am. Check-in opens at 9:15 am at the east entrance on River Street. Have your ticket ready when you arrive."

Then give people the details they need. Explain anything required for participation and link to the current programme. Keep optional promotional material out of the arrival instructions.

People who buy after this send still need the information. Omar checks the booking journey and schedules or configures the appropriate follow-up for later buyers. A communication plan needs to cover the audience as it changes, rather than assuming everyone booked before the reminder went out.

The day before: remind, then prepare the team

Omar sends a shorter attendee reminder after checking the details again. It leads with arrival and the help route. The full guide remains available through the link, so he doesn't make people work through every paragraph twice. Use our event reminder email examples if you need help shaping that message.

Maya also circulates the current staff brief and confirms the morning meeting. It includes positions, supervisors, break cover, the attendee help point, and how staff raise an issue. It points to the agreed emergency procedures rather than trying to reproduce them inside a general email.

The on-site briefing is at 8:30 am, before check-in opens. Leads check attendance and brief anyone who arrives later. The door team rehearses a few practical questions, including where an attendee without their ticket should go and who can resolve a booking problem.

An acknowledgement in the group chat can confirm someone received the brief. Maya still needs to know that each person understands their role. Asking someone to explain what they'd do with a specific query reveals gaps a row of thumbs-up reactions won't show.

During the event: change a session room

At 12:30 pm, the team decides to move the 1:30 pm sponsor session from Room A to Room B. This is an ordinary programme change in our example. The team has checked the new room's suitability, capacity, equipment and access before announcing it.

Maya confirms the decision and any required partner approval. Dan tells the speaker and sponsor contact what changed and gets confirmation. Leah arranges the room setup and signs. Omar updates the public information and prepares the attendee notice from the same confirmed details.

The attendee wording is direct: "The 1:30 pm sponsor session will now take place in Room B on the ground floor. The start time is unchanged. Follow signs from the main foyer, or ask the help desk for directions."

Staff at both rooms and the help desk get the update. The team uses visible signs and a spoken announcement, and sends a targeted email where useful. They don't assume everyone at the venue is checking their inbox.

Finally, Leah checks that the old room points people to the new one and that the new setup is ready. Dan confirms the speaker is in the right place. Sending the announcement is only one part of making the change work.

After the conference: deliver the promised follow-up

Omar sends attendees the promised materials once Dan has checked permissions and the files. The message explains what's included and where questions should go. If something isn't ready, he gives an accurate update rather than sending a link to an empty folder.

Partners receive their agreed follow-up separately. The sponsor gets the material promised in its agreement; suppliers get any outstanding operational queries and the agreed invoice route. Nobody receives an attendee contact list simply because they helped deliver the event.

The team can ask for feedback and plan a separate next-event promotion with the appropriate audience and permissions. Our post-event email examples cover the wording; this plan assigns who sends each message and when.

Before closing the plan, Maya checks open commitments. A thank-you email doesn't finish an unanswered support request or an outstanding sponsor deliverable. Those items keep an owner until someone resolves them.

Give changes a clear route before you need it

A good plan leaves room for facts to change. Put the change process near the top so a team member can find it while the event is running.

Start with who can verify the issue and who can authorise the response. For an ordinary programme change, that may be the event manager working with the venue and programme lead. For an emergency, follow your event's agreed emergency procedures and the people authorised under them. Don't wait for a routine marketing approval chain.

The UK's Health and Safety Executive recommends clear emergency roles, agreed public announcement wording, and testing communication systems before the event. Your communication plan should point people to those arrangements, including how the public will receive instructions. Email is no substitute for the on-site systems and trained people the event needs.

For a routine change, record the confirmed facts before different people start rewriting them. Say what changed, who is affected, what they should do, and what remains unchanged where that helps. If a decision is still pending, share only what is confirmed and say when the next update will come.

Then check everywhere the old information might survive. That includes scheduled reminders, website copy, signs, speaker notes, support replies and partner posts. Assign each update to a person. Otherwise the announcement goes out while an old scheduled email quietly puts the original instructions back into circulation.

Keep a brief record of the decision, the time, who sent what, and which actions remain open. That record helps the next shift give the same answer. It also saves you reconstructing the conversation afterwards when a buyer asks why they received conflicting instructions.

Test the plan with the people who will use it

Before event day, walk through a plausible change with your leads. Ask who spots the issue, who confirms the facts, who makes the decision, and who tells each affected audience. Use the contact routes in the plan, including the backup if the first person is unavailable.

Test a routine message too. Open the arrival email on a phone. Follow the directions without relying on your knowledge of the venue. Check the destination of every link, the reply address, and whether somebody is actually monitoring it.

Pay particular attention to handovers. A colleague taking over the inbox needs the latest instructions and unresolved questions. A new shift needs to know what's changed since the original briefing. Give them a short update, then confirm they know who to contact.

Don't use email opens as proof that somebody understood an instruction. Apple explains that Mail Privacy Protection can load remote email content in the background regardless of engagement. Even an accurate open wouldn't confirm that a supplier accepted a revised delivery time.

Use the confirmation that fits the job. For a supplier, ask for an explicit reply. For staff, check understanding at the briefing. For a room change, check the signs and the people directing attendees. For routine attendee information, review delivery problems and the questions arriving afterwards without claiming every recipient has read it.

Improve the next plan using what actually went wrong

After the event, look for repeated questions and missed handovers. Were people asking for information you never gave them, or information buried in a long message? Did staff disagree because a decision changed, or because they were reading different versions?

Make the fix specific. If buyers kept asking when the event finished, put the finish time beside the start time. If the later shift missed a room change, add a handover checkpoint. If the caterer called someone who was already on stage, change the receiving contact and backup.

Keep a small record of these problems across comparable events. Useful measures include repeated arrival questions, unconfirmed supplier instructions, and time spent correcting conflicting information. You're looking for work you can avoid and promises you can deliver more reliably, not an impressive count of messages sent.

For your next event, start with the template and the people whose work depends on a clear instruction. Give each message an audience, an owner, a useful deadline and a way to handle questions. Then check the handover worked. That's how your email, your venue team and your people at the door end up saying the same thing.