Why contingent offers are their own skill

Most offer-letter advice assumes a clean, unconditional offer: here's the role, here's the pay, start Monday. But a huge share of real hiring — and almost all of GovCon hiring — runs on contingent offers: offers that are genuine but conditioned on something that hasn't happened yet. The contract hasn't been awarded. The clearance hasn't adjudicated. The background check hasn't come back. The candidate is real, the role is real, but the start date depends on an event outside everyone's control.

Written well, a contingent offer lets you lock in a candidate now and start them the moment the condition clears. Written badly, it's a promise you can't keep that turns into a withdrawn-offer dispute. This is a recruiter-and-HR working guide, not legal advice — and because contingencies interact with at-will rules, reliance, and FCRA timing, run your template past counsel once and reuse it.

The contingencies that actually do work

A contingency only protects you if it's specific, objective, and tied to an event you can point to. Vague conditions ("subject to final approval") protect no one and look like bad faith. The ones that hold up:

  • Contingent on contract award or funding. Common in GovCon and staffing: "This offer is contingent on [Company] receiving award of [contract/solicitation number]. If award is not made by [date], this offer may be withdrawn with no further obligation." This is the honest way to recruit to a pipeline; for the proposal-stage version of this, see recruiting to the proposal.
  • Contingent on a favorable clearance adjudication or transfer. "This offer is contingent on your obtaining/maintaining a [level] clearance and being granted access on the program." Pair this with a realistic start window — a "clearable" candidate is months out, and pretending otherwise is how the offer falls apart. The SF-86 and e-QIP timeline is part of this start date, not a footnote to it.
  • Contingent on a satisfactory background check. Standard and enforceable — but the moment you run a third-party check, you're in FCRA territory, and "satisfactory" doesn't let you skip the adverse-action process. If the report is why you walk away, you still owe the pre-adverse and adverse action notices.
  • Contingent on I-9 / work authorization, a drug screen, a license or certification, or a physical where job-related and lawful.

The throughline: each names a concrete condition and, ideally, a deadline after which the offer can lapse without anyone breaching anything.

The contingencies that create liability

Some "conditions" do the opposite of protect you:

  • Conditions that are really discrimination in disguise. "Contingent on passing a physical" applied only to older candidates, or a medical exam demanded before a conditional offer, runs straight into the ADA. Medical exams and disability-related questions are only permissible after a real conditional offer and must be applied uniformly — the same discipline covered in the ADA in hiring.
  • Open-ended subjective conditions. "Contingent on continued mutual fit" isn't a contingency, it's a way to renege. A court reading it later will see exactly that.
  • Contingencies you don't actually enforce. If you let one candidate start before the check clears and hold another to the letter, the contingency stops looking like policy and starts looking like pretext.

Reliance: the trap that turns a withdrawn offer into a lawsuit

Here's the part that costs employers real money. Even a properly contingent offer can create liability through detrimental reliance (promissory estoppel): the candidate, reasonably relying on your offer, resigns their current job, declines other offers, relocates, or otherwise burns a bridge — and then your contingency fails and you withdraw.

The candidate didn't have a contract, but they had a promise they reasonably acted on, and they have measurable damages. This is the single most common way a "we had a contingency, we're covered" offer goes sideways. You reduce it by:

  • Stating the contingencies prominently and in plain language, not buried in fine print.
  • Telling the candidate explicitly not to resign or relocate until the condition clears — and meaning it. If you need them to wait, say so in writing.
  • Being honest about timelines. A candidate told "clearance usually takes a few months" makes different life decisions than one told "you'll start in two weeks."

For the broader mechanics of pulling an offer back once it's out, can you rescind a job offer? covers the withdrawal itself; this article is about writing the offer so you rarely have to.

What belongs in the contingent offer letter

Build on a clean base offer — title, pay, classification, at-will language, the usual; what to put in an offer letter covers the foundation. Then layer the contingency section:

  • A clearly labeled "Contingencies" section listing each condition specifically.
  • A deadline or review date for each open-ended condition where possible ("if award is not made by [date]...").
  • What happens if a condition fails — the offer is withdrawn with no further obligation, stated plainly.
  • An explicit note on reliance advising the candidate not to take irreversible steps until conditions clear.
  • An expiration date on the offer itself, separate from the contingencies, so a candidate can't sit on it indefinitely.

And then the operational half nobody writes down: somebody has to track the condition to resolution. A contingent offer that no one revisits becomes a candidate in limbo, a start date that drifts, and eventually a frustrated person who takes another job.

Tracking it so contingent doesn't mean forgotten

In Hosting HR, offers carry a status lifecycle — Draft, Sent, Accepted, Declined, Expired, Rescinded — with timestamps and an audit log, so a contingent offer's state is visible instead of living in someone's inbox. Tie the open condition (award, adjudication, background check) to a dated task in the pipeline and onboarding workflow, and the day the condition clears becomes a trigger to confirm the start date — not a thing you hope a recruiter remembered. The contingency is what lets you make the offer early. The tracking is what lets you keep it.