{"resourceId":"boston-olca-human-interpreting-rfp-no-ai-20261019","versions":[{"version":"external-ea8c7ec25c46d8918c93d3f66e3ec3b65a7ed7bda893049ffc162a47b8db1bbe","resource":{"id":"boston-olca-human-interpreting-rfp-no-ai-20261019","title":"Boston seeks a $3 million, human-only phone and video interpreting contract with no AI provisions; Massachusetts' statewide interpreting contract bars AI in sessions","organization":"City of Boston Office of Language and Communications Access (OLCA); Massachusetts Operational Services Division statewide contract PRF88","sector":"Language access for resident services","geography":"Boston, Massachusetts, United States","publishedAt":"2026-10-19","publicationDate":"2026-10-19","eventDate":"2026-11-06","sourceName":"Slator","sourceLabel":"Slator: Boston taking bids for remote interpreting contract","sourceUrl":"https://slator.com/boston-seeks-remote-interpreting-vendor/","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["accessibility-workforce","governance-procurement","data-security"],"finding":"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.","sledRelevance":"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":"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.","architectureImplications":"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.","governanceImplications":"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.","securityPrivacyImplications":"The RFP requires data isolation and explicit permission before constituent data is used for unauthorized purposes, a clause worth copying for any language vendor.","caveats":"Solicitation, not an outcome; AI exclusion in the city RFP is as reported by Slator; PRF88 date of the AI clause not shown.","streamIds":["citizen-engagement"],"roles":{"sales":"The lesson is that many buyers still want human interpreters, and Massachusetts' statewide contract forbids AI in sessions. Pitching AI translation into these accounts will fail unless it stays outside live interpreting. Discovery should ask where AI is barred, where written translation allows disclosed AI, and how wait times are tracked. A bounded engagement is a language access operations review. The source shows no AI performance data.","engineering":"Engineering fit is integration, not AI: the vendor must connect to Boston's call-center systems and single sign-on and report usage by department, language and wait time. Teams should check state contract terms before proposing any machine translation, because PRF88 bans AI during interpreting sessions, including captioning. Data isolation and limits on use of constituent data must be built into any language platform.","delivery":"Delivery should map which interpreting and translation channels allow AI under city and state rules, and keep live interpreting human where required. Use the RFP's reporting fields to build a baseline of demand and connection wait. Acceptance criteria below are proposals. Any AI translation pilot elsewhere in the organization needs separate approval, disclosure and human review."},"roleDetails":{"sales":{"customerProblem":"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"],"discoveryQuestions":["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?"],"valueHypothesis":"Central contracting with usage reporting can show where interpreting demand and waits are highest; no AI benefit is claimed.","potentialEngagement":"A language access operations review mapping channels, contract rules on AI and demand data.","unsupportedClaims":["That AI interpreting is acceptable under Massachusetts contracts","That human-only interpreting is cheaper or better by measure","Any outcome of the Boston award"]},"engineering":{"fit":"Fits cities with central language access offices and call-center integration needs.","architectureIntegration":"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.","proofOfValue":["Check that usage reports capture wait time by language","Confirm no AI captioning or transcription is enabled in sessions"]},"delivery":{"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.","skillsAdoption":"Staff need guidance on requesting interpreters and when certified interpreters are needed.","governanceCheckpoints":["Contract award review","Quarterly usage and wait-time review","Annual review of AI rules in language contracts"],"acceptanceCriteria":["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"]}},"retrievedAt":"2026-11-01T03:11:44Z","enrichedAt":"2026-11-01T03:16:59Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Requires ASL and prefers Certified Deaf Interpreters, keeping deaf and hard-of-hearing residents in scope.","procurementImplications":"Buyers can split human interpreting from any AI translation pilot and require usage reporting by department and wait time.","operatingModelImplications":"Departments draw on one central contract, so OLCA can measure demand and wait times across the city.","sourceVerification":{"openedUrl":"https://slator.com/boston-seeks-remote-interpreting-vendor/","referenceExcerpt":"The RFP contains no provisions for AI interpreting, machine translation, or other AI language services, and its scope is built entirely around human interpreters.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}