Talent SummonerBoolean Search to Outreach Transition Checklist
Move from a Boolean or discovery query to human-approved outreach by logging queries, checking evidence freshness, assigning owners and stopping safely.
A Boolean or discovery query can surface a promising profile, but it does not make that person ready for contact. The transition from search to outreach needs a small, reviewable handoff: preserve what was searched, check what the sources actually support, confirm the approved contact basis and give a named person authority to decide.
This is an implementation playbook for a sourcer at the plan stage. It ends at human approval for a proposed contact; it is not an outreach sequence, message template or response-rate forecast. As a supporting resource, it can later be merged into a canonical outreach hub alongside separate guidance on message quality, timing and replies.
Set the handoff boundary
Start with the approved role brief, not with a list of names. Record the role version, outcome, genuine must-haves, acceptable adjacent experience, location or working boundaries and the evidence question for each must-have. A title is a search clue, not a requirement by itself.
Then record the search method. For a Boolean search, preserve the exact string, platform or source, filters, date and owner. For a brief-led discovery pass, preserve the role input, source set, date and any changed terms or weighting. Syntax is platform-specific; LinkedIn's Boolean guidance, for example, documents its own operators and limitations. Do not treat one platform's syntax as a universal rule.
An illustrative query might be ("platform engineer" OR "site reliability") AND (Go OR Python). It is an example of a hypothesis, not a market benchmark or a complete role definition. Log why it was used and what it may miss.
Run the transition checklist
Use one record per search run and one evidence note per proposed contact. Every gate has a human owner and a stop condition.
| Gate | Record and check | Stop condition |
|---|---|---|
| Role version, outcomes, must-haves, boundaries, evidence questions and role owner | The role or contact boundary is still being negotiated |
| Exact Boolean string or discovery input, source, filters, run date, result notes and query owner | The search cannot be reproduced, or a changed query has no explanation |
| URL, retrieval date, job-related statement, visible update date and source limitation | The source is inaccessible, conflicting, materially stale or too thin to interpret |
| Direct, adjacent, unknown or contradicted signals; duplicate check; verification question | Relevance depends on a guessed, sensitive or identity-uncertain fact |
| Approved channel, documented contact basis (including consent where required), prior contact, suppression or opt-out status and role status | The basis, channel, prior history or suppression state is unresolved |
| Sender, role approver, reply owner, approved role/message version, decision date and stop condition | No named person can approve, answer replies or close the action |
The stop condition is part of the output, not a warning added later. A useful record can end in hold, verify, do not contact or approved for one human decision. It does not have to end in a message.
Review evidence before interpreting fit
Keep three layers separate. First write what the source says, using a short quotation or faithful paraphrase and its URL. Next write the narrow job-related interpretation. Finally write what must be verified directly or from an approved source. For example:
- Observed: a dated project description says the person maintained deployment tooling.
- Interpretation: this may relate to the role's reliability outcome.
- Verify: ownership, current scope, team context and interest in the role.
Source freshness is not a universal number of days. Set a review window that fits the role and source, record the date checked and re-open the note when the role, profile or contact plan changes. A current-looking title can still be incomplete; an old project can still be relevant historical evidence. Do not convert missing or stale information into a rejection. Mark it unknown and assign the next check.
Public professional visibility is a discovery signal, not proof of identity, current availability, interest, consent or permission to use every channel. Before contact, apply the organisation's approved policy for the contact basis, document the channel decision, check prior interactions and honour suppression or do-not-contact instructions. The Information Commissioner's Office guidance on AI-assisted recruitment, published 6 November 2024, highlights lawful basis, documented responsibilities, transparency, fairness and data minimisation. This article is general information, not legal advice; use the rules that apply to the employing organisation and candidate.
Prepare a human-owned record
Paste this into the role or recruiting record and complete it before asking for outreach approval:
Role and brief version:
Role owner:
Search method and exact query or discovery input:
Source or platform and filters:
Run date and query owner:
Candidate source URL and retrieval date:
Observed job-related evidence:
Source limitation and freshness review point:
Direct, adjacent, unknown or contradicted fields:
Verification question and verification owner:
Duplicate and prior-contact check:
Approved channel and contact basis (consent or other approved basis, where required):
Suppression or opt-out status:
Sender and reply owner:
Role/message version approved for review:
Stop condition:
Decision: hold, verify, do not contact or approve
Decision owner and date:The verification owner should be able to answer the open question without silently changing the role. If the answer would change a must-have, working boundary, compensation statement or contact basis, return to the role owner and create a new version. Keep the earlier record so another reviewer can understand why the decision changed.
Where Talent Summoner fits
Talent Summoner is our product for role-based candidate sourcing and ranking. Its candidate-sourcing workflow, checked 4 September 2026, starts from a role brief and returns ranked discovery results from public professional sources with reasoning against requirements. In this playbook, treat that output as discovery input; do not assume it runs the team's Boolean query or records the approved contact basis and handoff.
If you already have CVs, the separate candidate-ranking tool, checked 4 September 2026, compares supplied material with a job description and produces a report for human review. Neither workflow verifies every public claim or establishes contact permission; keep the query, evidence, contact basis, owners and stop condition in your team's record, with outreach actions assigned under your approved process.
FAQ
What is the transition from Boolean search to outreach?
It is the review step between finding a possible candidate and requesting human-approved contact. The team records the query, source evidence, freshness, contact basis, owner and stop condition.
Does a public profile give permission to contact someone?
No. Public visibility may explain why a person appeared relevant, but it does not prove interest, availability, consent or permission to change channels. Apply the organisation's approved contact policy and honour opt-outs.
How fresh should a candidate source be?
There is no universal threshold. Set a role- and source-appropriate review point, record when the source was checked and re-check it when material context changes. Unknown is safer than an unsupported assumption.
Does this checklist ask Talent Summoner to run Boolean searches or automated outreach?
No. The handoff remains team-owned: your team records the Boolean or discovery query, verifies evidence, confirms any required consent or other contact basis, approves the channel and message, handles replies and suppression, and makes hiring decisions. Re-check current product scope before assigning any of these steps to a tool.
When should a sourcer stop the transition?
Stop when the role, evidence, identity, contact basis, channel, suppression state or owner is unresolved. Hold or escalate the record rather than widening the query or switching channels to force progress.
Complete the record for one search run, assign the verification owner and document the stop condition. When the role owner approves the next action, start a focused candidate-sourcing search; if the candidates are already in your files, use candidate ranking for a separate evidence review.
