Skip forward into hiring notes
RosterAcorn

Criminal record data: 4 sources for hiring files

Criminal record data in hiring files can include police contact, court outcomes, and status notes; these four official sources explain definitions and access limits.

Key takeaways

  • Sort each entry using the applicable state's definitions.
  • Check the legal basis before requesting state data.
  • Read the detailed report before relying on its summary.
  • Document the reasoning and arrange another review before deciding.

Four official sources show how different states and agencies handle that data. This post reads each one for what it says, what it leaves open, and what a small team should do about it. None of these sources tells a hiring team what to decide. They set limits, and the judgment that follows is yours to document.

What does Wisconsin count as an arrest record?

Wisconsin defines an arrest record more widely than many readers expect. Under section 111.32 of the Wisconsin statutes, the term "includes, but is not limited to, information indicating that an individual has been questioned, apprehended, taken into custody or detention, held for investigation, arrested, charged with, indicted or tried for any felony, misdemeanor or other offense pursuant to any law enforcement or military authority."

Look at how much that list covers. Being questioned, held for investigation, or charged all count, and none of those words requires a conviction to follow. A screener who reads "arrest" as meaning "arrested and convicted" will misfile entries, and the error tends to hide itself. The file looks tidy, the entry sits under the wrong heading, and nobody notices until a decision is challenged. The practical step is to label entries that match Wisconsin's arrest-record definition in your notes, using the statute's own words, so nobody later confuses them with convictions.

The list is open-ended. The definition says "includes, but is not limited to," which means the named items are examples rather than a closed set. Do not assume a type of police contact falls outside the definition just because the list does not name it. When an entry is unfamiliar, ask a second reviewer to check it against the full text before you file it under anything else.

What does Wisconsin count as a conviction record?

The same section gives a separate definition for conviction records, and it reaches well past the plain word "convicted." The statute says the term includes information that someone "has been convicted of any felony, misdemeanor or other offense, has been adjudicated delinquent, has been less than honorably discharged, or has been placed on probation, fined, imprisoned, placed on extended supervision or paroled pursuant to any law enforcement or military authority."

Look at the items that go beyond a guilty finding. A screen that searches only for a conviction entry may skip these, because a status word like "probation" can appear without the word "convicted" anywhere near it. Read every file for status words of this kind, and record which definition each line matches.

The two definitions overlap in practice. One entry that says someone was charged, convicted, and placed on probation can match both categories, because the text of each definition reaches the same events. Record the category for each line, not only for the file as a whole. That way a reviewer can see which facts support which conclusion, and a file-level label does not hide the difference.

Does Massachusetts let a private employer get criminal data from the state?

A private employer should establish its legal basis before requesting state criminal data. General Laws chapter 6, section 172 lists several parties in separate subsections. The quoted ones cover a victim of a crime, a witness, or a family member of a homicide victim; the district attorney; the department of children and families; and a court, the office of jury commissioner, and the clerk of court or assistant clerk.

Each quoted subsection says the named group may obtain data from the department, limited to data permitted under another section of the law. So the list works as a pointer rather than a grant. The answer for any particular request sits in the section each subsection cites, not in this one. A reader who stops at the list will miss the limiting language that matters most.

For a screening team, the lesson is simple. Do not read this list as permission to request state data for a hiring decision. The quoted subsections do not name a private firm. A firm that wants a particular record should first ask what legal basis exists for it, rather than infer access from provisions about other parties. If the basis is unclear, leave the request unmade and ask counsel. Use the related guide to choosing a criminal record source when organizing that review.

Can a Virginia employer confirm that a criminal record exists?

Virginia's section 19.2-389 restricts confirmation for employment or licensing inquiries. The statute puts it this way: "No criminal justice agency or person shall confirm the existence or nonexistence of criminal history record information for employment or licensing inquiries except as provided by law."

The phrase "except as provided by law" means the answer turns on which other law applies. Before making that call, a screener should find the specific legal basis, if any, that allows the agency to answer. If there is none, do not make the call. A quick phone check can feel harmless, but it is exactly the disclosure the text restricts.

The same section also addresses a case where no conviction data is maintained on the data subject. It says: "In the event no conviction data is maintained on the data subject, the person making the request shall be furnished at his cost a certification to that effect." That is a different route from an informal answer, and a team should know the difference before it asks.

If no agency confirms either way, the team has to decide without that answer. Ask the applicant for their own account and any documents they can provide, and note in the file which facts came from the applicant and which came from a source the team can verify. Mixing those two categories is one of the quickest ways to lose track of what the file actually proves.

Note the effective date. The heading marks this version as effective January 1, 2027, which is still in the future as this post is written. Confirm which text governs any request made before then, because a request sent now may fall under the current version rather than the one printed here.

Can a criminal record alone rule out an applicant in Texas?

Prior justice-system involvement should not automatically disqualify an applicant unless a statute or relevant agency regulation requires it. The guidance on efte.twc.texas.gov says: "Prior involvement with the criminal justice system should never be used as a blanket disqualifier unless a statute or relevant agency regulation requires such a result."

The word "blanket" carries the point. A record can be one factor in a decision, but a rule that removes every applicant with prior justice-system contact, whatever the facts, is what the guidance warns against. So the first question for any exclusion is whether such a requirement applies to the job. If none does, the record has to be weighed against the facts of the case rather than applied automatically.

What does Texas expect when an exclusion has a disparate impact on minorities?

The guidance describes a targeted screen when an exclusion based on criminal conduct would have a disparate impact on minorities. Its wording is: "If an exclusion based on criminal conduct would have a disparate impact on minorities, EEOC expects the employer to develop a "targeted screen" that takes into account the nature and gravity of the crime, how much time has passed since the crime occurred, and the specific functions of the job in question."

Those three questions give a reviewer something to write down, which a gut reaction does not.

The guidance then adds a second step. Anyone excluded under those criteria "would then have an opportunity for an individualized assessment to determine whether the criteria as applied are job-related and consistent with business necessity." That wording means an exclusion is not the end of the review. The person gets a chance to show why it should not apply to them, and the team checks whether its criteria fit the job.

The text presents these as what the EEOC expects, so check the federal source before you copy its wording into a written policy. For a small team, the practical step is a dated note for each applicant that answers the three questions above in one or two sentences.

Illustrative example: review an entry before deciding

An illustrative file contains a charge followed by probation. A reviewer checks the applicable definitions, labels the entries separately, and records the job duty under review. Another reviewer checks those reasons. The team keeps the applicant's explanation separate from information it can verify. The result is a record of the review, rather than an automatic rejection based on a summary line.

What can a small team do today?

Choose one existing hiring file today and compare its summary with the detailed entries. Mark any entry whose category or source needs another review, and keep the review note with the file. The guide to recording a hiring decision can help organize the reasons.

Who should decide a borderline record?

A second reviewer should check any decision that might rest on a record. A small team may not have a spare person, but the habit still works: the first reviewer writes down reasons, and someone else reads them before a final decision. The point is consistency. If one person decides every case alone, nobody can tell whether two similar records were treated alike, and the team cannot correct a pattern it cannot see.

Write the reasons in plain sentences: the entry, the category it falls under, the job duty it touches, and why the decision follows. A reason like "not a good fit" tells the next reader nothing. Record how an entry relates to a duty, without treating that connection alone as a reason to exclude someone. Keep these notes with the file, not in a personal inbox, so the next reviewer sees the same facts you saw. If a reviewer cannot tie a reason to a duty the job actually requires, treat that as a signal to look again.

What should an applicant hear before a decision is final?

The applicant should learn that a record is under review and have a real chance to respond before anyone decides. The Texas guidance describes this assessment for people excluded under targeted criteria, and it is a useful model for any borderline case.

Tell the applicant what the record says, using the wording in the file. Let them explain the circumstances, provide documents, and describe what has changed since. Give a reasonable window to reply, and note the reply in the file before you decide. Do not ask for details that the category does not need. A screen that collects more personal history than the job requires creates risk without improving the decision, and it is harder to defend later.

How does the time since an event fit into the decision?

Time since the crime is one factor a targeted screen should weigh. A record from many years ago and one from last year should not carry equal weight by default. Treat elapsed time as a factor rather than inventing a cutoff and presenting it as a legal rule. A cutoff that sounds official but has no source behind it is easy to challenge and hard to explain.

Instead, record the date of each event beside the job duty it touches, and write one sentence on why the gap in time does or does not change the decision. That sentence matters more than a fixed number would, because it shows the reasoning a later reviewer can check. It also forces the team to say what changed in the applicant's life or in the job's demands, rather than relying on the calendar alone.

Why does a report's summary line matter?

A summary line can hide the distinction between arrest entries, convictions, and other status entries. A line that reads "no convictions found" does not show whether the file holds arrest-type entries, or probation and other status entries that the definitions above name. Those entries can still matter to a decision, even when the summary looks clean.

Ask your vendor or reviewer to list each entry with its date, status, and source. A one-word summary cannot do that sorting, and a team that relies on summaries alone cannot show later how it reached a decision. Treat the detailed list as the working record and the summary as a convenience only. Use the background report checklist to organize that review.

How should a small team use these four sources together?

Start by sorting each entry under the definition it matches, then check the law of the state that governs the request. These four sources are examples, not a full map. Each answers a different question: what counts as an arrest or a conviction, who may obtain state data, whether an agency may confirm a record, and when an exclusion is allowed. A rule from one state does not tell you what another state requires, so pull the current statute for every state where you run screens.

QuestionWhat to checkLimit for your team
What counts as an arrest or conviction entryThe definition's own wordsLabel each entry by its own category
Who may obtain data from the stateThe list of parties and the section each one citesA private firm needs a legal basis before it asks
Whether an agency may confirm a recordThe "except as provided by law" wordingDo not phone an agency without a legal basis
When a record may justify exclusionWhether a statute or regulation requires the result Where an exclusion would have a disparate impact on minorities, use a targeted screen and an individualized assessment

A workable order is this. First, label each entry as arrest, conviction, or neither, using the definition's own words. Second, confirm which state's law governs any request for data and whether it lets your firm ask at all. Third, if a record might justify exclusion, check whether a statute or agency regulation requires that result. If no requirement applies and the exclusion would have a disparate impact on minorities, use the targeted-screen and individualized-assessment steps described above, and check the federal source for their exact terms.

Fourth, keep a dated note of each decision and of the law that supported it. Revisit this sequence whenever a source you rely on is updated, and treat any file that cannot be sorted into these categories as one that needs another review before it goes further.

Sources