Most event briefs start with the wrong information.

Date, location, estimated numbers, catering requirements, AV specs. All the logistics, none of the clarity.

It is not that those details do not matter. They do, eventually. But if you lead with logistics, you end up designing an event that solves for the room layout instead of the problem.

A good brief should answer four questions before it touches venue selection or run sheets. Get these right and everything else gets easier. Miss them and you will be arguing about audio levels while nobody remembers why the event exists in the first place.

Question 1: What Needs to Change?

This is the question most briefs skip entirely.

They tell you what the event is: a conference, a roadshow, an incentive, a summit. They might even tell you what it should feel like. But they rarely tell you what needs to be different afterwards.

An event is not a thing you do. It is a lever you pull to shift something that is stuck or reinforce something that is fragile.

So the first question is: what needs to change because this event happened?

Not ‘we want people to be informed.’ Not ‘we want to build engagement.’ Those are not changes. They are vague hopes dressed up as objectives.

A real answer looks more like these:

• Sales reps need to stop avoiding a new product line and start leading with it in customer conversations

• Regional managers need to commit to a restructure they have been quietly resisting

• Members need to renew at a higher rate than they did last year

• Partners need to invest in co-marketing that has been stuck at zero for six months

If you cannot point to a specific behaviour, belief, decision or number that will be different three months after the event, you do not have a clear brief. You have a gathering.

The problem with most briefs is they confuse activity with outcome. They list what will happen, sessions, speakers, networking time, without ever asking what all that activity is supposed to produce.

Start with the change. Everything else is just scaffolding.

Question 2: For Whom, Specifically?

‘Everyone’ is not an audience.

Neither is ‘our customers’ or ‘the leadership team’ or ‘key stakeholders.

Those labels are too broad to be of value in the design. You end up with an event that tries to please everyone and satisfies no one.

A useful brief names the people who matter most to the change you are trying to create and it tells you something real about them.

Not demographics, age, geography, job title. Those are useful for logistics but they do not help you understand why someone would care about your event or what might make them act differently afterwards.

You need to know things like:

• What do they currently believe that needs to shift?

• What is getting in their way?

• What have they tried before that did not work?

• Whose opinion do they trust?

• What would make them walk out of this event and do something Monday morning they would not have done otherwise?

If your brief cannot answer those questions, the event will be designed around what you want to say rather than what they need to hear.

Here is an example of the difference.

A while ago, a client briefed us on a national sales conference. The brief said ‘audience: 200 sales reps, each with sales targets, distributed across six regions.’

That tells us how many chairs we need. It does not tell us anything useful.

We went back and asked: what is actually happening with these reps right now that this conference needs to address?

Turns out, half of them were hitting quota comfortably on legacy products and saw no reason to complicate their lives with a new product suite. The other half were struggling with quota and had started to disengage.

Same room. Two completely different problems. If we had designed one event for ‘200 sales reps,’ it would have failed both groups.

Instead, we designed two overlapping experiences, one that made the high performers feel like early adopters with an edge and one that gave the struggling reps a clear, achievable path back to confidence.

None of that would have been possible if the brief had stopped at demographics.

Question 3: What Is the Cost of Not Changing?

This is the question that separates events that matter from events that fill calendars.

If nothing bad happens when people ignore your event or forget it two weeks later, you do not need an event. You need an email.

The brief should be able to answer: what is the cost to the organisation if the change we want does not happen?

Sometimes that cost is financial. Revenue is leaking. Deals are stalling. Attrition is rising. Members are not renewing.

Sometimes it is strategic. A restructure that does not land will cost the organisation agility. A product launch that sales reps do not back will waste years of development investment.

Sometimes it is cultural. Leaders who do not align around a new direction will quietly undermine it, and the organisation will fracture.

The point is not to catastrophise. The point is to know whether the event actually matters.

If the brief cannot articulate a real cost to inaction, the event will feel optional. And optional events get deprioritised, under-attended and under-invested. Then someone will stand up six months later and say ‘events do not work for us,’ when the real problem was the event never had a reason to exist in the first place.

Question 4: How Will We Know It Worked?

This is where most briefs wave their hands and say post-event survey or satisfaction scores or social media engagement. None of those tell you whether the event worked. They tell you whether people enjoyed it.

A good brief defines success in terms of the change it set out to create.

If the goal was to shift sales behaviour, success looks like: opportunity volume, deal size  or win rates moving in the quarter after the event compared to before.

If the goal was member renewal, success looks like: renewal rates or member engagement in programs increasing in the three months following the event.

If the goal was leadership alignment, success looks like: decisions getting made faster, regional teams implementing agreed changes or staff engagement scores lifting in the areas you focused on.

The brief does not need a perfect measurement plan. But it does need to commit to looking at something real, not just how people felt on the day.

And it needs to commit to that measurement before the event is designed, not after. Because if you wait until the end to decide what success looks like, you will retrofit the definition to fit whatever happened. That is not measurement. That is storytelling.

Why Most Briefs Fail to Answer These Questions

It is not because the people writing them are careless or inexperienced.  It is because most briefs are written too early, before the internal thinking has been done.

The brief becomes a way of pushing the problem downstream to the event team or the agency, hoping the creative process will sort it out.

It rarely does.

A brief should be the summary of strategic decisions already made. What needs to change, for whom, why it matters, and how we will know. If those answers are not clear yet, the brief is premature.

The other reason briefs fail is internal misalignment. Different stakeholders want different things from the event, so the brief tries to accommodate everyone by staying vague. That way no one can be proven wrong.

The result is an event that does not offend anyone and does not move anything either

.

What This Means for Your Next Brief

Before you write or approve an event brief, ask yourself:

Can I answer these four questions clearly and specifically?

1. What needs to change?

2. For whom, specifically?

3. What is the cost of not changing?

4. How will we know it worked?

If the answers are vague or missing, do not start designing yet. Go back and do the strategic work first. Because an unclear brief does not produce a flexible, creative event. It produces an expensive day out that nobody remembers three months later.

And we already have enough of those.

Next week: why the best events feel effortless but are designed like military operations—and what that actually means in practice.