English-Only Rules and What the Law Allows

Why this matters

An English-only rule usually starts as a reasonable worry. A lift went wrong because the ground man shouted something the operator did not catch, or an English-speaking tech felt shut out of the crew's conversation, and the owner writes "English only on the job" on the break-room whiteboard. That sentence is the single most common way a small trade shop turns a safety concern into a national-origin discrimination claim. The law does not forbid every language rule. It forbids the broad one, and it sets out fairly precisely what a narrow one needs. This card is that test, run on two real drafts.

This is not legal advice. The point at which you stop reading articles and call an employment attorney is named below.

The federal layer: a presumption, an exception and a notice duty

The EEOC's guideline on speak-English-only rules is 29 CFR 1606.7, issued under Title VII of the Civil Rights Act, which covers employers with 15 or more employees. It has three parts.

• A rule requiring English at all times in the workplace, breaks and lunch included, is presumed to violate Title VII. The EEOC treats a person's primary language as closely tied to national origin, and a total ban as a burden on the people whose first language is not English.
• A rule applying only at certain times is allowed when the employer can show it is justified by business necessity.
• The employer must tell employees the general circumstances when English is required and what happens if they break the rule. Discipline under a rule nobody was told about can itself be evidence of discrimination.

One honest complication: federal courts have not uniformly adopted the EEOC's presumption. Some appeals courts, the Ninth Circuit most prominently, have declined to defer to it and asked the employee to prove harm instead. That matters to a lawyer arguing a case. It should not matter to you, because the EEOC applies its guideline when it investigates a charge, and in some states, California among them (below), the state rule is stricter than either version.

What counts as business necessity, and what does not

EEOC guidance gives the kinds of reasons that can justify a limited rule:

• Communicating with customers, coworkers or supervisors who speak only English.
• Emergencies and other moments where everyone must understand at once, such as a lift, an energized-equipment hand-off or an evacuation.
• Cooperative work that requires a shared language to be done safely or efficiently.
• Letting an English-only supervisor follow work where the job itself is spoken, such as a customer call the supervisor is responsible for.

Reasons that do not work, however often they are offered:

• Coworker discomfort. "The others feel they are being talked about" is a conduct issue. Address the conduct (exclusion, insults) with a conduct rule that applies in every language.
• Customer preference for not hearing another language, on its own.
• Breaks, lunch, the truck ride, personal calls. Time when the worker is not doing the task that needs a shared language.
• Two workers who share a language talking to each other while working alone. Nobody else needs to understand that conversation.

The test underneath all of these: the rule must tie a specific moment to a specific person who would otherwise not understand, and the harm that misunderstanding would cause.

The state layer: California's statute is stricter, and others go lower on headcount

States routinely override the federal floor here, in two ways.

• Who is covered. California's Fair Employment and Housing Act reaches employers with 5 or more employees; New York and New Jersey reach employers of any size. A ten-person shop outside Title VII is often inside its state law.
• How narrow the rule must be. California Government Code 12951 makes a language restriction unlawful unless it is justified by business necessity AND the employer has told employees when it applies and what happens if they break it. The state's regulations (2 CCR 11028) define business necessity tightly: an overriding legitimate business purpose, the rule must effectively serve it, and there must be no alternative practice that would do the job equally well with less discriminatory impact. The same regulations treat a restriction during non-work time, breaks and meals included, as not justified.

That third prong, the no-better-alternative test, is the one that changes drafts. Federal guidance asks whether you had a good reason. California also asks whether something less restrictive would have worked. Other states run their own versions; check your state's civil rights agency before you write anything.

The five parts of a rule that survives

1. Scope: the exact tasks or moments, not a place or a whole shift.
2. Reason: who would not understand, and what goes wrong if they do not.
3. The shared language: often English, but not always. If everyone on the task shares another language, the necessity points to that language, not to English.
4. Notice: written, given before enforcement, and in the languages the crew reads.
5. Enforcement: the same consequence for everyone who breaks it, recorded the same way.

One gate, two drafts: a 22-person roofing company

The shop has 22 employees, so Title VII applies, and it operates in California, so FEHA and 12951 apply as well. Two weeks ago a bundle came off a hoist early because the ground spotter's call was not understood by the hoist operator. Nobody was hurt. The operator speaks and reads English only. Of the six people on the lift crew, four are Spanish-dominant.

Draft A, the whiteboard version: "English only on all job sites. Violations will be written up."

Run it through the five parts. Scope: everywhere, all the time, which includes lunch and the drive. Reason: none stated. Shared language: assumed English for everyone, including four people talking to each other on the roof. Notice: a whiteboard in English only. Enforcement: undefined. It fails at every part, and under the federal guideline it is the presumed-unlawful shape. Under California's regulations its coverage of breaks alone would sink it.

Draft B, the scoped version: "During hoist lifts and roof-edge material hand-offs, every lift call is made using the shop's standard lift-call list. The calls are made in English because the assigned hoist operator speaks English only. This applies only from the 'ready' call to the 'clear' call. It does not apply to any other conversation, at any other time. A first missed call means the lift stops and the call is repeated; repeated missed calls are handled as a safety-procedure issue, the same as missing a harness check."

Run it through the five parts. Scope: a defined window with a start and an end call. Reason: a named person who would not understand, and a named harm (a load released on a wrong call). Shared language: English, because of the operator. Notice: given in English and Spanish, with the call list in both. Enforcement: the same as any other safety procedure, and it starts with stopping the lift rather than discipline.

Under the federal layer, Draft B is the kind of limited rule 1606.7 allows. Under California's third prong it still faces a question Draft A never got far enough to meet: was there a less restrictive way to get the same safety? Here there plausibly was. The operator could learn the dozen calls on the list in both languages, and the crew could use the standard hand signals as the primary channel with the spoken call as backup. If the shop does that, it may not need a language rule at all, only a call list and a signal standard that everyone drills.

What flips it the other way. Next season the shop hires a bilingual operator for that crew. The reason in Draft B is gone: everyone on the lift now shares Spanish, and requiring English for the calls would be a rule with no necessity behind it. A rule that was defensible in April can become indefensible in June because one person changed. Tie the rule to the condition, and review it when the crew changes.

The failure mode the shop actually risks is not the drafting. It is the foreman who reads Draft B, remembers "English on the roof," and tells two crew members to stop speaking Spanish while they tear off shingles twenty feet from any lift. That enforcement, not the written rule, is what ends up in the charge.

Where to stop and call an employment attorney

Stop and get advice before you act when any of these is true: you are about to discipline or fire someone under a language rule; an employee has complained that a language rule targets them; the rule would apply to customer-facing speech in a way that reaches the employee's own accent or fluency (see related: Accent and the Customer Phone Call); or you are in California or another state with a no-less-restrictive-alternative test and you cannot write down what alternative you considered. Walk in with the written rule, the date and form of notice, the incident that prompted it, the crew roster with the languages people work in, and every write-up issued under it.

How to check a rule you already have

Read your current rule against the five parts and answer each in writing. If you cannot name the person who would not understand and the harm, you do not have a reason. If the rule covers breaks or the truck ride, cut that. If the notice exists only in English, reissue it. Then ask each foreman to explain the rule back in their own words; the answer tells you what is actually being enforced.

References

• EEOC, Speak-English-only rules, 29 CFR 1606.7, under Title VII of the Civil Rights Act of 1964 (employers with 15 or more employees)
• EEOC Enforcement Guidance on National Origin Discrimination (2016), section on language-restriction policies
• California Government Code 12951 and California Civil Rights Council regulations, 2 CCR 11028
• See related: Building a Two-Language Shop Glossary
• See related: Safety Training in a Language the Crew Understands