Criminal Records

The FCRA Big Three Lawsuit Triggers

Hiring the right talent is critical but one overlooked detail in your background screening process can cost your company millions. Employers often assume background checks are routine, yet the legal landscape tells a different story. The majority of lawsuits tied to employment screening aren’t about discrimination or bad hires—they’re about technical compliance mistakes under the Fair Credit Reporting Act (FCRA). These errors are easy to make and expensive to fix.

Research shows that approximately 73% of FCRA-related lawsuits against employers stem from these three common mistakes:

  • Non-compliant disclosure forms
  • Missing or delayed pre-adverse action notices
  • Inadequate authorization forms

The consequences can be significant: statutory damages of $100–$1,000 per violation, plus attorney fees, with settlements often reaching mid-six to seven figures.

Emerging Risk: Disparate Impact Discrimination

Background check policies and particularly those applying strict pass/fail criteria based on criminal history can unintentionally violate Title VII if they disproportionately impact protected groups. The EEOC has successfully challenged such blanket policies in litigation.

EEOC guidance emphasizes individualized assessments, considering:

  • The nature of the offense
  • Time elapsed since the offense
  • Relevance to the job

Relying on generalized exclusions without job-specific review creates legal risk. Additionally, many state and local laws impose specific requirements for individualized assessments.

Best Practices to Reduce Lawsuit Risk

To minimize exposure from background screening:

  • Use standalone, plain-language disclosure forms before any check.
  • Obtain written authorization in a separate form, not embedded in applications.
  • Follow the adverse action protocol: provide a pre-adverse notice with a copy of the report and summary of rights, and wait at least five business days before issuing the final notice.
  • Allow candidates to dispute findings.
  • Implement individualized assessments, especially for criminal record policies.
  • Regularly audit processes and train HR staff on evolving regulations.

 

Disclaimer: This communication is for general informational purposes only and does not constitute legal advice. The summary provided in this alert does not, and cannot, cover in detail what employers need to know about the amendments to the Philadelphia Fair Chance Law or how to incorporate its requirements into their hiring process. No recipient should act or refrain from acting based on any information provided here without advice from a qualified attorney licensed in the applicable jurisdiction.

The Illusion of Instant Criminal Checks: Why a True National Criminal Database Still Doesn’t Exist

If you’ve ever been pitched a “national criminal database,” you’ve probably imagined a single, authoritative system that instantly returns every criminal record across the United States. That database doesn’t exist for non‑law‑enforcement users and relying on anything marketed that way can lead to missed records, inaccurate matches, and regulatory headaches.

What actually exists at the national level?

The FBI operates several national systems—NCIC, III, NGI, N‑DEx, and NICS—to support criminal justice operations. These are law‑enforcement systems, with access tightly constrained by federal law and regulation (including 28 C.F.R. § 20.33). Employers generally cannot query NCIC/III directly unless a statute authorizes fingerprint‑based checks for specific roles (e.g., child care, elder care, or other regulated positions) and the check is routed through the state repository per the Compact Council rules.

Even within law enforcement, these systems are indexes and exchanges that depend on state and local repositories to submit arrests and dispositions; coverage and timeliness vary. The DOJ/BJS surveys and FBI guidance repeatedly emphasize gaps and the critical need to report final court dispositions to keep records accurate.

So what are “national criminal databases” sold by private vendors?

Commercial “national” or multi‑jurisdictional files aggregate data from many sources (state repositories where available, departments of corrections, sex offender registries, selected county uploads, watchlists, etc.). They can be useful as a pointer or discovery tool, but they are not comprehensive and often not current enough to stand alone. Coverage varies by jurisdiction and update cadence; name‑match noise creates false positives/negatives, especially with common names.

Industry resources and compliance guidance are consistent on this point: use multi‑jurisdictional databases to broaden the net, then verify at the originating court or repository before reporting or taking action.

Why “database‑only” screening creates risk

  1. Incomplete coverage: Not all courts or states report; updates lag. Recent charges or local misdemeanors may be absent.
  2. Identity ambiguity: Limited identifiers can mis‑match results; aliases and data entry errors compound the problem.
  3. Stale or missing dispositions: Arrests without case outcomes mislead; expungements or dismissals may remain in bulk feeds.
  4. Fair Credit Reporting Act (FCRA) compliance exposure: The FCRA requires “reasonable procedures to assure maximum possible accuracy” and complete, up‑to‑date public record reporting. Database “hits” must be confirmed at the source, and consumers must be notified appropriately when adverse public records are reported for employment decisions.

Regulators have sharpened expectations. In 2024, the Consumer Financial Protection Bureau (CFPB) reiterated that consumer reporting agencies (CRAs) must prevent reporting of duplicate or expunged/sealed items and include disposition information where available. CRAs also must disclose the source(s), both original and any intermediaries, when consumers request their files.

Why this still matters

Despite modernization, data gaps persist—especially in disposition reporting and identity matching. The newest BJS/SEARCH survey shows continued dependence on state repositories and varying automation/completeness across states, reinforcing why source verification and robust procedures remain critical.

Meanwhile, regulators (CFPB/FTC) are raising the bar on “maximum possible accuracy.” Organizations that rely on “instant database” products without verification risk adverse action mistakes, consumer disputes, and enforcement exposure.

 

Disclaimer: This communication is for general informational purposes only and does not constitute legal advice. The summary provided in this alert does not, and cannot, cover in detail what employers need to know about the amendments to the Philadelphia Fair Chance Law or how to incorporate its requirements into their hiring process. No recipient should act or refrain from acting based on any information provided here without advice from a qualified attorney licensed in the applicable jurisdiction.

December 12th, 2025|Categories: Compliance Corner, Employment Decisions|Tags: , , |

Minnesota Petty Misdemeanors and How to Report Them

Although nearly all state laws include criminal offense levels divided into two types – felonies and misdemeanors – there are many states with offense levels peculiar to their state law. One such peculiarity is Minnesota’s petty misdemeanor offense level.

In Minnesota, a petty misdemeanor is the lowest level of offense. Many but not all Minnesota traffic violations are petty misdemeanors. The unique aspect of a petty misdemeanor is that it is not considered a crime. (See for yourself here: Minn. Stat. § 609.02, subd. 4a or the accompanying attachment.) A petty misdemeanor does not carry a jail sentence but can result in a fine of up to $300.

August 19th, 2022|Categories: Compliance Corner|Tags: , , |

Arrest record but no charges

Typically, an arrest record will show the date, arresting agency, and the subject’s name (and other identifiers such as DOB and address), without specifying the charge or charges. The reason for this is twofold: (1) until the district attorney (“DA”) files a criminal case, there are no charges; and (2) the charges filed by the DA may be different than the charges on which the arresting officer based the arrest. An “arrest” and “being charged with a crime” are different things (although obviously related).  An “arrest” means that a person is taken into custody because they have been accused either by a warrant or by probable cause of committing a crime. Once in custody, the prosecutor’s office will decide whether the person will be charged with a crime. The person will then be given a charging document (complaint or information) that will state what charges they are facing.

A record will never show that an arrest was “dropped.” At best, you can infer that no charges were filed after an arrest if there is no corresponding court case.

December 15th, 2021|Categories: Compliance Corner|Tags: |

San Francisco enacts ordinance for using criminal records in employment decisions

Effective August 13, 2014, under San Francisco’s Fair Chance Ordinance, companies with 20 or more employees are prohibited from inquiring about an applicant’s criminal history on the employment application or during the first live interview. Along with banning the box, the ordinance imposes several additional restrictions and mandates certain considerations for individualized assessment. San Francisco employers must also ensure that their notice and consent forms for criminal background inquiries later in the process comply with the guidelines that will be published by San Francisco’s Office of Labor Standards Enforcement (OLSE) as well as with the already existing background check disclosure/authorization requirements under California’s ICRAA and the FCRA.

San Francisco is the ninth jurisdiction with legislation that affects private employers. The remaining eight are the states of Hawaii, Massachusetts, Minnesota, Rhode Island, and the cities of Buffalo, NY, Newark, NJ, Philadelphia, PA, and Seattle, WA. Multi-state employers should consider whether their particular circumstances warrant adopting individualized employment applications for jurisdictions with ban-the-box laws, or whether to use a nationwide standard form. Employers who opt for a standard electronic application for all locations need to include a clear and unambiguous disclaimer for applicants in each applicable ban-the-box jurisdiction. It is uncertain whether such disclaimers are sufficient for paper applications of multi-state employers in at least one ban-the-box jurisdiction (Minnesota) or if the box must be removed altogether.

For more information on ban-the-box legislation, see the recently published briefing paper by the National Employment Law Project titled Statewide Ban the Box – Reducing Unfair Barriers to Employment of People with Criminal Records.

Note: Effective August 13, 2014, with our California employment-purpose disclosure/ authorization form, we will be including a supplemental disclosure/authorization notice as prescribed by the OLSE, to use by San Francisco employers. 

New law prohibits North Carolina employers from asking about expunged records

Effective December 1, 2013, employers in North Carolina will not be able to ask job applicants about arrests, criminal charges, or convictions that have been expunge SB 91 prohibits inquiries into expunged matters both on applications and during interviews, and was enacted to clear the public record of any arrest, criminal charge, or conviction that was expunged so that the subject is legally entitled to withhold all information about it from potential employers and others. Notably, employers will still be allowed to ask about arrests, criminal charges, or convictions that have not been expunged and can be found in public records.

Minnesota becomes the latest state to restrict employment criminal checks

On May 13, 2012, Minnesota became the latest state to restrict criminal background checks for employment purposes with its Criminal Background Check Act  (S.F. No. 523). Under the new law, which will go into effect on January 1, 2014, public and private employers may not inquire about, consider or require disclosure of an applicant’s criminal history until after the applicant has been granted an interview or before a conditional offer of employment is made. Since 2009, Minnesota law prohibited only public employers from asking about criminal records on job applications.

According to a report from the National Employment Law Project (the “NELP”) dated in April 2013, six states and 50 localities have adopted “Ban the Box” legislation.  And pending before Congress is the federal HR 6220 or “Ban the Box Act” introduced last July by Representative Hansen Clarke (D-MI-13) which similar to these state and local laws, would make it illegal for an employer to ask about criminal history in an interview or on an employment application.

State laws restricting the use of criminal records gain momentum

By now, most employers are familiar with the EEOC’s April 2012 updated enforcement guidance on the use of arrest and conviction records for employment decisions under Title VII of the Civil Rights Act of 1964. And related state and local laws are quickly gaining momentum. More than 30 cities and at least 26 states now limit the type of criminal background information that employers can obtain or when they can request it.

Effective July 1, 2012, Indiana will join the roster of the restricting states. Its  SB 1033 will, in part, ban certain pre-employment inquiries, limit the types of criminal record information that employers and consumer reporting agencies (CRAs) can obtain from Indiana courts, and restrict criminal history information that CRAs can provide in background reports.

This law also provides that Indiana residents with restricted or sealed criminal records may legally state on an “application for employment or any other document” that they have not been adjudicated, arrested or convicted of the offense specified in these records. Covered employers (the term “employer” is not defined) will be prohibited from asking an “employee, contract employee, or applicant” about such records.

Limiting the scope that can be included in a background report, the law further prohibits courts from disclosing information pertaining to alleged infractions where the individual:

  • is not prosecuted or if the action is dismissed;
  • is adjudged not to have committed the infraction;
  • is adjudged to have committed the infraction and the adjudication is vacated; or
  • was convicted of the infraction and satisfied any judgment attendant to the infraction conviction more than five years ago.

Criminal history providers, such as CRAs, that obtain criminal history information from the state may only furnish information pertaining to criminal convictions, and are prohibited from including the following in background reports:

  • an infraction, an arrest or a charge that did not result in a conviction;
  • a record that has been expunged;
  • a record indicating a conviction of a Class D felony if the Class D felony conviction has been entered as or converted to a Class A misdemeanor conviction; and
  • a record that the criminal history provider knows is inaccurate.

Among other significant mandates, criminal history information obtained from the state by CRAs may not include any Indiana criminal record information in an assembled report unless the CRA updates the information to reflect changes to the official record occurring 60 days or more before the date the criminal history report is delivered.

January 7th, 2013|Categories: Employment Decisions|Tags: , |

Diploma mill ordered to pay $22.7 million to 30,000 scam victims

On August 31, 2012, Belford High School, Belford University and several of their co-conspirators were ordered to pay $22.7 million to a class of more than 30,000 U.S. residents who were duped into purchasing fake high school diplomas from Belford. The defendants were also ordered to forfeit the websites used to perpetrate the scam, including www.belfordhighscool.com, www.belfordhighschool.org, www.belforduniversity.org, and www.belforduniversity.com.

The lawsuit, filed on November 5, 2009, charged that Belford High School is an Internet scam that defrauded students of their money by offering them a supposedly “valid” and “accredited” high school diploma. As affirmed by the judgment, the school is a fake and the diplomas are not valid. The lawsuit also alleged that the two accrediting agencies by which Belford claimed to be accredited – International Accreditation Agency for Online Universities and the Universal Council for Online Education Accreditation – are not legitimate accrediting agencies.

Notably, we came across Belford University in 2010 when a bachelor’s degree from the “school” was listed on an employment application by a candidate for a professional level position with one of our clients. Click here to read the 2010 blog.

 

December 18th, 2012|Categories: Employment Decisions|Tags: , , , |

What’s the practical meaning of EEOC’s new criminal records guidance?

On April 25, 2012, the U.S. Equal Employment Opportunity Commission (“EEOC”) approved new enforcement guidance regarding the use of arrest and conviction records in employment decisions. The guidance builds on longstanding court decisions and requirements that the EEOC issued over twenty years ago, focusing on employment discrimination based on race and national origin.

In brief, the new guidance’s position is more aggressive, affirming that employers cannot automatically disqualify applicants with criminal records, and that their screening policies need to be consistent and structured for “individual assessment.” The guidance’s main points state that:

  • An arrest record does not establish that criminal conduct has occurred, and an exclusion based on an arrest, in itself, is not job related and consistent with a business necessity. However, an employer may make an employment decision based on the conduct underlying an arrest if such conduct makes the individual unfit for the particular position.
  • A conviction record will usually serve as sufficient evidence that a person engaged in a particular conduct. In certain circumstances, however, there may be reasons not to rely on the conviction record alone when making an employment decision.
  • A violation may occur when an employer treats criminal history information disparately for different applicants or employees, based on their race or national origin (disparate treatment liability). An employer’s neutral policy (e.g., excluding applicants from employment based on certain criminal conduct) also may disproportionately impact protected-class individuals and may violate the law if not job related and consistent with a business necessity (disparate impact liability)

The EEOC specifies two circumstances in which employers will meet the “job related and consistent with a business necessity” defense:

  • The employer validates the criminal conduct exclusion for the particular position under the Uniform Guidelines on Employee Selection Procedures (i.e., if there is data or analysis about criminal conduct as being related to subsequent work performance or conduct;) or
  • The employer develops a targeted screen considering at a minimum the nature of the crime, the time elapsed, and the particular job. The employer’s policy then provides an opportunity for an individualized assessment for those individuals identified by the screen to determine if the policy, as applied, is job related and consistent with a business necessity.

The guidance further asserts that although Title VII does not require individualized assessment in all circumstances, the use of a screen that does not include such assessment is more likely to violate its provisions. As an example of individualized assessment process, the EEOC recommends providing the applicants an opportunity to explain why they should not be denied a position due to the criminal record. The guidance also specifies the following factors that employers should assess:

  • Facts or circumstances surrounding the offense or conduct;
  • Number of charges of which the individual was convicted;
  • Older age at the time of conviction, or release from prison;
  • Evidence that the individual performed the same type of work, post-conviction, with the same or different employer, with no known incidents of criminal conduct;
  • Length and consistency of employment before and after the offense or conduct;
  • Rehabilitation efforts, e.g., education/training;
  • Employment or character references and any other information regarding fitness for the particular position; and
  • Whether the individual is bonded under a federal, state, or local bonding program.

The guidance recognizes that some employers are subject to federal statutory and/or regulatory requirements that prohibit them from hiring individuals with criminal records for certain positions. The EEOC notes that its new guidance does not preempt such federal guidelines, and explains that employers may be subject to a claim under Title VII if they scrutinize individuals to a higher degree than required under applicable federal requirements.

As in its previous version, the EEOC’s new guidance is not meant to be a deterrent to conducting background checks. But it should serve as a reminder that hiring policies and practices must be structured in compliance with the law.  

June 1st, 2012|Categories: Employment Decisions|Tags: , |
Go to Top