Build an Event Brief That Makes Decisions Easier

Separate the objective from the format

A conference, launch or dinner is a format. Informing a group, helping people compare an offer or creating a useful conversation is an objective. Write the objective without naming a venue or production feature. Then ask which format gives the audience a credible way to engage with it. This simple separation preserves choices before supplier quotations make one direction feel inevitable.

Choose a primary objective and describe what a useful result would look like without promising a metric you cannot substantiate. If several stakeholders want different outcomes, record the priority and the trade-offs. A programme cannot give every idea equal emphasis indefinitely. The client sponsor owns this decision; the event lead makes its consequences visible in the proposal.

For a hypothetical product introduction, the objective may be that invited partners understand the new offer and know where to ask questions. A large reveal is one possible moment, but demonstrations and discussion may also matter. This is an illustrative brief, not a delivered project or a claim of commercial impact.

Describe the people and their starting point

List the audience groups, why they are being invited and what they already know. Describe what each group needs before, during and after the event. Do not reduce the audience to a guest count. A mixed group of employees, customers and partners may need different language, assistance or opportunities to participate.

The audience owner confirms invitation priorities and the source of the guest list. The guest lead identifies information needed for arrangements, including an agreed private route for relevant access, dietary or travel requests. Collect only what the planned service requires, with the organisation's information-handling arrangements confirmed.

Use this audience description to test proposals. Ask how a guest recognises the purpose, finds their way and takes the next step. If the answer depends on an unplanned announcement or a host improvising, the proposal needs more work. Link the brief to Design the Event Around the Guest Journey so the same audience assumptions shape invitations, registration, programme and departure.

Make decisions before asking for comparable proposals

Before agencies quote, provide the primary objective, expected audience, event type under consideration, date flexibility, city, indicative budget and any fixed commitments. Separate requirements from preferences. A contracted venue is a constraint; a preferred visual style is usually still a choice. State which deliverables the client already owns and which need to be proposed.

Name an approver for scope, budget and content. These may be different people. Explain how a proposal will be assessed and which questions remain open for the agency to solve. If budget information is provisional, label it rather than inviting suppliers to guess incompatible scopes.

The output is a common brief and an assumptions list, not an exhaustive technical specification. Relevant specialists should develop technical requirements from the event needs. Use How to Compare Event Budgets and Agency Quotations to compare the assumptions behind quotations. Comparable proposals require comparable assumptions, especially around guest numbers, access, hospitality and what the venue package includes.

Work backwards from the guest experience

Describe the final guest journey in plain language: the invitation received, the arrival, the main programme, the transition, the close and the promised follow-up. At each point, ask what must be ready and who provides it. Then work backwards from those dependencies to the decisions that release the work.

A guest cannot receive accurate arrival instructions until the venue entry and transport arrangements are confirmed. A presenter cannot rehearse the intended sequence until the content and relevant production setup are ready together. A personalised item cannot be approved from a provisional name list. These connections belong in the brief's decision schedule.

Use an illustrative 90-day framework as a starting conversation: earlier weeks for objective and feasibility, middle weeks for scope and detailed development, final weeks for approvals, checks and coordinated readiness. It is not a universal minimum or a promise of delivery. The actual schedule belongs to the event's dependencies. See The Event Critical Path: What Can Delay an Entire Production? for a fuller method.

Test scale through four illustrative scenarios

Counts of 100, 500, 1,000 and 5,000 guests are illustrative comparisons, not capacities or staffing prescriptions. At 100, the brief might explore direct discussion and personalised hosting. At 500, the team should test concentrated arrivals and shared transitions. At 1,000, multiple sessions or guest groups may require more explicit information ownership. At 5,000, distinct audience zones and coordinated support may become questions for the venue and relevant specialists.

The same count can produce very different requirements. An open exhibition, a seated dinner and a conference with breakouts use space and guest time differently. Record the arrival pattern, activities and movement assumptions alongside the number.

If attendance changes, ask the event lead to trace the effect on venue layout, registration, hospitality, production and departure before approval. Do not assume costs or resources move in a simple proportion. The brief should say who approves a revised scenario and which arrangements must be reassessed by their responsible owners.

Use approval gates and an exceptions list

A working brief needs a named owner, revision date and status. Record the decision being approved, the approver, the information required and the work it releases. Useful gates include purpose and audience, feasibility, proposed scope and budget, content release and operational readiness. Adapt them to the event rather than creating approvals that serve no decision.

Keep exceptions visible. An unresolved question should state its consequence and the latest useful decision point. If the venue is provisional, identify what can proceed and what should wait. If a stakeholder changes the objective, revisit the programme and scope rather than merely editing the opening paragraph.

Close the first briefing with a concise record: agreed purpose, audience, constraints, open choices, approval owners and next actions. This creates a useful basis for agency work and reduces repeated discovery. The editable event-brief worksheet in this resource package follows that structure. It is a planning document, not a contract or a technical approval.

Questions that sharpen the brief

Must every detail be decided before contacting an agency? No. Bring the objective and what you know. Label uncertainty so the planning conversation can resolve it rather than conceal it.

Should the format be fixed first? Only if it is a real constraint. Otherwise compare formats against the audience and purpose before committing.

Can one brief cover several events? A shared framework can help, but each event needs its own audience, dates, constraints and approval record. Do not carry assumptions forward without checking them.

What is the next step? Draft one sentence for the objective and list the three most important unresolved decisions. Share those with your planning partner, alongside dates, location and indicative budget. ThreeSixZero enquiries: hello@threesixzero.live.