A Hiring Freeze Ended. Your Old Shortlist Did Not Come Back to Life.

A restart protocol for paused requisitions: refresh role requirements, candidate interest, evidence validity and ATS state before resuming interviews.

The headcount is approved again. Someone clicks “reopen” in the ATS. That administrative action does not restore candidate availability, salary alignment or the validity of a six-month-old interview.

A restart protocol for paused requisitions: refresh role requirements, candidate interest, evidence validity and ATS state before resuming interviews. ↗

The false continuity of a reopened requisition

A hiring freeze creates two clocks. The ATS clock may preserve a candidate’s stage; the real-world clock keeps changing. Teams reorganize, salary bands move, candidates accept other jobs and previously assessed skills become less relevant. Treat reopening as a controlled restart, not a replay button. ↗

Platform documentation makes the distinction concrete: Oracle describes suspending requisitions, while Greenhouse documents how reopened frozen requisitions interact with HRIS synchronization. A status change is not a complete recruiting decision. ↗ ↗

Run the four-delta review before contacting anyone

Role delta: what changed in manager, scope, location, salary, seniority and must-have competencies? Candidate delta: who is still interested and what has changed in their circumstances? Evidence delta: which interview or work-sample results still assess the current role? Process delta: what must be re-approved or rebooked? ↗

If any delta is material, do not use the old shortlist as an unqualified ranking. A new requirement can make an old score noncomparable, even when it was valid at the time. Document a reasoned decision on which evidence to retain and which to refresh. ↗

The restart matrix

Same role, short pause, candidate reconfirms: resume at a comparable stage after checking scheduling and compensation. Changed role: obtain revised intake and re-evaluate only affected competencies. Long pause: check the age and relevance of each assessment; a calendar threshold alone is not a validity rule. Candidate declines: close the active outreach path, respect preferences and retention policy. ↗

Apply the matrix consistently to all candidates at the same stage. Avoid a private “favorites first” route unless a defensible priority rule existed before reopening. ↗

Send a truthful reactivation message

An honest message states that the process has resumed, summarizes confirmed changes, invites a fresh expression of interest and offers a no-pressure decline. It does not say “you are still a finalist” unless the team has actually reconfirmed that status. ↗

Example: “We have approval to restart the Product Analyst search. The role is now hybrid two days a week, and the salary range is unchanged. Would you like the updated description and a brief call before we discuss next steps? There is no expectation that you remain available.” The exact wording must reflect the actual requisition. ↗

Do not turn old consent into indefinite permission

Candidates may have applied for a specific vacancy, at a specific time, under a particular privacy notice. Recontact, retention and reuse should follow the lawful basis, transparency and retention rules that apply to the employer. ICO recruitment guidance covers applicant information throughout the process; its storage-limitation guidance cautions against indefinite retention without justification. ↗ ↗

Operationally, separate “candidate replied yes to a new conversation” from “data may lawfully be retained.” One does not automatically settle the other. ↗ ↗

The surprising failure mode: a clean ATS hides stale decisions

An ATS record can look complete: stage, interview score, positive feedback, approved requisition. Yet each field can refer to a different version of the job. Create a version bridge: role specification v1/v2, assessment rubric v1/v2, candidate interest confirmation date and owner of the reopen decision. ↗

If a candidate’s prior work sample measures a skill no longer needed, archive the result as historical evidence rather than silently translating it into a score for the new role. This is a process-integrity rule, not a prediction about the candidate. ↗

The seven-day reopening sprint

Day 1: finance and hiring manager confirm real headcount. Day 2: approve updated job specification. Day 3: map candidates by last contact and evidence relevance. Day 4: send transparent reactivation invitations. Day 5: schedule only opt-in candidates. Days 6–7: review fairness, old-versus-new rubric coverage and reporting definitions. ↗ ↗

Only after the restart should the dashboard resume measuring active-stage duration. Keep frozen days separate from active process time; otherwise a pause becomes a false measure of recruiter performance. Greenhouse explains how on-hold periods affect time-to-fill reporting. ↗

Run the operational check

Use the interactive worksheet below to test the decision logic with hypothetical or aggregated inputs. Keep identifiable candidate information out of this page.

Requisition restart gate

Check role and evidence changes before resuming the old candidate stage.

Enter values and run the check.

Runs locally in your browser. No data is transmitted. Results are operational prompts, not candidate or legal decisions.

The decision worth changing this week

Assign one owner, pilot the procedure on a small group, and record what evidence would falsify the hypothesis. Do not turn a process-audit score into an automated candidate rejection or a legal conclusion. ↗

Make evidence usable, not just searchable.

RoleRise supports evidence-led recruiting workflows and recruiter review.

Explore RoleRise