Event Brief Template (Free, With a Section-by-Section Guide)

An event brief is the short document you write before the planning starts: what the event is, why you are running it, who it is for, and what counts as success. It is the page everyone agrees to up front, so the budget, the goals, and the sign-off are settled before anyone books a venue or invites a speaker.

This page gives you the template, a note on each section, and how to use it. Keep the brief to a page or two. It is the foundation the rest of the work sits on. For the task list that comes after, pair this with the event planning checklist.

The event brief template

Copy this into a document and fill in the brackets. Aim for one page.

Event Brief

1. Overview. [Event name], a [one-line description], on [date or dates], delivered [in person / virtual / hybrid] at [venue or platform].
2. Why this event. The problem or opportunity it addresses, in two or three sentences.
3. Objectives. Two or three measurable goals, for example [150 registrations, an 80 percent show rate, half of last year's attendees returning].
4. Audience. Who the event is for, how many you expect, and what they care about.
5. Budget. The top-line figure or range, who owns it, and whether the event is meant to make money, break even, or run at a loss.
6. Format at a glance. The shape of the event, for example [a half-day with one keynote, three breakouts, and a networking hour]. Not the full agenda.
7. Key dates. The few milestones that matter: venue booked, registration opens, speakers confirmed, event day.
8. Roles. The owner, the approver, the core team, and the key vendors or partners.
9. Success metrics. How and when you will measure each objective, and where the number comes from: the registration system, the check-in count, a post-event survey.
10. Risks and constraints. The one or two things that could sink the event: a fixed budget cap, a hard date, a single critical speaker, a venue dependency.
11. Sign-off. Who approves this brief, and by when.

The sections that do the real work

Most of the brief is quick to fill. A few sections are what make it worth writing, so give them the time.

• Objectives and success metrics. These are the heart of the brief, and they have to be measurable. Write the metric next to the objective, so "a well-attended event" becomes "150 registrations and an 80 percent show rate," and note where each number will come from, so you can actually report it afterward.
• Budget. Name a number or a range and a single owner. A brief with no budget line is the one that gets overspent, because no one agreed to a limit.
• Roles. Name the owner who runs it and the approver who signs off. When those two are clear, the decisions later in planning get settled instead of stalling in a thread.
• Format at a glance. This is what the budget and the venue get signed off against, so describe the shape honestly. Get it wrong and you approve an event you cannot actually run.

How to use it

A brief is only worth writing if you actually use it.

• Write it first, before you book anything. The brief is how you get the budget and the goals agreed while they are still easy to change.
• Circulate it for sign-off. Send it to the approver and the people who fund or depend on the event, and settle the disagreements now, while they are cheap, not the week of the event.
• Keep one version as the source of truth, and update that one as things firm up, rather than emailing slightly different copies around.
• Let it brief your team, and share the relevant parts with vendors. The approved brief tells a designer or a speaker what the event is about, minus the budget line you keep internal. It also names the files and assets you will need, which you can then collect through one link instead of chasing them. Request beta access to Submitto, self-serve, no sales call, no setup fee.