Key Takeaways
- Eight of ten common production mistakes originate in pre-production decisions, not in show-day execution
- The most expensive mistakes (show delays, visible AV failures, speaker confusion on stage) are all preventable with a complete technical advance
- Budget cuts made to production rather than to other event categories consistently produce the highest visible impact on event quality
The ten mistakes
1. Cutting the technical rehearsal. The show-day discovery of confidence monitor failures, slide aspect ratio incompatibilities and microphone positioning problems that a 2-hour technical rehearsal would have caught and resolved in 45 minutes each. Prevention: budget the technical rehearsal as non-negotiable from week 1.
2. Speaker content received on show morning. The content brief that says "please send slides 48 hours before" is ignored by three of five speakers. The one who sends slides with embedded fonts the playback system cannot render crashes the presentation. Prevention: lock the content submission deadline and test every file as it arrives.
3. Undefined microphone protocol. Two speakers both walking on stage and reaching for the same handheld microphone. Or a lapel microphone left on during a speaker's bathroom break. Prevention: a microphone handoff protocol that is briefed to every speaker and confirmed in the run sheet.
4. No show-caller on a 500-person event. The production manager attempting to simultaneously manage vendors, answer client questions and call show cues. The result: late transitions, missed cues, a show that drifts. Prevention: treat the show-caller role as non-negotiable above 200 pax.
5. LED wall resolution mismatch. A presentation designed at 1920×1080 displaying on a P3.9 LED wall with a native resolution of 3,840×2,160 — the client cannot understand why their 4K presentation looks pixelated. Prevention: share the LED wall's native resolution and required content specifications with the client's content team at week 8.
6. HVAC not factored into room acoustics. A PA system specified for a quiet room deployed in a ballroom where the air conditioning produces 52 dB SPL ambient. The rear delegates cannot understand the speaker. Prevention: measure the room's ambient noise floor during the site visit, before the PA is specified.
7. No front-fill speakers. A line array that delivers excellent coverage from row 4 to the back provides inadequate sound level to rows 1–3 (too close to the main system). Front-fill speakers cost ₹40,000–80,000 to add to a PA specification. Prevention: include front-fill in the first PA draft for any room with rows within 5 metres of the main PA.
8. Venue exclusivity clause discovered after production is designed. The set design that requires an external structural staging supplier is in conflict with the venue's exclusive structural supplier agreement. Prevention: review the venue contract for all exclusivity provisions before any supplier is engaged.
9. Late catering service disrupting programme timing. The starter arrives during the CEO's address. Prevention: the catering service sequence must be in the run sheet, called by the show-caller, and coordinated with the kitchen manager from week 4.
10. No contingency budget. A power failure during load-in requires an emergency generator rental at short notice. The contingency is 3% of budget — ₹1.8 lakhs on a ₹60 lakh event. The emergency generator costs ₹2.2 lakhs. Prevention: 8–10% contingency from the first budget draft.
Failure 1: Content doesn't play on the playback system
A speaker's video file — embedded in their PowerPoint, exported at 4K resolution, encoded in a codec the playback laptop doesn't have — fails to play on the production system. The failure mode is consistent: the speaker built their presentation on a Mac, exported at H.265 codec, and the production playback runs Windows with a QuickTime installation that is 3 years old. Prevention: issue a content specification at week 8 (codec, maximum resolution, audio format, aspect ratio). Test every file as it is submitted. Not on a personal laptop — on the production playback system.
Failure 2: PA feedback during the keynote
The CEO begins their address and the PA system produces a high-frequency squeal. The cause: a wireless lapel microphone positioned too close to an on-stage monitor speaker, combined with an audio engineer who is not watching the gain structure of the channel when the speaker picks up the microphone. Prevention: a dedicated audio engineer on the event from load-in through event close — not a shared AV technician who is simultaneously managing the video system. The audio engineer's primary job during the keynote is gain management, not anything else.
Failure 3: The speaker goes 12 minutes over time
A keynote speaker, no longer governed by the airline gate they thought would naturally end their presentation, speaks for 47 minutes when allocated 35. The subsequent programme runs late for the rest of the day. Prevention: a show-caller who calls time warnings to the speaker via confidence monitor (text overlay: "5 minutes remaining"), who has the authority to signal the speaker to conclude, and who has a clear instruction from the client-side lead about what to do when a speaker refuses to close. The show-caller cannot solve this problem if they have not been given the authority to exercise it.
Failure 4: The wrong person receives the award
The MC announces the wrong winner. Or announces the winner before the sizzle reel has finished. Or stumbles over the winner's name because they received the envelope 45 seconds before walking on stage. Prevention: the MC receives the full winner list at week 2 of production (not on show day), rehearses the announcement sequence in the technical rehearsal, and is not handed a sealed envelope mid-programme. The sealed envelope tradition is theatre. The production alternative — an MC who has the winner's name memorized from a week-2 brief and announces it with the confidence of preparation — produces a better result every time.
Failure 5: Registration queue at doors open
200 delegates arrive in the first 15 minutes after doors open and form a queue that extends out of the lobby. The registration desk is operating at full speed but was not designed for peak-load arrival. Prevention: calculate peak arrival load: a 300-person event where doors open 30 minutes before programme start will have 40–60% of delegates arriving in the first 10 minutes (120–180 people). A single registration desk with 2 operators handles approximately 60–80 people per 10-minute period in a smooth flow. A 300-person event needs 3 operators minimum, or a digital self-check-in option for pre-registered delegates.