The Offer Approval Black Hole: Why a Yes Turns Into a Lost Hire

The most dangerous word in recruiting: “approved”

At a debrief, the hiring manager says “Approved—make the offer.” Finance has not signed off on the grade, the start date requires immigration review, and equity terms are still a spreadsheet assumption. The recruiter sends an excited message implying finality. Then the offer changes. The candidate distrusts the process, even if the eventual terms are competitive.

Define approval states precisely: selection decision (“preferred candidate”), compensation authorization (“band and proposed placement approved”), legal/operational readiness (“terms, checks and start date reviewed”), and issued offer (“authorized communication sent”). A yes at one state must never masquerade as a yes at the next.

Build the seven-field decision-ready packet

1. Role identity: requisition ID, reporting line, level, work location and classification.
2. Compensation: proposed base, range, variable conditions, sign-on or equity approvals and currency.
3. Decision evidence: job-relevant scorecard, known evidence gaps and hiring-manager selection rationale.
4. Headcount authorization: budget owner, requisition status, hiring type and approval expiry.
5. Timing: proposed start date, notice period assumptions and any permit or equipment dependencies.
6. Conditions: only approved, lawful checks and relevant documents; distinguish conditional from unconditional terms.
7. Communications owner: who can make a verbal/written commitment, who sends updates, and by when.

A packet can be brief. Its job is to make each owner able to decide without asking the recruiter to reconstruct the entire hiring story from chat messages. Do not include unnecessary sensitive candidate information.

Separate blockers that run in parallel from those on the critical path

Consider a role where finance approval takes two business days, a background check five business days after lawful initiation, and HR document production one day after finance. Simply adding 2 + 5 + 1 creates an imaginary eight-day delay. Depending on the offer’s conditions and internal policy, some activities can proceed in parallel; other activities must not begin until a lawful or contractual condition is met.

Map each step with owner, prerequisite, earliest permissible start, expected duration and escalation time. Use the longest valid dependency path as the planning constraint, not the sum of every task in the chain. Do not initiate vetting prematurely just to speed up the process: ICO guidance stresses proportionality and limits around candidate vetting. ICO guidance.

The candidate update that avoids false commitment

The safest concise update is: “You are our preferred candidate. We are completing internal approvals before we can issue an official offer. The proposed compensation and start date are not confirmed yet. I will update you by Thursday, including if the timeline changes.” Do not present a budget placeholder as a final salary. Do not use “formalities” to describe substantive immigration, employment or legal requirements.

In the UK, official guidance distinguishes conditional and unconditional offers and warns that accepted unconditional offers may have binding contractual consequences; verbal offers can also matter. Other countries differ. Have authorized HR/legal personnel approve offer language. Acas offering a job and GOV.UK job offer rights.

Escalation: If approval misses a date, the recruiter owes a transparent status update—not a renewed promise that “the letter is coming today” without evidence.

Use an exception ledger instead of invisible backchannels

Store decision dates and document versions, not unsupported “X is always fine” assertions. The candidate should not become a messenger between legal, finance and the hiring team.

A case: fast recruiter, slow approval circuit

Illustrative example: the recruiter obtains a verbal yes on Monday. Compensation approval is still pending on Thursday because a proposed level has no approved salary placement. The formal offer goes out the next Tuesday. The recruiter’s follow-up speed was excellent; the authorization was not.

Root-cause audit: was grade approval required before interviews? Were exceptions expected? Was the designated approver out of office without delegate coverage? Did someone make a candidate-facing commitment before terms were authorized? Correcting any one of these may be more valuable than buying another email automation.

Do not call a missed offer an “offer decline” if no valid offer was issued. This changes the analytics denominator and hides where the work stalled.

A two-speed process that preserves fairness

Standard path: preapproved role, grade and compensation placement, complete evidence, fixed sign-off owners. Exception path: material scope, budget, jurisdiction or terms change requiring documented human review. Do not fast-track a favored candidate around consistent controls while holding others to a longer process.

A good internal SLA is a contract about who acts when, not a blanket legal guarantee. Start with an agreed response window and backup approver. Track elapsed business hours separately from elapsed clock hours, and never compare them on the same chart without a label.

After launch, track decision-to-approved-terms, terms-to-letter, approval rework, and candidate withdrawals before letter. Attach the reason code to the stalled dependency rather than the candidate.

What the offer packet must never claim

A readiness checklist is not a contract, a right-to-work determination or a compensation equity study. It can reveal missing information; it cannot grant legal authority or certify compliance. Do not request sensitive documents earlier than needed, and do not disclose confidential feedback in a candidate-facing approval trail.

The final publication of a job offer requires the employer’s competent HR/legal approval and jurisdiction-specific terms. Prioritize accurate promises over spectacularly fast but revocable messages.

Try the operational check

This small calculator runs entirely in the browser; no real applicant records are required. Use it to make a process assumption visible before reporting a conclusion.

Make this a repeatable standard, not a one-off hack

Capture the date, decision owner, source data, role family and exception reason every time you apply the method. Review the oldest unresolved examples with a second person. If the evidence points to another root cause, update the workflow rather than forcing a convenient metric to match your theory.

All cases and numerical values in this article are illustrative unless explicitly attributed. The operational checklists are a transparent practitioner synthesis of source guidance, not a claim of a universally validated test, legal rule or proprietary measured result. Jurisdiction-specific requirements require local review.

Research basis and further reading

Primary regulatory/professional guidance and explicitly identified vendor operational analysis. Sources are relevant reference points; the specific operational framework and synthetic cases above are our synthesis rather than findings directly measured by every linked source.

1. Acas offering someone a job
2. GOV.UK job offer rights
3. Acas if an offer is withdrawn
4. Acas employment contract formation
5. Acas reference timing and consent
6. ICO candidate pre-employment vetting
7. ICO recruitment selection overview
8. CIPD recruitment appointment stage
9. EEOC compensation discrimination
10. Ashby startup offers (vendor dataset)

Apply the finding before the next decision

Choose a single open role, review real process events, and document one falsifiable improvement. Keep the decision in human hands and show candidates what changed in their experience—not just on a dashboard.