The Interpreter Who Quit at Intermission of Our 9-Language Conference

He found me near the registration desk during the twenty-minute break at 11:40am. He was a compact man with a careful way of speaking, and he said what he had to say without preamble: he was leaving. He could not continue. There had been an incident in the booth — a dispute with the second interpreter on his language pair — and he would not return to that environment. He handed me his event badge and walked out through the lobby doors.

The annual general assembly of a mid-Atlantic regional trade federation. Eleven member nations. Nine interpretation languages running simultaneously. 340 delegates. Our afternoon agenda ran from 1:00pm to 5:30pm and included a legislative review session, a vote on the following year’s host city, and a keynote from a minister of trade who was flying out at 7pm.

The language pair he covered was Portuguese. Forty-two of the 340 delegates needed Portuguese interpretation.

It was 11:43am.

The structure of the problem

Simultaneous interpretation at this scale is not like hiring an extra caterer. Each language pair required a certified conference interpreter with specific technical credentials — AIIC membership or equivalent — and relevant subject-matter fluency in trade and commerce. You cannot put a bilingual staff member in the booth. You cannot ask a delegate to interpret for their colleagues. The equipment — the booths, the headsets, the distribution system — was already set and calibrated. The gap was the human being.

My interpretation services vendor was a Washington DC firm I had worked with for six years. I called the account manager before the break even ended. She had been monitoring the conference remotely — her teams always do for events of this size — and she already knew. She had the incident call from the second interpreter in the Portuguese booth while I was still talking to the man who left.

She told me: she had one available Portuguese interpreter in their roster who was not on another assignment that day. That interpreter was currently in Baltimore, about forty minutes by car. She was qualified. She was willing to come if I could get her there and if the client would authorize the emergency rate — double the standard day rate, call it $2,400 for the afternoon block — plus a car service.

I said: “Authorize it. Send the car.”

She said: “The car is already ordered.”

That is why you work with firms who monitor remotely.

The forty-minute gap

We had a problem I had not yet solved: the afternoon session started at 1:00pm. The replacement interpreter would arrive no earlier than 12:50pm, assuming traffic. That was ten minutes of margin, assuming we could get her to the booth and oriented immediately. If traffic was any worse, or if she needed time to review the afternoon materials, we could have a gap.

I walked to where the Portuguese-language delegation was gathered for the lunch break. Forty-two people, mostly standing in a cluster near the window. I introduced myself — I had met a few of them at the opening welcome, not most of them — and explained the situation plainly. There had been an interpreter transition in the Portuguese booth. A replacement was arriving by car. The afternoon session would begin on schedule. If there was any brief delay in interpretation at the 1:00pm start, it would be resolved within minutes.

I said this in English. One of the delegates — a woman from one of the Azorean member associations — translated for the others. A few of them looked concerned. Most of them nodded. One of them asked me: “Is there anything we can do?”

I said: “No. But thank you for asking.” And I meant it.

1:00pm — the seams

The replacement interpreter arrived at 12:47pm. She had thirteen minutes. I had my assistant take her directly to the Portuguese booth with a printed copy of the afternoon agenda, the key terminology glossary we had prepared for all interpreters during vendor onboarding, and a one-paragraph briefing on the vote agenda item — the most technically specific part of the afternoon.

The afternoon session opened at 1:00pm on schedule. For the first eleven minutes, the Portuguese booth ran slightly behind — you could see it in the slight delay of the headset listeners — because the interpreter was reading agenda materials while simultaneously working. At 1:11pm, she hit her stride. I watched the Portuguese-language delegates and could see the tension in the room ease.

The vote on the following year’s host city was conducted at 3:22pm. All forty-two Portuguese-language delegates participated. The vote was valid. The motion carried.

What the afternoon cost

The emergency interpreter fee: $2,400. The car service from Baltimore: $180. An additional $320 in per-diem adjustments that the vendor’s account manager flagged for my invoice later. Total: $2,900.

The budget impact was meaningful but contained. I had a contingency line for interpretation emergencies — not because I had anticipated specifically this scenario, but because interpretation is one of the highest-variance vendor categories I manage and I had learned that from an earlier conference. That contingency line was $3,000. It was almost exactly the right amount.

The afternoon ran to 5:28pm. The trade minister’s keynote was received well. She flew out at 7:00pm as scheduled. The vote results were announced via member communication the following morning without any reference to an interpretation disruption.

The second interpreter

I should say something about the second interpreter — the one who remained in the booth and was still there when the replacement arrived. I did not know, during the event, what the dispute had been about. I learned afterward from the vendor’s account manager: it had been a disagreement about interpretation style and pacing that had escalated during the morning session. Both interpreters were experienced. Both had, in retrospect, legitimate points. The situation was a chemistry failure, not a competence failure.

The interpreter who left did so in a manner that created significant difficulty for forty-two delegates. I do not pretend that was a neutral act. But I also don’t think he was a bad person. Conference interpretation is an intensely pressured cognitive environment and booth chemistry is real. I now request references between co-interpreters — specifically asking whether they have worked together before — before confirming pairs.

What I take from it

1. Use interpretation vendors who monitor remotely. The forty-minute solution was possible because my vendor’s account manager already knew about the incident before I called. Remote monitoring is not standard practice across all interpretation firms. Ask explicitly: what is your on-site and remote support structure for events of this size?

2. Have an emergency rate pre-authorized in your contract. I did not spend twenty minutes on that call negotiating. The emergency rate structure was defined in our vendor contract — I only needed to verbally authorize it. Pre-authorizing emergency rate structures for key vendors (interpretation, AV, catering) is standard practice for events where a mid-event replacement could be needed.

3. Brief the affected delegation before the problem becomes visible to them. The forty-two Portuguese-language delegates did not experience a gap because I told them what to expect before 1:00pm. If they had arrived at their seats at 1:00pm and simply noticed that the interpretation was delayed, the trust damage would have been different. Managed expectation is not the same as a solved problem, but it is meaningfully better than a surprise.

4. Interpreter pairing is a technical decision, not just a staffing decision. Request records of whether co-interpreters have worked together before. For high-stakes content — a legislative vote, a keynote from a government official — familiarity between booth partners is not optional. I now treat this like I treat AV lead pairings: established teams first, new combinations only when necessary and with a tested chemistry reference.

5. Build a per-category contingency line, not just a total contingency pool. A $3,000 interpretation contingency protected this event. A $3,000 pool buried inside a $200,000 budget total is not the same thing — it gets raided earlier for smaller issues. Separate contingency lines per high-variance category make it harder to rationalize early drawdowns.

The trade federation has run their general assembly every year since. I’ve staffed it four more times. The Portuguese interpretation booth now has three interpreters assigned rather than two, and the pairing request goes out with a co-work reference requirement attached.

If you’re planning a multilingual conference or association event with simultaneous interpretation and want a second set of eyes on your vendor structure and contingency planning — send me the brief. I’ll show you where the seams are before someone else finds them.