A workable audio standard fits on one page and covers four things: the equipment people should use, the settings they should apply, the behavior expected on calls, and who to contact when something sounds wrong. Anything longer goes unread. State the purpose at the top: every employee should be easy to understand on every call, whatever room they happen to be in.
Why write it down at all
Most companies have an unwritten audio standard, which is “whatever came with the laptop.” The results are uneven. One person sounds like a radio host, another like they are calling from inside a dishwasher, and nobody feels entitled to mention it because nothing says what good looks like.
A written standard fixes that in three ways. It gives new hires a clear setup to follow on day one. It gives managers a neutral reference, so feedback about someone’s audio is about the standard and not about the person. And it gives IT and finance a defined list to buy and support, in place of a stream of one-off requests.
Equipment: set a floor, not a shopping list
Specify outcomes and a minimum, then offer a short approved list for people who want to be told what to get. The minimum for most knowledge workers is a headset or earbuds with a microphone close to the mouth. Proximity matters more than price: a modest wired headset will outperform a laptop’s built-in microphone in an echoey room nearly every time.
Avoid naming a single mandatory model, since comfort and accessibility needs differ. Define tiers instead. A baseline tier applies to everyone. A higher tier, perhaps a better headset or a USB microphone, applies to roles that are on external calls most of the day, such as sales, support, recruiting and anyone who presents to customers.
State who pays and how to order. A standard that tells people what to own without telling them how to get it will be ignored.
Software and settings
This section does the most work for the least money. Start with what your meeting platform already provides. Zoom, Teams and Google Meet all include noise suppression, and your standard should say which level you expect people to use and link to your internal instructions for finding it, since menu locations change with updates.
Then decide whether you need a dedicated noise cancellation application on top. Companies with staff in shared offices, contact center roles or several different calling tools often do. If so, name the approved product and have IT deploy it centrally so people are not installing their own choices. When you evaluate options, vendor pages will only take you so far; independent category reviews, such as those published at https://thequietstandard.org/, give you a way to compare products on the same terms before you run a pilot of your own.
Add one technical rule that prevents a common fault: use a single layer of noise suppression. If the dedicated app is active, set the meeting platform’s own suppression to low or off. Two layers stacked tend to produce thin, choppy speech.
The test call
Include a two-minute self-check that everyone does once when they set up, and again after changing equipment. Record yourself using the meeting app’s test feature or a short solo recording, with your usual background conditions. Listen back on headphones. You should hear your voice clearly, with no echo, no hum and no clipped words.
Call etiquette belongs in the standard
Equipment does not fix habits. Keep this part brief and concrete:
- Mute when you are not speaking in meetings of more than a few people.
- Join from a room with a door when you can, and say so at the start when you cannot.
- In hybrid meetings, people in the conference room use the room system and keep laptop microphones and speakers off to prevent feedback.
- Tell a colleague promptly and kindly when their audio is poor, and expect the same in return.
That last point needs explicit permission from leadership. People hesitate to tell a director that their microphone is crackling, so the standard should say that doing so is helpful, not rude.
Support, exceptions and ownership
Name an owner, usually someone in IT or workplace operations, and a channel for help. Describe how exceptions work, including accommodations for employees who cannot use standard headsets, and handle those requests privately. Put the standard in onboarding so it reaches people before bad habits form.
Finally, give it a review date. Platforms change their settings and approved products get discontinued, so a yearly check keeps the page accurate.
Keep it to a page and keep it alive
The best audio standard is one people can follow in ten minutes and remember afterwards. Resist the urge to cover every scenario. Publish it, then ask for feedback after a month. If calls become easier to follow and nobody needs to ask what to buy, the page has done its job.