Talent SummonerSourcing Plan for a Two-Week Hiring Sprint
Run a focused two-week sourcing sprint in a new market with daily checkpoints, scope controls and clear exit decisions.
Entering a new talent market can turn one open role into an unbounded research project. A two-week hiring sprint gives the work a calendar, a decision owner and a defined end. It does not promise a hire in 10 working days. It creates a reliable point at which to decide whether to continue, change the brief, use another route or pause.
This plan is for one role in one new market. Treat the days as working-day checkpoints, not a candidate-supply or response forecast. Keep one evidence log beside the brief so another person can understand what was searched, learned and left unknown.
Set the sprint contract before Day 1
Write a short sprint charter before searching:
- Role and outcome: the work this person must own in the first period of the role.
- Market boundary: country, city or remote location, plus working hours and language assumptions to test.
- Search scope: approved role variants, adjacent backgrounds, channels and exclusions.
- Evidence rule: what would support each must-have, what is merely a lead and what needs a human check.
- Owners: one recruiter runs the plan; one role owner approves changes and exit decisions.
- Out of scope: other roles, unapproved markets, speculative personal data and automatic rejection.
Ask the role owner to approve this charter before the first search. If a new request changes the role, market or decision owner, put it in a parking list. It may become the next sprint; it should not quietly consume this one.
The 10-day sourcing plan
| Day | Focus | Output and checkpoint |
|---|---|---|
| 1 | Lock the role and market hypothesis | Signed sprint charter, evidence questions and a list of assumptions to test. Do not search until the owner can explain what would count as relevant. |
| 2 | Map local language and routes | A small map of title variants, adjacent work, relevant public sources, referrals and communities. Mark each route as approved, untested or out of scope. |
| 3 | Run the first controlled pass | A reviewable batch with the source, date, supporting signal, unknowns and reason for inclusion. Record the search wording and boundaries so the pass can be repeated. |
| 4 | Inspect against the brief | The recruiter and role owner review strong, adjacent and surprising profiles. Separate "not shown" from "not present", then write the single most important correction. |
| 5 | Hold the first go/no-go gate | Choose one path: continue the approved search, adjust one rule, add one justified route or pause. Retire channels that produced no useful evidence, and record why. |
| 6 | Run the corrected pass | Apply only the approved change. Compare the new evidence with Day 3; do not change seniority, location and must-haves together. |
| 7 | Test coverage and duplicates | Check whether the search is finding the same people or one narrow background. Deduplicate records, preserve source traces and add only a market hypothesis that answers a named gap. |
| 8 | Prepare a contact-ready set | For each proposed candidate, record the job-related evidence, unresolved question, source date, duplicate check and human owner for contact. Do not infer interest, availability or permission from visibility. |
| 9 | Run the decision review | The role owner chooses which records move to human outreach, verification, hold or close. Capture the reason and the next owner; a ranking is not the hiring decision. |
| 10 | Close the sprint | Publish an internal decision note: continue with a stated hypothesis, extend for a stated reason, hand off to another route, pause until a dependency changes, or close the search. Archive the brief version, log and open questions. |
The Day 5 and Day 10 gates are decision points, not browsing sessions. If an approver is unavailable, mark the sprint blocked and preserve the work rather than expanding scope.
Control changes without losing learning
Use a one-change rule for every new pass. Change a title variant, adjacent background, channel or one non-essential constraint, then record the reason and expected signal. A four-column log is enough: issue, approved change, expected signal and result.
Keep three queues separate: in sprint, parked for later and closed with a reason. Another role or country belongs in a new charter. Lowering a must-have needs the role owner's explicit approval. This prevents a thin market signal from changing the job accidentally.
At each gate, ask whether the next action is still a sourcing question. If the uncertainty is employment authorisation, compensation, data handling or assessment design, assign it to the appropriate owner instead of trying to solve it through more profiles. The ICO's recruitment AI guidance, checked 2 September 2026, highlights lawful basis, transparency, data minimisation and fairness monitoring as considerations for organisations using AI in recruitment. This is general information, not legal advice; apply the rules for the actual market and organisation. NIST describes its AI Risk Management Framework as voluntary guidance, which can be another general checklist when an AI tool is part of the process.
Define the exit before the sprint starts
The sprint is complete when the owner can answer four questions without reopening the entire search:
- Which market and sourcing hypotheses were tested?
- Which evidence supports, weakens or leaves unknown each must-have?
- Which candidates have a human-owned next action, and what must be verified?
- What is the next route, pause condition or reason to close?
An empty shortlist is still a useful exit if the log shows what was tested and why the scope failed. Do not claim that the market has no talent. A promising shortlist is not a hiring outcome; outreach, consent-aware contact, interviews, assessment and selection remain human decisions.
Where Talent Summoner fits
Talent Summoner is our product for role-based sourcing. Its candidate-sourcing workflow, checked 2 September 2026, starts from a role description, searches LinkedIn, GitHub and other public professional sources across 200M+ profiles, and returns ranked candidates with must-haves, nice-to-haves and plain-English reasoning. Use those results as an input to the daily review log, not as proof that a person is suitable or available. The product does not replace verification, outreach, interviews or the hiring decision.
If the sprint starts with an existing CV pool rather than discovery, candidate ranking is the more relevant workflow. Keep its output separate from the public-source search log so the team does not confuse ranking supplied records with discovering people in a new market.
Next step
Copy the sprint charter, name the Day 5 and Day 10 approvers, and write the first three evidence questions. Then start a focused candidate sourcing search. At the end of Day 10, keep the decision note with the brief so the next sprint starts from tested assumptions rather than memory.
Can a two-week sourcing sprint guarantee a hire?
No. It is a time-box for learning and decision-making, not a promise of candidate volume, response or hiring speed. The exit may be a continuation, a handoff, a pause or a close.
How many candidates should the sprint produce?
Do not set an invented market benchmark. Set a review capacity and require each record to have a source, evidence, unknowns and a next action. A smaller reviewable set can be more useful than an unexamined list.
What should change when the first search is weak?
Change one approved variable and state what it should reveal. That may be a title variant, adjacent background or channel. Record the result before making another change.
Should a recruiter contact candidates during the sprint?
The plan prepares a contact-ready set on Day 8 and leaves the contact decision to the role owner on Day 9. Verify material facts and follow the organisation's contact and privacy process. A public profile does not prove interest or availability.
Does Talent Summoner manage the sprint?
No. Talent Summoner is our sourcing and ranking product. It can provide role-based discovery and a reasoned shortlist, while the recruiter and role owner control scope, verification, communication, interviews and selection.
