Caption Etiquette for Hearing Participants

Simple speaking habits that keep captions accurate and readable.

Voiskey Voiskey Team
Real-Time CaptionsAccessible CommunicationCaption Etiquette Hearing

Agree on Etiquette Before You Start

Caption Etiquette for Hearing participants is easier to follow when the group agrees on a few rules before the first sentence is spoken. Choose five rules, no more, and write them at the top of the shared text window where everyone can see them. Good candidates include one voice at a time, say your name before speaking, pause after a question, keep side comments out of the room, and repeat numbers and names. Read the list aloud at the start of the meeting and ask whether anything is missing. A short list that people remember beats a long policy nobody reads.

Etiquette matters because captions are linear. A reader follows one line at a time and cannot rewind a live conversation the way a listener can ask for a repeat. When two people speak at once, the text loses both voices; when someone whispers a side comment, the reader sees a gap and has no way to know what filled it. The rules are not about policing manners. They are about protecting the one channel the deaf reader depends on. Framing them that way helps hearing participants understand why a small habit, such as saying a name, has a large effect on the text.

Write each rule as a plain action rather than an abstract value. Instead of be inclusive, write say your name before your first sentence. Instead of be patient, write pause after asking a question. Instead of avoid interruptions, write raise a hand and wait for the host to name you. Put the rules in the same document the producer uses, so they scroll with the conversation and remain visible when a new person joins. Add a one-line example under each rule showing a good turn and a tangled turn. Concrete examples settle arguments about what the rule means in practice.

Get a commitment instead of an announcement. Ask two participants to restate one rule in their own words, then have the host model a good turn: name, short sentence, pause. Agree on a gentle signal for violations, such as the host raising a hand and saying hold that thought. The signal should correct the turn without embarrassing the speaker. At the end of the meeting, spend one minute asking which rule was hardest to remember. The answer tells you which rule needs a better example next time. Etiquette becomes real when people practice it once together, not when they read it silently.

Speak One Voice at a Time

Make the handoff visible. Ask anyone who wants to speak to raise a hand or type a single character into the shared window, then let the host name the next speaker. The speaker starts with their own name and one short sentence. This feels slow for the first few minutes and then saves far more time than it costs, because the reader never has to guess who said what. When the host forgets to name a speaker, anyone can point at the queue and ask for the next turn. A visible handoff also gives quiet participants a fair path into the conversation. The host should read the queue aloud so remote attendees hear who is next.

Handle crosstalk with a pause, not a scramble. When two voices overlap, the producer should stop rather than guess at the words. The host then pauses the discussion, restates the overlapping point in one sentence, and asks one person to repeat it. Mark the restatement as a summary so the reader knows it is not a direct quote. If the overlap was a quick agreement, record the agreement rather than the exchange. Trying to capture both voices produces a line that is incomplete and misleading. A ten-second pause is almost always better than a paragraph of invented text. It also keeps the record honest about what was actually confirmed.

Keep side comments out of the main room. A whisper is invisible to the reader, and a comment made while someone else is speaking splits the text into fragments. If a side point matters, type it into the shared window with a clear label such as side note, or save it for after the meeting. If it cannot wait, ask the host for a turn and say it once, in the main channel. This rule is often the hardest for hearing participants, because side comments feel private. Explain that the reader experiences them as unexplained gaps, and the habit becomes easier to keep.

Adapt the rules for remote calls. Ask participants to mute when they are not speaking, to wait for the host to name them, and to avoid speaking over a video that is still connecting. Use the chat queue for questions and let the host read each question aloud before answering, so the text contains both the question and the answer. If someone joins late, the host should repeat the current topic and the rules in one sentence. Remote calls remove visual cues that normally manage turns, so the spoken handoff has to carry more of the load. A little structure replaces a lot of confusion.

Name People and Topics Out Loud

Say names instead of pronouns when the referent could be unclear. A sentence such as she said the other one was late is nearly impossible to caption into a reliable record, because the reader has no way to resolve she or the other one. Replace it with Maya said the Tuesday draft was late. The extra second of speech buys a line that can be reviewed later without a transcript of the discussion around it. In a written record, a resolved name is worth more than a smooth sentence. This habit matters most in groups of three or more, where pronouns change referent from sentence to sentence and the reader cannot see who is looking at whom.

Announce topic changes explicitly. Say moving to the budget, then pause before the first detail. The producer can add a heading at the same moment, which gives the reader a visual landmark in a long document. Without an announcement, a new subject arrives as a continuation of the old one, and a decision from the previous topic can appear to belong to the new one. A short phrase such as next item or back to hiring is enough. It also helps the producer place a heading at the right point in the document. The goal is not formal language; it is a reliable boundary that the reader and the notes can both use.

Expand acronyms on first use. Say the full name, then the short form, then use the short form afterward. Add the term to the shared glossary so a substitute producer and a late joiner see the same definition. If the group uses several similar acronyms, say the distinguishing part rather than relying on a single letter. When a new participant joins, repeat the key acronyms once instead of assuming they heard the earlier explanation. Acronyms are efficient only when everyone shares the expansion; otherwise they become the most common source of misread lines in technical meetings. A single clear expansion at the start saves a dozen corrections later.

Treat numbers and dates as fragile. Say them in two forms, such as four fifteen and four one five, and pause between the forms. For dates, say the month and the day rather than a pair of numbers that could be read in either order. Write the figure into the shared window when it matters to a decision, and ask the reader to confirm it. If a number is corrected, say the correction and the original together so the note shows both. Numbers carry disproportionate weight in decisions, and a single transposed digit can send a project in the wrong direction for a week.

Respect the Reader's Pace

Watch the reader rather than only the speaker. Scrolling back, leaning toward the screen, or a pause before responding are signals that the text is arriving faster than it can be read. Slow the next few turns and add a short pause between sentences. If the reader is on a video call, ask them through the agreed signal whether they need a moment. Do not assume that silence means agreement or that a nod means the line was read. The reader is managing two streams at once, the spoken room and the written line, and a small pause from the speaker protects both. A reader who is behind will often stop responding, and the silence can be mistaken for agreement.

Avoid constant checking. Asking did you get that after every sentence turns the meeting into a test and interrupts the reader's rhythm. Use periodic checkpoints instead, such as once per agenda item, and let the reader control the frequency. Agree on a simple signal for slow down, such as a raised hand or a typed pause. When the signal appears, finish the current sentence, stop, and wait. The reader should not have to compete with the speaker for control of the pace. A single agreed signal is easier to remember than a long list of requests. A predictable checkpoint is less disruptive than a stream of anxious questions.

Summarize at natural boundaries. Every few minutes, say so far we have agreed and give two or three short lines. This gives the reader an anchor and catches drift before it compounds. Invite correction immediately after the summary; a reader who can fix the anchor will follow the next section more confidently. Keep the summary factual and brief, with names and numbers repeated rather than replaced by pronouns. A summary is also useful for anyone who joined late. It costs thirty seconds and often prevents a long argument about what was actually decided earlier. If nobody corrects the summary, treat it as the working record for the rest of the meeting.

Use the tools without making them the topic. Voiskey adapts punctuation and formatting to the task, so cleanly spoken sentences tend to arrive with readable breaks. It removes filler words, stutters, and self-corrections, which reduces the noise the reader has to filter. Mention the setup once at the start, then talk normally. If a regular participant wants the same habit on their own device, they can download Voiskey and use the same shared window. The technology should fade into the background; the etiquette is what keeps the conversation readable. A steady routine matters more than a perfect one, so keep the same shortcut and layout from meeting to meeting.

Coach New Participants

Write a one-page etiquette card that a new participant can read in two minutes. Include the five rules, one good example, one tangled example, and the name of the person who can answer questions. Put the card in the meeting invite and at the top of the shared window. A new participant who reads it before joining arrives with a mental model rather than a surprise. Keep the language plain and avoid scolding. The card should explain why each rule exists, because a rule with a reason survives longer than a rule without one. The card should fit on one screen and survive being read in a hurry.

Pair a newcomer with an experienced participant for their first captioned meeting. The experienced person can model a good turn, point out the queue, and answer a quick question in the chat without disrupting the room. Ask the newcomer to observe one full agenda item before speaking, then invite them to take a turn with a simple point. This lowers the cost of the first mistake. A buddy system also gives the host an extra pair of eyes for the handoff, which makes the whole room more readable during a busy discussion. The new participant also learns where the queue lives before they need it.

Debrief after the meeting with two short questions. Ask the reader which moments were hardest to follow, and ask the hearing participants which rule they forgot under pressure. Write the answers in the same place as the etiquette card. If one rule keeps failing, rewrite its example rather than adding a sixth rule. If a particular speaker keeps causing overlap, talk to them privately and practice one turn together. The debrief should produce one concrete change for the next meeting, not a general promise to do better. Keep the note beside the card so the next debrief can compare what changed.

Refresh the routine every quarter. Re-read the card with the reader, update the examples, and remove rules that no longer match how the group works. When a new team member joins, have them download Voiskey, read the card, and rehearse one turn with a colleague before their first real meeting. Keep the rules visible in the shared window so nobody has to rely on memory. A short quarterly review catches drift, such as a rule that has quietly stopped being followed, and gives the reader a regular chance to shape the room they work in. A fixed date makes the review happen even when the group is busy.

FAQ s

Speak one voice at a time, say your name before a point, pause after questions, keep side comments out of the room, and repeat names and numbers. Voiskey removes filler words and false starts, but those speaking habits are what keep each line easy to read and easy to review afterward.

Voiskey cleans up what one speaker says, including filler words, stutters, false starts, self-corrections, and grammar slips. It cannot separate two people who speak at the same time. The host should pause the discussion, restate the overlapping point in one sentence, and ask one person to repeat it before the group continues.

Yes. Voiskey works at the system level, so you press a shortcut, speak, and text appears at the insertion point in any app or text field. The group can keep the notes document or message window it already shares, which means the etiquette card and the captions can live in the same place.

Voiskey learns names, jargon, acronyms, and spelling preferences. When a name is corrected once, later mentions are more likely to arrive as intended. For unusual names, keep the three-step repair habit: say the correct term alone, use it in a short sentence, then continue without replaying the whole paragraph.

Say less. Get more
Say less. Get more
Say less. Get more
Say less. Get more
VoiskeyVoiskey

Your voice, amplified.

Download Voiskey for Mac and Windows to keep captioned conversations readable for every participant.

Use it across macOS, Windows, iOS, and Android

Use it across