The room applauds. In the Jakarta office, fourteen people are watching a locked wide shot of an empty lectern, because nobody re-cued the camera when the panel took the stage — and the only person who could hear the question from the floor was standing next to the person asking it.

Neither of those is an equipment problem. Every hybrid checklist online tells you to book a camera, a microphone and a screen, and all of those were booked. What failed was a handover nobody had run, at a moment nobody had assigned.

So this checklist is ordered by when, not by what, and each item carries the failure it exists to prevent. If you cannot name the failure, you probably do not need the item.

One boundary. The stream itself is covered link by link in what happens if a live stream fails. This is the rest of the event: the room, the speakers, the rehearsal, the people.

Three weeks out

Order the dedicated upload from the venue. In Singapore hotels and convention centres the wired circuit is usually provisioned by the venue's IT contractor, not by the events coordinator you have been emailing, and it moves at their lead time rather than yours. Ask at load-in and you are on guest Wi-Fi by default. Budget roughly 10 to 15 Mbps of dedicated upload per simultaneous stream.

Get the room handover window in writing. Not the event date — the hour the room is yours, empty, with the previous booking's furniture gone. Ballrooms here routinely run a lunch until 3pm the day before a 9am start, which leaves a night rig and no realistic rehearsal. Finding that out at T-minus-four-days is how rehearsal quietly disappears from the plan.

Map the remote audience against the clock. Regional audiences are the normal case in Singapore, not an edge case: a 3pm start here is 2pm in Jakarta, 5pm in Sydney, 12.30pm in Mumbai and 8am in London. That map decides which sessions matter live and whether the Q&A window is worth holding open for a region that is asleep.

Decide the language plan before the room plan. Human interpretation needs booth space, floor area and a clean feed; AI captions to attendees' phones need none of that, but do need a decision about unscripted or regulated content. Either way it moves the floor plan.

One week out

Test the circuit as a sustained push at show bitrate. A speed test that peaks beautifully for eight seconds tells you nothing about hour two. Push a real stream for twenty minutes and see whether it holds.

Check the slides in the remote frame, not on the wall. A 16:9 deck stretched across a 21:9 LED wall looks fine in the room and crops badly in the stream. Text set in 18pt survives a ballroom and dies on a laptop in a meeting room in Manila.

Put names against the show roles. Not job titles — names, on the run sheet. Who calls the show. Who watches the remote feed as an ordinary viewer for the full duration. Who owns the question queue and decides which ones reach the chair. On most events that go wrong, all three were the same person, who was also walking the CFO to the stage.

Confirm what the room draws, and from where. Lighting, LED and audio sharing a ring with the catering urns is an avoidable way to lose a show, and it is a five-minute conversation with the venue's engineer.

The remote speaker check

The most-skipped item on any hybrid checklist, and the one that fails most visibly.

Test on the machine they will present from, on the network they will be sitting on, at the hour they will speak. All three, or the test is theatre. A speaker who checks in from the office at 9am and then presents from a hotel room at 4pm has tested nothing that will be true on the day.

What the check covers: camera at eye height rather than looking up their nose; a light in front of them rather than a window behind; a headset or lapel mic instead of laptop speakers feeding the room back into itself; screen sharing tested with their real deck, including the embedded video they did not mention. Then the awkward question — what happens if their connection drops mid-answer, and who tells the room. That answer should be a sentence they can repeat, not a plan.

Fifteen minutes each, booked as a calendar invitation with a joining link, not offered as "let me know if you'd like a test". Nobody lets you know.

The day before

Send programme audio to the stream, not room sound. A camera microphone pointed at the PA gives your remote audience the room's reverb and the air conditioning. The feed comes off the audio desk as a mix-minus, so remote viewers hear what the microphones hear.

Put a real microphone on audience questions. Roving handhelds, or a floor stand people walk to. The commonest complaint from remote attendees is hearing the answer and not the question, which makes the session feel like eavesdropping.

Light faces for the camera, not just the stage. A wash that looks dramatic in the room renders as silhouettes on a stream. Front light on the lectern and the panel chairs, checked on a monitor rather than by eye.

Then rehearse. Which is the item most likely to be taken away from you, so it needs its own argument.

Why rehearsal is not an equipment test

Rehearsal loses to the executive's diary because it looks like a technical activity, and technical activities can be compressed. That framing is wrong, and worth correcting out loud in the planning meeting.

The equipment was tested at load-in. What rehearsal tests is the handovers: lectern to panel, panel to a video roll, video back to a remote speaker, remote speaker back to a question from the floor. Each is a moment where two people have to act at once, and none can be tested on paper. A hybrid event does not break at the camera. It breaks in the four seconds between two things.

For a half-day hybrid conference that is two to three hours with the room already rigged. The sentence that tends to work on a reluctant executive: rehearsal is not for the equipment, it is so nobody has to improvise in front of the audience. If the diary will not yield, run the handovers without the speakers — a crew rehearsing against empty chairs is worth more than nothing, though less than the real thing.

Show morning

Watch the stream from outside. On the platform the audience is using, on a device outside your corporate network, before doors. From inside the building it always looks fine. Corporate VPNs, meeting-room TVs on an old app version and privacy settings nobody changed are invisible from the production desk.

Run a comms check with everyone on headsets, including the remote-feed seat. That person notices trouble first and is easiest to leave off the loop.

Walk the question path once. Somebody submits from Kuala Lumpur, it lands in the queue, the queue owner picks it, the chair reads it. If that path has never been walked end to end, it gets walked for the first time in front of the audience.

During the show

Called from one desk, cue by cue. The remote-feed watcher reports there and nowhere else. The question owner works one list mixing room and remote submissions, so the chair is not holding two queues in their head while chairing.

One honest limit: nothing on this list protects you against a platform-side outage. A second destination and a decided way to move the audience across is the best available answer, and a vendor implying more is describing a wish.

After

Pull the recording before you leave the venue, from the local files rather than the platform. Chapter it by session that week, while the internal news cycle is still running. Attendance figures for both halves of the audience are what the next budget conversation rests on.

When most of this does not apply

A fully in-person session of around 30 people needs the venue's screen, one good microphone and somebody to advance the slides. That is the whole list. Cameras in a room where nobody is remote buy a longer setup and nothing else.

Production earns its cost when part of your audience cannot ask you to repeat something, when an executive is personally exposed, when the content is regulated, or when the day cannot be run again. Our hybrid conference work starts where those conditions do, and not before.

Frequently asked questions

What should be on a hybrid event AV checklist? Order it by when the work happens. Three weeks out: venue upload, room handover window, timezone map, language plan. One week out: sustained upload test, slide legibility in the remote frame, names against roles. Day before: room audio into the stream, a microphone on audience questions, camera-usable lighting, rehearsal.

How far ahead do I order internet for a hybrid event in Singapore? Two to three weeks. The circuit is usually provisioned by the venue's IT contractor, not the events team, so it runs on their lead time.

How do I check a remote speaker properly? Their machine, their network, their hour. Change any one of the three and you have tested a situation that won't exist on the day.

How long should a technical rehearsal be? For a half-day hybrid conference, two to three hours with the room rigged — long enough to run every handover once. It isn't an equipment test.

Does a 30-person in-person meeting need hybrid AV? No. The venue's screen, one good microphone and someone on the slides.

Interframe runs conference AV, streaming and audience engagement for Singapore corporate events on one technical plan, with one crew accountable for the room and the remote audience together. Tell us your venue, your agenda and where the feed needs to reach, and we'll come back within one business day with a plan and a quote.