Boston's $3M Interpreting Contract and What Cities Miss

Boston Just Put $3 Million on the Table for Remote Interpreting

The City of Boston is soliciting bids for a remote interpreting contract worth up to USD 3 million, requiring around-the-clock over-the-phone interpreting (OPI) and video remote interpreting (VRI) coverage across 17 spoken languages plus American Sign Language. Slator has the details.

No AI tools are mentioned in the requirements. That alone is worth noting in 2025.

Boston's procurement approach reflects a model you see across US municipal governments: define a language list, set a coverage window, and find one vendor who can handle all of it. It works reasonably well for Spanish, Portuguese, Haitian Creole, and Mandarin. It breaks down quietly for everything else.

The 17-Language Problem

Publishing a list of 17 required languages signals that Boston knows its population is linguistically diverse. Greater Boston is home to significant communities speaking Cape Verdean Creole, Vietnamese, Cantonese, Somali, and Arabic, among others. A contract of this size should cover those speakers reliably.

But "17 languages" is a procurement ceiling, not a floor. City residents who speak languages outside that list still walk into emergency rooms, courthouses, and social services offices. When they do, whoever holds the contract has no obligation to help them.

This is how language access gaps persist even inside well-funded programs. The contract looks comprehensive on paper. The coverage is real for most callers. But the resident who speaks Chuukese or Pohnpeian, two Micronesian languages spoken by growing communities across the US mainland, is outside the scope before the call even connects.

What Rare-Language Speakers Actually Experience

Chuukese and Pohnpeian speakers are concentrated in Micronesian diaspora communities in Hawaii, Guam, Arkansas, and increasingly in Pacific Northwest and mid-Atlantic cities. Federal Compact of Free Association agreements give Micronesian citizens the right to live and work in the United States without a visa. Many do. And when they interact with public services, they frequently encounter a wall.

A typical scenario: a Chuukese-speaking patient arrives at a hospital. The hospital's contracted OPI vendor covers 240 languages on their marketing sheet. The patient's language is listed. But the vendor's actual on-demand availability for Chuukese at 2 a.m. is near zero. The hospital ends up using a bilingual family member, which creates liability, or documents the encounter as "interpreter unavailable," which creates a compliance problem.

Municipal interpreting contracts rarely solve this because they are structured around volume. A vendor wins a $3M contract by demonstrating capacity in the high-demand languages. Chuukese and Pohnpeian generate a small fraction of call volume, so they get deprioritized operationally even when they appear on a coverage list.

How Cities Can Write Better Procurement Language

Boston's RFP, as described, doesn't mention performance standards by language. That's a missed opportunity. Here's what stronger procurement language looks like:

That last row matters. Large LSPs routinely win government interpreting contracts and then subcontract rare languages to smaller specialists. There's nothing wrong with that model, but the subcontractor's qualifications, availability data, and interpreter credentials should be visible to the government buyer, not just to the prime.

The AI Silence Is Interesting

Boston's RFP apparently makes no mention of AI-assisted interpreting tools. Given how aggressively machine translation vendors have been pitching to public sector buyers, that's a deliberate or at least notable omission.

For high-stakes municipal contexts like emergency services, healthcare intake, and legal proceedings, human interpreting isn't a legacy preference. It's the right call. Telephone and video interpreting by trained human interpreters remains the standard that language access law and professional ethics actually require.

The risk in the next contracting cycle is that budget pressure pushes buyers toward hybrid or AI-first solutions without adequate testing in rare-language pairs, where machine translation quality is weakest and the consequences of errors are highest.

What Any City Bidding This Type of Contract Should Ask

If you're a procurement officer or language access coordinator evaluating an OPI/VRI contract, push your vendor candidates on three specific questions before you score their proposals.

First, ask for actual interpreter availability data by language, not a language list. Any vendor can print 200 languages in a brochure. Ask for average queue times and on-demand interpreter headcount for each language at three time windows: 9 a.m. weekday, 8 p.m. weekday, and 3 a.m. weekend.

Second, ask how they handle languages outside the contract list. Residents don't stop needing services because their language isn't on your RFP. Knowing the vendor's protocol for unlisted languages tells you a lot about how they'll actually perform.

Third, ask about subcontractor transparency. If a specialty language is being handled by a third party, you should know who that third party is, what their interpreter qualifications look like, and whether they have any track record with your specific resident population.

Boston's $3 million commitment is real money for language access, and that's worth recognizing. The question is whether the contract structure captures the full complexity of who actually needs help.

If your organization is working through a remote interpreting procurement and needs guidance on rare-language coverage, TXLOC is happy to talk through what realistic availability looks like for Pacific and Micronesian languages specifically.