What to test, who tests it, and when, so nothing fails in front of a live room.



Pre event testing is the scheduled process of checking every technical system and live element of an event before guests arrive: sound, lighting, screens, power, Wi-Fi, registration, performers and emergency exits. It usually runs in stages from two weeks before an event down to a final check one to two hours before doors open, and it is separate from a rehearsal because it tests equipment and systems, not just performance.
Pre event testing is a systems check, not a performance rehearsal. A rehearsal confirms that the emcee's lines land and the dance routine hits its marks. Pre event testing confirms that the microphone the emcee is holding actually turns on, that the cue for the dance act's track fires at the right volume through the house speakers, and that the LED wall behind the stage displays the file in the correct resolution without a green border around the edge. The two overlap in practice, which is exactly why the top result most people read on this topic blurs them together and calls the whole thing a dress rehearsal. It is more useful to treat them as separate checks that happen at the same time, because a performer can run a flawless rehearsal and the event can still fail if the wireless mic frequency clashes with another device in the building.
For a corporate dinner, a wedding, or a public festival stage, pre event testing covers eleven areas: sound and microphones, projection and screens, lighting, power and backup, Wi-Fi and livestream feed, registration and scanning, stage and signage, performer and emcee cues, food and beverage timing, safety exits, and a weather contingency if any part of the event is outdoors. Skipping any one of these because "it worked last time" is the single most common reason events open late or run into a visible fault in the first twenty minutes.
Pre event testing is not one session. It is a sequence of checks that gets more specific as the event gets closer, starting with a paper review two weeks out and ending with a live check in the final hour before guests walk in. Compressing this into one afternoon before the event is the main reason small faults get missed, because there is no time left to fix anything that fails.
| When | What gets tested | Who runs it |
|---|---|---|
| Two weeks before | Equipment list confirmed against the venue's technical capacity. Power load calculated against the room's circuit limit. Act's rider checked against what the venue can actually supply. | Planner and AV crew |
| One week before | Site visit or video walkthrough of stage, loading bay, power points and Wi-Fi coverage. Backup equipment confirmed, not just listed. | Planner, venue engineer, AV crew |
| Two days before | Full technical rehearsal: sound check with actual tracks, lighting cues run in sequence, screen content played start to finish at full length. | AV crew, emcee, performers |
| Day before | Registration and scanning system tested with sample guest list. Signage and seating confirmed against the final floor plan. | Registration team, planner |
| Morning of, load-in | Power draw tested with every system running simultaneously, not one at a time. Wi-Fi and livestream feed load-tested. | Venue engineer, AV crew |
| Two to three hours before doors | Full run of show order with cue sheet, F&B timing checked against kitchen readiness, emergency exits and security checkpoints confirmed clear. | Planner, security, caterer, emcee |
| One hour before doors | Final mic check, final lighting look, final screen on standby, final weather check for any outdoor segment. | AV crew and planner |
Pre event testing fails more often from unclear ownership than from bad equipment. Every item on the checklist needs one named person who confirms it, not a department. "AV will handle it" is not an answer anyone can be held to on the day.
| Role | Responsible for |
|---|---|
| Event planner or project manager | Owns the master checklist and timeline, confirms every area signs off, is the single point of contact if something fails |
| AV crew | Sound, lighting, projection, power distribution to AV equipment, backup units on standby |
| Venue engineer or facilities manager | Building power supply and circuit limits, Wi-Fi infrastructure, loading bay access, air conditioning and room setup |
| Emcee | Mic check, script timing against the run sheet, cue familiarity with AV |
| Performers (band, DJ, dancers) | Own instrument and costume checks, line check with sound engineer, confirming playback files |
| Caterer | F&B timing against the programme, confirming course timing does not clash with key stage moments |
| Registration team | Scanning system and guest list loaded and tested, backup paper list printed |
| Security | Emergency exits clear, crowd flow at entry points, coordination with venue security on evacuation routes |
This is the part most guides skip or compress into a bullet list. Printing it by area and ticking it off with a name attached to each row is what actually prevents the fault, not the general idea that testing matters.
| Check | Confirm | Confirmed by |
|---|---|---|
| Wireless mic frequencies | No clash with other devices or other events in the building that day | AV crew |
| Backup mic | Charged, on a different channel, within reach of the stage | AV crew |
| Speaker coverage | Volume even across the room, no dead zones at the back or sides | AV crew, planner |
| Check | Confirm | Confirmed by |
|---|---|---|
| File format and resolution | Plays at full length with no stretching, cropping, or colour shift | AV crew |
| Brightness in the actual room | Screen is readable with house lights at the level planned for show time | AV crew, planner |
| Backup playback device | Second laptop or media server loaded with the same files | AV crew |
| Check | Confirm | Confirmed by |
|---|---|---|
| Cue sequence | Runs in the correct order against the programme, no gaps or stuck cues | AV crew |
| Stage lighting on performers | No harsh shadow or glare for cameras and livestream | AV crew |
| House lights transition | Dim and rise timing matches the run sheet | AV crew, emcee |
| Check | Confirm | Confirmed by |
|---|---|---|
| Total load test | Every system running together does not exceed the room's circuit limit | Venue engineer |
| Backup power or UPS | On standby for mics, playback device and any recording equipment | AV crew |
| Extension and cable runs | Taped down, not crossing guest walkways | AV crew |
| Check | Confirm | Confirmed by |
|---|---|---|
| Bandwidth at event capacity | Tested with guest device load simulated, not an empty room | Venue engineer, AV crew |
| Livestream encoder | Feed tested end to end to the actual platform, not just locally | AV crew |
| Backup connection | Mobile hotspot or secondary line on standby for the stream | AV crew |
| Check | Confirm | Confirmed by |
|---|---|---|
| Scanning app or device | Loaded with the final guest list, tested on venue Wi-Fi | Registration team |
| Backup list | Printed copy on hand if the scanning system fails | Registration team |
| Entry flow | Queue layout tested against expected arrival rate | Planner, security |
| Check | Confirm | Confirmed by |
|---|---|---|
| Stage stability and sightlines | No blind spots from key seating sections | Planner, venue engineer |
| Seating plan | Matches the final guest count and table arrangement | Planner |
| Signage and wayfinding | Legible from the entry point, correctly spelled | Planner |
| Check | Confirm | Confirmed by |
|---|---|---|
| Individual mic levels | Set for each performer and the emcee, not one generic level | AV crew |
| Cue sheet walkthrough | Every act and the emcee know their entry cue and exit cue | Emcee, performers, AV crew |
| Transition timing | Gap between acts rehearsed, not left to guesswork on the night | Planner, emcee |
| Check | Confirm | Confirmed by |
|---|---|---|
| Course timing | Does not clash with speeches, performances or key announcements | Caterer, planner |
| Service staff briefed | Know to pause service during specific programme segments | Caterer |
| Check | Confirm | Confirmed by |
|---|---|---|
| Exit routes | Clear of cables, staging, and decor at the final setup | Security, venue engineer |
| First aid point | Stocked and staffed, location known to all crew | Security, planner |
| Check | Confirm | Confirmed by |
|---|---|---|
| Rain contingency | Indoor backup space or tent confirmed and tested, not just agreed in principle | Planner, venue |
| Equipment weatherproofing | Power points and AV equipment covered or raised off the ground | AV crew |
The fault that causes the most damage is testing each system on its own and never testing them all running together at once. Sound checks fine, lighting checks fine, the screen plays fine, and then at doors open everything is switched on at the same time and the room trips a circuit, because nobody tested the combined power draw against the venue's actual limit. A full load test with every system live, done during the morning of load-in rather than the day before, is the single check that prevents this.
Pre event testing in Singapore has to work around fixed building constraints that do not show up in a generic checklist. Hotel ballrooms generally allocate a tech rehearsal window the day of or the evening before, and that window is often shorter than planners expect once setup, soundcheck and a full run are all squeezed into it. Confirm the exact rehearsal slot with the venue in writing, not verbally, because ballrooms are frequently double-booked with another event either side of yours.
Loading bay and access times are another recurring issue. Many venues restrict large vehicle access to specific hours, and AV trucks arriving outside that window can push the entire testing schedule back by hours. Confirm loading bay booking and lift access separately from the room booking, since they are sometimes managed by different departments within the same building.
Building power limits vary by venue and by room, and older buildings in particular may not support the combined draw of modern LED screens, moving lights and a full PA system without prior notice to the facilities team. Ask the venue engineer for the circuit capacity of the specific room, not the building average, and run the full load test described above before relying on it.
For any event with an outdoor component, from a garden reception to a rooftop segment, confirm the indoor backup space and test it as if it were the primary venue, since rain in Singapore can arrive with very little warning and a backup that has not been walked through is not a real backup.
A failure during pre event testing is normal and expected. It is a failure during the live event that is the actual problem, and the entire point of testing early is to catch the fault while there is still time to fix it. When something fails, the sequence that works is: isolate the fault to one system rather than assuming the whole setup is broken, switch to the backup unit immediately rather than troubleshooting the original live, and only then diagnose the original once the backup is confirmed working and the show can proceed.
The planner's job in that moment is not to fix the fault personally, it is to keep the timeline moving and decide whether the fix can happen before doors or needs to be absorbed into the run of show. A mic that fails during the two-days-before rehearsal is a minor delay. The same mic failing with no backup tested is a visible gap in front of guests. This is also why the roles table above matters: if nobody owns "backup mic ready and charged," nobody checks it until it is needed.
Entertainment acts need a different kind of pre event testing than a corporate speaker or a projector feed, because the test has to cover both the technical setup and the performer's own equipment or costume. A band, a DJ, a dance troupe and an LED performance each have a distinct checklist, and treating them all as "sound check" misses the parts that actually go wrong.
A band needs a line check on every instrument and vocal mic individually, not just a combined sound check, because a single bad cable on one instrument is easy to miss in a full mix but very obvious once the band is playing live. A DJ needs their own setup tested with the venue's actual mixer and speaker system, since DJ equipment compatibility varies and a USB port or input type that works at home does not always match what the venue provides. Dancers need a floor check for grip and clearance, particularly on marble or polished tile common in hotel ballrooms, plus a costume check under the actual stage lighting rather than daylight or a dressing room, since colours and fabric can read very differently once lit. An LED or projection performance needs a full cue run of every file in sequence, at the actual resolution and brightness the room will use at show time, because a file that looks correct on a laptop screen can appear washed out or cropped on the venue's screen.
This is the standard we hold ourselves to: every act booked through Bella Entertainment goes through a technical rehearsal and soundcheck ahead of the event, matched to the specific venue and equipment on site, rather than a generic run-through done somewhere else. If you are booking dancers in Singapore, Bollywood dancers, or bhangra dancers and dhol players, ask the agency directly what their pre event testing process covers and when it happens relative to your own AV schedule, since a touring act's rehearsal and the venue's technical check need to be coordinated, not run separately.
If you are still deciding on the act itself, our act type and event type pages break down what suits a corporate dinner versus a wedding or a public festival, which affects how much testing time you need to budget before doors open.
Pre event testing is the process of checking every technical system and live element of an event before guests arrive, including sound, lighting, screens, power, Wi-Fi, registration and emergency exits. It is separate from a rehearsal, which checks performance rather than equipment, though both usually happen in the same window before an event.
Pre event testing catches equipment faults, power overloads and timing clashes while there is still time to fix them, rather than discovering them in front of a live audience. Events that skip it most commonly fail on combined power draw, microphone frequency clashes, or screen content that was never tested at full length in the actual room.
It varies by event size, but a typical sequence runs from a paper review two weeks before down to a final check one to two hours before doors open. The core technical rehearsal, where sound, lighting and screens are tested together with actual content, usually happens one to two days before the event and takes a few hours depending on complexity.
Responsibility is shared but should be assigned by name, not department: the planner owns the master checklist, AV crew owns sound, lighting and projection, the venue engineer owns power and Wi-Fi infrastructure, and performers own their own instrument, costume or playback checks. A single point of contact should confirm every area has signed off before doors open.
A dress rehearsal focuses on performance, timing, blocking and how the programme flows. Pre event testing focuses on whether the equipment and systems behind that performance actually work, such as whether a mic is on the correct frequency or a screen file plays without distortion. In practice the two usually happen together, but they check different things.
A failure during testing is expected and is not a problem in itself, since the purpose of testing is to catch faults before the event starts. The correct response is to isolate the fault to one system, switch to a backup immediately rather than troubleshooting live, and diagnose the original fault only once the backup is confirmed working.
Yes. A DJ's own equipment needs to be tested with the venue's actual mixer and speaker system ahead of the event, since input types and compatibility vary between setups. A test that only checks the venue's house system, without the DJ's own gear connected, does not confirm the act will work on the night.
Smaller events still benefit from a scaled-down version, even if it is a single afternoon rather than a multi-day timeline. The areas that matter most at small scale are microphone and speaker check, a power load test if several devices run at once, and a Wi-Fi check if any part of the event relies on scanning or streaming.
Bands need an individual line check on every instrument and mic, DJs need their own setup tested with the venue's mixer, dancers need a floor grip check and a costume check under actual stage lighting, and LED or projection acts need a full cue run of every file at the venue's real resolution and brightness. Testing each separately catches faults a combined check can miss.
An outdoor weather plan should include a confirmed indoor backup space that has actually been tested, not just agreed on paper, plus weatherproofing for power points and AV equipment. In Singapore, rain can arrive with very little warning, so the backup space should be walked through as if it were the primary venue, with the same sound and lighting checks applied.
Every act we book goes through a full soundcheck and technical rehearsal matched to your venue.
Get a Free QuoteSHARE TO:
Looking for an act or service? Browse all acts and services · Corporate event planning · Dinner and dance