Testing microphones before participants arrive

This guide helps you verify table-level capture quality before participants begin the real discussion. Use it in every RoomRadar workshop, especially in noisy rooms or unfamiliar venues. In a hurry: run one normal-voice test per table, run one overlap test on risky tables, fix placement before doors open, and keep a risk list for early monitoring.

Fast path

1. Place one phone at each table in likely speaking position.
2. Run a normal-volume test sentence at every table.
3. Verify transcript clarity and group placement.
4. Retest weak tables after moving phone or clearing clutter.
5. Mark high-risk tables for first-round checks.

Why pre-flight testing matters

Audio pre-flight is a facilitation safeguard. If table capture fails during round one, participants switch attention from topic work to technical noise.

You do not need studio-grade capture. You need stable, understandable table-level signal so you can monitor discussion quality and generate useful summaries.

Step-by-step test routine

1. Run baseline tests table by table

Use the same phrase everywhere so results are comparable:

Table C test. Normal discussion voice, one two three.

At each table, confirm:

• text appears in expected group
• delay is acceptable
• wording is understandable at normal pace

2. Stress test likely problem tables

For larger/noisier tables, run a short two-voice overlap test. This simulates real workshop behavior better than a single speaker test.

If output drops, adjust placement before participants arrive.

3. Fix and retest immediately

When a table underperforms:

1. move phone toward active speakers
2. remove obstructions from mic area
3. check permission/page state
4. rerun exact same test phrase

No retest means no proof of improvement.

4. Keep a quick table log

Use simple notes:

• table
• baseline pass/fail
• overlap pass/fail
• action taken

This prevents memory-driven mistakes during launch pressure.

Common testing mistakes

Testing only from facilitator position

Table conditions vary. Podium success does not prove back-corner reliability.

Speaking louder than real discussion

Loud tests hide placement problems.

Accepting "connected" as "good audio"

Connection status alone is not enough. You need understandable transcript output.

Leaving duplicate active phones

Duplicate devices often reduce clarity.

Table risk scoring before doors open

If time is limited, score each table quickly and prioritize work where risk is highest:

• low risk: stable network zone, clean audio environment, clear baseline test
• medium risk: occasional delay or moderate noise, acceptable after one adjustment
• high risk: repeated delay, unclear text, or known noisy corridor position

In round one, scan high-risk tables first after the opening prompt. This small prioritization step catches fragile capture conditions before they escalate into session-wide confusion.

This guide is for...

Use this guide when your risk is weak capture quality during round one.

If your risk is room layout or network zones, pair this with [Preparing the room before a workshop starts](/guides/setup/preparing-a-room-for-a-multi-table-workshop) and [Network basics for stable workshops](/guides/setup/network-basics-for-workshops).

Related guides

• [Preparing the room before a workshop starts](/guides/setup/preparing-a-room-for-a-multi-table-workshop)
• [Connect phones as microphones for multi-table workshops](/guides/setup/connect-phones-as-microphones)
• [Fixing microphone permission problems](/guides/setup/microphone-permissions-ios-android)
• [Starting a RoomRadar session](/guides/setup/start-a-roomradar-session)
• [Facilitate effectively in noisy rooms](/guides/workflows/facilitating-in-noisy-rooms)