# How to Reduce Omissions and Additions on OPI Calls > Omissions and additions usually happen when memory, speed, and role pressure collide. Use these OPI habits to keep your rendering tighter. Author: Mirkamol Published: April 16, 2026 Updated: September 8, 2026 Categories: Skills & Wellness Canonical page: https://useinterpreter.com/blog/reduce-omissions-additions-opi-calls/ An OPI accuracy problem may not sound dramatic while it happens. You leave out "with food." You add "today" because the instruction sounded urgent. You soften a rude sentence because you want the call to go smoother. You summarize a long answer because the provider sounds rushed. The call keeps moving, but the meaning has changed. Omissions and additions can come from weak listening, but they often come from pressure. OPI gives you fast speech, poor audio, no visual cues, and little time to recover. The fix is not more willpower. You need habits that protect completeness when the call gets messy. For professional accuracy expectations, compare your routine with the [NCIHC standards of practice](https://www.ncihc.org/standards-of-practice). > Most accuracy errors are small until the one small detail changes the outcome. ## Name the two error types An omission happens when the speaker said something and your interpretation leaves it out. > [!TIP] > After a hard call, review one miss type only: number, omission, addition, register, or sequence. One focused repair beats vague self-criticism. An addition happens when you include meaning the speaker did not say. Both can be small. Both can matter. "Take one tablet daily" is not the same as "take one tablet daily with food." "I have pain" is not the same as "I have severe pain." "I think he was there" is not the same as "he was there." You reduce these errors by treating accuracy as a workflow. You listen in chunks, manage memory, clarify at the right time, and avoid filling gaps from context. ## Work in shorter units Long turns can make it harder to retain every detail. If a speaker gives you four sentences, you may remember the topic but lose a qualifier, date, or condition. The interpreter then faces a choice: summarize or interrupt late. Neither feels good. Set the pace before the call runs away. These are illustrative practice scripts; adapt them to your agency's protocol: "Interpreter speaking. Please pause after one or two sentences so I can interpret everything accurately." If the speaker ignores it, step in with a calm process request: "For accuracy, I need to interpret that part before we continue." You do not need to apologize for managing turn length. You are protecting the record of the conversation. For more scripts, see [Clarification Scripts for OPI Interpreters](/blog/clarification-scripts-opi-interpreters/). ## Stop polishing the speaker Additions often come from trying to help. The caller gives a vague answer, and you make it sound clear. The provider says something blunt, and you make it softer. A patient uses a family term for a body part, and you replace it with clinical language. That may feel professional, but it can change the speaker's intent. Render the register you hear. If the speaker is vague, preserve the vagueness. If the provider asks a closed question, keep it closed. If the patient answers with a story, interpret the story instead of turning it into the answer you think the provider wanted. You can ask for clarification when meaning is unclear. You should not supply the missing meaning yourself. ## Use notes only for fragile details Writing too much can cause omissions because your ears leave the call while your pen moves. Use notes for the details your memory drops: - Numbers - Names - Dates - Addresses - Medication names - Multi-step sequences Let active listening handle the rest. If you try to write the whole sentence, you may miss the next sentence. [Interpreter note-taking for OPI](/blog/interpreter-note-taking-opi/) covers this in more depth. The short version: write less, but write the details that break accuracy when lost. ## Use the transcript as a cue Live text can offer a second look at a detail. It can also show an error confidently. When a phrase seems uncertain, compare the display with what you heard and ask the speaker to clarify. [Interpreter](/) gives OPI interpreters a live transcript, two-way translation, speaker labels, floating notes, quick lookup, and domain settings. It is not there to interpret for you. It gives you another channel for details that your memory may drop under pressure. Use it briefly and only in an approved workflow. Recognition can misstate numbers or drop negation; an AI transcript cannot independently confirm the source speech. ## Build a repeat-back habit Some details deserve confirmation before you render them. When clarification is needed, use your agency's confirmation protocol for medication doses, times, addresses, IDs, and instructions. An open request for repetition may be safer than offering a guessed number. Try: "Interpreter clarification: Please repeat the medication strength, dose, and schedule." "Interpreter clarification: Was that apartment 3B or 3D?" "Interpreter clarification: Did you say the deadline is July 15?" Keep the script neutral. Do not explain the whole reason. Do not blame the speaker. Ask, confirm, continue. ## Do a quiet self-audit After a shift, think about the moments where you asked for repeats or felt unsure. Look for patterns: - Do you omit final conditions, like "unless symptoms get worse"? - Do you add time words, like "today" or "right now"? - Do you summarize emotional answers? - Do you lose numbers after the second digit group? One pattern is enough for practice. If you lose conditions, listen for words like "unless," "except," "after," and "before." If you add time words, force yourself to render only the time marker the speaker used. If you summarize emotional answers, practice first-person rendering from authorized training recordings, never a privately retained client call. ## Protect accuracy with process OPI interpreters work inside pressure. You cannot remove the pressure from every call, but you can design habits around it. Shorter turns reduce memory strain. Narrow notes protect fragile details. Repeat-backs catch risk before it becomes an error. A live transcript gives you another cue to check against what you heard. It is not independent confirmation. Build a routine that gives you time to hear, ask, and render the complete message. Judge it by the details you preserve, not by how rarely you interrupt. --- *Related reading:* - [Active listening for interpreters](/blog/active-listening-for-interpreters/) - [Memory techniques for interpreters](/blog/memory-techniques-for-interpreters/) - [Numbers, dates, and addresses in OPI](/blog/numbers-dates-addresses-opi/) - [The interpreter's toolkit](/blog/interpreter-tools-guide/) - [Interpreter self-review after difficult calls](/blog/interpreter-quality-assurance-self-review/)