The brief is the single document an agency builds a proposal, a concept and a budget from — the less it leaves out, the fewer rounds of clarifying questions stand between you and a real proposal. A brief for an event agency is a short summary of the event's goal, context and constraints, detailed enough for the agency to build a meaningful proposal without guessing. Most of the wasted time in event preparation doesn't happen during delivery — it happens in round one, when the brief contained nothing but a date, a guest count and a budget.
What routinely gets left out of a brief
The goal is the most commonly missing piece — not the theme, but what's supposed to change. "We want a conference for our partners" describes a format, not a goal. A goal sounds more like "we want partners to leave with confidence in our new product line" — and that single sentence decides whether the agency proposes a formal, content-heavy programme or a looser gathering with room for informal conversation. Without a goal, you get a proposal that's technically correct and misses the point entirely.
The second thing that regularly goes missing is history — what was done last time, and what worked or didn't. An agency that doesn't know last year's gala had an acoustics problem in the room, or that the programme ran too long, risks repeating the same mistake in good faith.
A basic brief structure
The structure below covers what an agency needs for a first meaningful conversation — not a perfect document, just enough information that the next step is a proposal rather than a round of guessing.
| Section | What to include | |---|---| | Goal | What's supposed to change or improve, not just the format you want | | Audience | Who's attending, how many people, their relationship to the company | | Date and flexibility | A fixed date, or a window you can shift within | | Budget range | At least roughly — a range, not a precise figure | | Venue | Preferred region, or leave it open to the agency's suggestion | | Must-haves | What has to be there (an awards ceremony, a leadership speech) | | History | What was done before and what did or didn't work | | Point of contact | Who decides and who's just copied in |
Why a budget range matters more than a precise number
A missing budget range is the single most common reason a first proposal misses the mark entirely. Without a rough range, an agency proposes either too modestly or too generously — either way, the feedback comes back as "that's not what we had in mind" and the whole process resets. The range doesn't need to be precise; "somewhere between X and Y" is enough to get the proposal in the right order of magnitude. What the brief doesn't need is a detailed vendor list or full dramaturgy — that's the agency's job, not the client's.
When it's fine to leave something open
Not every part of the brief has to be final at the first meeting — what matters is naming clearly what's settled and what's still moving. If you don't know the exact date yet, write a three-week window instead of a made-up date. If you're not sure whether you want a conference or a smaller format, write both as open questions. An agency can work with open points — it can't work with false certainty that collapses two weeks later and pushes the whole timeline off course.
How the brief shapes the first proposal
The more specific the brief, the closer the first proposal lands to what you actually want — and the less time gets spent on rounds that don't move anything forward. Take a look at our portfolio too, where you can see how different goals — from an annual conference to a company anniversary — led to entirely different solutions precisely because they started from a clearly named brief.
How a brief differs by event type
A brief for a company anniversary or a gala evening needs different details than a brief for team building, even though the formal structure stays the same. For formal events, it matters to name the expected level of formality and whether programme elements like a leadership speech or an awards ceremony are planned — these elements fundamentally shape the evening's dramaturgy. For team building, on the other hand, what matters most is describing the team's composition and its current dynamic — whether it's a newly formed team that doesn't know each other yet, or an experienced group that needs informal downtime more than icebreaker activities. A generic brief that ignores these differences leads to a generic proposal that could be tweaked into almost anything — and that's exactly the sign that it isn't built from a specific brief at all.
Who should actually write the brief
A brief works best when it's written by someone who understands both the business goal and the operational constraints, not just one of those perspectives. If HR writes the brief alone without input from leadership, a clear business goal can be missing. If leadership writes it alone without input from the people who'll be handling the event operationally, it can lack a realistic view of capacity and timelines. Ideally the brief is the result of a short internal alignment before it goes to the agency — not one person's first draft that changes shape halfway through preparation.
What happens when there's no brief at all
Without a brief, the agency works from assumptions instead of facts, and that shows up in the very first proposal. In practice that means a longer first meeting, where most of the time gets spent on basic questions instead of discussing the concept, and a higher risk that the first proposal will need to be rebuilt from scratch. A short, even incomplete brief is always a better starting point than none at all — an agency can work with gaps, but not with a blank page.
Next step
Before you send that first email to an agency, answer three questions: what the event is supposed to change, who's attending, and what range the budget sits in. If you're not sure how to put a brief together, get in touch — we can walk through it on a short intro call before you draft a formal document.