Talent SummonerHow to Pause and Restart a Search
A practical runbook for pausing, merging or restarting a hiring search with a preserved record, evidence review and named owners.
To pause and restart a hiring search, record why the work stopped, who owns the blocked condition and what must change, then reverify inherited work before the first new batch. Pausing is an operating decision, not silent abandonment: it preserves an approved need while the team lacks capacity, timing or a dependency needed to act responsibly. Restarting creates a new, bounded work period; it is not permission to resume an unexamined queue.
Should you continue, merge, pause, escalate or close a search?
Keep one shared record for every search. It needs the role-brief version, decision owner, search owner, current state, next action, dependencies and last review date.
| Signal | State | Record before moving it |
|---|---|---|
| The approved work and owner can take the next action | Continue | Next action, owner and review date |
| Two records have the same outcome and decision owner | Merge | Canonical record, retained history and one next owner |
| The need remains approved but capacity or a dependency is unavailable | Pause | Reason, frozen work, owner and restart condition |
| Scope, budget, location or another question exceeds the team's authority | Escalate | Exact question, decision-maker, due date and interim state |
| The outcome no longer has approval | Close | Effective date, decision authority and record instruction |
Similar titles alone are not enough to merge work. Compare outcome, must-haves, market boundary, decision owner and start context. These states describe work, not candidate quality.
What goes in a search pause record?
Capture why the work is pausing, the brief version, current queue, open questions, contact actions that are frozen, the person who owns the blocked condition, and the next review event or date. Preserve source links and decision history under the team's approved record and retention process.
State the limits of a pause: the role stays open, no person is labelled, the market is not declared exhausted and the brief does not change without approval. Candidate communication requires a current human decision and an approved route; an old profile or earlier conversation is not a reason to open a new conversation.
How to reverify inherited work before restarting a search
Before new discovery, compare the pause record with the proposed next step. Confirm that the role owner still approves the outcome, review capacity is available and the named pause condition actually changed. Then work through the inherited records.
| Check | What to compare | Required action when unclear |
|---|---|---|
| Role version | Outcome, must-haves, working pattern and market boundary | Create a new version and mark records needing comparable review |
| Evidence freshness | Source date, retrieval date and what the source actually supports | Treat stale or incomplete facts as a question, not proof |
| Prior decisions | Progress, hold, close and their stated reasons | Keep history; do not silently relabel a prior decision |
| Contact history | Previous route, response, opt-out or follow-up instruction | Ask the responsible owner before taking another contact action |
| Capacity | Search owner, reviewer and next gate | Keep the search paused when the next batch cannot be reviewed |
There is no universal age limit for evidence. Freshness means when information was observed, not whether it is true today. A current-looking title or new public project can prompt a focused human question, but it does not establish scope, availability or interest.
How much search history to keep for a fair restart
Keep enough history that a new reviewer can tell what a source showed from what the team later decided. Keep the role version that governed the original review, the reason a record progressed or closed, and any unanswered question. This gives a new reviewer context without claiming that the old observation is still current.
If the team changes its search boundary, record what changed: geography, work pattern, role outcome, required evidence or source route. Compare inherited records only against the part of the brief that remains relevant. A person should not be silently treated as unsuitable because the company changed its plan during the pause.
Use the same discipline for candidate-facing work. A paused search may create uncertainty for the team, but that uncertainty does not justify an unplanned message or an implied commitment. The contact owner should decide whether there is a legitimate next communication, what it can say truthfully and when it should be reviewed again. Preserve that decision separately from source freshness.
The same rule applies to tools and spreadsheets. Do not reopen an old search simply because the records remain available. Confirm the current role question first, then decide which records may be useful to a human reviewer. A restart record should explain why a work item returned to the queue and what the team will do differently this time.
Review that record with the role owner before the first new batch, and keep the decision beside the current brief version.
How to pass the search restart gate
Before adding new candidates, write down the first step of the restart. It might be one source review, a versioned discovery pass or a decision on a named dependency. Assign a scope, owner, due date and a stop condition. If the brief changed, keep new discovery separate until inherited records receive the same relevant review.
Fictional example: a team paused a backend-engineer search while the engineering manager was unavailable. At the review date, the manager returns but the location requirement has changed. The team starts brief version 2, asks which original records need a location recheck and only then decides whether to continue discovery. The pause did its job: it kept old work understandable without treating it as current.
Where Talent Summoner fits in a search restart
Talent Summoner fits after the restart gate passes, for the next discovery pass. Talent Summoner is our product for AI candidate sourcing, CV ranking and outreach you confirm before it sends (checked 30 September 2026). Candidate sourcing can support a new role-brief discovery pass; it does not manage the pause state, preserve contact permissions or decide who progresses. Candidate ranking is a separate review workflow for supplied CVs. Your team owns the search state, evidence, contact decisions, interviews and selection.
Is pausing a search the same as closing the role?
No. A pause keeps an approved need conditional on a named restart condition. A close records that the work is not proceeding under the authorised process.
What should trigger a restart?
Use the condition in the pause record, such as restored review capacity or an approved dependency decision. Recheck the role, owners and first action before work resumes.
Should old candidate records be deleted after a pause?
Follow the organisation's approved retention process. Keep enough decision history to explain the pause and restart, and ask the responsible owner about any unresolved retention or access question.
Can Talent Summoner restart the search for me?
No. Talent Summoner supports sourcing and ranking inputs. The team controls the role version, search status, contact decisions and next hiring step.
Write one pause record with a restart condition and first review date. When the gate passes, begin the next bounded discovery pass with candidate sourcing.
