Event brief template One document the whole team plans from

Put the why, the room and the roles in one place your whole team can find.

The Event Brief Template is a Word document with a section for every question your team keeps asking. Why are we doing this? Who is coming? What is the theme, and how is the room set? It also holds a one-page run-of-show summary, staff roles for the day, the items still outstanding, the comms plan and the handoff pack for whoever sets the room.

We filled every section with prompts and added sample text where an example helps, so you start by editing, not by staring at a blank page. Write the why first, then work down the sections and overwrite each sample as you go. Put a date on each edition and send it to everyone who works the event.

What is an event brief?

Decisions get made in meetings. Then they scatter, into email threads, chat messages and the notebook of whoever was in the room, and before long the team is arguing about something it already settled. The brief is where they stop scattering.

An event brief is one current document that answers three questions: why the event is happening, who it is for, and who does what. Anyone who picks it up, even someone who joined last week, should be able to run the event from the plan.

It sits between two other documents, and people mix them up. The run of show is the timed script for the day: every segment, its cue and its fallback. The ownership matrix, often called a RACI, lists every planning task with the role that owns it. The brief carries a short summary of each and says where the full version lives. What it adds is the part neither of them holds: the why.

If your team can run the event but nobody has the hours to write the plan, Events Authority offers help writing and running the plan. If you have the hours, the template gives you the sections.

What goes in each section of an event brief?

The template runs in ten sections, in the order you’ll fill them. Each one answers a question someone on the team would otherwise stop you in a hallway to ask.

Section	What it answers	Common mistake
1. Why	What is this event for, in one sentence, and what should be true 30 days after it?	Listing activities (a keynote, a workshop, a dinner) instead of the result they are meant to produce.
2. Who, what, when, where	Who is hosting, who is coming, what it is, when and where.	Pasting the guest list in. It belongs in a separate attachment, shared only with the people who need it.
3. Audience	Who the guests are, what they know about you, what they came for, and what would make them tell a colleague that afternoon.	Stopping at job titles. The line that shapes the agenda is what they came for.
4. Theme system	One idea, and how it shows up at every touchpoint from the invitation to the thank-you.	Forcing the theme onto a touchpoint that can’t carry it. Leave that one plain.
5. Room	Seating, AV, signage, Wi-Fi and what the venue is placing.	Writing the Wi-Fi password into the brief. It goes on a sign at the podium and on the back of badges.
6. Run of show	A summary of each segment: the time, the owner and what the guest leaves with.	Copying the whole timed script in. Then two versions drift apart.
7. Staff roles	Who does what on the day, where they stand, and what they own.	Treating this table as the full ownership matrix. It covers the day only.
8. Outstanding items	Everything still missing a commitment, an owner or a confirmation.	An open item with no name and no date beside it. It stays open.
9. Comms plan	Every message, who it goes to, when it’s sent, who owns it, and whether it’s written yet.	Listing the messages without their text.
10. Handoff pack	What the on-site lead needs to set and run the room without calling you.	Writing it for yourself. If the on-site lead has to call and ask what’s in a box, it isn’t finished.

Three of those sections are summaries on purpose.

The run of show in the brief gets one line per segment. The cues, the exact timings and the fallbacks stay in the full run-of-show sheet. The brief shows the team the shape of the day; the sheet is what they run it from.

The staff roles table covers the day and nothing more. Every planning task before it belongs in the ownership matrix, and the brief names the file or tool where that lives.

The comms plan tracks each guest message, and the full text of every one goes in an appendix. That way the team has read what the guests have read, and nobody at check-in is caught out by a promise made in an email.

How do you write an event brief?

This assumes the event is agreed and you’re the one pulling the plan together. If you’re earlier than that, start with the step-by-step guide to planning a corporate event. Then fill in the brief in this order.

1. Write the why first. One sentence on what the event is for, then the outcomes you want to be true 30 days after it. In a video I posted on LinkedIn on January 29, 2026, I put it as one question: “What do you want to be true 30 days after this event?” Teams spend weeks on logistics like swag and staffing before anyone answers it. Answer it on the first page, where every later section can be checked against it.
2. Fill in the basics, then the audience. Who, what, when and where are quick, and everyone asks for them. The audience takes longer. Guest profiles go in the attachment: one short paragraph per guest company, closing with one thing to ask them about.
3. Pick the theme and carry it through. A theme is the set. It tells guests which show they’re at before anyone says a line. Write it in one line (the template’s sample is a test kitchen, because guests will make something with the product before they leave), then fill in each touchpoint from the invitation to the thank-you.
4. Describe the room so someone else could set it. Seating, AV, the tables at the back, signage, and what the venue or host is placing, so nobody brings a second one.
5. Summarize the run of show. The template names three things to build into any agenda: a demo with an outcome, so guests leave with something finished; energy resets between heavy segments; and a named fallback if the Wi-Fi or the product fails, with whoever makes that call. Add the day-before walkthrough and the morning room check.
6. Name the roles for the day. Who fills each role, where they stand and what they own.
7. List what’s still open. Each item gets a name and a date. Three days out, paste the open lines from your outstanding-items checklist here, so the final edition shows exactly what’s left.
8. Build the comms plan. Give every message a send date and an owner. Any message not yet written is an open item, so it goes in section 8 too, with a name beside it.
9. Write the handoff pack. What’s in each box and where it goes, what to switch on and by when, which photos to take, and who is on call. Tracking numbers go to the on-site lead directly, not into the brief.
10. Date the edition and send it. Fill in the edition line at the top (for example, “3 days out”) and send it to everyone who works the event, not just the people who planned it. When something changes, send a new edition, so nobody keeps working from the old one.

The finished brief has to pass one test, and it’s the one the template opens with: if the person running the room reads only this document, they can run the day.

What goes wrong without an event brief?

The failures are quiet. None of them looks like a failure until late.

Decisions get made twice. The theme was settled in a meeting. Later, someone who missed it reopens the question in a new thread, and the team decides it again, maybe differently.

The new team member never sees the why. Someone joins halfway through, gets the task list and does every task well, for a slightly different event than the one intended, because the purpose was never written anywhere they could read it.

The on-site lead works from an old version. The agenda moved, the room changed, a segment was cut. The on-site lead is holding last week’s copy. The guests notice before the team does.

Each of those looks like a communication problem. Here’s the truth: if it isn’t in the brief, it wasn’t decided. It was discussed. A decision that lives in somebody’s memory leaves the stage when they do, and whoever takes their place is working without a script.

So end every planning meeting with one question: what changed in the brief? If the answer is nothing, check whether anything was actually decided. If something was, write it in, date the new edition and send it before the end of the day.

Common questions

What is an event brief? An event brief is one current document that says why an event exists, who it’s for and who does what on the day, so anyone on the team can run the event from the plan.

What should an event brief include? Ten sections: why; who, what, when and where; audience; theme system; room; run of show; staff roles; outstanding items; comms plan; and handoff pack. Start with the why, written as what should be true 30 days after the event.

How long should an event brief be? There’s no set length. Early on it can fit on a single page: the why, the audience, the date and the owner. By the final edition it holds all ten sections, and the template’s working rule is one page per section where you can. If it runs much longer, check whether the full run of show or the guest list has crept in.

Who writes the event brief? The brief owner, named at the top. Others supply details for their sections, but one owner edits, dates and sends each edition, so there’s never a question about which copy is current.

What is the difference between an event brief and a run of show? The event brief explains why the event exists and how the plan fits together. The run of show is the timed script for the day, with an owner, a cue and a fallback for every segment. The brief carries a one-line summary of each segment.

Write the why, then hand it over

Why first, one current edition, and everyone who works the room holding the same copy.

For an outside read on your brief before it goes to the team, ask for a complimentary event assessment.