The sixty-second room check

Why a ritual and not a fix

Room audio problems are rarely new. They're the same four or five problems, recurring, because the fix from last Tuesday lived in one person's head and that person is on holiday. A ritual survives holidays. It also survives new starters, visiting contractors and the reorganisation that moved your team into a different room — none of which a clever one-off fix survives.

The check below is deliberately short enough that someone will actually do it while waiting for the meeting to start, which is the only design constraint that matters. A twelve-point audit is a better audit and nobody has ever run one twice.

1. 1Count the open audio paths.0:00–0:15
2. 2Confirm what the anchor is actually listening through.0:15–0:25
3. 3Clear the microphone.0:25–0:30
4. 4Set the speaker volume at about two-thirds of instinct.0:30–0:35
5. 5Read the participant list.0:35–0:50
6. 6Ask the far end how you sound.0:50–1:00

Brass: checks one, five and six — the three this page says to keep if you only have time for three.

The six checks

1. Count the open audio paths. (15 seconds) Look around the table, not at the screen. Every device with a live microphone or a live speaker is a path, and there should be exactly one — the anchor. If someone has opened the meeting on their own laptop "just for the slides," that's a path until they disconnect audio. Say it out loud: "anyone else joined with audio?" This one check ends the majority of echo incidents before they happen.
2. Confirm what the anchor is actually listening through. (10 seconds) Open the anchor's audio settings and look at the selected microphone. If the room has an attached audio device, this is where you find out the meeting is about to run on a laptop's built-in mic instead — the single most common reason a room with perfectly good audio equipment sounds like somebody's keyboard. Docking, updates and a different user logging in all reshuffle this, so it's worth a glance every time rather than once a quarter.
3. Clear the microphone. (5 seconds) Notebooks, laptop bags, a stack of handouts, a tent card, someone's elbow. Table microphones accumulate objects across a working day exactly the way a windowsill accumulates mugs, and a covered mic is indistinguishable from a bad one.
4. Set the speaker volume at about two-thirds of instinct. (5 seconds) A room speaker turned up to fill a long room feeds its own microphone harder and gives echo cancellation more to fight, which costs you clarity in the outbound direction. If the far end is hard to hear at a moderate setting, move people closer rather than turning it up.
5. Read the participant list. (15 seconds) Not the table — the list. You're hunting for a second join from inside your own room: a phone that dialled in from someone's pocket, a wall panel signed into the meeting, a neighbouring room joined with the door open. Zoom documents a participant having both computer and telephone audio active as a primary echo cause, and it's the one variety that survives every visual check of the table, because the offending device is in a pocket.
6. Ask the far end how you sound. (10 seconds) Address a named person: "Priya, how are we sounding?" Not the group — groups don't answer. This is the check that matters most and gets skipped most, because it feels like fuss. It isn't: the room physically cannot hear its own echo, so the remote participants hold information you do not have, and they will generally wait until minute nine to volunteer it. Asking at minute one buys you eight minutes of fixable time.

What the check doesn't cover, on purpose

This is a pre-flight, not a diagnosis. It confirms the room is configured the way you decided it should be; it doesn't decide anything. If check one keeps finding extra audio paths week after week, the problem isn't the check — it's that nobody has made the anchor decision and written it into the invite, which is the Join Map's job. If the check passes cleanly and the room still sounds wrong, you've got a real fault, and the diagnosis pages take over: conference room echo if people are hearing themselves back, remote can't hear the room if the far end reports you as faint or cutting out.

It also deliberately contains no settings changes beyond the volume. Mid-meeting settings tourism is how rooms get mysteriously worse: a helpful person changes a suppression level to fix something, the meeting ends, and nobody afterwards knows what the room is supposed to say. Choose those levels deliberately, once, following the Zoom Rooms or Teams Rooms guides — then write them on a dated card in the room and leave them alone.

Who should do it

Whoever arrives first, which in practice means whoever is least important to the meeting — and that's fine, because none of the six checks requires any authority or any knowledge of the agenda. Rooms that work reliably tend to have one person who has quietly adopted this, and the useful move for a team is to stop relying on that being an accident: name the role, rotate it if you like, and put the six checks on a card in the room so the person doing it doesn't have to have memorised anything.

That's the whole ritual. Sixty seconds, no budget, no tickets, no procurement. If your room needs more than this, the rest of the site is here — but a surprising number of rooms don't.

More short items at A.O.B. — including why the room always blames the remote folks, which is the reasoning behind check six.

Verification note: Zoom's documented echo causes, including a participant having both computer and telephone audio active, were read on Zoom's official support documentation on 20 September 2026. Krisp pricing was read on krisp.ai the same day. Everything else on this page is MidTable's own operational judgement, offered as such — we run no test lab and publish no measurements.