Policy

Can You Rescind an Offer After the Take-Home Broke Your AI Rule?

You can usually rescind an offer after learning a take-home broke your stated AI rule; employment is presumed at-will almost everywhere, and withdrawing before day one is the easy case unless your own letter promised a term, a bonus or a notice period. Defensible is the harder half: the rule in the brief before the task, the same line held on every candidate who got that brief, and a receipt or an admission rather than prose that read oddly. And weigh what the candidate has already given up.

The takeNotice which law is going to decide this. The AI hiring statutes are where the attention has gone. A rescission runs on McDonnell Douglas, which is 1973, and the retention rule at 29 CFR 1602.14. Both ask the same unglamorous question: what did you do with the other people on that req. There is no tally of how these end. On the shape of the doctrine, though, the employer who loses is the one holding a written rule and no comparison. The tool was never the issue. The other candidates are.

Where Olive fits

Open a role and see what the work shows

What made this decision expensive was reaching it on inference, weeks after the work happened. An Olive report is six findings a human reviewer writes by hand, each carrying the timestamped excerpt it rests on, exported with its rubric, scorer and bank versions, and the candidate is granted the identical document.

Rank your shortlist

Can you legally rescind the offer over AI use?

In almost every state, yes. Employment is presumed at-will in 49 states where no express or implied agreement says otherwise, and Montana is the single exception, generally requiring good cause once an employee has passed a probationary period 1. Withdrawing before a start date is the easy case, because the same employment could otherwise end the following week. What makes a withdrawal expensive is not the withdrawal.

Read the letter you sent before you read the submission again. An offer letter naming a term of employment, a guaranteed bonus schedule or a notice period is a promise sitting on top of at-will, and it is the first document counsel asks for. So is whatever a recruiter wrote in a thread after the offer went out, which is usually warmer than the letter and rarely reviewed by anyone.

Two other things drive the cost, and neither is about AI. The first is what the candidate has already given up on the strength of the offer, which sets the size of any claim. The second is the reason you put in writing, which becomes the reason on the record: it has to be true, it has to be the actual reason, and it has to be one you applied to other people who did the same thing.

Most of the exposure sits in that third requirement, and it is the half nobody writes about.

What had to be true before the take-home went out?

Two things, and both are dated. The rule had to exist in writing in the brief the candidate received, before they started the task. And it has to apply to every candidate who got that brief, not only to the one whose submission read oddly on a second look. A rule that surfaces in the breach is a standard invented after reading one person's work.

Start by rereading your own words, because there is often a reading in which nothing was broken. A line buried on page two of an attachment, a sentence that said "we'd prefer you didn't," a rule that reached them by email after they had already begun: each one is the difference between a violation and a misunderstanding, and you can settle it in the time it takes to open the sent folder.

Then the comparison, which is where uneven enforcement stops being an internal problem and becomes a legal one. In McDonnell Douglas Corp. v. Green (1973) the Supreme Court set out the Title VII framework under which a rejected applicant must "be afforded a fair opportunity to show that petitioner's stated reason for respondent's rejection was in fact pretext," adding that "especially relevant to such a showing would be evidence that white employees involved in acts against petitioner of comparable seriousness to the 'stall-in' were nevertheless retained or rehired" 2. The candidate you rescind gets compared to the candidates you kept. If two other people on the same req used AI on the same brief and one of them starts Monday, the thing under examination is your stated reason rather than their conduct.

The call you made after reading the submission is itself a selection procedure, whatever it felt like at the time. The Uniform Guidelines define one as "Any measure, combination of measures, or procedure used as a basis for any employment decision," reaching "the full range of assessment techniques" from paper-and-pencil tests "through informal or casual interviews and unscored application forms" 3. There is no carve-out for a judgment made over email on a Thursday. Same expectations: job-related, applied the same way, written down.

So write it down. Federal rules require personnel and employment records to be preserved "for a period of one year from the date of the making of the record or the personnel action involved, whichever occurs later" 4, and the EEOC's own guidance for employers is that once a charge is filed "these records must be kept until the final disposition of the charge or any lawsuit based on the charge" 5. Keep the brief as sent, the date it was sent, the list of everyone who got it, what each of them submitted and what you decided in each case. That file is either your answer or the gap in it, and the same file is what defending an AI-skills assessment to legal rests on.

How do you know the AI rule was actually broken?

Name the evidence before you name the consequence. A rescission survives on a receipt: a pasted chat window left in the file, a prompt fragment in a comment, the candidate's own account in a debrief or on a call. It does not survive on prose that reads a certain way, and it does not survive on a detector run three weeks after the submission landed.

Rank what you actually hold, because the three tiers are not close to equal.

  • A disclosure or an admission. They told you, in the submission or when asked. This is the only tier that settles anything by itself.
  • An artifact receipt. Something in the file a model session leaves behind. Strong, but read it for what it proves: that a tool was used, not that no thinking happened.
  • Style. Even paragraph lengths, confident hedging, a register that struck you as off. Most late discoveries are made here, and this tier proves nothing at all. Whether AI detectors work on written work is a question with a settled answer, and it is not the answer a rescission needs.

What a tier-two receipt looks like depends on the work. In software engineering, a commit landing nine hundred lines in a minute, or a test asserting the behavior the bug produces. In financial analysis, a growth rate that appears nowhere in the source packet. In legal operations, a citation that resolves to a real case saying something else. In marketing, a statistic attributed to a study nobody can find. Each of those proves carelessness before it proves a tool, and carelessness is the thing you were hiring against anyway.

Ask where the report came from, too. A teammate's hunch, a rejected finalist's complaint and an onboarding buddy's aside all arrive with an interest attached, and none of them was looking at the other submissions. If nobody has reread the rest of the cohort with the same eye, you don't have a violation yet. You have one person who got looked at harder.

Then have the conversation instead of the confrontation. Twenty minutes on their own submission: which claim the recommendation rests on, where the number came from, what they could not settle in the time. Someone who did the thinking answers in specifics inside a minute. You can ask a candidate directly how they used AI, because it is a question about work method. It gets you evidence, where an accusation gets you an argument that ends up in writing.

Weigh what the candidate has already given up

Ask, before the letter goes out, what they have done on the strength of the offer: resigned, given notice, turned down a competing offer, signed a lease, moved a household. None of it is visible from your side unless you ask, and each item changes the number and the story at once. A rescission on day thirty of a notice period is a different act from one sent the afternoon the offer landed.

Relocation is its own category, and in California it is a statute rather than a theory. Labor Code section 970 bars influencing a person to "change from one place to another in this State or from any place outside to any place within the State" for work "through or by means of knowingly false representations" about "The kind, character, or existence of such work" 6, and section 972 makes a violator "liable to the party aggrieved, in a civil action, for double damages resulting from such misrepresentations" 7. Both were enacted in 1937 and both are in force.

Read that narrowly, because it deserves to be read narrowly: it reaches representations that were false when made, not every offer later withdrawn. What it changes is the shape of the conversation. A candidate who moved for this job is not the same file as one across town, and the recruiter's messages become evidence rather than correspondence. Other states run their own versions of reliance doctrine; the local rule is a question for counsel with the dates in front of them.

Rescission is also not the only lever, and it is the only one you cannot take back. When the rule was ambiguous, or reached them late, or the evidence sits in tier three, there are moves between doing nothing and pulling the offer:

  • Delay the start and run a short, paid, differently-shaped task with the rule stated at the top.
  • Let it stand, state the disclosure expectation in writing for the role, and hold everyone to it from that date.
  • Withdraw, and say plainly which rule, when it was sent, and what it said.

Whichever you pick, expect to explain it. A rescinded candidate asks the same question a rejected one does, and what you owe a candidate who asks why does not change because the decision came late.

Write the rule so the next candidate reads it first

The uncomfortable finding here isn't about the candidate. A process that discovered AI use after the offer went out found it in the wrong order, and no forensic step repairs that. By then the decision is made, and every remaining move is expensive. Put the rule in the brief, ask for something gradeable instead of a promise, and make the work visible while it is being done.

Three lines, at the top of the brief rather than in an attachment:

  • Whether AI is allowed on this task, in one sentence.
  • What has to be disclosed: what was generated, what was verified, and against what.
  • What happens if that is not followed, named before anyone starts.

The third line is the one almost every brief skips, and it is the line that would have made this week a paragraph instead of a legal question. Whether the rule should be permission or a ban follows what the job itself permits, so allow AI on the take-home if the job allows it, and ban it only where a client contract, a data policy or an export rule genuinely does.

Then change what the task asks for, because a brief that wants a polished artifact is now grading whose assistant writes better prose, and the thinking has to be excavated afterward. That excavation is exactly what went wrong here. Hand over source material with something wrong in it that only checking catches, then ask which claim was checked and what changed as a result. A candidate who generated a draft and re-added the figure against the filing did the job. One who wrote every word by hand and shipped an unchecked number did not.

And say it twice. If a rule is worth rescinding an offer over, it belongs in the brief and in the offer letter, in the same words. A standard that exists in only one of those places is a standard you will be explaining under pressure, on the worst possible day, to someone who has already handed in their notice.

Read the evidence

Common questions

Can you rescind a job offer after the candidate has already resigned?

Legally, in most states, yes. But resignation is the fact that turns a withdrawal into a claim, because it is the reliance a court can price. Ask what they gave up before you decide: notice given, a competing offer declined, a lease signed, a move made. If the answer is substantial and your evidence is thin, a delayed start on a differently-shaped task costs less than the letter. In California, a candidate who relocated brings a statute with double damages into the conversation, so get counsel involved before anything goes out.

Does an at-will offer letter protect you if you withdraw the offer?

Partly. At-will is the default presumption in 49 states, and it means an offer can generally be withdrawn before a start date. What it does not cover is a promise the letter itself made, such as a stated term, a guaranteed bonus or a notice period. Nor does it cover a reason that is unlawful, or a reason applied to one candidate and not to others who did the same thing. Read the letter, then read what the recruiter wrote afterward. That second document is usually warmer than the first and rarely reviewed.

What if the take-home brief never mentioned AI at all?

Then there was no rule to break, and a rescission on that basis is a standard invented after reading one submission. The honest options are to let the hire stand and fix the brief, or to reopen the assessment for everyone on the req with the rule stated up front. What you cannot do defensibly is apply an unwritten expectation to the one candidate whose work struck you as unusual, because the comparison to the candidates you kept is exactly what gets examined later.

Is a detector result enough to rescind an offer?

No. A detector output is a probability about prose style, not a record of what a person did, and the error falls unevenly across writers. It is also the weakest tier of evidence available to you: a disclosure settles the question, an artifact receipt supports it, and a style judgment supports nothing. If the detector is all you have, treat it as a prompt to reread the whole cohort the same way, not as grounds for a decision about one person.

Should you tell the candidate the real reason for the rescission?

Yes, and in one specific sentence: which rule, where it was stated, when it was sent, and what it said. Vagueness reads as pretext and invites the question you least want asked. If the reason cannot be written in a sentence you would be comfortable having read back to you, it is not yet a reason. It is a suspicion, and the fix is a conversation about the work rather than a letter about the tool.

How do you keep this from happening on the next req?

Put the rule, the disclosure requirement and the consequence in the first screen of the brief, not in an attachment. Repeat the rule in the offer letter in the same words. Then change the task so the checking is what gets graded: source material with something wrong in it, and a question about which claim was verified and what changed as a result. A brief that grades polish will always send you looking for the thinking afterward, which is where late discoveries come from.

References

  1. 1. At-Will Employment (Wex) Wex Definitions Team, Legal Information Institute, Cornell Law School, 2021. law.cornell.edu Supports the at-will baseline: "In 49 U.S. states, employment is presumed to be at-will if there is no express or implied employment agreement to state otherwise," and "The only exception is Montana, which generally requires employers to have good cause for dismissing an employee who has passed the probationary period." Page states it was last reviewed in May of 2021.
  2. 2. McDonnell Douglas Corp. v. Green, 411 U.S. 792 (1973) Supreme Court of the United States, via Legal Information Institute, Cornell Law School, 1973. law.cornell.edu Supports the comparator and pretext point: a rejected applicant must "be afforded a fair opportunity to show that petitioner's stated reason for respondent's rejection was in fact pretext," and "Especially relevant to such a showing would be evidence that white employees involved in acts against petitioner of comparable seriousness to the 'stall-in' were nevertheless retained or rehired."
  3. 3. 29 CFR 1607.16 - Definitions (Uniform Guidelines on Employee Selection Procedures) Legal Information Institute, Cornell Law School, 1978. law.cornell.edu Supports the claim that a post-offer judgment about AI use is a selection procedure. Paragraph (Q) defines one as "Any measure, combination of measures, or procedure used as a basis for any employment decision," covering "the full range of assessment techniques from traditional paper and pencil tests, performance tests, training programs, or probationary periods and physical, educational, and work experience requirements through informal or casual interviews and unscored application forms."
  4. 4. 29 CFR 1602.14 - Preservation of records made or kept Legal Information Institute, Cornell Law School (current text; source credit 37 FR 9219, as amended through 89 FR 46021, May 28, 2024), 2024. law.cornell.edu Supports the one-year retention rule: records "shall be preserved by the employer for a period of one year from the date of the making of the record or the personnel action involved, whichever occurs later."
  5. 5. Recordkeeping Requirements U.S. Equal Employment Opportunity Commission, 2026. eeoc.gov Supports the hold-once-a-charge-is-filed point in the agency's own words: employers "keep all personnel or employment records for one year," and where an EEOC charge has been filed "these records must be kept until the final disposition of the charge or any lawsuit based on the charge."
  6. 6. California Labor Code section 970 California Legislative Information, California Legislature, 1937. leginfo.legislature.ca.gov Supports the relocation point. Bars influencing a person to "change from one place to another in this State or from any place outside to any place within the State" for work "through or by means of knowingly false representations" concerning, at subsection (a), "The kind, character, or existence of such work." Enacted by Stats. 1937, Ch. 90.
  7. 7. California Labor Code section 972 California Legislative Information, California Legislature, 1937. leginfo.legislature.ca.gov Supports the double-damages point: a person who violates section 970 "is liable to the party aggrieved, in a civil action, for double damages resulting from such misrepresentations." Enacted by Stats. 1937, Ch. 90.

7 sources, numbered by first appearance. Every one was opened and checked against the claim it carries. How Olive sources claims

General guidance, not legal advice. Hiring rules differ by state and country and change often; check anything here against your own counsel before you act on it.

Olive assesses how a person works with AI. It does not detect AI-written documents, and it never produces a score, a ranking, or a match percentage for a person. Candidates read the same report the employer reads.

Back to answers

Open your first role Ten attempts a month against a live item bank, with a human-written report on every one.