Skip forward into hiring notes
RosterAcorn

Withdrawing a conditional offer: 3 checks to settle first

In the District of Columbia, a conditional offer may be withdrawn only for a legitimate business reason. The District of Columbia text, according to Council of the District of Columbia, sets that standard first. Three checks follow from it: the reason, the notice the same text lists, and the rehabilitation material it also lists. Each one should be settled and written down before the offer is ended.

Key takeaways

  • Write the legitimate business reason in your own words before any message goes to the applicant.
  • Check that the reason ties to the duties listed in the job posting.
  • Keep a dated copy of the Office of Human Rights notice in the applicant file.
  • Record whether the applicant produced rehabilitation material, and say so plainly if none was produced.
  • Treat vendor figures as vendor claims, not results your firm will get.

Why a vendor result is not the reason

A background report feeds the hiring decision, but the District of Columbia text asks for a legitimate business reason, and a background report or vendor result is not, by itself, that reason. The standard is the employer's reason, not the document that informed the employer's view. A reviewer reading the file later will look for the reason first, so the file has to contain one.

Checkr describes its adjudication tools this way: "Adjudication tools are designed to support compliance, increase consistency, and optimize your talent pool," according to Checkr. That sentence describes what the product is designed to support, and the file should not treat it as a ruling on whether a particular withdrawal is lawful.

A practical habit is to write the reason down before the report's summary circulates to other people on the team. Writing it first keeps the report from becoming the reason by accident. The reason should be the employer's own statement, in the employer's own words, and it should refer to the role being offered rather than to the summary alone.

If your team reads results inside a vendor's product, keep the vendor's wording and your wording apart in the file.

Before: confirm a legitimate business reason

The first check is the reason itself. The hiring team has to state its own reason in plain terms. The statement has to make sense to a reviewer who never saw the hiring discussion.

As an editorial suggestion, not a legal rule, a reason is easier to review when it fits in one sentence and ties to the duties of the role. A reason that refers only to a general impression of the applicant is harder to tie to the role. A reason that names the part of the report that raised the concern is easier to review later, because the reviewer can find that part in the file.

The reason should be drafted before anyone sends a message. The draft should be read against the duties listed in the job posting. The reviewer test is simple: could someone who was not in the hiring discussion follow the link between the duties and the reason? If not, the wording needs to be tightened before it goes into the file.

Use the same wording in the applicant file that you would use in a message to the applicant. Matching the two records means the file and the message tell the same story, and a later reviewer does not have to reconcile two versions.

If your team uses a staffing firm, see our staffing firm offer withdrawal guide. The reason check here still applies to the employer's own file.

Keep the reason separate from the background report's summary. The report can be attached to the file, but the reason should sit in its own note with its own date. That separation makes it clear which statement came from the report and which came from the hiring team.

During: give the Office of Human Rights notice

The second check is the notice. The District of Columbia text lists "A notice that advises the applicant of his or her opportunity to file an administrative complaint with the Office of Human Rights," according to Council of the District of Columbia. The quoted item names the notice and its purpose.

Read the full section before the notice is drafted. The quoted text covers the District of Columbia, so a notice practice from one jurisdiction should not be carried into another without checking that jurisdiction's own rules.

Timing has to be checked against the full text before the decision is communicated to the applicant. A notice that arrives before the timing question is settled leaves the file with a gap.

A dated copy of the notice belongs in the applicant file next to the reason, so the record shows what was sent and when. If someone outside the hiring team drafts the notice, the hiring team should compare it with the quoted item before it goes out. That comparison catches wording that describes the complaint process differently from the list.

During: weigh rehabilitation information

The third check is rehabilitation material. The District of Columbia text lists "Any information produced by the applicant, or produced on his or her behalf, in regard to his or her rehabilitation and good conduct since the occurrence of the criminal offense," according to Council of the District of Columbia. The quote lists that information as one item in the section.

A practical step is to record whether the applicant, or someone on the applicant's behalf, produced any rehabilitation material. If material was produced, the file should show that it was received and reviewed alongside the stated reason. A file that contains only the reason does not show the full set of items the list describes.

The item is limited to conduct "since the occurrence of the criminal offense." Note the dates the material refers to, and compare them with the offense date shown in the background report, if the report shows one. That comparison is an editorial recommendation, not a rule from the quoted text.

Silence should not be treated as a finding. If the applicant produced no such material, the file should say so in plain words. A plain statement stops a later reader from assuming the material was overlooked.

For the report itself, our background report checklist can sit beside this step as a companion check.

After: record what the tool did and what you decided

After the decision, the file should show two things: what the tool returned and what the team decided. Checkr says that "Configurable workflows make it easy to select packages, order reports, manage adjudication, and more," according to Checkr. That describes a workflow setting in the product, and the team's reason still has to be written in the team's own words.

Good records name the tool output that was reviewed, the legitimate business reason, the notice item, and the rehabilitation material that was considered. Each item should be listed separately, so a later reviewer can match each one to its source. A single combined paragraph makes that matching harder. For recording the decision itself, see our hiring decision debrief.

The file should include the name of the person who made the decision and the date of the decision. A later reviewer can then trace the decision to its author. If a withdrawal is later questioned, the reason, the notice, and the material considered should be found together in one place.

The output and the reason should sit in separate sections of the file, with the output labeled as the vendor's result. Labeling keeps the vendor's wording from being mistaken for the employer's conclusion. A record should not be described as a change history unless your own system keeps one.

Illustrative example: a file with 3 checks

This example is illustrative only. A hiring team extends a conditional offer, then receives a background report with a summary. Before anything is sent, the team writes its reason in a single sentence and ties that sentence to the duties in the posting. It saves the report as a separate item with its own date. It then records whether the applicant produced rehabilitation material, and writes down the answer even when it is no. The finished file has 3 entries, each with a date and the name of the person who made the decision.

Where automation claims stop

Checkr's staffing page states "Reduce manual reviews by up to 80% with Checkr Assess, an automated adjudication tool," according to Checkr. That is a vendor claim, not a result your firm will get. The same company says "97% of customers say our turnaround times are faster than the competition," according to Checkr. That figure describes speed, and speed is a separate question from whether a withdrawal is lawful.

Goodhire's company page says "more than 100,000 employers have trusted GoodHire for employment screening services," according to Goodhire. The same page says "We have 10+ years of experience organizing government records and identity data," according to Goodhire. Its blog says "We offer 100+ screening options to meet your business needs," according to Goodhire.

These claims should not be read as support for any particular decision. Where a vendor page makes a claim, the file should record it as the vendor's claim and keep it apart from the employer's reason. That separation keeps marketing language out of the legal basis for the decision.

PublisherSourceQuoted wording
Council of the District of ColumbiaDistrict of Columbia code section on inquiries into arrests, accusations, and convictions an employer may only withdraw the conditional offer to an applicant or take an adverse action against an applicant for a legitimate business reason
Checkr Checkr background check pageAdjudication tools are designed to support compliance, increase consistency, and optimize your talent pool.
Goodhire Goodhire company pageThat’s why more than 100,000 employers have trusted GoodHire for employment screening services.

Next step: Before you send any withdrawal, write the legitimate business reason in the applicant file next to the vendor result.

FAQ

Can I withdraw a conditional offer after a background result?

The District of Columbia text allows a withdrawal of a conditional offer only for a legitimate business reason, according to Council of the District of Columbia. The text covers the District of Columbia, so other jurisdictions need their own rules checked.

Which notice does DC code list for the applicant?

The text lists a notice that advises the applicant of the opportunity to file an administrative complaint with the Office of Human Rights, according to Council of the District of Columbia. Timing and delivery should be checked against the full section before the notice goes out.

Does an automated adjudication tool make the hiring decision?

The decision rests on the employer's legitimate business reason, and a tool's output is not that reason. The District of Columbia text sets that standard, according to Council of the District of Columbia.

How much do vendors say their tools cut manual reviews?

Checkr's staffing page claims a reduction of up to 80% in manual reviews with Checkr Assess, according to Checkr. That is the vendor's own claim about its product, not a measure of what your team would see.

Using AI software to screen job applicants? AI Hiring Paperwork Pack is a workbook filled from your answers that shows which rules reach each tool and the wording applicants should get.

Sources