Skip to main content
All articles

How to Write a Marketing Event Brief Your Team Can Execute

By RunCue · · 10 min read

Key takeaways

  • A marketing event brief is ready for vendors when it answers five questions: what the event is, who it's for, what success looks like, the budget ceiling, and when load-in happens.
  • Turn vague goals into two or three KPIs you can measure, and name where each number will come from.
  • Give a range and a hard ceiling for each budget line, and don't send numbers to vendors until they're approved internally.
  • Give each section of the brief one named approver so sign-off happens in parallel, then lock the approved version so the scope stays put.
  • Seating charts, floor plans and the run of show come after you've chosen vendors. In the first brief they're placeholders with due dates.

A marketing event brief turns a client's goals into tasks, budget lines and a run of show your planners can work from without guessing. Each section needs to be specific enough that vendors and your own team get venue capacity, catering numbers and arrival times right from it. This guide gives you the template, what goes wrong when each field is left blank, and how the brief hands over into planning.

What is a marketing event brief and who should write it?

A marketing event brief says what an event is for, who it's for, what success looks like, and what the budget and timeline are. Call sheets, floor plans and vendor contracts all come after it, so if the brief is vague, everything built from it will be vague too.

Brief vs proposal vs run of show

The brief sets out what the event is meant to do. The proposal sells your plan to the client and puts a price on it. The run of show schedules the day itself, minute by minute, from load-in to doors open to the last guest leaving. People mix these up all the time. Agencies send the client a draft run of show when what the client needs first is a brief they can sign off.

Who owns it when an agency runs the event

When the event is run in house, marketing owns the brief. At an agency, the account lead owns it and the operations lead delivers it. Ownership matters because planners already lose hours copying information between tools that don't talk to each other. Have one named owner and one approved version. Our client brief template is set up that way.

What must a marketing event brief include before it goes to vendors?

A brief is ready for vendors when it answers five questions without anyone needing a follow-up call: what the event is, who it's for, what success looks like, what it can cost, and when load-in happens. Anything missing gets priced as a guess, and the guess comes out of your margin.

The copy-ready template

Fill this in before you send anything to a vendor:

  • Event name and type (conference, activation, gala)
  • Client and key stakeholders, with the decision makers named
  • Date, venue status, and the time doors open
  • Main goal (registrations, qualified leads, retention)
  • Attendance target and when RSVPs are expected
  • Budget ceiling as a firm number
  • Load-in and load-out windows
  • Non-negotiables (brand rules, accessibility, security)
  • Known risks (weather, vendor conflicts, a guest list that changes late)

Field by field: why it matters and what goes wrong

FieldWhy it mattersWhat usually goes wrong
GoalEvery later decision depends on itIt's vague ("great event"), so vendors bid on a scope they made up
Budget ceilingVendors quote against itA range like $30k to $50k gets read as $50k every time
Load-in windowDrives labor and truck quotesLeft out, then turns up as a rush fee on the invoice
Attendance targetSizes catering, badges and check-inWritten as a hope instead of a minimum and maximum
Non-negotiablesSaves reworkNever written down, so the vendor's default breaks a brand rule

The budget ceiling is the field agencies most often leave soft. If your brief gives vendors numbers before they're approved internally, you've skipped a step. In RunCue, each event's budget lines and vendor commitments sit in the event record, so you check vendor quotes against approved lines instead of against memory (budget commitments).

What can wait until after vendor selection

The seating chart, the run of show and the floor plan can all wait. They depend on which vendors you hire and what the venue allows. Put a placeholder for each in the brief with a due date, and turn them into tasks once a vendor has signed. Agencies that write them early often end up retyping speaker bios and exporting registration lists again, because the early version was built on assumptions that later changed.

How do you set measurable goals and KPIs in an event brief?

A vendor can't plan against "generate leads." Turn it into a number with a deadline, such as "150 qualified badge scans at check-in and 40 booked follow-up meetings within 10 days." Whoever builds the registration flow, prints the badges or draws the floor plan needs that number to size the job.

Pick two or three numbers, not ten

With only two or three KPIs you're forced to choose what matters, and you can still track them on a busy event day. Every extra metric is another number that has to be copied between tools and can end up wrong. A sensible set is the share of registrants who attend, qualified leads, and one revenue or cost per lead figure. Map each one to a line in your event planning checklist so it doesn't get lost at handover.

State how each number will be measured

For each KPI, name the system the number comes from and the format you'll export it in. Be upfront about attribution, which is often self-reported. Say whether "leads from this event" means badge scans, CRM records tagged to the event, or a survey afterwards. Agreeing the method in the brief avoids an argument after the event about whose number counts.

How detailed should budget, audience, and logistics sections be?

Detailed enough that a vendor can price the job without calling you, while still leaving the craft to them. Three sections do most of that work.

Budget: ranges with hard ceilings

Give a range and a ceiling for each line, for example catering at $75 to $95 a head and never above $110. Vendors will price up to any ceiling you publish, so mark which numbers are fixed and which are open to negotiation. Name the approval threshold too, for example that anything over $2,500 needs the client's sign-off, so work doesn't stall halfway through.

Audience: counts and constraints, not personas

Vendors need the headcount, when people will arrive and the hard limits: 300 guests, 60% arriving in the first 45 minutes, 12 wheelchair-accessible seats, no under-18s after 9pm. A caterer or an AV tech can't do anything with a persona. Numbers and times are what they work from.

Logistics: load-in, doors, and hard stops

Give the load-in window, vendor arrivals, doors open and the hard finish as clock times. They become your run of show, and the cues your team tracks in RunCue from the call sheet through to check-in. One thing RunCue won't do is price your budget lines for you, so the numbers still come from your brief.

How do you get stakeholder sign-off on an event brief quickly?

Send one brief, once, with a deadline. Sign-off gets slow when each stakeholder replies to a different draft and the third version of the budget ends up arguing with the second version of the audience section. Planners already spend too long copying information between tools and tabs, so don't add an approval process that creates more of it.

One approver per section

Give each block a named owner. The client's marketing lead owns the goals and KPIs, their finance contact owns the budget, and your operations lead owns the logistics and the run of show. Each person signs off only their own section, all at the same time instead of one after another. If a section has no owner, it isn't ready to send.

Version the brief, don't email it

Keep the brief in one shared document with a version number and a line at the top saying what changed. Run approvals through your project tool instead of email threads. Once it's signed off, lock it. Any change becomes a new version that needs approving again, which is what stops the seating chart and floor plan quietly growing in scope.

What are the most common reasons event briefs fail in execution?

The brief approved but nobody worked from it

A lot of briefs stop being used the moment they're approved. The client signs off, the PDF gets filed, and the planners go back to their own notes, spreadsheets and inboxes. If your team doesn't open the brief on event day to check the run of show, you wrote a proposal.

Too many tools, and someone stuck retyping between them

When ticketing, check-in, schedules and email each live in a different tool, they stop agreeing with each other, and you find out when guests are queuing at the door. Then someone has to retype RSVP counts, speaker bios and vendor arrival times from one tab to the next. That retyping is how load-in times and seating charts end up wrong.

No owner per line item

If the brief says "catering: confirmed" with no name next to it, nobody chases the caterer when their arrival slips. Every line item needs one owner and a deadline. Otherwise it stays as "someone's on it" until the doors open. In RunCue, tasks have a named owner and a deadline on every plan. Team adds client portals and approvals, though that still only covers part of your setup, and you may keep using something like Airtable alongside it (pricing).

How does an approved brief flow into your event planning workflow?

From brief fields to system records

Once the brief is approved, each field should become a record that someone owns. The audience section becomes RSVP tracking with a target and an owner. The budget section becomes line items, with committed and estimated amounts and an approval threshold on each. The logistics section becomes tasks such as load-in windows, vendor arrivals and check-in staffing, each with a named person and a deadline. The timeline becomes the run of show, with every cue given a person and a clock time, so the team checks progress against the plan instead of relying on memory.

If that conversion happens by hand, in a document nobody opens after sign-off, the brief is forgotten within a week and the team goes back to spreadsheets and inboxes. This step decides whether the brief gets used or just filed.

Running this in RunCue

In RunCue, the brief, the budget lines, the tasks and the run of show sit in the same event record instead of a PDF. A planner still turns the approved brief into those records: budget decisions become budget lines, owners become task assignees, and the timeline becomes cues your team can tick off on the day. Editing the brief doesn't create or change them for you. Client-facing pieces such as the portal, proposals, invoices and approvals are on Team and Business (pricing).

RunCue doesn't do ticketing, badge printing or check-in hardware. If your events rely heavily on technology for attendees, you'll run a second system alongside it, so allow time for keeping the two in step.

What still lives outside the tool

Vendor contracts, insurance certificates and venue paperwork stay wherever your legal process already keeps them. The path from brief to run of show is the core of the work. For everything around it, decide on purpose where it lives.

FAQ

How long should a marketing event brief be?

Two to three pages, or one page for a small event. Answering the five core questions fully matters more than length. If your brief runs past four pages, you're probably writing things like floor plans or a draft run of show that belong after you've chosen vendors. Leave placeholders with due dates for those instead.

Can I use the same event brief template for a trade show booth and a hosted dinner?

Yes. The fields are the same for both: goal, attendance, budget ceiling, load-in window and non-negotiables. Only the values change. A booth brief might aim for 150 qualified scans, while a dinner might aim at retention or moving deals forward. Keep one template, fill it in for each event, and avoid adding fields for one event type that nobody else fills in.

What is the difference between an event brief and a creative brief?

An event brief covers logistics and money: headcount, the budget ceiling, load-in times and vendor constraints. A creative brief covers the theme, visual direction, messaging and tone. They overlap on audience and goals, but a caterer prices from the event brief and a designer works from the creative one, so keep them as two documents.

Should I send vendors the full brief or just an RFP summary?

Send the full brief, minus anything internal such as your margin or negotiation notes. Vendors treat missing information as risk and pad their quotes to cover it. The brief should already have firm budget ceilings, load-in windows as clock times and minimum attendance. If a section isn't settled yet, mark it as pending instead of leaving it out without saying so.

How do I write a brief when the client hasn't confirmed budget yet?

Write down a working assumption with a hard ceiling and label it as unapproved, for example "assumed $40k ceiling, waiting for finance sign-off." Don't send numbers to vendors before they're approved, because their quotes will anchor to whatever ceiling they see. Send the budget section to the finance approver at the same time as everything else, so it's settled before you contact vendors.

Run your next event from one plan

Tasks, guests, vendors, budget and the run of show in one place your whole team works from.

More articles