# Interpreter Self-Review After Difficult Calls > A practical self-review routine for OPI interpreters who want to catch omissions, additions, terminology gaps, and fatigue patterns without spiraling. Author: Mirkamol Published: May 28, 2026 Updated: September 8, 2026 Categories: Skills & Wellness Canonical page: https://useinterpreter.com/blog/interpreter-quality-assurance-self-review/ You hang up and know something felt off. Maybe you asked for three repetitions. Maybe you stumbled on a medication name. Maybe the caller spoke for a full minute and you returned a version that felt shorter than it should have been. That moment can turn into shame, or it can turn into quality assurance. The difference is structure. You do not need a full audit after every call. The routine below is a suggested reflection exercise, not a validated QA instrument or a substitute for your agency's reporting process. If you discover a material error that could affect care, rights, or another important decision, use the agency's correction or incident process promptly. Do not leave it in a private training log. For professional practice context, use the [NCIHC standards of practice](https://www.ncihc.org/standards-of-practice) as a neutral reference point. > Self-review should make the next call better, not punish the last one forever. ## Start with the miss type Do not begin with "I was bad on that call." Name the miss. > [!TIP] > Try a ten-minute timebox for routine reflection. Serious incidents may need a separate supervisor-led review; a timer is not a reason to stop reporting a safety concern. Use these categories: - Omission: you left something out - Addition: you added something the speaker did not say - Substitution: you changed the meaning - Register shift: you made speech more formal, softer, harsher, or less direct - Terminology gap: you did not know the term - Number error: you missed a date, dose, amount, address, or ID - Role drift: you explained, advised, or answered instead of interpreting - Audio failure: you could not hear enough to work safely One call can have more than one category, but choose the main one. A clear label helps you fix the next call. ## Use a five-question review After a hard call, ask: 1. Which detail created the most risk? 2. Did I ask for clarification soon enough? 3. Did I preserve the speaker's tone? 4. Did I stay in role? 5. What one phrase or term should I add to my glossary? Keep the answers short. This is a reset, not a diary. If your agency allows live transcripts and the session data can be reviewed under policy, use the transcript as a fallible reference, not proof of what was said. An authorized source recording or supervisor review may be needed to establish the error. If policy does not allow review or retention, do not create your own record. Use memory and destroy notes according to policy. For note privacy, read [HIPAA for Interpreters](/blog/hipaa-for-interpreters/) if you handle medical calls. ## Score the call without punishing yourself For personal reflection, try this informal 1 to 3 scale: | Area | 1 | 2 | 3 | |---|---|---|---| | Accuracy | Meaning changed | Minor miss | Meaning preserved | | Completeness | Key content missing | Small gap | Full content rendered | | Register | Tone changed | Tone uneven | Tone preserved | | Control | Too late to intervene | Some delays | Timely clarification | | Role | Drifted | Slight blur | Clear boundary | Keep this practice rubric small. Its lowest score marks a training target, not a moral failure or an official judgment of competence. If the same area scores low across several calls, build practice around that area. For memory issues, use [memory techniques for interpreters](/blog/memory-techniques-for-interpreters/). For speed control, use [slow-down scripts](/blog/slow-down-fast-speakers-opi/). For role drift, revisit the [interpreter code of ethics](/blog/interpreter-code-of-ethics/). ## Build a personal error log without sensitive details You can track quality without storing client information. Use entries like: - "Missed medication suffix in cardiology call" - "Asked too late for shorter segments during benefits explanation" - "Softened angry caller's accusation" - "Confused pending transaction with posted transaction" - "Needed better term for prior written notice" Do not include names, addresses, case numbers, dates of service, account numbers, or rare details that identify the call. Review the list once a week. If you see the same miss three times, create a drill: - Add five terms to your glossary - Practice a role intervention aloud - Build a call-type template - Review one official source - Ask a supervisor for training material Quality improves through small repairs, not through self-criticism. ## Watch fatigue patterns Sometimes the problem is not a missing term. It is the fifth hour of calls. Track when misses happen: - Early shift - After back-to-back calls - After traumatic calls - During fast speakers - During bad audio - During rare-language calls - After skipping breaks If errors cluster late in a shift, more glossary work may not fix it. You may need better breaks, hydration, audio setup, or a lower call volume when possible. Our guide to [interpreter burnout](/blog/interpreter-burnout-opi/) covers the load problem in more depth. Quality assurance that ignores fatigue will blame the interpreter for a capacity issue. ## Use QA to prepare, not to ruminate A useful self-review ends with one action: - "Ask for shorter segments sooner." - "Add utility shutoff terms." - "Spell back addresses on 911 calls." - "Keep fraud claim terms on screen." - "Use first person even when the caller is angry." Then stop. You have taken the lesson from the call. If a call involved trauma, do not turn QA into replay. Use your agency's support process, a supervisor, or a qualified professional. Keep details confidential. Our guide to [vicarious trauma in interpreting](/blog/vicarious-trauma-interpreters/) can help you separate skill review from emotional recovery. The best interpreters do not remember every mistake forever. They notice patterns, fix one thing, and take the next call with less noise in their head. --- *Related reading:* - [Interpreter Burnout: Why OPI Burns You Out Faster (and What Helps)](/blog/interpreter-burnout-opi/) - [Memory Techniques for Interpreters: Retain More, Interrupt Less](/blog/memory-techniques-for-interpreters/) - [Interpreter Code of Ethics: What the Rules Say vs What Happens on Calls](/blog/interpreter-code-of-ethics/) - [The Interpreter's Toolkit: What Belongs on Your Screen](/blog/interpreter-tools-guide/)