From the Citizen Engagement & Services edition of October 30, 2026
Washington County, Oregon's 2026 Language Access Framework limits AI translation to brief contacts, requires human review, disclosure and a no-training clause
Washington County, Oregon, Office of Access and Opportunity · County language access policy · Washington County, Oregon, United States
- Publisher
- Washington County, Oregon
- Original publication
- 2026-09-30 (date of certification)
- Source retrieved
- 2026-10-31
- Event date
- 2026-09-30
What happened
The framework, certified Sept. 30, 2026 for 2026 to 2028, allows AI and automated translation only for brief initial point-of-contact exchanges and says these tools are not an acceptable substitute for qualified interpretation in substantive interactions. Machine translation may not be the sole method for rights and benefits information, eligibility, deadlines, legal notices, emergency instructions, complaint intake or public participation materials. Residents must be told at the outset when an AI tool is used and offered a qualified interpreter. Departments must notify the county before piloting AI language tools and log translation errors. The county evaluates vendor data practices and requires a contractual ban on using county interactions for model training unless an exception is granted. Vital webpages must be professionally translated.
Why it matters
A concrete, adoptable county policy for AI in language access, newly relevant this week as California's courts cancelled an AI counter-translation rollout. It gives other counties and cities model language for disclosure, human review, error logging and vendor data terms.
Evidence and measured results
Primary policy document; describes requirements, not measured outcomes. Implementation timelines run from adoption over 30 to 180 days.
Limitations and uncertainty
Policy, not evaluation; compliance and enforcement not yet observable; written for one county's Title VI obligations.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-31; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Agencies need clear rules for when AI translation is acceptable for residents with limited English.
- Stakeholders
- Language access or equity officer
- Department directors
- County counsel
- Procurement and IT
- Discovery questions
- Do you have written limits on AI translation for rights, benefits and safety topics?
- Do vendor contracts prohibit training on resident interactions?
- How are AI translation errors reported and reviewed?
- Value hypothesis
- Clear policy and contract terms could lower legal and trust risk when adopting AI language tools; benefit is not measured.
- Potential engagement
- A policy and contract-terms review that adapts this framework's AI provisions to the client's jurisdiction.
- Unsupported claims
- That AI translation is safe for vital documents
- Any outcome data from Washington County
- Applicability without legal review in other states
Pre-sales engineering
Role takeaway
- Fit
- Applies to AI interpretation, chat translation and website translation used by any county department.
- Architecture and integration
- Require disclosure at start, trigger-topic handoff to human interpreters, error logging and data-location controls in each tool.
- Prerequisites
- Vital document and webpage inventory
- Interpreter service on call
- Vendor data-flow documentation
- Constraints
- Title VI obligations
- Safe Harbor language list
- Vendor platforms may route data outside the United States
- Security
- Contractual ban on model training with county interactions and review of storage location and data transfer.
- Proof of value
- Confirm disclosure appears in each supported language
- Test that trigger topics hand off to a human
- Audit vendor data handling against the contract
Delivery
Role takeaway
- Work
- Roll out AI language-tool governance across departments.
- Dependencies
- Access office staff
- County counsel
- Vendors and interpreter services
- Ownership
- County Office of Access and Opportunity, with department language liaisons.
- Skills and adoption
- Front-desk staff need training on trigger topics and disclosure scripts.
- Governance checkpoints
- Pre-pilot notification and approval
- Vendor data-governance review
- Periodic error-log review
- Acceptance criteria
- Proposed: 100% of approved AI tools disclose AI use at the start of each interaction
- Proposed: vital webpages professionally translated on the framework timeline
- Risks
- Staff using unapproved tools
- Errors not reported
- Vendor terms not updated
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?
Website machine translation stays available for general understanding, but vital pages and forms need professional translation; AI tools must support disclosure and handoff to human interpreters.
Governance
Who approves, reviews and stays accountable for outcomes?
Central review of any AI language pilot, error logging, and vendor data-governance review before approval.
Security and privacy
What data, permissions and controls need testing?
Requires review of where conversation data is stored, whether it trains models and whether it leaves the United States, with a default contractual ban on training use.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Front-desk staff must recognize topics that trigger an immediate move to a qualified interpreter; the framework also covers digital accessibility standards.
Procurement
What should contracts, pricing and exit terms secure?
Vendors may not use AI machine translation for county services without prior written approval and disclosure.
Operating model
Which teams own the service once it runs?
Puts the county access office in charge of approving, monitoring and evaluating AI language tools across departments.
Publication history
Read preserved resource versions (JSON)Stable resource ID: washington-county-or-language-access-framework-ai-limits-20260930