Check hiring decisions for race bias by reviewing motivation, stereotypes, vague wording and every basis a claim could raise before the decision is final.
Key takeaways
- write the stated reason for each decision before it is final.
- ask whether any reason depends on a stereotype about a group.
- treat vague phrases such as soft skills as a prompt for a closer look, not as proof.
- list every basis a claim could raise, not only the one you expect.
- keep a record that lets another reader follow your reasoning.
Title VII is violated, according to U.S. Equal Employment Opportunity Commission, if race was all or part of the motivation for an employment decision. That test does not require race to be the only reason, so a decision with several stated factors still needs review.
The four checks below turn that standard into questions you can answer from your own records.
Why hiring decisions get a second look
Small firms often make hiring calls quickly, and one hiring manager may be the only person who reads the reason behind a decision. A stated reason that nobody else reviews is hard to test later, so the review has to happen while the file is still open. The goal is not to accuse anyone. The goal is to make sure the reasoning can be read and checked by someone other than the person who made the call.
The guidance itself names the pattern that makes this review worthwhile. According to U.S. Equal Employment Opportunity Commission, people of color are more likely than Whites to work in lower-paying jobs and less likely to work in higher-paying jobs. The same passage says unlawful employment discrimination is one of the reasons for these disparities.
The useful test is whether a stranger could follow the logic from the notes alone. If the reasoning only makes sense to the person who made the call, the file will not hold up well under a second reader. That is a point about record quality, not a legal conclusion, and it applies to every file you keep.
The checks in this article draw on Section 15 of the new Compliance Manual. According to U.S. Equal Employment Opportunity Commission, that section is on “Race and Color Discrimination” and provides guidance on analyzing charges of race and color discrimination under Title VII of the Civil Rights Act of 1964. The questions below are editorial, built on that guidance.
The table below lists the three sources cited in this article and the wording each one supplies.
| Publisher | Source | Quoted wording |
|---|---|---|
| U.S. Equal Employment Opportunity Commission | Section 15 | provides guidance on analyzing charges of race and color discrimination under Title VII of the Civil Rights Act of 1964 |
| Minnesota Office of the Revisor of Statutes | Sec. 363A.02 | race, color, creed, religion, national origin |
| Colorado General Assembly | SB23-172 | Concerning protections for Colorado workers against discriminatory employment practices |
These checks do not make a firm immune from a claim, and they are not advice about a particular case. A written review shows that the reasoning was examined, which is useful on its own, but it does not settle the legal question. Bring a specific file to counsel when a claim is possible.
Check 1: Was race any part of the motivation
The first check is the plainest one. According to U.S. Equal Employment Opportunity Commission, the most obvious violation is a decision driven by racial animus. Most written reasons will not state animus in plain words, though, so this check reads the wording closely. Softer phrases can still carry the same problem, and the review has to look at what those phrases were meant to cover.
The useful starting point is the reason you wrote down for the decision. Read it as the applicant who was not selected would read it, and ask whether race could have been one of the things that moved the call. A reader outside the room often notices a gap that the person who made the call cannot see, because the call felt sound at the time. Write down what that outside reader would ask before you finalize.
A reason that never mentions race still needs the question asked of it, because race can be part of what drove a choice without appearing in the notes. A decision can have several stated factors, and each one needs its own answer. A passing overall reason does not clear a factor that was weak.
For each factor that carried weight, keep a short note on what it was and where it came from. Record the source of the factor, such as a test score, a reference answer or a work sample, so a reviewer can trace it. If a factor could only be explained by pointing to an applicant's race, color or national origin, mark the decision for a second reader before it is final.
A clean note is not proof of a clean decision. This check surfaces reasoning that needs a second look, and a passing answer here does not settle the other three checks. Keep the note with the file so that the next reviewer sees what was tested and what was not. A note that says the reason was tested is more useful than a note that says the decision was fair, because the first can be checked by a reviewer.
Check 2: Could stereotyped thinking have shaped the call
The second check looks past the reason you would defend in a meeting. According to U.S. Equal Employment Opportunity Commission, the statute covers not only decisions driven by racial animosity, but also decisions infected by stereotyped thinking or other forms of less conscious bias. That wider coverage is why a stated reason can pass a surface review and still fail this check.
The question is what the reasoning rests on, not what the decision-maker meant. A reviewer can ask whether each reason points to something in the applicant's record, and whether the same reason would appear for another applicant with a different background.
A practical test is to compare the notes for each applicant in the same round, and to see whether the same questions were asked and scored the same way. Use a shared scorecard format for this comparison.
Look for reasons built on a group's general traits rather than on the applicant's own record. A phrase such as “an applicant would not fit the team's culture” can hide an assumption, so ask what evidence in the applicant's record supports it. If the answer points only to a general impression, write that down as an impression and do not treat it as a finding.
This check cannot show what a decision-maker was thinking. It can show which reasons rest on evidence written down during the process and which rest on impressions that nobody recorded. That distinction is useful when a file is reviewed later, because an impression that was never recorded is hard to examine. Keep the answer to this check beside the answers to the other three.
Check 3: Do vague phrases like soft skills hide bias
The third check looks at the words used to justify a decision. The guidance quotes an employer who said, “I have to make sure the people I hire have, you know, the ‘soft-skills’ we need.” According to U.S. Equal Employment Opportunity Commission, statements like that could be reflective of racial stereotyping and bias.
The wording itself matters here. A reason stated in general terms gives the reviewer nothing specific to test, so the vague phrase itself becomes part of the file that needs review. Vague wording turns an evaluation into a label, and a label cannot be checked against a record. The phrase may be sincere, but the file still needs a concrete basis.
The phrase alone does not prove a violation. Treat it as a flag that prompts a closer look at what the decision actually rested on. A flag is a reason to review the file, not a finding about the person who wrote the note. Ask what the decision would look like if the phrase were removed and only the observed behavior remained.
For each soft-skill label, record the behavior you saw in the interview or work sample instead of the label. A note that says the applicant explained a past project clearly is easier to check than the phrase “soft skills.” Write the question you asked, the answer you heard and the score you gave, so the reasoning can be followed step by step.
If the criteria came from a test, the Validate hiring tests: 4 checks for small staffing firms article is a relevant place to look. Vague wording is not limited to soft skills, and phrases that stand in for a documented reason deserve the same review. Replace each general phrase with the documented reason it was meant to describe, and mark any phrase that has no documented reason.
Check 4: Have you named every basis a claim could raise
The fourth check is about the claim, not only the decision. According to U.S. Equal Employment Opportunity Commission, a discrimination complaint by an “Asian Indian” can implicate race, color, and national origin. A single complaint can therefore name more than one basis, and a file that lists only the first one may miss the others.
The same guidance gives further examples. According to U.S. Equal Employment Opportunity Commission, a complaint by a Black person from an African nation, or by a dark-skinned Latino, can also implicate race, color, and national origin. These examples show that the bases do not always line up with a single label, so the list has to be built from the facts of each complaint.
A claim that leaves out a basis raises a concern the guidance names. According to U.S. Equal Employment Opportunity Commission, failure to include all possible bases may result in a court dismissing a legitimate claim. A complete list helps the review.
A file note can list each basis a claim could raise, so the list is written down in one place. Update that list whenever a complaint is filed about a decision you made. Add each new basis as it appears, and record the date of the update so a reviewer can see when the list changed.
Lists differ by jurisdiction, and one state's list is not automatically another's. According to Minnesota Office of the Revisor of Statutes, one listed item covers discrimination in education because of one or more of the following: race, color, creed, religion, national origin, sex, gender identity, marital status, disability, status with regard to public assistance, sexual orientation, and age. The Colorado bill, according to Colorado General Assembly, concerns protections for Colorado workers against discriminatory employment practices.
Records to keep with the decision
Keep the stated reason with each decision, written before the decision is final. A reason written after the fact gives a reviewer less to test. Write the reasons in plain sentences rather than in shorthand that only the author can read. Date the note on the day it was written, and keep the first version even if the wording is later improved, because the first version shows what the decision-maker relied on at the time.
For each file, record your answers to the four checks: whether race was part of the motivation, whether stereotyped thinking could have shaped the call, whether vague wording was tested, and which bases a claim could raise. Writing the answers in the same order each time makes the files easier to compare. Use the same headings in every file so a reviewer can find each answer without searching.
For a format built around recorded decisions, see the Hiring Decision Debrief: Notes to a Recorded Decision page. The debrief format is one option for the same purpose. A short debrief written soon after each interview is easier to reconstruct than one written after a long delay, and the notes should answer the same questions for each applicant in the round.
These notes belong with the application and interview notes for the same applicant, so a later reader can follow the decision in one place. Notes scattered across separate email threads are harder to follow. If the decision-maker and the note-taker are different people, both sets of notes should be filed together so the reasoning can be compared.
Review your recent decisions on a regular basis, not only after a complaint arrives. A short review now is easier to finish than a long review under pressure. Pick a fixed time for the review so the habit does not depend on a complaint arriving first. The review does not need to reopen every file in full; it needs to confirm that each recent file has the four answers written down.
Illustrative example: Review a vague reason
A reviewer finds 5 notes that say only “soft skills.” For each, the reviewer looks for the interview question, recorded answer and score. Where the record supports a clearer explanation, the reviewer adds it while keeping the first note. Where it does not, the reviewer marks the reason for a second look rather than inventing an explanation.
Your next step: pick your last three hiring decisions, write down the stated reason for each, and check it against the four checks above.
Questions
Does Title VII cover unconscious bias?
Yes; the coverage described in check 2 extends beyond deliberate intent. This article does not give a claim outcome for any specific case, and a file that raises the question is best reviewed with counsel.
Can one complaint raise race, color and national origin?
Yes; a single complaint can raise all three together. A file should therefore keep a list of bases rather than only the one an applicant named first. That list gives a reviewer the full set of bases to test against the decision.
Why are soft-skills statements flagged?
They prompt closer examination because they could reflect racial stereotyping and bias. According to U.S. Equal Employment Opportunity Commission, the investigator evaluates the employer's decisionmaking very carefully when reviewing such statements.
What happens if a basis is left out of a claim?
A court may dismiss a legitimate claim, as explained in check 4. A review that checks the list against each complaint is a practical way to apply the point.