Skip forward into hiring notes
RosterAcorn

Race bias complaints: 4 evidence sources to gather first

For a race bias complaint about hiring, gather documents, witness statements, direct observations, and statistical evidence before drawing a conclusion.

Key takeaways

  • Preserve documents and sort them by creation and edit dates.
  • Separate firsthand witness accounts from assumptions and secondhand reports.
  • Record raw counts before calculating percentages.
  • Compare the employer's explanation with the timeline and written criteria.

This post walks through four kinds of evidence to collect before you draw any conclusion. The U.S. Equal Employment Opportunity Commission (EEOC) lists these as sources of information in its guidance on race and color discrimination: witness statements, documents, direct observation, and statistical evidence. The post then covers two checks that sit on top of those sources: whether the decision-maker's race settles anything, and whether the employer's explanation holds up.

This post is written for hiring managers and small staffing teams who need general reading on the subject. It does not replace legal advice. Your state may add its own rules, and an employment lawyer should review your steps before you act on them.

Federal law prohibits employers from depriving employees of employment opportunities by limiting, segregating, or classifying them on the basis of race. The EEOC describes this prohibition under Title VII in its race and color guidance, and that is the standard your review should test against.

Your job at this stage is narrower than deciding whether the complaint is right. You are deciding whether the evidence shows that race played a role in this particular decision. The EEOC guidance says that answering this question "requires examination of all of the surrounding facts and circumstances," so your review should look at the whole picture rather than one moment.

Keep the scope tight: one role, one hiring process, one set of dates. A review that drifts into the company's whole history becomes hard to finish and easy to attack. If the complaint names other roles or other decisions, note them, then decide with counsel whether they belong in a separate review.

What documents should you pull first?

Start with documents, because they show what the employer said it wanted before anyone saw the applicants. Documents are one of the four sources the EEOC lists, and they are usually the easiest to verify because they carry dates.

Collect at least the following, where they exist:

  • The job posting and any written criteria or scoring rubric
  • The applications and resumes for every applicant who reached a stage in the process
  • Screening notes, interview notes, and scorecards, with the author and date on each
  • Offer, rejection, and follow-up emails
  • Messages in chat tools or text threads about the applicants or the role
  • Calendar entries showing when interviews happened and who attended
  • Applicant tracking system logs showing when records were created or changed

Then build a timeline. Sort every document by the date it was created and the date it was last edited. If two versions of a document exist, keep both and note which one came first.

Pull the criteria as they were written at the time, not as they appear in a later version. If the posting was edited after applications arrived, keep the version applicants actually saw, and record the date of each edit. For help organizing the scoring record, see the interview scorecard guide.

Work from copies, not originals. Do not annotate, reorganize, or clean up the source files. If something seems to be missing, write that down rather than trying to recreate it from memory. Ask counsel how long these records must be kept before any routine deletion runs, and suspend that deletion if counsel gives that instruction.

What do witness statements add, and how do you weigh them?

Witness statements add firsthand accounts that documents cannot give you, but you weigh each statement by how credible the witness is. The EEOC lists witness statements as a source of information, "including consideration of their credibility."

Interview each witness on their own, not in a group, and ask the same questions of people on both sides of the complaint. Write down the words used as close to verbatim as you can, not your summary of them. Ask what the witness saw or heard directly, and separate that from what they assumed or heard secondhand.

Record each witness's relationship to the applicant and to the decision-maker, since those relationships affect how much weight a statement can bear. Ask for dates and places. A statement that cannot be placed in time is hard to test, and you should say so in your notes rather than filling the gap yourself.

Watch for pressure. A witness who is friendly with the decision-maker, or who fears for their own job, may tell you what seems safe rather than what they saw. Note that possibility in the file without assuming the worst about the witness.

What counts as direct observation?

Direct observation means evidence from someone who saw or heard the conduct firsthand, or from a recording or record that captured it. The EEOC names direct observation as its own source of information, so treat it as a separate category rather than folding it into witness statements.

For a hiring decision, direct observation might be a panel member who sat in on every interview, a scoring session someone attended, or a recorded interview where recording was lawful and the process allowed it. Ask who was in the room at each stage, and what each person noticed at the time.

Observations outside the formal process matter too, such as a pre-interview introduction or a comment made at a team meeting. Record them only where a witness or a document captures them. Label whether the account comes from memory or a record made at the time.

If a reviewer has never seen the process, they cannot observe it now. Your task is to find out who did observe it, and what those people wrote down or said afterward. Distinguish between someone who watched a moment and someone who heard about it later. That distinction usually matters more than who spoke loudest in the complaint.

Are statistics useful for a small team?

Statistics can show a pattern, but a small team may have too few decisions for a pattern to carry much weight on its own. The EEOC guidance lists "statistical evidence such as EEO-1 data, among others" as a source of information. The same guidance says that the presence or absence of any one piece of evidence often will not be determinative, so treat numbers as one input among several.

Start by comparing the applicant pool for the role with who reached each stage and who was hired, over a defined period. Decide before you count who counts as an applicant. Some applicants apply through a referral, some withdraw early, and some never finish a form. Write down the rule you used and apply it the same way at every stage, so the numbers can be checked later. Write down the raw counts before you calculate any percentages. Small counts can make a rate look precise when it is not, so say the numbers are small in your review rather than presenting a figure that suggests more certainty than the data supports.

Where you have EEO-1 data, check what it shows for the relevant job category, and note the limits of comparing that category to one hiring round. Ask someone who can read data carefully to check your arithmetic and your assumptions before anyone relies on the result. Keep the calculations in a separate file so a reviewer can follow each step back to the source counts.

Illustrative example: connect counts to records

Record those raw counts, then check which applications met the written criteria and whether withdrawals were counted consistently. If the explanation for an interview decision first appears after the complaint, mark that timing and compare it with the original notes. The counts organize the review; the documents help test the explanation.

Does one stray remark prove race played a role?

A race-related remark needs to be weighed in context; no single piece of evidence automatically settles the question. The EEOC guidance notes that discrimination is often subtle and that there is rarely a "smoking gun."

The guidance also reminds reviewers that race-related statements include more than slurs. It describes "code words" that are "purportedly neutral on their face but which, in context, convey a racial meaning." A word that sounds neutral in one setting can carry racial meaning in another, so record the exact wording, who said it, to whom, when, and what was being discussed at the time.

Then ask what the remark meant in that room. Check whether the same person used similar language about other applicants, and whether the remark connects to a decision in the file. If your organization has a written policy on workplace conduct or complaints, check whether the remark falls under it and whether that policy calls for steps beyond this review. Those questions belong with counsel or your HR lead, and the answers should be in writing.

Do not decide what a phrase means from your own impression alone. Your notes should show the evidence you relied on, so that another reviewer could reach the same reading or explain why they disagree.

How do you test the employer's explanation?

Test the explanation by checking whether it is specific, supported by the record, and the same each time it has been given. The EEOC guidance states that "an employer's credibility will be undermined if its explanation is unsupported by or contrary to the balance of the facts." That is the first test to run, and it is often the most revealing one.

Next, check the explanation against the timeline. The guidance says vague explanations, reasons developed after the event, shifting explanations, and inconsistent reasons can call credibility into question. Write the reason down as it was given at each point, from the first interview note to the most recent statement, and compare them side by side. If a reason first appears after the complaint, say so plainly in your review.

Then compare the explanation with the written criteria from the posting and the scorecards. If the stated reason relies on a qualification the posting never mentioned, or one that was never scored, record the gap. Do not treat every gap as proof of bias, but do not overlook it either.

The stakes of this check are high. The guidance also states that if an explanation for an employee's treatment "ultimately is not credible, that is powerful evidence that discrimination is the most likely explanation." A reviewer who skips this step can miss the most useful evidence in the file.

A shifting reason is not automatically proof of bias. Someone may have remembered the decision poorly or described the same reasons in different words. Ask the decision-maker about the change directly, record the answer, and then compare it with the documents before you draw a conclusion.

How should you handle contact with the complainant and the decision-maker?

Keep communication about the complaint in writing where you can, and keep it short. Tell each person what the review involves and who will contact them, and avoid discussing the complaint with peers who have no role in the process. Gossip spreads fast in small teams, and it can shape witness memories before you have taken their statements.

Avoid any step that could look like punishment for raising the complaint, including changes to the complainant's duties, schedule, or evaluations during the review. If you think a change is needed, ask counsel first. Counsel can tell you which steps create risk and which can wait until the review is finished.

Give the decision-maker a chance to answer the evidence in writing, and give the complainant a chance to add anything they think the review missed. Both responses go into the file. An answer that never gets recorded cannot help you later.

Who should gather this evidence?

Ideally, someone who was not part of the original decision should gather it, and the decision-maker should not collect their own file. This keeps the collection from looking like a defense of the decision before the review has started. If your team is too small to separate those roles, bring in an outside person, such as an HR consultant or counsel, for the collection step.

Keep a log of every step: what was collected, from whom, when, and by whom. Store copies in one place with restricted access, and do not let copies spread through email threads. A log helps you later, and it shows that the material was gathered in order rather than selected to suit a conclusion.

Note any gaps in the log as well. If a witness was unavailable, or a message thread could not be exported, the gap belongs in the record with a date and a reason. A visible gap is easier to explain than one that a reviewer discovers on their own.

What should you do when the evidence points both ways?

When the evidence points both ways, write down what each source shows, where the sources conflict, and what you could not confirm, then take that record to counsel before you decide.

Write the reasons for your decision in plain words, tied to specific documents and statements. Avoid conclusions you cannot point to. If you change the hiring decision, record why. If you decide not to change it, record that reason too. Whatever you decide, the file should show how you reached the result, so that someone reading it later can follow your reasoning without asking you. The hiring decision debrief guide can help organize that written explanation.

Keep the review proportionate to the complaint. A narrow complaint about one interview does not need an audit of every hire the company has made. A broad complaint about a pattern may need more statistics and more witnesses than a small team can comfortably gather alone, and that is a reason to bring in outside help early.

If you share draft findings, do it only through the channel counsel approves, and expect questions in return. A draft that gives each side a chance to correct the facts is more reliable than one that surprises them when it is final.

What can you do today?

Today, copy the original job posting and interview notes into a restricted review folder. Record their creation and edit dates, and note anything missing before arranging witness interviews.

Does the decision-maker's race settle the question?

No. A shared race between the decision-maker and the applicant does not rule out bias, and a complaint should not be dismissed because the hiring manager looks like the applicant. The EEOC guidance quotes the Supreme Court on this point: "[b]ecause of the many facets of human motivation, it would be unwise to presume as a matter of law that human beings of one definable group will not discriminate against other members of their group."

Practically, this means you should treat the decision-maker's race as neither an alibi nor an accusation. Write it down as one fact among many, then move on to the evidence. Any reviewer on your team should be able to say the same thing if asked, and should be able to explain why it does not change the analysis.

Sources