Offer Letters and Hiring Promises: When Recruiting Emails Become Binding Commitments

A recruiter, close to landing a strong candidate, sends a warm follow-up: “We would love to have you here, and I can confirm the role comes with a guaranteed 15% bonus and a clear path to the senior title within a year.” No contract has been signed. HR has not finalised the compensation band. The candidate resigns from their current job, turns down a competing offer, and relocates. Six weeks later the business restructures, the bonus scheme changes, and the promotion timeline slips. The candidate’s lawyer now has three emails, and every one of them reads like a promise.

This is the quiet failure mode of hiring communication. The signed offer letter usually gets legal review. The forty emails, LinkedIn messages, and Slack notes around it almost never do. Yet courts and tribunals routinely look past the formal document to the surrounding words, because that is where intent, inducement, and reliance actually live. For compliance, legal, and HR risk owners, the offer paper trail is a live source of contractual and misrepresentation exposure, created by well-meaning people who were simply trying to be encouraging.

This is a field guide to the words around an offer: how an invitation quietly turns into a binding commitment, how to tell the two apart, and a checklist your recruiters can use before they hit send. It covers general legal principles across common-law and EU systems and is not legal advice; confirm the position in your jurisdiction with counsel.

How a friendly email becomes an enforceable term

Three legal mechanisms do most of the damage. Each one turns on specific words, and each one is triggered by phrasing recruiters use every day.

1. Reliance and promissory estoppel

Consider a real, anonymised case that HR lawyers still teach. A US health plan offered a pharmacist a position. Relying on that offer, he resigned from his existing job. Before he started, the employer withdrew the offer. The court held that even without a completed contract, a clear promise that the employer should reasonably expect to induce action, followed by the promise-holder acting on it to their detriment, could be enforced. The employer was liable for the loss the pharmacist suffered by giving up his other job. This is promissory estoppel, captured in the United States by the Restatement (Second) of Contracts section 90, and it has close cousins in most common-law systems.

The trigger is reliance language: any wording that invites the candidate to act (resign, relocate, decline other offers) before anything is signed. “Go ahead and give notice, this is a done deal” is the classic example. It reads as reassurance. It functions as an inducement. What makes it dangerous is that the recruiter is usually trying to be kind, easing a nervous candidate over the line, with no idea that the reassurance itself is the legally operative act.

2. Misrepresentation

A statement of fact made to induce someone to enter an employment relationship can create liability if it turns out to be false, even where the person making it believed it. In England and Wales, the Misrepresentation Act 1967 and the line of negligent-misstatement cases give a recruit a route to damages when they accept a role on the strength of an inaccurate assurance about pay, security, the state of the business, or the scope of the job. Overstating a bonus, describing a fragile role as stable, or promising resources that do not exist all sit here.

3. Terms imported into the contract

Where the signed contract is silent or ambiguous, tribunals will look at the offer emails to work out what was actually agreed. A “guaranteed” bonus mentioned in an email can be read as a contractual entitlement rather than a discretionary payment. A start-date assurance, a stated notice period, an equity figure, or a described reporting line can all be pulled into the binding terms if the surrounding correspondence treated them as settled. The formal document does not seal off the emails; it sits alongside them.

The common thread: liability attaches to definiteness. The more specific and unconditional the wording, the more it looks like a term. Vague enthusiasm is usually safe. Precise, unconditional commitments are where the exposure lives.

Invitation or commitment: the test

Before any offer-stage message goes out, run each sentence through four questions. If a line fails even one, it needs a rewrite or a caveat.

• Is it definite? A specific figure, date, title, or entitlement reads as a term. A range or a “subject to” reads as an invitation.
• Is it unconditional? Commitments that are not gated by “subject to contract”, board approval, references, or right-to-work checks are the ones that bind.
• Does it invite reliance? Any nudge to resign, relocate, or turn down another offer before signing creates estoppel risk.
• Is it accurate today? A statement about the bonus scheme, the role’s security, or the health of the business must be true when sent, or it is a misrepresentation waiting to surface.

The offer-email checklist: binding term vs safe invitation

Here is the artifact to hand your recruiters. The left column is language that commonly creates a binding term or misrepresentation exposure. The right column keeps the same warmth while staying an invitation. The rewrites are deliberately phrase-level, which is how a pre-send check should work: change the risky span, keep the rest of the message intact.

Risky phrasing (creates a term or exposure)	What goes wrong	Safer phrase-level rewrite
“You will receive a guaranteed 15% annual bonus.”	“Guaranteed” imports a contractual entitlement, overriding a discretionary scheme.	Replace “guaranteed 15% annual bonus” with “eligible for the discretionary bonus scheme (target 15%)”.
“This is a permanent, secure role for as long as you want it.”	Reads as a promise against dismissal and a statement of fact about security.	Remove “for as long as you want it”; keep “This is a permanent role, subject to the terms of the contract.”
“Go ahead and hand in your notice, the offer is a formality.”	Invites reliance before signing: textbook promissory estoppel.	Replace with “Please wait to give notice until the signed contract and pre-employment checks are complete.”
“You’ll be promoted to Director within twelve months.”	A definite, unconditional future promise that can be read as a term.	Change “will be promoted” to “will be considered for promotion, based on performance and business needs”.
“We can confirm a start date of 1 September.”	An unconditional date the business may not control; reliance if the candidate relocates.	Insert “target start date of 1 September, to be confirmed in the contract”.
“The team is fully funded and growing fast.”	A statement of fact about business health; misrepresentation if untrue when sent.	Remove the claim, or narrow to “the team is hiring for this role now”.
“We would love to have you, consider yourself part of the team.”	Warm, and low risk on its own, but read alongside specifics it colours the whole exchange as a deal.	Keep the warmth, add the anchor: “subject to the formal written offer”.

Two structural safeguards make the whole trail safer. First, put “subject to contract and satisfactory pre-employment checks” at the foot of every offer-stage email, so the surrounding messages inherit the caveat. Second, route all figures, dates, titles, and entitlements through the single signed document, and keep the emails to logistics and encouragement. The moment a specific term appears in free text, it is evidence.

The commitment risk in offer emails is a close relative of the exposure in the job advert itself. Where the advert can overpromise to the whole market, the offer email overpromises to one person who then acts on it. For the wording risk on the public-facing side, see our guide to promises in job ads and offer language.

Where a pre-send check fits (and where it does not)

Be honest about the boundary. A pre-send check will not stop a recruiter who deliberately wants to promise something off-book, and it is not a security control against a bad actor. What it addresses is the far more common problem: the careful, well-intentioned recruiter who writes “guaranteed bonus” because it sounds generous, and does not register that one word changed a discretionary payment into a contractual entitlement. That is accidental human risk, and it is exactly the category a check at the point of writing can catch.

This is where VerbaPulse sits. It reviews the draft in the browser, in Gmail and the tools recruiters already use, and flags the span that creates exposure with a short, phrase-level safer suggestion before the message is sent. When no safer wording preserves the intent (for example, a flat promise to override a discretionary scheme), it says so plainly.

It works as the front-end shield in front of your existing stack. Archiving and supervision platforms such as Smarsh and Proofpoint capture and review what has already been sent, which is essential for the record and for investigations. A pre-send check reduces how many risky offer emails reach those queues in the first place, so supervision spends its time on genuine signals rather than avoidable phrasing errors. The two complement each other: one catches the line before it leaves, the other preserves and reviews everything that does.

The takeaway

Do one thing this quarter: pull ten recent offer-stage email threads at random and read them against the four-question test above. You will almost certainly find “guaranteed”, a firm date the business does not control, or a “go ahead and resign” nudge sitting in free text with no caveat. Fix the template, add the “subject to contract” footer, and give recruiters a way to catch the risky span while they are writing, before the encouraging email becomes the exhibit. The offer letter was never the whole contract. The emails around it were always part of the deal.