The corporate event checklist nobody hands you

Eight weeks out

This is the window where decisions are still cheap. Everything after this point costs money to change.

• Lock the date and the city. Check it against the festival calendar, exam season and the local political calendar — a bandh or a VIP visit closes roads without notice.
• Confirm headcount within ten per cent. Every other number depends on this one.
• Sign the venue, and read the annexure, not just the rate. Sound cut-off time, outside catering rules, load-in hours, whether you may drill or rig from the ceiling.
• Decide the single outcome. If the audience remembers one thing, what is it? Write it down. It settles two dozen arguments later.
• Appoint one decision-maker on the client side. Not a committee — one person who can approve a change at 9pm on the setup day.

Six weeks out

Production and permissions run on their own clocks and neither can be compressed at the end.

• Stage and set design signed off, with a rendered view from the back row — not just the front elevation everyone approves.
• Technical recce at the venue with the production team. Measure the room; do not trust the venue’s floor plan.
• Start permissions. Police, municipal, fire, and a sound licence if you will run past the local limit. In most Indian cities this takes two to four weeks and cannot be hurried.
• Book power. Generator plus a standby, sized by the production team, not guessed.
• Confirm the artist or host, in writing, including their technical rider.

Three weeks out

The content block. This is where events quietly go wrong, because everyone assumes someone else is writing it.

• Run sheet, cue to cue, with times against every item — not a rough agenda.
• Every presentation collected and checked on the actual playback machine, in the actual aspect ratio.
• Speaker briefs sent, including how long they have. Nobody has ever run short.
• Invitations out, with an RSVP mechanism that gives you a real number rather than a hopeful one.
• Hospitality plan for out-of-town guests: travel, stay, pickup, and who is calling them if a flight moves.

One week out

Nothing new gets added this week. This week is for rehearsal and for closing gaps.

• Full technical rehearsal at the venue, with the real content, the real playback and the real crew.
• Walk the guest journey end to end — car park, entry, registration, seating, washroom, food, exit. Time each step.
• Registration plan for the peak fifteen minutes, not the average. Queues form because everyone arrives at once.
• Final headcount to catering, with the venue’s own cut-off in mind.
• Print and distribute a contact sheet: every vendor, every client contact, every crew lead, one page.

The contingency plan that gets used

Everyone writes a contingency plan. Very few write one for the three things that actually happen.

Power. The generator is in place, but is it tested under load, with the changeover timed? A four-second gap in the middle of a keynote is a different event from a four-second gap during registration.

Audio. One spare handheld and one spare lapel, charged, on the console — not in a case in the van. Microphone failure is the single most common visible fault at Indian corporate events.

Weather. For anything outdoors between June and September, the plan is not an umbrella. It is a covered alternative you have already priced and can call by a stated hour.

Also decide, in advance, who has the authority to trigger each plan. A contingency nobody is allowed to invoke without a phone call to a director is not a contingency.

On the day

The run sheet is now the only document that matters. One person owns it and calls the show; everyone else executes against it.

Set a rule that changes stop at a fixed time — usually when doors open. After that point, the answer to “can we just add a two-minute video” is no, regardless of who is asking. Events do not fail from one change; they fail from the fourth change made without telling the sound engineer.

Keep one person free of any task, whose entire job is to walk the room and notice things. Every event has a problem nobody reported because everybody assumed it was someone else’s.

After

Photographs and video edited and sent within a week, while people still care. A gallery that arrives a month later gets opened by nobody.

A short debrief with the vendors, not just the client. The production crew know exactly what nearly went wrong, and they will tell you if you ask within a few days.

And the honest one: write down the three things that did not work, before memory tidies them up. That list is worth more than the photographs next time.