Event remote presenter connection test
A speaker will join from another city or country, and the first time anyone checks the link should not be live in front of the audience.
The short answer
A remote presenter connection test is a scheduled session, held before show day and again close to the event, where the remote speaker joins from the actual location and device they will use, and the AV supplier and organiser check picture, sound, screen sharing and the handover to the room.
The organiser schedules the test, briefs the speaker and decides the fallback. The AV supplier configures and operates the connection with the venue's network.
What to settle before the first test
- Which meeting or streaming platform the AV supplier will use, and whether the speaker has used it before.
- Where the speaker will be, with a quiet place, wired network if possible and a second device.
- Who in the room hears the speaker, who speaks back, and how questions from the audience reach them.
- Whether the speaker shares slides remotely or the room's playback team shows them, to avoid two sets of controls.
- Time zone and call times written in both zones.
Two tests, not one
| Test | When | What it checks |
|---|---|---|
| First test | Some weeks before, once the platform is chosen | Speaker can join, microphone and camera work, screen sharing works, the speaker understands the instructions. |
| Final test | At or just before the technical rehearsal, with the real room set up | Connection through the venue's network, echo control, audio to the room, cue handover with the stage manager. |
A run order for the test
- Speaker joins from the final location on the final device and wired network if available.
- Check what the room hears and what the speaker hears. Ask the AV supplier to say when audio is correct.
- Test slide control and any live demonstration or video.
- Practise the cue: who tells the speaker to start, and who signals the end of the slot, using the stage cue sheet.
- Test a question from the room, relayed to the speaker.
- Record issues in the rehearsal issue log and agree who fixes each and by when.
Agree the fallback before the event
Decide what happens if the connection drops: switch to a phone line, play a pre-recorded version, move the slot, or have a moderator continue. Record it and the person who makes that call. See backup playback coordination for the recorded option.
Worked example · Fictional example
A forum with one overseas keynote speaker
Fictional organisation and figures, for illustration only.
A fictional regulator forum in Kuala Lumpur has an overseas keynote speaker joining live. The first test, three weeks before, finds the speaker's hotel network drops regularly, so the speaker agrees to join from a partner office with a wired connection.
At the final test the AV supplier hears an echo because the speaker is also on a second device; the speaker closes it. The organiser records a fallback: a pre-recorded 15-minute version held on the playback laptop, which the moderator may trigger if the link fails for more than a minute.
Use this yourself
Remote presenter test plan
Fill in one plan per remote speaker.
- Speaker, location, time zone:
- Platform and joining link sent (date):
- Device and network used (wired or wireless), second device:
- First test date and result:
- Final test date, with the real room set up, and result:
- Slides shown by: speaker / room playback team:
- Audio to the room and back to the speaker confirmed by AV supplier (name, date):
- Cue to start and end, and who gives it:
- How audience questions reach the speaker:
- Fallback if the link fails, and who decides:
Handle it in-house, or bring in help?
Your team can usually handle this when
- One remote speaker, a familiar platform and an AV supplier that runs these links regularly.
- The speaker is experienced with remote presenting.
- A team member can attend both tests.
Outside planning help earns its fee when
- Several remote speakers across time zones, or a hybrid audience.
- The programme depends on live interaction between room and remote speakers.
- No team member can join the tests and chase the issue list.
Need the remote speaker tests organised?
A conference project lead can schedule the tests across time zones, brief each remote speaker, keep the issue list, and make sure the fallback is agreed with your team and the AV supplier. The connection itself remains configured and operated by the AV supplier.
Questions organisers ask
How early should the first test be?
Early enough to change the plan if it fails, for example to change location or platform. Agree the date with the AV supplier once the platform is chosen.
Is a test on the speaker's usual laptop enough?
No. Test from the actual location, on the actual device and network, and again at the final rehearsal with the room set up.
Who decides to switch to the fallback?
Name one person before the event, usually the programme lead or stage manager, so the decision is not discussed in front of the audience.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.