A criminal record can affect a hiring decision, but the review should distinguish arrests from convictions, consider the circumstances, and connect the record to the job.
Key takeaways
- Confirm the record type and final disposition before drawing conclusions.
- Review the offense, time elapsed, and essential job duties together.
- Give the applicant a chance to explain and correct errors.
- Document your reasoning and check the rules for your location.
A record is a piece of information, and what it means depends on what it says, how old it is, and what the job requires. This post covers three rules to check before you decide, along with the habits that make those checks reliable.
A federal source on this topic is the U.S. Equal Employment Opportunity Commission (EEOC). Its enforcement guidance on the consideration of arrest and conviction records explains how Title VII of the Civil Rights Act applies when employers use these records. The EEOC notes that the document "combined and replaced 3 guidance documents from the 1980's," so the guidance pulls together earlier positions into one place.
This post is general information for hiring teams, not legal advice. Employment rules differ by location and by role, so your employment lawyer or compliance team should review your process before you rely on it.
Rule one: Separate arrests from convictions
Start by checking the record type. An arrest is not a conviction. A person can be arrested, charged, and later cleared, or a charge can be dropped, or a case can end without a finding of guilt. A record that shows only an arrest tells you that a police contact happened. It does not tell you what happened next.
The gap between an arrest and its outcome can be large. The EEOC cites a 2006 study by the Department of Justice's Bureau of Justice Statistics (DOJ/BJS). According to the EEOC's guidance, that study found that only 50% of arrest records in the FBI's III database were associated with a final disposition.
What this means in practice is simple. If a background report lists an arrest with no outcome, you do not know the result, and you should not treat the arrest as if it were a conviction. Ask the applicant about it. Ask your screening provider whether the report includes a final disposition. If the outcome is missing, confirm it through the court record before you draw any conclusion. Use the background report checklist to organize the file review.
Keep the distinction visible in your notes. When you write up a decision, record whether the item was an arrest, a charge, or a conviction, and what the disposition was. Notes such as "criminal history, concerns" are not enough. They invite inconsistent decisions, and they make it hard to explain your reasoning later to the applicant, to a colleague, or to an investigator.
Pending cases need special care too. A charge that is still open has no outcome yet, so it cannot support a conclusion about what happened. Note that the case is pending, set a follow-up date, and revisit the file when the outcome is known. If the decision cannot wait, be clear with the applicant and with your team about what is still unknown and why the decision is being made without it.
Rule two: Look at the conviction and its circumstances
When a conviction is confirmed, look closely at what it involved. Labels such as "felony" or "misdemeanor" are a starting point, not the full picture. Two records with the same label can differ widely in what happened and when it happened.
The EEOC's guidance uses concrete examples to make this point. In one, an applicant named Tad discloses a guilty plea to a felony entered at age 16. The offense involved accessing a school computer system without authorization over several months and changing classmates' grades. The example shows why the nature of an offense can matter more than its label. Whether that record affects a particular role depends on the duties of that role and the facts of the case.
A second example in the same guidance involves an applicant named Nelson. In an interview, Nelson points to a successful work history and good references. Nelson also discloses a guilty plea to breaking and entering into a high school at age 16, which was part of a class prank that caused little damage to school property. The contrast is useful. The record exists in both examples, but work history, age at the time, the nature of the offense, and references all bear on how much weight it should carry.
Hiring teams can use three questions for each record:
- What exactly was the offense, in plain terms?
- How much time has passed since it happened?
- Does the offense relate to the core duties of the job?
Write the answers down. If you cannot connect the offense to the core duties of the job, the record probably should not decide the outcome on its own.
Time matters, but there is no single number that applies everywhere. Some hiring teams set their own windows for how far back to look, and those windows should match the role and the record. Write down the rule you use and apply it the same way to every applicant. If you cannot explain why a record from years ago matters for this job, say so in your notes.
Rule three: Tie every decision to the job
The third rule is that the decision should connect to the job. A record that relates to a role handling cash may matter little for a role with no financial duties. A record that relates to work with vulnerable people may call for a different response than one that relates to a warehouse floor. The point is not to memorize a list of banned offenses. It is to ask what risk the job actually creates and whether the record speaks to that risk.
Start by writing down the essential duties of the job. Then ask whether the record, as you have verified it, relates to any of those duties. If the answer is no, the record should not be the reason for a rejection. If the answer is yes, ask a second question: is the risk serious enough, and recent enough, that no other arrangement would manage it?
Some teams skip this step. They move straight from "there is a record" to "we cannot hire." That shortcut is where many avoidable mistakes happen. It also makes the process look arbitrary to an applicant who later asks why they were rejected, and to anyone who reviews the decision afterward.
Check the job description too. If a posting says the role handles sensitive data, but the person will never see that data, the record analysis rests on a false premise. Confirm the duties with the hiring manager before the review begins, and write down what you confirmed.
Be wary of blanket lists that label entire categories of offenses as automatic disqualifiers. A list like that is simple to apply, but it asks a single label to answer a question that needs the facts. If your policy includes a list, check it against the essential duties of each role and ask whether the list would still make sense if a reviewer had to explain each line to an applicant.
Match the check to the role
A background check should match the role, not the other way around. Running the same broad review on every position can add time and noise without adding insight. Decide in advance which roles need which kinds of checks, and document that choice. This protects both sides. Applicants know what to expect, and your team can show that the same standard applied to everyone in a similar role. If a role changes during the hiring process, revisit the check before you move forward.
Give the applicant a real chance to explain
Before any adverse decision, give the applicant an opportunity to respond. This is good practice regardless of the legal details, and it can change the picture. Records can be incomplete, and the context around them can be important.
When you contact an applicant, be specific. Name the item you are reviewing and what the report says about it. Ask for their account, any documents that show the outcome, and any relevant information about their work since then. Give them a reasonable amount of time to reply, and tell them who to contact with questions. Keep the conversation factual, and avoid judgments about character.
Record the response in the file. If the applicant says the report is wrong, such as an incorrect date or an offense that was dismissed, treat that as a reason to verify, not a reason to dismiss what they say. Then check it. Correct the file before you make a decision based on it.
Weigh what the applicant offers honestly. Court dispositions, training certificates, and references from past employers can all help you understand the record. Decide in advance what kind of evidence you will consider, and apply that standard to every applicant.
Watch for patterns that harm groups of people
Individual decisions can add up to patterns, and patterns can create legal exposure even when no one intended to discriminate. The EEOC's guidance cites the Supreme Court's decision in the Duke Power Company case, in which the Court first recognized that Title VII permits disparate impact claims. The guidance quotes the Court's explanation that Title VII "proscribes . . . practices that are fair in form, but discriminatory in operation."
A rule that screens out everyone with any record can affect some groups more heavily than others. Even if the policy is written neutrally, it can have a discriminatory effect in practice.
The EEOC also looks at the applicant pool. Citing Rawlinson, the guidance says an employer's "application process might itself not adequately reflect the actual potential applicant pool since otherwise qualified people might be discouraged from applying." For that reason, the Commission "will closely consider whether an employer has a reputation in the community for excluding individuals with criminal records."
The guidance also explains that evidence of this kind may come from ex-offender employment programs, individual testimony, employer statements, evidence of employer recruitment practices, or publicly posted notices, among other sources. The Commission will determine the persuasiveness of such evidence on a case-by-case basis.
Hiring teams can take a few practical steps to check for patterns:
- Track how often applicants are screened out at the record stage, by role and location.
- Compare outcomes across applicants with similar records and similar jobs.
- Ask whether job postings or public statements suggest that people with records are unwelcome.
If the numbers show a pattern, review the policy itself, not only individual decisions. A pattern is a signal that a rule may be doing more than the business needs it to do.
Consider reviewing your policy with a sample of past decisions. Look at applicants who were screened out, and check whether the reasons were tied to the job. Look at applicants who were hired, and check whether any had records that were handled differently. The review does not have to be large. A focused review of recent decisions can reveal whether the written process is being followed in practice.
Keep a written, consistent process
Consistency is what makes decisions defensible. A written process means that two applicants with similar records and similar jobs get similar treatment, and that you can explain the reasoning if someone asks later.
A workable written process usually covers:
- Which positions require a record check, and why.
- Which types of records are reviewed, and how arrests are handled compared with convictions.
- The questions asked in each individual review, such as the nature of the offense, the time elapsed, and the link to the job.
- How the applicant is notified and given a chance to respond.
- Who makes the final decision, and how it is documented.
Train the people who make these decisions. A recruiter who has never worked with disposition codes may misread a report. A hiring manager who has not seen the EEOC's examples may treat a single entry as disqualifying. Short training sessions that use anonymized examples can prevent many of these errors.
Review the process on a schedule. Roles change, screening vendors change their reports, and laws change too. Keep a record of each review, including what changed and why.
Store the background report and your notes in a secure place, limit who can see them, and follow your organization's retention rules. Only people with a need to know should see the details of a criminal record.
Know that local rules can differ
Federal guidance is a useful baseline, but it is not the whole picture. States and cities can set their own rules, and some of those rules add requirements beyond federal guidance. For example, the New York City Commission on Human Rights says on its guidance page that the guidance "has been updated to reflect amendments to the New York City Human Rights Law under Local Law 4 (2021), which took effect July 29, 2021." Read the local guidance that applies to your location, and do not assume the federal document answers every question.
Before you finalize a process, find out which laws apply to your location and to each role. Some industries have licensing or regulatory requirements that set their own standards for certain records. Those standards can differ from general guidance, so do not assume that one standard fits every position.
If you are unsure, ask your legal or compliance team before you reject an applicant.
Common mistakes to avoid
Several mistakes come up again and again. Treating an arrest as proof of conduct is the first. Relying on a single line in a report without checking the source is another. Applying a stricter standard to one applicant than to others with similar records is a third, and it makes the process hard to defend. Finally, a process can let a first reaction decide the outcome, with no written reasoning behind it.
A short checklist for each decision
Use this list when an applicant's record appears in a background report:
- Confirm the record type: arrest, charge, or conviction.
- Confirm the final disposition, using a court record if the report does not show it.
- Write down the offense in plain terms.
- Note the date and how much time has passed.
- Identify the essential duties of the job.
- Decide whether the record relates to those duties.
- Give the applicant a chance to explain and provide evidence.
- Weigh the evidence case by case, and write down your reasoning.
- Check whether your decisions, across applicants, could fall more heavily on any group.
- Have the final decision reviewed by someone who did not do the first review, when possible.
None of these steps requires a complicated system. They require attention, consistency, and a habit of asking what the record actually tells you. A record can be a reason to look more closely. It should not be a shortcut that ends the review before it starts.
Illustrative example: An arrest without an outcome
A hiring team reviews an illustrative file containing 1 arrest entry and no final disposition. Rather than counting it as a conviction, the reviewer asks the applicant for documents and asks the screening provider about the missing outcome. The reviewer then checks the court record and updates the file before drawing a conclusion. The exercise ends with a documented review, rather than an automatic rejection.
Start with one role today. Apply the three rules, write down what you decided and why, and look at the result. Use a hiring decision debrief to organize your reasoning before expanding the process to the rest of your hiring.
Related guides: Age discrimination: 8 hiring and benefits rules · California fair chance hiring: 3 rules to check · Criminal record requests: 5 steps to choose a source.
Common questions
Does an arrest establish guilt?
Check the final disposition before drawing a conclusion about the outcome.
Does federal guidance cover every local requirement?
Check the rules for the location and role with your legal or compliance team.