How to Build a Language Access Plan for Your Bay Area Organization

What Is a Language Access Plan?

A language access plan is a written policy that spells out how an organization identifies people with limited English proficiency, decides which languages to support, and delivers interpretation, translation, and staff training to reach them. A solid plan usually covers four things: how the organization learns which languages its community speaks, which services and documents get translated first, how it trains and deploys interpreters, and how it checks whether the plan is actually working.

Some organizations write a language access plan because a law requires it. Others write one because it is simply good practice: a documented plan turns "we'll find someone who speaks Spanish" into a repeatable process, and it gives every employee a clear answer when a client, patient, or resident with limited English proficiency walks in the door.

Who Actually Has to Have One?

The legal picture here has shifted recently, so it is worth being precise about what currently applies. Title VI of the Civil Rights Act of 1964 prohibits national-origin discrimination, including denying someone meaningful access to a program because he or she has limited English proficiency, by any organization that receives federal financial assistance. That statute has not changed. For 25 years, Executive Order 13166 told federal agencies and federal-fund recipients exactly how to meet that obligation. In March 2025, a new executive order designating English as the official language of the United States revoked Executive Order 13166, which gives individual federal agencies more discretion over how they enforce language access under Title VI going forward. It did not repeal Title VI itself, and it did not direct any organization to stop offering language services it already provides.

Two groups face requirements that federal change did not touch. Healthcare organizations that receive federal funding, including most hospitals, clinics, and health plans that take Medicare or Medicaid, must still meet Section 1557 of the Affordable Care Act, which sets a "qualified interpreter" standard and requires a posted notice of free language assistance. California adds another layer: state and local government agencies, along with many of their contractors and grantees, have carried a language access obligation since 1973 under the Dymally-Alatorre Bilingual Services Act, which requires bilingual staff and translated materials once a non-English-speaking group makes up a substantial share, generally 5 percent, of the people an office serves.

Because federal guidance is in flux, an organization that is unsure whether it is legally required to have a language access plan should confirm its current obligations with legal counsel or the relevant agency rather than rely on this article as legal advice. Plenty of organizations without a strict legal mandate build a plan anyway, for the same reason a good customer-service policy exists without a law requiring it.

The Core Elements of a Language Access Plan

Whether a language access plan is required or voluntary, the strongest ones share the same basic structure:

• Language data: a simple process for tracking which languages the people an organization serves actually speak, updated on a regular schedule instead of assumed once and forgotten.
• Qualified interpreters: a defined way to reach a trained interpreter (on-site, by phone, or by video) for every language the data shows matters, not just the one or two most common ones.
• Translated vital documents: intake forms, consent forms, notices of rights, and other documents a person needs to understand before he or she can make an informed decision, translated into the organization's priority languages.
• Staff notice and training: a posted or handed-out notice that free language assistance is available, plus training so front-line staff know how to request an interpreter instead of relying on an untrained bystander or a relative.
• A complaint and feedback process: a clear way for someone who was denied language access to say so, and a process for the organization to review and respond.
• A review cycle: a set schedule, typically annual, to revisit the language data, confirm the plan still matches the community being served, and update it.

What Bay Area Organizations Should Watch For

The San Francisco Bay Area's language diversity makes this more than a paperwork exercise. San Francisco's own Language Access Ordinance requires public-facing city departments to translate vital documents, signage, and even certain website and social media content into the city's threshold languages: Chinese (Cantonese and Mandarin), Spanish, Filipino, and, since a 2024 amendment lowered the qualifying population threshold, Vietnamese. An organization that contracts with the city, or that simply serves the same neighborhoods, will likely need to reach the same residents in the same languages.

Beyond those four threshold languages, Bay Area organizations commonly need support in Russian, Korean, Japanese, Arabic, and a range of Chinese and Filipino dialects, depending on the neighborhood and industry. A language access plan built only around Spanish will miss a meaningful share of the region's limited-English-proficient residents. Reviewing current, local population data, instead of assuming last year's mix still holds, is part of what keeps a plan accurate.

Common Mistakes Organizations Make

A few patterns show up again and again in language access plans that do not hold up under review. The most common is relying on a bilingual employee or a client's family member for anything beyond a routine, non-clinical conversation; current guidance treats a professional, qualified interpreter as the standard once a conversation touches on consent, legal rights, or a diagnosis, and a person's minor child should not be asked to interpret except in a genuine emergency. A close second is writing the plan once and never updating the language data, so the organization keeps translating into a language its community stopped needing years ago while missing one it now needs. A third is treating free machine-translation tools as a substitute for a trained interpreter or translator; they can work as a reasonable stopgap for a quick, low-stakes exchange, but they routinely miss idiom, tone, and cultural context, which matters most in medical, legal, or benefits-related conversations where getting it wrong carries real risk.

How Auerbach International Supports Language Access Plans

Auerbach International has supported healthcare organizations, government agencies, and Bay Area businesses with language services since 1990. Building a language access plan usually starts with the same conversation: which languages does your community actually speak, which documents and services matter most, and how quickly do you need an interpreter available? From there, our team can provide on-demand telephonic and video interpretation for the languages your plan identifies, along with certified translation of vital documents such as intake forms, consent forms, and notices of rights. For a closer look at how the interpreting side works day to day, our guide to over-the-phone versus video remote interpreting compares the two most common on-demand formats.

If your organization is ready to document or update its language access plan, request a quote from Auerbach International and share your top languages, document volume, and delivery preferences so our team can recommend the right mix of services.

Frequently Asked Questions

Is a language access plan legally required?

It depends on the organization. Healthcare organizations that receive federal funding must meet Section 1557 of the Affordable Care Act, and California state and local government agencies, along with many contractors and grantees, must meet the Dymally-Alatorre Bilingual Services Act once a non-English-speaking group reaches a substantial share of the people they serve. Title VI of the Civil Rights Act applies more broadly to organizations receiving federal funds, though 2025 federal guidance changes give agencies more discretion in how they enforce it. An organization unsure of its own obligations should confirm them with legal counsel rather than assume either way.

What counts as a "vital document" that needs translation?

A vital document is anything a person needs to understand to access a benefit, service, or right. Consent forms, applications, notices of rights or denial, and instructions for what to do next are common examples. Marketing materials and internal memos generally are not vital documents, though an organization may choose to translate them anyway.

Can a bilingual employee serve as the organization's interpreter?

A bilingual employee can often help with quick, routine, non-clinical, non-legal exchanges. Once a conversation touches on medical consent, legal rights, or a formal complaint, current guidance calls for a trained, qualified interpreter, because being bilingual and being trained to interpret accurately and impartially are two different skills.

Which languages should a Bay Area organization prioritize first?

Start with the languages your own client, patient, or resident data actually shows. San Francisco's four citywide threshold languages (Chinese, Spanish, Filipino, and Vietnamese) are a reasonable starting checklist for organizations serving the general public in the city, but Bay Area organizations in specific industries or neighborhoods often need to add languages such as Russian, Korean, or Arabic based on who they actually serve.

How often should a language access plan be reviewed?

An annual review is a common baseline, though an organization with a fast-changing client or resident population may want to check its language data more often. California's Dymally-Alatorre Act specifically requires state and local agencies to review their language needs at least every two years.