From the Citizen Engagement & Services edition of October 31, 2026
Boston seeks a $3 million, human-only phone and video interpreting contract with no AI provisions; Massachusetts' statewide interpreting contract bars AI in sessions
City of Boston Office of Language and Communications Access (OLCA); Massachusetts Operational Services Division statewide contract PRF88 · Language access for resident services · Boston, Massachusetts, United States
- Publisher
- Slator
- Original publication
- 2026-10-19
- Source retrieved
- 2026-11-01
- Event date
- 2026-11-06
What happened
Boston's OLCA is seeking one vendor for over-the-phone and video remote interpreting worth up to $1 million a year, or $3 million over three years, running November 2026 to October 2029. Required coverage is 17 spoken languages plus American Sign Language on video. Interpreters must be pre-qualified, tested and professionally trained, and the city can request court-certified interpreters. The vendor must report usage by department, language, call length and connection wait. Per Slator, the RFP has no provisions for AI interpreting or machine translation, and it requires city data isolation and written permission before constituent data is used for other purposes. Proposals are due Nov. 6. Separately, the Massachusetts statewide interpreting contract PRF88 bars vendors from using AI or machine translation during interpreting sessions, including for notetaking, transcription and captioning.
Why it matters
A large city and a state contract are both building language access around human interpreters while other jurisdictions pilot AI translation. With bids due Nov. 6, it shows the choice agencies face between human-only interpreting and AI language tools. It is newly relevant because the bid window closes next week.
Evidence and measured results
Trade-press summary of RFP documents; the city bid page was opened and confirms the solicitation; the PRF88 user guide was opened and states the AI prohibition. The full RFP PDF was not read line by line, so the absence of AI provisions rests on Slator's reading.
Limitations and uncertainty
Solicitation, not an outcome; AI exclusion in the city RFP is as reported by Slator; PRF88 date of the AI clause not shown.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-01; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Cities must provide interpreting across many languages and ASL while rules limit AI use in live sessions.
- Stakeholders
- Language access office director
- Department heads using interpreters
- Procurement
- Deaf and hard-of-hearing community representatives
- Discovery questions
- Which of your contracts bar AI in interpreting or require disclosure in translation?
- What are current connection wait times by language?
- How is constituent data from calls protected?
- Value hypothesis
- Central contracting with usage reporting can show where interpreting demand and waits are highest; no AI benefit is claimed.
- Potential engagement
- A language access operations review mapping channels, contract rules on AI and demand data.
- Unsupported claims
- That AI interpreting is acceptable under Massachusetts contracts
- That human-only interpreting is cheaper or better by measure
- Any outcome of the Boston award
Pre-sales engineering
Role takeaway
- Fit
- Fits cities with central language access offices and call-center integration needs.
- Architecture and integration
- Interpreting platform connected to the city call center and single sign-on, with usage reporting by department, language and wait.
- Prerequisites
- Call-center integration points
- SSO configuration
- Reporting requirements
- Constraints
- PRF88 bars AI during interpreting sessions
- Data must stay isolated
- Certified interpreters on request
- Security
- Require written permission before constituent data from sessions is used for any other purpose.
- Proof of value
- Check that usage reports capture wait time by language
- Confirm no AI captioning or transcription is enabled in sessions
Delivery
Role takeaway
- Work
- Transition to a new interpreting contract while keeping service continuous.
- Dependencies
- Vendor onboarding
- Call-center integration
- Department training
- Ownership
- Office of Language and Communications Access.
- Skills and adoption
- Staff need guidance on requesting interpreters and when certified interpreters are needed.
- Governance checkpoints
- Contract award review
- Quarterly usage and wait-time review
- Annual review of AI rules in language contracts
- Acceptance criteria
- Proposed: median connection wait reported by language each quarter
- Proposed: all 17 required languages and ASL available at launch
- Risks
- Service gaps during transition
- Vendor shortfalls in rare languages
- Confusion over where AI is allowed
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Integration with the city's call-center infrastructure and single sign-on is priced as a platform fee; usage reporting gives a baseline for any later comparison with AI tools.
Governance
Who approves, reviews and stays accountable for outcomes?
Human-only scope and the state contract's explicit AI ban set a clear default; any AI translation would need a separate decision and disclosure.
Security and privacy
What data, permissions and controls need testing?
The RFP requires data isolation and explicit permission before constituent data is used for unauthorized purposes, a clause worth copying for any language vendor.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Requires ASL and prefers Certified Deaf Interpreters, keeping deaf and hard-of-hearing residents in scope.
Procurement
What should contracts, pricing and exit terms secure?
Buyers can split human interpreting from any AI translation pilot and require usage reporting by department and wait time.
Operating model
Which teams own the service once it runs?
Departments draw on one central contract, so OLCA can measure demand and wait times across the city.
Publication history
Read preserved resource versions (JSON)Stable resource ID: boston-olca-human-interpreting-rfp-no-ai-20261019