Practice · Client relationships
Managing client expectations
Live events have no second take. How to set scope, approvals, budget honesty and contingency so the brief and the show room agree — from Orora's productions across the GCC.
Why live events punish vague agreements
Every other medium allows a second pass. A film gets re-edited, a campaign gets optimised, a website ships a fix. An event happens once, in front of the people who matter most to the brand, and then it is over.
That single characteristic is why expectation management is a production discipline rather than a soft skill. The practices below are the ones we hold to across launches, national celebrations and conferences in the Gulf.
Start from the outcome, not the deliverables
Most expectation problems begin at the brief. A client asks for a stage, a screen and a launch film; what they actually want is press coverage, a room that feels premium and a product moment guests will film. Deliverables are negotiable, outcomes are not — so write the outcomes down first and get them agreed in the client's own words.
Once the outcome is explicit, every later trade-off has a reference point. Cutting a second screen stops being a loss and becomes a decision measured against whether the room still delivers the moment.
Agree before design
- Two or three success measures agreed in writing before design starts
- The single hero moment named — the thing guests will remember and share
- Non-negotiables separated from nice-to-haves on the first scope document
- One decision-maker identified per workstream on the client side
Be uncomfortable about budget early
The most expensive conversation in events is the one postponed. Ambition set against an undisclosed budget produces designs that must be dismantled later, and every dismantling costs trust as well as time.
We prefer showing three honest tiers against a real number: what the budget buys comfortably, what it buys with risk, and what genuinely sits out of reach. Clients rarely object to a limit they helped define; they object to discovering it two weeks before load-in.
Put in the numbers
- Contingency stated as a line item, typically 10–15%, not hidden in margins
- Currency, freight and customs assumptions written into the quote
- Change-order pricing agreed before the first change is requested
- Clear cut-off date after which scope changes cost time as well as money
Approval gates and the content freeze
Live production runs backwards from an immovable date. That makes approvals structural, not administrative: content freeze, rehearsal lock and technical lock all have to sit far enough from show day for the crew to actually build what was approved.
Name the gates in the schedule and state plainly what happens if one slips. A film approved 48 hours before doors does not get colour-graded, checked on the real screen or rehearsed with sound — and that is a quality decision the client should make knowingly, not discover on the night.
Lock the calendar
- Content freeze dated and signed, with a named approver
- Rehearsal schedule protected in the client's calendar, not just ours
- Version control with one channel for approvals — no side-thread sign-offs
- Written consequence attached to each missed gate
A predictable rhythm beats constant contact
Anxiety grows in silence, so replace ad-hoc reassurance with a rhythm: a weekly status note, a single risk register everyone can read, and a short daily call in show week. Clients stop chasing when they trust the next update is coming.
Keep the risk register blunt. A risk written down and owned is a managed risk; the same risk mentioned verbally in a corridor is a surprise waiting for show day.
Set the cadence
- One weekly written update covering progress, decisions needed and risks
- Live risk register with owner and mitigation per line
- Escalation path agreed for on-site decisions during the show
- Show-week contact list with roles, not just names
On site, and the day after
During build, the client's expectation shifts from documents to what they can see. An empty hall at 40% build looks alarming to anyone who has not lived through one, so walk them through it and say what will change by when. A guided site visit prevents a dozen panicked messages.
After the show, close the loop with evidence: measured results against the agreed outcomes, what we would repeat, what we would change. That report is what converts a delivered event into a returning client.
Close it properly
- Scheduled client walk-through with an explanation of build stages
- Single on-site point of contact with authority to decide
- Snag list handled quietly during rehearsal, not raised at doors
- Post-event report within two weeks, measured against the original outcomes
The short version
Agree outcomes before deliverables. Talk about money before design. Date the approvals and defend them. Communicate on a rhythm rather than on demand. Then prove what happened with numbers.
None of it removes pressure from show day — it moves the difficult conversations to the point where they are still cheap.
Planning something with a fixed date
We scope, design and deliver live experiences across the UAE, Saudi Arabia and the GCC — with the schedule and the numbers on the table from the first meeting.