Event Brief Format: Guide With Two Examples
By RunCue · · 10 min read
Key takeaways
- A standard event brief has nine sections: overview, objectives, audience, budget, timeline, vendors, a pointer to the run of show, contacts, and approvals.
- Keep it to one or two pages. A new planner should be able to read it in ten minutes. Seating charts and cue timings go in linked documents.
- The brief records what was agreed. The event plan is where the work happens, and the run of show is the script for the day. Each one has its own owner and changes at its own pace.
- Corporate briefs name stakeholders and approval chains. Wedding briefs name the family members who make decisions, plus vendor arrival windows and loading entrances.
- Put a name next to every line item, and log who approved each change after sign-off and when. Without that record, nobody can settle a dispute on event day.
An event brief format is the fixed set of sections every brief at your agency uses, so any planner can pick up any event without a handover call. This guide walks through each section, gives you a template to reuse, and annotates two filled-in examples: a corporate summit and a wedding.
What is an event brief and what does it need to include?
An event brief tells your team and vendors what the event is, who it's for, when and where it happens, what the budget covers, and who makes each decision. Everything else is built from it. The run of show, the call sheet, vendor contracts and the schedule for the day all trace back to the brief.
At a minimum it should carry the event overview (type, date, venue, headcount), the goals the client actually cares about, the budget and its approval limits, the audience, key contacts and decision makers, the vendor list, hard deadlines, and known risks such as a late load-in slot or an RSVP cutoff. Keep it to a page or two. Anything you leave out tends to come back as a scramble on the day, and a consistent format stops planners copying conflicting details between tabs. The client brief template is a good starting point.
What is the standard event brief format, section by section?
The standard format has nine sections: overview, objectives, audience, budget, timeline, vendors, a pointer to the run of show, contacts, and approvals. Keep each one short and link out to the detailed working documents. A useful test is whether a planner who has never seen the event can read the whole brief in ten minutes. If they can't, you've started writing the plan.
Section-by-section breakdown
| Section | What it's for | Common mistake |
|---|---|---|
| Overview | Event name, date, venue, client, headcount | Putting load-in details here instead of in the timeline |
| Objectives | What the client will measure | Vague goals like "a great experience" |
| Audience | Who walks in the door | Leaving out accessibility and dietary notes |
| Budget | Approved spend by category | Totals with no cap per vendor |
| Timeline | Key dates: load-in, doors open, strike | No buffer between vendor arrivals and doors open |
| Vendors | Who is booked, their contact, their arrival window | No phone number for the day itself |
| Run of show pointer | A link to the cue sheet | Pasting the run of show into the brief, so the two copies stop matching |
| Contacts | Who to call about what | One contact list for everyone instead of one per vendor |
| Approvals | Who signs off on what | No deadline on approvals, so they land on event day |
What belongs in each section (and what does not)
Decisions go in the brief. Execution goes in the plan. Seating charts and floor plans live in their own documents, cue timings live in the run of show, and the pointer section links to the current version of each. Registration lists and RSVP tracking belong in your event tools.
RunCue keeps tasks, the run of show and the event records in one workspace. Client portals, commercial documents and approvals are on Team and Business, and RSVP forms and guest check-in are included from Personal upward. Pricing has current rates and Founder terms, and What is RunCue? shows how the pieces fit together. If you need ticketing or check-in hardware, confirm those requirements with the provider.
How does an event brief differ from an event plan or run of show?
The brief is the record of what was agreed: objectives, audience, budget, date, venue, and who signs off. The event plan is the working document built from it, with vendor contracts, the floor plan, the seating chart, RSVP tracking and payment schedules. The run of show is the script for the day: cue times, vendor arrivals, doors open, load-in.
Each has a different owner and changes at a different speed. The brief rarely changes, the plan changes every week, and on event day the run of show can change every hour. Trouble starts when one document takes over another's job. The brief starts repeating vendor details, the plan restates the objectives, and soon nobody is sure which copy is current.
Let each document do its own job, and log every change made after approval in one place. The change log template works for this, and it keeps planners, vendors and clients off stale copies.
What does a completed event brief example look like for a corporate event?
The brief itself
Here's a filled-in brief for a made-up corporate event, with notes underneath. The numbers are only examples.
- Event name: Meridian Software Q3 Customer Summit
- Date and venue: Thursday, October 16, 2025, The Foundry Hall, Austin TX. Load-in 7:00 AM, doors open 9:30 AM, last guest out 4:00 PM.
- Client and stakeholders: Dana Reyes (VP Marketing, decision maker on the client side). Agency lead: Priya. Budget ceiling: $85,000, approved.
- Attendance: 250 guests, 12 speakers, 8 sponsors and exhibitors. Registration closes October 9.
- Objectives: 40% of attendees book a demo; sponsors score the event 4 or higher out of 5.
- In scope: run of show, seating chart, floor plan, vendor arrival schedule, check-in, badges, sponsor ROI reporting.
- Out of scope: travel booking, AV rigging design (handled by the client's AV vendor).
- Key deadlines: venue walkthrough Oct 2; final RSVP count to the caterer Oct 10; call sheet sent Oct 13.
Annotations: what each section is doing
The dates line does more work than it looks like. Load-in, doors open and last guest out are three separate times because your vendors, your guests and your venue each care about a different one. If the brief only says "October 16," the caterer plans around the wrong window and the check-in crew turns up after the first vendor. Write the day as a set of boundaries.
The attendance figure has a deadline attached because headcounts go stale. A caterer can't do much with "250" unless they also know it locks on October 10. And if registration data sits in a spreadsheet, someone ends up retyping it into the check-in tool, which is the manual copying the brief is meant to prevent. RunCue keeps guest records and vendor arrivals in the event workspace. When the brief changes, check it against those records and update whatever instructions it affects, because editing the text doesn't change the records for you. Event Day covers how the day itself runs.
The out-of-scope line is the cheapest insurance in the document. Writing down that the AV vendor belongs to the client saves you the call on October 14 where rigging suddenly becomes your problem, at your cost. Every exclusion you write down is a change order you won't have to argue about later. Anything left unnamed tends to come back as unpaid work.
How do you write an event brief for a wedding?
A wedding brief uses the same nine sections as a corporate one. What changes is the content. Stakeholders become family members, and the biggest risk moves from AV failure to vendor timing. Here's a made-up example you can adapt.
A filled-in wedding brief
Client: Priya and Dan, 120 guests, ceremony and reception at one venue, Saturday 5 October 2024. Family contacts: the bride's mother decides ceremony timing, and the best man handles speech order and passing the mic. Budget: $68,000 all in, with catering and florals already contracted. Vendors: florist at 1:00pm, cake delivery at 2:30pm, photographer at 3:30pm, DJ load-in at 4:00pm, each with a phone number and a loading entrance noted. Seating: two exceptions at the top table (divorced parents seated apart), everyone else assigned by table number. Cues for the day: processional at 4:30 sharp, first dance after the toasts, last call at 11:00pm, load-out by midnight.
Where the wedding brief diverges from the corporate one
Corporate briefs name stakeholders and approval chains. Wedding briefs name the family members who make decisions, because the person paying often isn't the person deciding the seating chart. For both, link to the current run of show instead of copying it into the brief. At a wedding, share the cues the coordinator needs through Event Day.
RunCue includes RSVP forms and guest check-in and floor plan editing and seating assignments from Personal upward. Try the guest workflow and the exports you'll need, and check what support you'll get, before you commit to any tool for an event.
What common mistakes make an event brief useless to vendors and teams?
Four mistakes do most of the damage. The first is missing owners. If a line item has no name next to it, it sits there until someone notices the vendor arrival was never confirmed. The second is stale copies. When planners edit their own versions, the florist ends up working from last Tuesday's floor plan. Keeping one shared document fixes that, and it's the same reason teams move from spreadsheets to tools like Airtable.
The third is duplication. A brief that repeats the run of show gives you two documents to keep in step, and they won't stay in step for long. Keep timings in the run of show, keep scope, budget and decisions in the brief, and link the two. The fourth is having no change log. When the client moves doors open from 6:00 to 6:30, write down who approved it and when. Otherwise there's nothing to point to when someone disputes the time on the day.
How do you adapt a free event brief template to your own event type?
Start by filling in the template for an event you've already delivered. Delete every field nobody used, and add the decisions your team actually needed: load-in times, when doors open, check-in staffing, and a link to the run of show. Agreed decisions go in the brief and the execution detail stays in the linked plan.
Then make a version for each event type. Corporate briefs need sign-off blocks for stakeholders and speaker logistics. Wedding briefs need the status of the seating chart and rules for family contacts. Keep the nine sections underneath the same, so planners can switch between events without learning a new format.
Keep one approved version with the event records. Log each change, give someone the job of updating the tasks or cues it affects, and check that the people running the event have seen the new version. RunCue's Team and Business plans include client portals and approvals alongside the run of show, and pricing lists plan limits and Founder eligibility. Editing the brief won't rewrite the schedule for you, so plan for that step.
Some requirements need specialist tools, such as ticket sales, venue engineering drawings or dedicated check-in hardware. RunCue includes floor plan editing and check-in, but those won't cover every venue's technical requirements or every piece of hardware, so confirm them early.
FAQ
How long should an event brief be?
One to two pages. A new planner should be able to read it in ten minutes and run the event from it. If it's longer, you're probably repeating the run of show or the plan, and those repeated sections will go out of date. Keep seating charts and cue timings in linked documents.
Who writes the event brief, the client or the planner?
The planner writes it, with input from the client. The client supplies the objectives, the budget ceiling, the audience and the named decision makers. The planner turns that into the nine sections and owns the document from then on. Every line item still needs a named owner, or things like an unconfirmed vendor arrival slip through.
Can I use one event brief template for both corporate events and weddings?
Yes. Keep the sections the same and change what goes in them. Corporate briefs need stakeholder sign-off and speaker logistics. Wedding briefs need family contacts who can make decisions, seating exceptions, and vendor arrival windows with loading entrances. With the same nine sections underneath, planners can move between event types easily.
What is the difference between a client brief and an event brief?
A client brief captures what the client wants: goals, audience, budget range and constraints, usually before anything is booked. The event brief is the working document built from it, with confirmed dates, the venue, the vendor list, deadlines and approvals. The client brief feeds the event brief, and the event brief is what your team and vendors work from.
How do I keep an event brief updated after the client changes something?
Log every change made after approval in one change log, with who approved it and when. Keep the brief attached to the event record so edits happen in one place instead of in emailed copies. If the client moves doors open from 6:00 to 6:30, that log entry is what you point to when someone disputes the time on the day.