Test interpreting performance, not conversational fluency
What happened: In June 2026, a language-services partner reported unsuccessful interpreting assessments despite favourable comments on fluency or pronunciation. The interpreting exercises included omissions, insertions, vocabulary problems or hesitation. The record contains an acknowledgement, not evidence of a successful retest.
Dated outside evidence: The Home Office's Interpreter code of conduct and guidance (accessible), updated 4 March 2026, requires interpreters on its assignments not to summarise, omit or change responses. Its remit is Home Office work, not every public-sector contract. For the Home Office completeness requirement: Home Office, Interpreter code of conduct and guidance (accessible) (updated 4 March 2026).
What it suggests (inference): A fluent conversation cannot stand in for an interpreting exercise. The recorded assessment and the public guidance both make completeness relevant to selection, without establishing why any particular candidate failed.
What to check: Put a representative interpreting exercise and its acceptance criteria in the brief. Ask who assesses omissions and additions, how feedback is recorded, and what evidence is required before a previously unsuccessful candidate is reconsidered. Keep that decision separate from a conversational language check.
Test the connection before confirming the booking
What happened: In October 2025, a language-services buyer declined to progress interpreters after a test call, reporting an unstable or very poor connection as well as an accent preference. The record does not isolate the connection fault or show that a later test resolved it.
Dated outside evidence: The Home Office's Interpreter code of conduct and guidance (accessible), updated 4 March 2026, requires a reliable internet connection for its remote video assignments and provides for raising audio or video difficulties during interviews. For the Home Office remote-video requirement: Home Office, Interpreter code of conduct and guidance (accessible) (updated 4 March 2026).
What it suggests (inference): Language suitability and technical readiness need separate acceptance decisions. A poor test call alone cannot establish whether the interpreter, equipment or platform caused the problem.
What to check: Name the intended platform and arrange a test using the proposed equipment and connection. Record language feedback separately from technical findings, assign responsibility for investigating faults, and specify the fallback and retest decision before confirming coverage.
Continue the interpreting brief
Use these MoniSa pages to continue scoping the assignment and reviewing assurance:
- Interpretation services: describe the live-session requirement.
- Trust evidence: review the assurance material before supplying files.
- Translation quote scope: use a separate scope process if the requirement is a written deliverable.
- Languages spoken in the United States | MoniSa Enterprise: A practical guide to the language varieties that shape US language work, and the questions that turn a language list into a workable brief.
- Setting up an interpretation program (OPI and VRI): A practical guide to standing up an over-the-phone and video remote interpretation program, from interpreter sourcing to assessment and live quality.
Specify the two acceptance decisions
Advice drawn from the assessment and test-call observations above:
- Describe the representative interpreting exercise and who will assess it.
- Record how omissions and additions will be evaluated separately from conversational fluency.
- Name the proposed platform, equipment and connection for the technical test.
- Agree how a failed test will be investigated and what evidence permits reconsideration.
Conclusions the records do not support
Keep these limits beside the procurement decision rather than treating a reply as proof:
- An acknowledgement of assessment feedback does not establish a successful retest.
- A poor connection report does not isolate the party or equipment that caused it.
- The cited Home Office guidance does not establish the requirements of every public-sector assignment.
Preserve the test findings
Advice for carrying the two checks into a booking decision:
- Keep the interpreting assessment findings and technical findings separately identifiable.
- Name the person investigating unresolved connection faults.
- Record the fallback, retest decision and evidence reviewed before confirming the booking.