Event Brief Template: Budget, Vendors and Run-of-Show
Turn an event idea into an executable brief with objective, audience, budget, venue, permissions, vendors, milestones and day-of controls.
A strong event plan connects the objective to the guest experience, budget and execution owners. Vendor selection becomes easier when the brief and acceptance criteria are written first.
Define success before sourcing
State the event type, purpose, date window, city, audience, expected count and must-have outcome. Separate fixed requirements from preferences so trade-offs can be made responsibly.
Create budget buckets for venue, production, talent, food, logistics, permissions, staffing, marketing, contingency and taxes. Keep an approval owner for every change that affects cost or scope.
Contract the deliverable, not the promise
For each vendor, document scope, quantity, specification, milestone, access requirement, payment schedule, cancellation terms and proof of completion. Verify identity, experience and applicable permissions.
A low quote with missing elements can become expensive during execution. Compare quotes on the same scope and record exclusions explicitly.
Operate from one run-of-show
Build a timed sequence covering load-in, technical checks, rehearsals, guest entry, programme cues, service, emergency contacts, close and load-out. Assign one responsible owner to each cue.
After the event, reconcile purchase orders, changes, completion evidence and feedback. Capture reusable learning while it is still fresh.
Worked example: a 100-guest half-day event
This is a fictional planning exercise, not an Earnifyy package or a market-rate quote. The purpose is to compare quotes on the same scope and expose exclusions before approval.
| Budget line | Illustrative assumption | Planning amount |
|---|---|---|
| Venue | One half-day booking | ₹20,000 |
| Catering | 100 guests × ₹450 | ₹45,000 |
| Sound and microphones | Specified equipment and operator | ₹10,000 |
| Crew and registration | Agreed staffing window | ₹8,000 |
| Transport and setup | Agreed scope | ₹7,000 |
| Base subtotal | Sum of the five lines | ₹90,000 |
| Contingency | 10% of base subtotal | ₹9,000 |
| Working ceiling before applicable taxes | Base plus contingency | ₹99,000 |
Compare the scope, not the headline price
Give every vendor the same guest count, access time, event duration, equipment list and delivery responsibilities. Ask whether taxes, power backup, travel, setup, cleanup and overtime are included. A ₹10,000 equipment quote with an operator is not directly comparable to a ₹9,000 equipment-only quote. Add exclusions to a separate comparison column before choosing.
Define a count-freeze rule
Record when the catering count becomes final, how late additions are priced, and whether a reduction changes the bill. A change from 100 to 120 guests at the illustrative ₹450 rate adds ₹9,000 before any other changes. That alone uses the entire example contingency; it does not cover extra chairs, staff or taxes.
Make the run-of-show operational
For each segment record start time, finish time, owner, location, equipment and backup action. Place setup and sound check before guest arrival. Give registration, stage and catering teams a single approved schedule and a named decision-maker. Do not leave all exception handling to a shared group chat.
Close against agreed evidence
Check the actual count, accepted deliverables, approved changes and overtime against the order. Store vendor bills and written acceptance. Dispute unresolved items before marking settlement complete; a deposit transfer alone is not evidence that the service was delivered.
Use your own figures
Copy these fields into your planning sheet: Budget line · Vendor · Quantity · Unit rate · Tax included · Exclusions · Approved total · Delivery time · Owner · Acceptance evidence · Payment reference. Keep private customer and payment details in your authorised workspace.
Download the blank planning sheet (CSV)Before you proceed
How much contingency should an event keep?
It depends on event risk and certainty. Keep a separately approved contingency rather than hiding it inside vendor scopes.
What is the first document vendors should receive?
A common written brief with scope, dates, quantities, service levels and acceptance criteria.
Use the guide. Then choose the right public pathway.
Share this page with someone who needs the checklist, or continue to EARNIFYY's login-free public guidance.