How communications teams and event leads divide responsibilities
The communications team and the event lead each assume the other is sending the speaker announcement.
The short answer
Divide the work by what each side is accountable for: the event lead owns what happens at and around the event, and the communications team owns what the organisation says in public. Everything in between, such as speaker announcements and attendee updates, needs one named drafter and one named approver.
Write the split down task by task before the first announcement is due. A responsibility matrix makes missing owners and double owners visible while they are still cheap to fix.
Two kinds of ownership
The event lead is accountable for the programme, venue, suppliers, run sheet and registration data. The communications team is accountable for the organisation's voice, brand rules, media relations and public statements.
Trouble starts at the boundary. An email to registered attendees is event operations, but its wording is also the organisation speaking.
A starting split
| Task | Usually led by | Approves | Consulted |
|---|---|---|---|
| Event name, key messages, brand use | Communications | Communications head | Event lead |
| Programme content and speaker confirmation | Event lead | Committee or sponsor of the event | Communications |
| Speaker and programme announcements | Communications drafts | Event lead confirms facts, communications approves wording | Speaker |
| Registration page and confirmation emails | Event lead | Event lead | Communications for tone |
| Attendee updates on venue, timing or changes | Event lead drafts | Named senior approver | Communications |
| Media invitations and press enquiries | Communications | Communications head | Event lead for facts |
| Photography, recording and consent wording | Event lead | Whoever owns privacy questions | Communications |
| Public wording if something goes wrong | Communications drafts | Senior executive | Event lead for facts |
Where the handover usually breaks
- Facts change after wording is approved, for example a session time moves and the social post is already scheduled.
- Two people can approve, so each waits for the other, or each approves a different version.
- Communications is told about the event after dates are public.
- Attendee questions arrive on social channels and nobody owns the reply.
Agree the working rhythm
Set a short weekly check, fifteen minutes, with a shared list of what will be published in the next two weeks. The event lead brings confirmed facts, and communications brings the publishing calendar.
Agree a turnaround for approvals, and a rule for what happens when an approver is unavailable.
Worked example · Fictional example
A conference with a shared speaker announcement
Fictional organisation and figures, for illustration only.
A fictional professional institute plans a one-day conference with 280 expected attendees. Its communications team of two plans a three-week announcement series, and the event lead is a secretariat manager.
They agree that the event lead keeps a confirmed-speakers sheet with a status for each person. Communications drafts each announcement only from that sheet, and the event lead confirms the facts within one working day. When one speaker withdraws, the sheet changes first and communications pulls the scheduled post the same day.
Use this yourself
Communications and event lead split worksheet
Copy this table, list every public-facing task for your event and fill in one name per cell. Any task with two names under Approves or none under Drafts needs a decision.
| Task | Drafts | Confirms facts | Approves wording | Publishes | Backup if unavailable |
|---|---|---|---|---|---|
| Speaker announcements | |||||
| Registration page | |||||
| Attendee updates | |||||
| Social posts during the event | |||||
| Media enquiries | |||||
| Post-event thank-you and follow-up |
Handle it in-house, or bring in help?
Your team can usually handle this when
- Both teams already work together and approval lines are written down.
- The event is small and one person can approve wording quickly.
- A shared sheet of confirmed facts is easy to keep current.
Outside planning help earns its fee when
- Neither team has the capacity to chase facts, suppliers and approvals together.
- Several departments claim a say in announcements and nobody arbitrates.
- You want a project lead to hold the confirmed-facts sheet and run the weekly check.
Want the split agreed before announcements start?
A conference project lead can draft the responsibility split with your communications team, keep the confirmed-facts sheet current and run the weekly check between both sides. Send the roles involved and the date of your first public announcement, and we can talk through what to agree first.
Questions organisers ask
Who should own the registration page?
Usually the event lead, because it holds operational facts and attendee data. Communications reviews tone and brand use.
Who approves wording when the two teams disagree?
Name one senior person in advance. Without that, disagreements are settled by whoever is least busy.
Should communications attend event planning meetings?
Attend the ones where public facts are decided, such as date, speakers and venue. A short weekly check is often enough after that.
Where do we record the decisions?
Use a decision log so each approval and date is easy to find.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.