How to write a corporate event brief

A corporate event brief is the document that consolidates everything the organisation needs to communicate before production work begins. It is not a form or a wish list: it is an alignment tool. A well-written brief saves time in meetings, reduces misunderstandings, and allows proposals from different agencies to be compared on the same terms.

What a brief is actually for

There are two uses of the brief worth distinguishing. The first is internal: gathering the needs of different stakeholders — HR, marketing, leadership — into one document that aligns them before approaching any agency. The second is external: giving an agency or supplier the starting point to put together a realistic proposal. In both cases, the goal is the same: everyone starts from the same understanding.

What it must include

1. Event objective (with a success metric where possible)
2. Event type and format (convention, gala, team building, product launch…)
3. Date and time window
4. Expected attendance and attendee profile
5. Available budget or indicative range
6. Geographic location, or whether the venue is open or already defined
7. Brand tone and values that should be reflected
8. Known constraints (dietary, mobility, scheduling, confidentiality)
9. References or precedents (previous editions, reference events)
10. Decision process and proposal deadlines

The right level of detail

A brief that is too thin generates generic proposals. A brief that is too detailed becomes a specification document that leaves the agency little creative room. The balance is in detailing the non-negotiable parameters — budget, date, headcount — and leaving open what can be the subject of a proposal: concept, venue, format.

Internal brief vs. agency briefing

The internal brief usually has more detail and may include sensitive information: revenue forecasts, headcount data, business objectives. The briefing sent to an agency can be a condensed version, focused on what the agency needs to know to propose. There is no point sharing the company’s strategic plan with five agencies to get three quotes for a 200-person event.

Who should own the brief

The brief should not be drafted by a single person without input from everyone affected. When an event touches multiple departments — internal communications, HR, leadership — the person writing it acts as a collector of information, not the sole source. It is common practice to circulate the first draft for a 48-hour review before treating it as final. Skip that step and objections tend to surface after the brief has already gone out to agencies, forcing the same conversation to reopen with all of them at once.

A quick test before sending the brief

Before sending it, it helps to run a simple test: read the brief as if you knew nothing about the company or the project. If basic questions remain unanswered after that read — how many people, what budget, by when — the brief is not ready. Another useful check is asking someone outside the project to read it and note what confuses them; those questions usually match the ones the agency will ask.

• Is the objective understandable without extra explanation?
• Is the budget stated, even as a range?
• Is it clear who signs off on the final proposal?
• Is there a clear deadline for receiving proposals?

Briefs for recurring events

When an event repeats — the annual convention, the Christmas dinner, the January kick-off — the brief can build on the previous year's record instead of starting from zero. That does not mean recycling the same document: it is worth reviewing what worked, what did not, and what has changed in the company since the last edition (headcount, budget, priorities). Including that comparison in the brief saves the agency from re-asking questions already answered and lets the proposal focus on real improvements.

Common mistakes when writing a brief

• Defining the objective as an activity rather than an outcome (“hold a gala dinner” vs. “reinforce leadership team cohesion after the integration process”)
• Omitting the budget for tactical negotiation reasons, leading to proposals that do not reflect reality
• Assuming the agency knows the company’s internal culture
• Requesting a proposal before the date is confirmed
• Not specifying who makes the final decision or how many people sign off

A brief does not need to be long. A single well-structured page is usually enough. What matters is that whoever reads it can form a clear picture of the event and know what is expected from their proposal.