Skip forward into hiring notes
RosterAcorn

2 NYC exemption points: the employer's burden and reach

An NYC employer that invokes an exemption from criminal-history protections must prove it applies, and exemptions attach to defined positions, not whole agencies.

New York City's rules on criminal history in hiring are built around a general rule and a short list of exceptions. Recruiters and hiring managers often reach for the exception first, because it is the answer they want. That habit causes most of the trouble. This post covers two points that decide whether an exemption really applies to a role: who has to prove it, and how far it reaches.

Key takeaways

  • Treat an exemption as a narrow carve-out, and confirm the role clearly falls within a listed exception.
  • Expect the employer to carry the burden: when it invokes an exemption to defend against liability, it must prove the exemption by a preponderance of the evidence.
  • Write the exemption analysis when the decision is made, and keep the duties, the exemption text, the reasoning and the reviewer's name in the file.
  • Check the position, not the agency: police and peace officers as defined under the Criminal Procedure Law are exempt, while other positions at law enforcement agencies, including civilian positions, keep partial protections.
  • Compare the job's actual duties to the exemption's words, and treat real doubt as a reason not to rely on the exemption.

The main source here is the NYC Commission on Human Rights' legal guidance on the Fair Chance Act, at nyc.gov/site/cchr/law/fair-chance-act.page. I quote it where the exact wording matters and keep everything else general. This is orientation for hiring teams, not legal advice. If a real decision turns on an exemption, bring the specific role and facts to counsel before you act.

Start from the general rule, not the exception

The guidance is organized around a general rule with limited exceptions. In one passage it points readers back to a list of those exceptions rather than describing them as broad categories: "See note 52, supra, for a list of limited exceptions to this general rule." The word "limited" is the important part. An exemption is a narrow carve-out from a rule that otherwise applies. So the question for any role is not "could this role be exempt?" but "does this role clearly fall within one of the listed exceptions?"

The guidance also states a construction rule that should shape every exemption conversation: "Consistent with the Local Civil Rights Restoration Act of 2005, all exemptions to coverage under the NYCHRL's anti-discrimination provisions must be construed narrowly." In practice, when a role sits at the edge of an exemption, the reading that keeps the protections in place is the one the guidance favors. A hiring team that wants to rely on an exemption has to justify the fit. It cannot assume the fit and wait for someone to disprove it.

That framing changes the first meeting about a role. Instead of asking the hiring manager, "Is this one of the exempt jobs?", ask for the job's actual duties in writing, then compare those duties to the exemption's words. Titles are a poor guide. A title such as "officer" or "supervisor" may describe a role that falls inside an exemption, outside it, or partly inside it. The duties and the exemption text decide the matter. The title is only a label.

Narrow construction also affects how you document the decision. If an exemption is the reason you can consider someone's record, the file needs to show the reasoning in plain terms. The sentence "this role is exempt" is a conclusion with no support behind it. A useful note says what the role does, which exemption text it matches, and why the match is clear. Someone who reads that note later should be able to follow it without asking the person who wrote it. For a format for that note, see Hiring Decision Debrief: Notes to a Recorded Decision.

Consider how this plays out across a typical hiring cycle. A hiring manager asks for an exemption on a role because the team has always treated it that way. Nobody can say which words of the exemption the role meets. The recruiter passes the request along, the exception is applied, and the reasoning lives only in people's memories. Months later, when an applicant asks why a record was considered, the team has no written answer. The narrow-construction rule exists for exactly this situation. The team has to show the fit, and "we have always done it" does not show it.

The employer carries the burden of proof

The first point is about who must prove the exemption. The guidance is direct: "Employers who invoke an exemption to defend against liability have the burden of proving the exemption by a preponderance of the evidence."

Three things follow from that sentence.

First, the burden sits with the employer, and it applies when an employer invokes an exemption to defend itself against liability. A recruiter who says "the role is exempt" in an internal meeting has made an internal claim. If that claim is later raised as a defense, the employer is the party that has to prove it. The applicant does not carry the job of showing that the exemption is missing.

Second, the standard is "a preponderance of the evidence." How it applies to the evidence your organization would actually have is a question for counsel. What you can do now is ask a harder question: if the decision were challenged, what would we show, and would that persuade someone who was not in the room when it was made?

Third, the burden is about evidence, which means the record has to exist before any dispute. Documentation written after a complaint arrives under pressure and invites doubt. A better practice is to write the exemption analysis when the decision is made: the role's duties, the exemption text, the reasoning, the date, and the name of the person who reviewed it. That file is what you will have if someone asks later.

It helps to be concrete about what a hiring team can and cannot do with this point. The team can rely on an exemption when it has the proof to support it. It cannot treat an exemption as a shield that works without a record. The burden of proof is the reason the record matters as much as the decision itself.

One more caution. The burden principle is about defending a claim of liability. It does not settle whether a process should ask about criminal history in the first place, and it does not excuse an inquiry that was made before anyone looked at the role. If your process asks about criminal history for roles that nobody has analyzed, the analysis is happening after the inquiry, which is the wrong order. Do the analysis first, then decide what, if anything, the process should ask.

It is also worth separating two questions that teams often merge. The first is whether an exemption exists for a role at all. The second is whether the team can prove that the role falls inside it. A team can be right on the first question and still lose on the second if its reasoning was never written down. Treat them as separate steps, and do not let confidence on the first stand in for evidence on the second.

The guidance also cites a New York decision on a related point, and it is worth reading closely. The guidance quotes the court: "A failure to take into consideration each of these factors results in a failure to comply with the Correction Law's mandatory directive." The guidance cites that case together with another decision. The passage is about a state law requirement rather than the NYCHRL exemption itself, but the lesson carries over. When a rule lists factors that must be considered, a decision that skips them is not a decision that complies with the rule, however sound the outcome may feel.

Reach stops at the position

The second point is about how far an exemption reaches. The clearest example in the guidance involves police and peace officers, and the lesson applies more widely.

The table below sets the two groups side by side.

Position Exempt from NYCHRL criminal-history employment protections?Protections
Police and peace officers, as defined under the Criminal Procedure Law YesExempt from the criminal-history employment protections.
Other positions at law enforcement agencies, including civilian positions Not described as exempt Protected from discrimination based on an ACD or a favorable outcome under CPL § 160.50. Not protected against inquiries or adverse actions based on a conviction, youthful offender adjudication, or pending case. Not entitled to the Fair Chance Process before adverse action on those cases.

The guidance states the exemption first: "Police and peace officers are exempt from the NYCHRL's employment protections based on criminal history." It then ties those positions to a legal definition: "Under the NYCHRL, police and peace officers refer to those positions as defined under the Criminal Procedure Law."

That second sentence is the key to reach. The exemption does not cover everyone who works for a police department, or everyone who works in a building that houses law enforcement. It covers positions that meet the definition the Criminal Procedure Law supplies. A hiring manager at a law enforcement agency therefore cannot treat the agency as one unit. Each position needs its own analysis, starting with whether it meets the definition at all.

The guidance addresses the other positions directly: "Other positions at law enforcement agencies, including civilian positions, are protected from discrimination based on an ACD or a favorable outcome under Criminal Procedure Law § 160.50, but are not protected against inquiries or adverse actions based on a conviction, youthful offender adjudication, or pending case, and are not entitled to the Fair Chance Process before adverse action is taken based on such cases."

Read that sentence slowly, because it is the reason partial coverage is a real category. A civilian role at a law enforcement agency is not described as exempt, and it still has some protection. Inquiries and adverse actions based on a conviction, a youthful offender adjudication, or a pending case are not covered by the same protection. The guidance also says those positions are not entitled to the Fair Chance Process before adverse action is taken on those cases.

So the reach of an exemption is not all or nothing within an organization. The same agency can have one position where the exemption applies and another where protections are partial and the Fair Chance Process still does not apply to certain cases. Hiring teams should not read "law enforcement agency" as a single category, and they should not read "civilian" as a synonym for "unprotected." The guidance describes a middle ground, and that middle ground is where recruiters most often make mistakes.

Here is a practical way to apply that. Before anyone discusses an applicant's record for a role at a law enforcement agency, write down whether the role is one of the defined positions. If the answer is unclear, you do not yet know the reach of the exemption, and you should not act as though you do. If the role is not one of the defined positions, the partial protections apply (civilian positions included), and the file should say which kinds of records the team considered and why.

A partial exemption also changes how the decision is explained to the people who make it. Hiring managers often hear "the agency is exempt" and conclude that every question is open. The guidance supports a narrower message: the exemption attaches to particular positions, and other positions at the same agency keep their protections. When you brief a hiring manager, name the position, name the category it falls into, and say what the team may and may not consider for that category. A short, specific briefing prevents the broad assumption that causes most errors.

The reach question also works in the other direction. A role can contain a few duties that look like they fall within an exemption and many that do not. A team that treats the whole job as exempt because of one part has stretched the exemption past its words. The narrow-construction rule points the other way: the exemption covers what the text covers, and the remaining duties stay under the general rule.

Illustrative example: a role with 5 duties

A hiring team at a law enforcement agency opens a role with 5 listed duties. Before anyone looks at an applicant's record, the recruiter writes the duties in plain words and compares each one to the exemption text, not to the job title. Two duties match the exemption text and three do not, so the team does not treat the whole role as exempt. It records the duties, the exemption text relied on, the date and the reviewer's name, and it asks counsel before using the exemption as a defense.

Where the review still applies

The guidance also describes what a review can look like in practice. Its first scenario reads: "After completing its review, DOH notifies the employer that nothing in an applicant's criminal record requires the employer to reject the applicant and provides the employer a copy of the applicant's criminal record." DOH is the abbreviation the guidance uses for the agency in that scenario.

Two points matter for hiring teams. First, the notice says that nothing in the record requires rejection. That is not the same as requiring a hire. The employer still has to make a decision, and that decision still needs the analysis and the written record discussed above. A team that reads "nothing requires rejection" as "we must hire" has made a second mistake on top of the first.

Second, the employer receives a copy of the applicant's record. Once the employer holds that information, its handling of the record becomes part of the file. Who saw it, when they saw it, and how it was used are questions that a reviewer could ask later. Write down the answers at the time, not from memory.

The court passage cited earlier points to the same discipline from a different angle. A decision that considers the required factors and records that consideration is in a much stronger position than one that reaches a sensible result without showing the work. The factor analysis is not a formality to be completed after the decision. It is part of the decision.

Brief the people who make the decision

Most exemption errors do not start with a lawyer or a compliance officer. They start with a hiring manager who heard a shorthand version of the rule and passed it on. A recruiter who sends a one-line summary such as "that job is exempt" has handed over a conclusion without the reasoning, and the next person will repeat the conclusion without checking it.

A better briefing has three parts. It states the role's duties in plain words. It names the exemption text the team believes applies, and says whether the role meets the definition in full or only in part. And it lists what the team has decided it will and will not consider for that role. Each part should be short enough to read in a minute and specific enough that a stranger could check it.

Briefings also need an owner. Decide who is responsible for the exemption analysis for each role, who approves it, and where the final version is stored. If the answer to any of those questions is "whoever is available," the process will drift. The guidance's emphasis on the employer's burden makes the ownership question more than an administrative detail, because the employer is the party that must be able to produce the proof later.

Finally, revisit the analysis when the role changes. A job description that is rewritten, a new supervisory duty added, or a move between units can change the answer. The analysis reflects the role as it was described when it was written. If the role is described differently later, the old analysis does not automatically carry over.

A checklist before you decide

Use these steps before relying on an exemption for any role. They are general practice, not a substitute for the guidance or for counsel. For related rules, see Criminal record hiring: 3 rules before you decide.

  • Write the role's actual duties in plain words before anyone reviews an applicant's record.
  • Compare those duties to the exemption's text, not to the job title.
  • If the role has several parts, check each part. Do not let one exempt duty cover the whole job unless the text supports that reading.
  • At a law enforcement agency, first decide whether the role is one of the defined positions, or whether it is another position at the agency, which keeps partial protections (civilian positions included).
  • Treat real doubt as a reason not to rely on the exemption, consistent with the narrow-construction rule.
  • Record the decision with its date, the reviewer's name, the exemption text relied on, and the reasons.
  • Keep the review of any criminal-history information separate from the rest of the applicant file, and record who had access.
  • Ask counsel before relying on an exemption as a defense to a claim.

Keep the file, not the slogan

The two points work together. The first says the employer carries the burden of proof when it invokes an exemption to defend against liability, and that the proof is a preponderance of the evidence. The second says that exemptions attach to defined positions and can reach some parts of an organization while leaving others under the general protections. Together they mean that a hiring team cannot treat an exemption as a label it applies to a department, a building, or a job title. It is a claim about a specific position, backed by evidence.

Many teams want a simple rule, such as "law enforcement is exempt" or "civilian roles are covered." Neither slogan holds in that form. Police and peace officers, as defined under the Criminal Procedure Law, are exempt from the NYCHRL's criminal-history employment protections. Other positions at those agencies are protected in part, and the guidance describes exactly which parts. The details are the rule, and the details are what you have to be able to prove.

The narrow-construction principle sets the tone for all of it. Exemptions are limited, and doubt cuts against relying on them. A recruiter who keeps that in mind will ask better questions, write better notes, and avoid the most common error, which is assuming that a role is exempt because it feels like it should be.

If you take one action from this post, make it this: before the next role is posted or the next applicant's record is reviewed, write a short analysis that names the role's duties, the exemption text, the reach of that text, and the reason the match holds. Date it, sign it, and keep it with the file. That document is the employer's burden in practice. It is also the first thing you will want if anyone ever asks how the decision was made.

Related guides: Delaware criminal history: 4 public hiring rules · Contract job ad rules for the $10,000 exemption · Criminal record data: 4 sources for hiring files.

Frequently asked questions

Who has to prove that an NYC exemption applies?

The employer does, because when it invokes an exemption to defend against liability, it must prove the exemption by a preponderance of the evidence.

Are all jobs at a law enforcement agency exempt?

No, only police and peace officers as defined under the Criminal Procedure Law are exempt, while other positions at those agencies, including civilian positions, keep partial protections.

Does "nothing requires rejection" mean the employer must hire?

No, a notice that nothing in a record requires rejection does not require a hire, so the employer still makes the decision with its analysis and written record.

Sources