What an Event Brief Should Include (With Structure and Example)

An event brief should state the objective and how success will be judged, the audience, the budget as a real number, which dates are genuinely fixed, the non-negotiables including accessibility, who approves decisions, and any commitments already made. It is the document a requester hands to whoever will deliver the event, written before planning starts.

A brief is not a plan. It is the input to one. The plan, the event timeline and the run of show come afterwards and belong to whoever is delivering; the brief is the requester’s side of the exchange and it is finished before the first venue is called. This covers what goes in it, the two sections that most briefs get wrong, and a worked example.

Start with the outcome, not the format

The reason most event briefs are useless is that they describe an event the requester has already imagined. A venue, a format, a month, a rough head count. All of it arrived before anyone asked what the event was supposed to achieve.

A brief that opens with “a drinks reception for 150 at a central London venue in October” has skipped the only question that matters. Achieve what? Renew fifty accounts that are up in Q4? Get thirty engineers to meet the people whose code they review? Those two events look nothing alike, and neither of them is necessarily a drinks reception.

A planner given the outcome can propose something better than the thing you pictured. A planner given the format can only book it. If you want the second thing, you are not writing a brief, you are placing an order.

So write the objective first, in one sentence, and write the success measure directly under it. “Sixty per cent of invited renewal accounts attend, and each one has a conversation with their named account manager” is a brief. “A well-received evening event” is a wish.

What should an event brief include?

An event brief should include nine sections. Most fit on one page.

1. Objective and success measure. What the event is for, and the specific thing you will look at afterwards to decide whether it worked. Attendance is a measure of logistics, not of success, so pair it with something about what attendees did.
2. Audience. Who they are, roughly how many, and, more usefully, why they would give up an evening or a working day for this. If nobody can answer the second part, the format is not the problem.
3. Budget. A number or a range. See below.
4. Dates and constraints. The dates you want, and separately, which are genuinely immovable and why. A board meeting is fixed. A vague preference for early autumn is not, and labelling it as fixed removes options for no gain.
5. Format preferences. Flag these as preferences. If you want a panel, say so and say what you think it achieves, so a planner can propose something that achieves it better.
6. Non-negotiables. Accessibility requirements, dietary provision, travel and timing limits, brand or legal constraints, anything that cannot be traded away later.
7. Approvals. Who signs off spend, who signs off the guest list, who signs off content, and how quickly each of them responds. A two-week approval loop on a six-week lead time is a scheduling fact, not an inconvenience.
8. Commitments already made. Everything you have promised, booked, held or announced before writing this.
9. Who provides what. What you will supply (the speaker list, the guest data, the branded assets) and what the planner is expected to source. Assume nothing here is obvious.

The commitments you have already made

This is the field everyone forgets and the one that wrecks proposals. By the time a brief gets written, the requester has usually held a venue, asked a speaker, told a client the date, or mentioned it in an all-hands. None of that reaches the brief, because it does not feel like a requirement. It feels like progress.

It is neither. It is a constraint, and an expensive one to find halfway through a proposal. A planner who spends two days on an alternative approach, then hears that the CEO already promised a keynote to a partner, has been wasting time on your behalf.

List every commitment with the name of whoever made it and whether it can still be unmade. Prising those out of people’s heads is a question-asking job rather than a writing job. Projan can pull the original Slack or Microsoft Teams thread into a planning session as context and then put the questions to the requester and to whoever made the promise, so what was actually committed is written down before anyone proposes something incompatible with it.

Why refusing to state a budget costs you money

Refusing to state a budget is the most common brief failure and the one that most reliably backfires. The theory is that naming a number invites a supplier to spend all of it. What happens instead is three proposals costed at random, none comparable with the others, then a round of rework once everyone learns what you were willing to spend.

Write a real number or a real range. “Fifteen to twenty thousand, including venue and catering, excluding staff travel” tells a planner what kind of event they are designing. “Competitive” and “we are flexible for the right idea” tell them nothing, and both usually mean the number exists and is being withheld.

If the budget genuinely is not signed off, say that. An unapproved ceiling with a decision date attached is still information.

Accessibility is a brief item, not a venue question

Accessibility belongs in the brief because it constrains venue, format and cost from the first shortlist. Discovered later, at the site visit or worse in the week of the event, it either forces a venue change or produces the retrofit that everyone can see: the accessible entrance round the back, the interpreter booked too late, the step-free route that ends at the stage.

Put the specifics in writing. Step-free access to every part of the event including the stage, hearing loop or captioning, a quiet space, dietary provision beyond one vegetarian option, and how far anyone should have to travel between sessions. If there is a registration form or an event website, name who is accountable for those meeting the same standard, because the first barrier most attendees meet is the sign-up page.

What does an event brief look like?

It looks like one page of short labelled sections, written in plain sentences, with numbers where numbers exist. Not a deck, not a form with forty fields, and not prose. The difference between a brief that works and one that does not is rarely structure. It is the specificity of each line.

Section	Weak line	Strong line
Objective	Build stronger relationships with key customers	Get the twelve accounts renewing in Q4 into a conversation with their account manager before the renewal call
Success measure	Positive feedback	Nine of the twelve attend, and each account manager files one note on what the customer said
Audience	Senior customer stakeholders	Decision makers at twelve named accounts, mostly ops directors, who will not travel more than an hour after work
Budget	Competitive, open to ideas	18,000 to 22,000 including venue, catering and AV; staff travel sits on a separate cost centre
Dates	Autumn, ideally October	Any Tuesday or Wednesday between 6 and 24 October. Nothing after 24 October, the renewal window closes
Commitments	Nothing noted	Venue held on a provisional 48-hour option until 12 September, our CMO has been told she is speaking

Six lines like the right-hand column beat three pages like the left. A planner reading them can tell you within a day whether October is realistic and which of your assumptions will break first. Once the brief is agreed, ownership moves across and the planning process, roles and handoffs take over.

Frequently asked questions

What are the parts of an event brief? Nine sections cover most events, but four of them carry the weight: the objective with its success measure, the budget, the fixed dates, and the commitments already made. On a small internal event you can write those four on half a page and skip the rest. On anything with external guests, add accessibility, approvals and the split of responsibilities.

How long should an event brief be? One page for a routine internal event, two or three for a conference or an external launch. Length is a poor test. The better test is whether a planner who was not in any of your conversations could read it and come back with a proposal you recognise. If they would have to guess at the budget or the deadline, it is too short.

Who writes the event brief, the requester or the planner? The requester writes it, because it records what they want and what they have already committed to. A good planner will help draft it by asking questions, and that is fine. What does not work is the planner writing the brief alone and sending it back for approval, because the requester then signs off an interpretation rather than stating an intention.

What is the difference between an event brief and an event proposal? The brief states the problem and the constraints. The proposal answers it with a format, a venue, a schedule and a price. The brief goes from requester to planner; the proposal comes back the other way. If your brief already contains a venue and a running order, you have written a proposal to yourself and left the planner nothing to solve.

A brief earns its place by removing guesswork, so agonise over three sections: the objective, the budget, and the list of things you have already promised. Get those right and a competent planner handles the rest. Get them wrong and you find out in week four, when the errors that cost real money start surfacing.