Event Management
Events, vendors, budgets and client schedules — so the real margin on a job is known before the last vendor invoice arrives.
An event company's numbers are only honest after the event, which is far too late. The client was quoted a figure, the brief grew — a second stage, extra lighting, a changed menu — and the vendor invoices came in over the following three weeks. By the time everything has landed, the job that felt profitable has a margin nobody can explain and nobody can learn from.
What gets built is a per-event cost and schedule record: a quotation built from costed line items, vendors booked against the event with their rate and advance, scope changes logged with a price at the moment they are agreed, and a running budget against actuals. The production schedule and the crew assignment sit alongside, because on the day the sheet everyone works from matters as much as the margin.
What it fixes
- Quotations built from memory and last year's rates, so a job is priced before anyone knows what it will cost
- Scope creep agreed over phone calls — one more stage, extra lights, a bigger backdrop — and never priced, which is where the margin goes
- Vendor advances paid out of client advances with no event-wise record, so cash flow and profitability are both opaque
- Vendor invoices arriving weeks after the event, by which point the client has settled and the real cost is unarguable
- Equipment and staff double-committed across two events on the same weekend, discovered during load-in
- Production schedules on WhatsApp in several versions, with the crew working from whichever one they happened to see
- Client advances and payment milestones tracked loosely, so a final payment is chased for weeks after delivery
What gets built
A starting point, not a fixed list. The build is scoped to your own process before anything is written.
Event file and quotation
One file per event with brief, venue, dates and client, and a quotation built from costed line items — stage, sound, lighting, decor, catering, crew — so the quoted price has a known cost sitting behind it.
Change log with pricing
Every addition or change to the brief recorded with its cost, price and who approved it, at the time it was agreed. This single discipline recovers more margin than any other part of the build.
Vendor and subcontractor management
Vendors booked against the event with agreed rate, advance paid, balance due and confirmation status, and a vendor-wise account so the payable position is current rather than discovered.
Budget against actuals
Estimated cost against committed and paid cost per line, with a live margin that updates as vendor bills land instead of resolving three weeks later.
Resource and crew calendar
Owned equipment and crew committed per event on a calendar, with clashes flagged — which is what stops two jobs being accepted for the same weekend on the same sound system.
Production schedule and client billing
A single run sheet per event with timings, responsibilities and vendor call times as the one current version, plus client advance and milestone billing with the balance due tracked to settlement.
Who this is for
Event management and production companies running roughly a few events a month and up, with subcontracted vendors and per-job profitability to defend. Wedding planners, corporate event producers, exhibition and conference organisers and sound and lighting companies all fit. A single planner doing one wedding a month, mostly personally, does not need this — a spreadsheet per event and a careful eye will do, and the money is better spent elsewhere. If you are purely a venue with a fixed rate card rather than a producer buying in vendors, the marriage hall and banquet build fits you better than this one.
Questions
Our clients change things constantly. Can software fix that?
No. It can make the change cost visible at the moment it happens, which changes the conversation but not the client. The value is that when a client asks for a second stage on the Tuesday, the price is recorded on the Tuesday rather than absorbed. If your team will not log changes as they are agreed, this build will not help you, and that is a working-practice decision more than a software one.
Can we use it on site during an event?
The schedule and crew views should be built for a phone, because that is where they will be read. But be realistic: during load-in nobody updates software. On-site use works for reading the run sheet and ticking off vendor arrivals, not for data entry. The costing gets updated back at the office, and the build should assume that rather than pretend otherwise.
We work with different vendors on every job.
That is normal and it is fine — vendors get added as they are engaged, and the useful thing that accumulates is the rate and reliability history, which makes the next quotation faster and better founded. Where it is worth more caution is if your events are entirely one-off with no repeating line items at all; then the quotation library adds little and the build should be scoped down to costing, vendors and schedule.
Tell us how your event company runs.
We scope it first — what it takes, how long, what it costs. No obligation.