Event Management Brief: The Template That Runs Your Event
By RunCue · · 9 min read
Key takeaways
- Write the brief before you contact any vendor, so quotes are priced against real scope.
- Give each vendor one row per deliverable, with a due date, a cost and the point at which payment is due.
- Build the run of show from the brief's timeline: reorder it by clock time and turn each item into a cue with a time, an action, an owner and a dependency.
- Give each event one named brief owner, and send every client change through a single channel that gets logged.
- Version the brief. Update the date on every edit and send out the affected documents the same day.
An event management brief should be the document your team works from every week. Too often it's a kickoff memo that nobody opens again. Written well, each section turns into something you use: a table of vendor commitments, a list of floor plan constraints, and the outline of your run of show. This walkthrough goes through the template section by section. Start from the client brief template and fill in the decisions below.
What should an event management brief include before you contact vendors?
Three sections need to exist before you talk to any vendor: the client's goals and hard constraints, the budget and who approves spending, and the picture of the guests. The rest can be refined later. If a vendor hears a vague brief, they'll quote against their own assumptions, and you'll be stuck with them.
Client goals and hard constraints
Write down what the event has to achieve for the client and the things that can't move: venue status, date, capacity, insurance requirements and anything already promised. If the client has promised a seated dinner for 300 in a room that holds 200, that conflict belongs in the brief. You don't want to discover it on a phone call two weeks before load-in.
Budget envelope and approval chain
Write the total budget, what it covers (production, food and drink, vendor fees, contingency) and who approves spending at each threshold. Vendors price differently when they know the budget is fixed rather than a rough guide. And once the approval chain is written down, your planners stop chasing sign-off over email.
Guest count, arrival pattern and VIP list
A headcount on its own doesn't tell you much. Record the expected number, when RSVPs are due, how arrivals spread across the day, how many walk-ins you can absorb, and the VIPs along with whoever looks after each one. This section feeds the seating chart, check-in staffing and vendor arrivals. Turn the actions into tasks with owners and deadlines in task and project management.
When should you write the brief relative to vendor selection?
Before you contact any vendor. A draft brief sets the load-in windows, headcounts and floor plan constraints you need for an RFP vendors can price properly. Without one, every quote is a guess, and correcting those guesses later costs money.
Think of the brief you send with the RFP as version one: scope, dates, guest numbers and hard constraints. It doesn't need final catering numbers or a finished run of show yet.
What changes once vendors sign
Once contracts are signed, the vendors' commitments become fixed. Write the caterer's arrival time, the AV power needs and the rigging deadlines back into the brief, then carry them into the schedule. RunCue's venue workflows help with that handover. From here on, changes to the brief go through a written change note rather than a quick chat in the corridor.
How does the brief feed into your floor plan and seating decisions?
Before anyone opens a drawing tool, the hard constraints in your brief become a list of floor plan requirements. Write down venue capacity, fire exits, how wide the load-in door is and when vendors arrive, as fixed facts. A ballroom for 300 with two exits and one loading dock gives you a very different plan from the same headcount in an open warehouse.
| Brief constraint | Floor plan output | Seating output |
|---|---|---|
| Headcount and VIP list | Zones for each section | VIP tables closest to the stage |
| Exits and minimum aisle widths | Clear aisles, no blocked exits | No seat behind a pillar |
| Load-in window and dock access | Vendor booths near the doors | n/a |
| AV and sightlines | Stage position, screen height | Seats angled once they're past 30 degrees |
Once the zones are set, turn them into a seating chart and name the people responsible: who seats the VIPs, who handles changes on the day, where walk-ins go. Keep one current guest list and check every change against the room layout before the event.
RunCue's floor plans and seating tools let you lay out the room, seat guests from the event's guest list, check capacity and save revisions. Changing the seating won't change the run of show, so whoever owns the affected cues needs to review them. Check any technical requirements specific to the venue with the venue itself.
How do you turn the brief into a run of show?
You don't have to write the run of show from scratch. Take the timeline sections of the brief, put them in clock order and break them into cues. If the brief says load-in at 2:00 PM, vendors in by 4:00 PM, doors at 6:30 PM and last guest out by 10:00 PM, you already have the outline. Working from the brief also means you're starting from the version everyone signed off.
Cue-by-cue structure
Turn each commitment in the brief into a cue with four fields: time, action, owner and dependency. "Caterer starts plated service at 7:15 PM, once the ballroom reset is done" is a cue. A paragraph about how dinner should flow isn't. Every cue needs one named person, because on the day nobody acts on something assigned to "the team."
Vendor arrivals and doors open
Vendor cues go in the run of show. Email threads are where they get lost. Take each vendor's arrival window and setup time from the brief, then order them so nothing gets in the way of doors open. RunCue's run of show works alongside Event Day to coordinate the schedule, check-in, arrivals and open issues. Whenever the brief changes, review the cues it touches.
What does the brief need to cover for event vendor management?
Commitment table format
Give each vendor one row per commitment: the deliverable, the section of the brief it comes from, the due date, the cost and when payment is due. "AV package per floor plan v3, due on load-in day, 50% on delivery and 50% after doors open" tells your planner and your bookkeeper the same thing. If a commitment can't point to a section of the brief, it's scope creep, and you can cut it.
Tie payments to moments you can check: a deposit when the commitment is signed, the balance at the agreed delivery point, and the final invoice once the agreed checks are done. Put these terms in the commitment table and keep approvals and invoices with the event's commercial records. RunCue's budget and commitments tools support this. Client portals, commercial documents and approvals are on Team and Business, and pricing has current rates and Founder eligibility. RSVPs and check-in sit in guest management. Keep legal review and signed contracts in your usual document process.
Who owns the brief and who signs off on it?
Give every event one named owner: a planner who holds the document, merges edits and decides when a change is real. With three events running at once, a brief anyone can edit will give you two versions of the run of show by load-in week.
The owner writes the sections that feed vendor commitments and the floor plan, and teammates add the cue detail for the day. Owning the brief means being responsible for the current version. It doesn't mean writing every word.
Client sign-off and change requests
Get the client to sign off the budget, guest count and floor plan constraints in writing, once, before you brief vendors. After that, every change comes through one channel, and a client email only becomes an edit to the brief when the owner logs it. That way vendors keep quoting against one document instead of an email thread.
How do you keep the brief updated as event details change?
A brief you wrote once and never touched again just tests everyone's memory. Version it: update the date on every edit, note what changed and who approved it, and send out the documents it affects the same day. If a vendor's arrival time moves, the brief, the call sheet and the run of show should all change together, not weeks apart.
One brief or three separate documents?
The trouble with separate documents is that they slowly stop matching. The schedule, the guest list and the check-in records each get updated at different times, and the mismatch shows up when guests arrive. Keep one approved brief, and when a decision changes, review the floor plan, seating chart and run of show it affects. Note who updated each one.
RunCue keeps tasks, vendor commitments, floor plans, guests and the run of show in one event workspace. The brief owner still has to carry approved changes into the records they affect, because editing the text doesn't update everything else. Use the event change log to record the decision, the owner and the follow-up. If you keep a separate venue drawing, agree who updates it and when the new version goes out.
What makes an event brief commercial-grade versus an internal note?
Judging tools: cost, export, support
When you compare tools for running briefs, look at what the whole workspace costs, including features locked behind higher tiers. Check that you can get your records out in a format you can use. And find out which support channels exist and how quickly they answer, before event week rather than during it.
Where RunCue falls short
RunCue's client portals, commercial documents and approvals are on Team and Business. Check pricing for current rates, workspace limits and Founder eligibility, and don't assume a promotional rate applies to every workspace. Test the exports you need and confirm what support you'll get before you commit. Floor plan editing and guest seating are included from Personal upward, but check them against your venue's drawing requirements. Where RunCue fits best is keeping tasks, guests, vendor commitments and the cues for the day in one workspace.
FAQ
Can I use one event management brief template for weddings and corporate events?
Yes. Keep the sections fixed and change what goes in them. Goals, budget, the guest picture, vendor commitments and the timeline apply to both. A wedding swaps sponsor deliverables for family VIPs and the people looking after them, but the structure, sign-off chain and versioning rules should be the same for every event you run.
How long should an event management brief be?
Long enough that every section turns into something your team uses, and short enough that planners actually read it. Most land between two and five pages: hard constraints, the budget with approval thresholds, the guest picture, the vendor commitment table and an outline of the timeline. Anything beyond that usually belongs in an attachment.
What is the difference between an event brief and a run of show?
The brief records the decisions and the run of show carries them out. The brief says load-in is at 2:00 PM and doors open at 6:30 PM. The run of show puts those in clock order and breaks them into cues, each with a time, an action, an owner and a dependency. Building it from the brief means you start from the version everyone signed off.
Should the client see the full brief or just a summary?
The client signs off the budget, guest count and floor plan constraints in writing before vendors are briefed. They don't need the vendor commitment table or your internal cue detail. After sign-off, their changes come through one channel, and an email only becomes an edit to the brief when the owner logs it.
How do I attach vendor contracts to a brief without losing track of versions?
Keep the contract in your legal or document tool and refer to it from the commitment table in the brief, with one row per commitment showing the deliverable, due date, cost and payment terms. Update the brief's date on every edit and note what changed. The table points to the contract, and the contract stays a separate document.