top of page

Product Launch Event Rehearsal Kuala Lumpur: Why 2 Days Pays

Writer: Andrew Chu
Andrew Chu
Nov 6
9 min read

A product reveal gets one take. The video either plays or it doesn't, and the mic either works or it doesn't, with your guests and your CEO watching. A product launch event rehearsal in Kuala Lumpur is how you find those faults while fixing them is still cheap. This post covers the cost logic, a two-day schedule, a contingency table and the sign-off process before doors open.

By Andrew Chu, Technical Event Director at Shockwave. 17 years, 1,000+ events, 180,000+ guests across Malaysia.


A wide view of a large ballroom set with round tables dressed in black cloths and black chair covers, filled with seated


Quick Takeaways


  • Rehearsal moves failures to cheaper moments

  • Day one: test systems, then integrate

  • Day two: full run in show order

  • Freeze files 24 hours before showtime

  • Log every defect with owner and retest


Why a Rehearsal Saves Money, Not Just Nerves


Think of a rehearsal as moving the discovery of problems. Every launch has faults. The only question is whether you find them on a quiet preparation day or in front of guests.


These are the cost lines a rehearsal tends to prevent:


  • Rush equipment hire when a screen, processor or microphone turns out to be wrong

  • Reprinting signage, backdrops or guest materials after a spelling or sizing error

  • Crew overtime from fixing things during guest arrival

  • Venue overrun when the programme runs long

  • Repeated production work, such as re-rendering a video under pressure


I can't give you a percentage saving, and anyone who does is guessing. Every launch differs. The logic is simple, though. A fault found in rehearsal costs a few hours and a calm conversation. The same fault live costs labour, replacement, and a reveal that guests remember for the wrong reason.


A useful way to judge it is probability times impact. A dead clicker is likely but low impact. A corrupted hero video is less likely but severe. Rehearse hardest where the impact is highest.


Technical Rehearsal vs Full Dress Rehearsal


These are two different tests, and people often blur them. A technical rehearsal tests equipment, cues and venue integration. A full dress rehearsal runs the real programme with real people at real timing.



Technical rehearsal

Full dress rehearsal

What it tests

Playback, audio, lighting, LED, power, cues

Programme flow, handovers, timing, entrances

Who must attend

Production crew, venue technicians, show caller

Everyone: presenters, host, security, registration, caterer

What it catches

Format, codec and signal faults

Awkward transitions, overruns, confusion on stage

What it misses

Human flow and pacing

Deep equipment faults, if rushed


If you only do one, you leave a gap. A technical run with no people won't reveal a presenter who walks on from the wrong side. A dress run with unstable playback will just stall repeatedly. That is why the sequence matters: technical first, then dress.


Day One: Technical Integration Schedule


The principle is to test each component alone, then test the system together. When you combine untested parts, you can't tell which one failed.


A sensible day-one test order:


  1. Load-in check: staging, LED, sound, lighting, power distribution and backup equipment are in place.

  2. Playback: every video and deck runs from the actual playback system, at the actual screen resolution.

  3. Microphones: test coverage for every presenter and walking route, including handheld and lapel backups.

  4. Clickers and presenter confidence monitors.

  5. Lighting cues, then sound cues, one at a time.

  6. The integrated check: all systems running against the cue sheet together.

  7. Venue sightlines and the audience route, from arrival through registration, seating, product area and exit.


Launch videos deserve their own line item. Marketing teams often deliver files optimised for social media, not for an LED wall. The aspect ratio may not fit the screen, and I won't accept a picture that looks stretched or cropped. Our rule is that every video is tested on the actual event hardware, never just on a laptop.


Before you load in, you also need these permissions:


  • Ask the venue about rigging and LED rules early. MITEC, for example, requires HIRARC documentation for high-risk activities like LED installations and rigging. The submission is due at least 30 days before the event, so this is a lead-time issue, not a rehearsal-day one.

  • Check entertainment permits with the local authority where your venue sits.

  • Venue packages, halal status, and AV capabilities change. Always confirm directly with the venue.


A woman in a grey cape blazer and white skirt holds a microphone and notes while standing on the open floor in front of the

Day Two: Full Run in Show Order


Day two is the dress run. The principle is that it must feel like launch day: same order, same timing, same people, same clothes where possible.


What a proper full run includes:


  1. Doors and registration, with the registration team handling mock arrivals.

  2. The host's opening and every presenter's entrance and exit.

  3. Every video, demo, product reveal and handover, in programme order.

  4. Pauses, Q&A and closing, timed on the clock.

  5. Security, caterer and venue team working to the same timeline.

  6. The show caller calling every cue aloud, from the cue sheet.


Don't stop for every small fix. Note it, keep running, and fix at the end. Stopping repeatedly hides the real timing.


The most expensive absence is the CEO or senior spokesperson. When they skip the run, their entrance, their slides, their mic and their cue are untested, for the person whose moment matters most. If their time is tight, give them a short, protected slot on the stage rather than nothing.


Expect last-minute changes from speakers even at this stage. That's normal. Absorb them on day two, not at 6pm on launch day.


What Goes Wrong Without a Rehearsal


These failure patterns repeat across launches. Each costs real money live and almost nothing in rehearsal.


The usual suspects:


  • Late decks. Large presentation files with embedded video, missing fonts or unsupported transitions crash playback systems. Files that arrive minutes before showtime can't be tested.

  • Wrong codecs. A master file that plays on a laptop fails on the venue's media server.

  • Late animation changes. Senior management asks for changes after the final run, and a large motion graphics file needs re-rendering.

  • Untested handovers. The host and presenter collide, or the product arrives on stage late.


Case in point: At one product launch, the client sent the final launch video less than an hour before doors opened. The master file had codec issues that broke playback on the venue's media server. Because we'd already built the habit of testing on real hardware, the technical team transcoded the file on the spot. They optimised it for live playback and tested it across several playback systems before showtime. Guests saw a clean reveal. In a proper rehearsal, that fault would have surfaced a day earlier, without the pressure.


The lesson is not that emergencies can be solved. It is that they are cheaper when they happen early.


Contingency Plan: A Failure, An Owner, A Response


A contingency plan is a predefined action for a foreseeable failure. The test of a good one is simple: every risk has a named owner, a first response and an escalation route. If any of those is missing, it's a wish list, not a plan.


Here is a starting map for a launch. Adapt it to your format:


Failure

Owner

First response

Escalation

Dead microphone

Audio engineer

Swap to backup handheld or lapel

Show caller pauses programme

Failed video playback

Playback operator

Switch to backup file on second system

Host fills with a prepared line

Late product stock

Event manager

Use display unit or backup product

Client lead decides on reveal order

Power cut

Production lead

Switch to UPS or venue backup supply

Venue engineer called

Connectivity loss

Technical lead

Fail over to second connection

Stream paused; room continues

Crowd congestion

Security lead

Redirect flow at registration

Venue team opens another entry


For hybrid or livestreamed launches, add a dedicated person watching the stream as a viewer would, plus a second internet connection. Test stream delay and the balance between room audio and online audio during the full run.


Then actually rehearse a few of these. Pull a cable on day two and see who moves first. A plan nobody has practised tends to fall apart under pressure.


A large red LED screen on the left shows a logo, large Chinese characters and an English theme line.

Defect Log, Change Freeze and Go/No-Go Sign-Off


Rehearsal is only useful if what it finds gets fixed and retested. That takes a defect log.


Log each issue with:


  • Severity: could it stop the launch, injure someone, breach venue rules, or damage the audience experience?

  • Owner: one named person.

  • Deadline: before the freeze, not "soon".

  • Retest status: fixed means retested, not just changed.


Fix the severe items first. A typo on a slide matters less than a video that doesn't play.


Then freeze the content. Our rule is that presentation files and launch videos are submitted 24 hours before showtime so they can be tested on the actual event hardware. This is also standard good practice for product launches in Kuala Lumpur. Speakers will still make changes. We accommodate them, but there is always a backup version the speaker can fall back on.


Finally, hold a go/no-go decision. Sign off the running order, cue sheet, files, seating plan, emergency contacts, supplier responsibilities and contingency plan. After sign-off, any change triggers a short documented impact review: what is changing, what else it touches, and who retests it.


For emergency planning, the Department of Standards Malaysia publishes relevant Malaysian Standards, and your venue should have its own emergency procedures. Ask to see them.


Product Launch Event Rehearsal Kuala Lumpur: Is One Day Enough?


Sometimes. The decision comes down to how much can go wrong and how much needs retesting.


One day can work if:


  • The programme is simple, with few cues and no complex video.

  • There is no hybrid broadcast.

  • The venue and crew are familiar with each other.


Choose two days if:


  • You have a big reveal with staged lighting, LED content or special effects.

  • It is a hybrid or livestreamed launch.

  • A VIP or senior guest list raises the cost of a visible mistake.

  • You want fixes from day one retested on day two, rather than hoped for.


Two days is not about doubling the effort. The first day finds faults. The second day proves they were fixed.


Then book it properly:


  • Ask the venue early about rehearsal access. Hotel ballrooms and convention halls in KL, from KLCC to Bukit Jalil, are often booked around events, so rehearsal days may not be available at short notice.

  • Clarify deposits and cancellation terms. Reported deposits for KL venues commonly run between 30% and 50% of the booking, with cancellation notice often around 30 days, but your venue's terms apply.

  • Confirm permit and HIRARC lead times before you lock the date.

  • Plan the final week for rehearsal, AV and playback testing. A full-production launch typically needs 10–12 weeks overall.


Planning Checklist


✅ Freeze the operating brief: running order, cue sheet, contact list.

✅ Book two rehearsal days with the venue, and confirm access times.

✅ Confirm permit and HIRARC lead times with the venue and authority.

✅ Collect all decks and videos 24 hours before showtime.

✅ Test every file on the actual event hardware.

✅ Assign an owner and response to each contingency risk.

✅ Run the full show in order, with the CEO present.

✅ Log defects, retest fixes, then hold the go/no-go.


Suggested Internal Links



Frequently Asked Questions


Q: Why does a product launch event need a rehearsal?

A: Some faults only appear when the full team runs the show in the real venue. A rehearsal finds them while fixing is still cheap and calm.


Q: How does a rehearsal save money on a product launch?

A: It prevents rush hire, reprinting, overtime and venue overrun, which usually cost more live than in preparation. Savings vary with every launch.


Q: What should happen during a two-day rehearsal?

A: Day one tests each system, then the integrated setup. Day two is a full run in show order, timed to launch day.


Q: What is the difference between a technical and a full dress rehearsal?

A: A technical rehearsal tests equipment, cues and venue integration. A full dress rehearsal runs the real programme with people and timings.


Q: How much does a product launch event cost in Malaysia?

A: Cost is driven by production complexity, AV and LED scope, venue, entertainment and contingency. Contact us for a quote.


Q: Who should attend a product launch rehearsal?

A: Presenters, host, show caller, production crew, venue team, registration staff, caterer and security. The CEO should attend too.


Q: What should a contingency plan include?

A: List foreseeable failures such as a dead mic, failed video, late stock, power cut and connectivity loss. Give each an owner, response and escalation route.


Q: How do I rehearse a hybrid or livestreamed launch?

A: Test internet backup, stream delay and room-versus-online audio during the full run. Keep a second connection ready.



Ready to Plan Your Product Launch?


Talk to us about your launch, your venue and how many rehearsal days it needs.



External References


header.all-comments


bottom of page