Put the AI Expectation in the Role, Not the Offer Letter

What is the offer letter for, and what does an AI paragraph add?

An offer letter states the terms of the offer: title, salary, start date, reporting line, contingencies such as references and work authorization, and the sentence saying employment remains at will. Everything past that list is either duplication or exposure. A paragraph describing how the person is expected to work with a model is a performance standard sitting inside a contract document.

In 1985 the New Jersey Supreme Court decided Woolley v. Hoffmann-La Roche, a case about an employee manual. The court held that an implied promise in a manual, that an employee will be fired only for cause, may be enforceable against the employer even where the employment runs for an indefinite term ¹.

The same opinion says what stops a manual from being read that way.

All the court asked for was a statement in a very prominent position: the employer promises nothing, remains free to change wages and working conditions without anyone's agreement, and keeps the absolute power to fire with or without good cause ¹.

But a disclaimer that broad reads badly two paragraphs above a description of how the job is to be done. One sentence says nothing here is a promise. The next describes a standard.

Woolley is New Jersey law, and at-will doctrine varies by state, so ask counsel about your own before drafting either way.

As a drafting habit rather than a rule of law, assume a document handed to an employee is easier to read as a promise than a conversation nobody wrote down.

Where does the AI expectation belong?

In the written role scope first, and in the first performance plan after that. The role scope is the document that says what the job is, and it exists before the posting goes out. It is the document to hand over when somebody asks what the work requires.

Federal disability regulation already counts a written description as evidence.

Under 29 CFR 1630.2(n)(3), the evidence of whether a job function is essential includes the employer's judgment and 'written job descriptions prepared before advertising or interviewing applicants for the job' ².

The regulation is about disability, not about AI. What it shows is one document the law weighs when it asks what a job requires. The list says it is not limited to its seven items, and the offer letter is not among them.

So the sentence goes where the requirement was first written.

If the posting already carries an AI line, writing an AI-skills requirement that is not legally vague is the same drafting problem one stage earlier.

Copy the wording across rather than paraphrasing it. The standard a person was hired against is the one they can fairly be held to, and a rewrite at each stage is how the two versions drift apart.

Write the expectation as tasks, not as fluency

'AI fluency required' is not a standard anyone can be measured against, and a signature underneath it does not make it one. Name the work instead. Which deliverables get drafted with a model here, what has to be verified before any of it ships, who reads it first, and what the person is still expected to do without a model open.

Three lines usually cover it:

• Which tasks a model is expected to be used on, and which it is not.
• What gets checked before the work leaves the desk, and against what source.
• Who reads it before it ships, and when that review stops.

Each of those is answerable yes or no at a review. 'Fluent' is not.

Setting a defensible bar for good enough at AI in a specific role writes that standard for the requisition rather than for one hire, and the two should not disagree.

The third line has an end date, and the end date is the part that goes unwritten.

Retiring the second reader by decision type rather than by date is a call somebody has to make out loud, and a plan is where a call like that gets recorded. An offer letter cannot carry a review that is supposed to stop.

A letter has no revision history.

Who reopens the AI line after day one?

The manager does, in week one and again at the thirty-day mark, if anyone does. An offer letter is not reviewed after it is signed. It goes into a file and comes out again, if at all, in a dispute. A performance plan gets opened, argued with and revised, which is why it is the right home for an expectation that will move as the tooling moves.

Role clarity is one of three parts of newcomer adjustment in the standard meta-analysis of onboarding.

Talya Bauer and colleagues fitted a model across 70 unique samples of newcomers. They tested whether role clarity, self-efficacy and social acceptance are the path from onboarding to satisfaction, performance, intention to remain and turnover. The results generally supported the model ³.

The abstract, the only part of the paper that could be opened, reports a design and a direction. It gives no effect size.

Timing may matter too, though the evidence is thin.

In a meta-analysis of realistic job previews, previews delivered after hire were associated with a larger drop in voluntary turnover than previews given before hire ⁴.

The authors say the ranges around the two measurements overlap for voluntary turnover, and five studies stand behind the after-hire one.

Read it as the direction the evidence leans.

The AI line goes into the performance plan as a task, with a date and a reviewer on it, and it moves when the work moves. What actually goes in a 30-60-90 day plan, and who writes it is the longer answer to the same question.

What if legal wants the AI expectation signed?

Then sign the employee AI policy, which is the document built to be signed. A policy names the approved tools, the data that may go into them, what has to be disclosed, and what happens when any of that changes. An acknowledgment on a policy is meant as a compliance record, though Woolley itself was about a manual, so ask counsel whether the policy needs its own prominent disclaimer.

The same acknowledgment inside an offer letter sits among the terms of the offer itself.

Employers deploying AI in the European Union carry a related duty already. Article 4 of the AI Act has applied since 2 February 2025, and it requires providers and deployers to take measures supporting the AI literacy of their staff and of anyone operating AI on their behalf ⁵.

The European Commission's own questions-and-answers page is blunt about what Article 4 does not require. It creates no obligation to measure an employee's knowledge of AI, no certificate is needed, and organisations can keep an internal record of trainings ⁵.

The duty runs to the employer, and the measures it asks for are the employer's to take.

Anyone who wants the AI paragraph in the letter is arguing about attention. An offer letter is the one document a candidate reads closely, and a role scope emailed in week two competes with laptop setup and benefits enrollment.

So the letter goes out at one page, saying what an offer says. The AI paragraph sits in the role scope attached to the requisition, and in the plan the manager walks through on day three, where somebody will open it again in November and change a line.

A sentence in the letter would still read exactly as typed, describing a job that had moved on without it.

Read the evidence >