Bilingual Pay Programs: How Government Agencies Qualify Staff — and Prove It

Your best Spanish-speaking caseworker resigned last month. In the exit interview she mentioned, almost in passing, that a colleague two desks over has been drawing a language differential for three years — and that she has never once heard him speak Spanish to a resident.

Now you have two problems and documentation for neither. Somebody who genuinely carried the agency’s Spanish-language workload was never paid for it. Somebody else may have been paid for a skill nobody ever measured. If a union representative, an auditor, or a reporter asks how your agency decides who gets bilingual pay, “the supervisor vouched for them” is not an answer that survives the follow-up question.

This is the quiet failure mode of bilingual pay programs. They are usually created with good intent, funded in the budget, written into an MOU — and then run on self-reported fluency for a decade. Here is how to put a defensible one in place.

What is a bilingual pay program?

A bilingual pay program — also called foreign language incentive pay (FLIP), a bilingual differential, or language proficiency pay — is additional compensation for public employees who use a language other than English as part of their official duties. It shows up as a flat monthly amount in some jurisdictions and as a percentage of base pay in others.

Whatever it is called locally, a working program has three parts:

1. Designated positions. Which roles actually require the language, and how much of the job it represents.
2. A proficiency standard. What level of skill qualifies, in which modalities, measured how.
3. A recertification cycle. How often qualification is re-verified, and what happens when it lapses.

Most programs that get into trouble have the first part and skip the second.

What law actually authorizes bilingual pay?

There is no single national bilingual pay statute. Authority is layered, and where your agency sits determines which layer governs you.

Federal law enforcement. Under 5 U.S.C. §§ 4521–4523, an agency may pay a cash award of up to 5 percent of basic pay to a law enforcement officer who “possesses and makes substantial use of 1 or more foreign languages in the performance of official duties.” Read § 4523 closely: it requires the agency head to prescribe regulations that “include procedures under which foreign language proficiency shall be ascertained.” Testing is not a nice-to-have layered on top of the statute. The statute contemplates it.

Military. Service members receive the Foreign Language Proficiency Bonus under 37 U.S.C. § 353(b), implemented through DoD Instruction 1340.27, which caps the bonus at $1,000 per month per member. Eligibility is tied to Defense Language Proficiency Test results mapped to Interagency Language Roundtable (ILR) levels — a fully standardized, test-driven model.

State and local government. Here, authority comes from state statute, local ordinance, or a collective bargaining agreement. California is a useful template because its rules are public and specific: the Dymally-Alatorre Bilingual Services Act (Cal. Gov. Code §§ 7290–7299.8) drives the underlying obligation, and CalHR requires that a designated bilingual position use the non-English language for at least 10 percent of work time, with the employee scoring at least ILR level 2 in listening and speaking. CalHR also states plainly that a state agency may develop and provide language proficiency testing directly or by contract.

That last clause matters. Nothing requires an agency to build a testing apparatus in-house — only to have one.

Does the shifting federal language access landscape change any of this?

It changes the framing, not the obligation. Executive Order 14224, signed March 1, 2025, designated English as the official language of the United States and revoked Executive Order 13166. Federal agencies were subsequently directed to review and rescind guidance built on the revoked order.

What did not change: Title VI of the Civil Rights Act of 1964 (42 U.S.C. § 2000d) is a statute, and an executive order cannot amend it. Section 1557 of the Affordable Care Act still applies to health programs. State language access laws are untouched. We covered the details in our guide to what language access requires of public agencies now.

For a bilingual pay program, the practical read is this: qualified bilingual staff are one of the most cost-effective ways an agency has to serve limited-English-proficient residents. Tightening the verification behind the differential makes that spend easier to defend, not harder.

What proficiency standard should you require?

The ILR scale is the common currency of U.S. government language work. It runs from 0 (no practical proficiency) to 5 (functionally native), with plus levels between the base levels.

• ILR level 2 — Limited Working Proficiency. The speaker can handle routine social demands and limited work requirements, gets the gist of most non-technical conversation, and can respond with some circumlocution. This is California’s floor for a bilingual differential, and it is a reasonable floor for routine public-facing contact: intake, scheduling, directions, general questions.
• ILR level 3 — General Professional Proficiency. Accurate, structured, professional-register language. This is the honest minimum for encounters where a misunderstanding does real damage — benefits eligibility, investigative interviews, clinical intake, anything with due-process consequences.

Two design details separate a real standard from a checkbox:

Test the modalities the job actually uses. A 911 dispatcher needs listening and speaking. A benefits worker who drafts determination letters needs reading and writing too. Testing speaking alone and then assigning written translation work is how bad translations end up on agency letterhead.

Set the standard before you test anyone. Publishing the threshold and the scale in advance — in the policy, not in an email after the fact — is what makes the program survive a grievance.

Does bilingual pay mean the employee can interpret?

No, and this is the single most expensive misunderstanding in the field.

Federal regulation actually draws the line for you. Under 45 CFR 92.4, implementing Section 1557, “qualified bilingual/multilingual staff” means a workforce member designated to provide in-language oral assistance as part of their assigned duties, who has demonstrated proficiency in speaking and understanding both English and the other language — including the necessary specialized vocabulary — and who can communicate effectively, accurately, and impartially with LEP individuals in their primary language. Meeting that definition does not, by itself, qualify someone to interpret or translate. Those are separate standards.

Interpreting is a trained skill layered on top of bilingualism: managing register, rendering meaning completely without editing it, staying impartial, handling terminology under time pressure. A perfectly bilingual nurse is not automatically a medical interpreter, and a bilingual clerk is not a court interpreter.

So build the program with that ceiling in mind. Bilingual staff handle the everyday volume. Professional interpretation covers the high-stakes encounters, the languages your staff do not cover, and the days your bilingual employees are on leave.

How do you stand up a defensible program?

Four steps, in order:

1. Designate the positions. Document which roles use a non-English language and roughly how much of the job it represents. Ten percent of work time is a widely used threshold and a sensible starting point.
2. Set and publish the standard. Pick the scale (ILR is the safest default for public agencies), pick the level, and specify the modalities per job family. Put it in the policy before testing begins.
3. Test independently. Use a standardized assessment administered by someone with no stake in the outcome, and require a written, scored report that goes into the HR file. Independence is what converts a pay decision into a documented one.
4. Requalify on a calendar, and cover the gaps. Most programs recertify on a one-to-five-year cycle. Track it centrally so nothing lapses silently, and keep a translation and interpretation provider on contract for everything your bilingual roster cannot cover.

How does Taika Translations help agencies run this?

We work with federal, state, local, and tribal agencies across the whole cycle: designing or reviewing the qualification standard, administering standardized oral and written proficiency assessments scored on ILR, CEFR, or your agency’s own scale, and delivering the written reports your HR and legal teams need in the file. Assessments cover spoken and written languages as well as ASL, which many bilingual-pay policies recognize.

When the roster does not cover the need — an unusual language, a vacancy, or a high-stakes encounter that calls for a trained interpreter rather than a bilingual employee — the same team provides interpretation and professional document translation across 300+ languages, backed by our government language services practice. Our processes meet and exceed ISO 17100, 9001, and 27001 standards. Our accuracy commitment is scoped to the language work we deliver — never to any personnel, pay, or program decision an agency makes using it.

This article is general information, not legal or labor-relations advice. Confirm your obligations with agency counsel and your bargaining unit before changing a compensation policy.

---

Stop paying for a skill nobody measured. Tell us which roles use a second language, which languages your community speaks, and what your policy currently requires, and we will scope proficiency testing and backup language coverage that stands up to an audit. Request a quote or read more about government bilingual pay and language proficiency testing.