# Between Candidate Sourcing and Response By Lindsey Light (@lindseylight) · Published 2026-09-21 Canonical: https://voce.com/@lindseylight/between-candidate-sourcing-and-response-xm0wmj --- A role reopens on Monday morning and the search starts from a blank page. Somewhere in last year’s outreach are people who matched the work. A few never replied. Others said the timing was wrong. One may have reached a late interview stage before the role changed or closed. Nobody has spoken to them since. So the team starts over, reaching out cold to people it has already spent time finding, researching and, in some cases, getting to know. This is usually described as a sourcing problem. Often, it is a continuity problem in the stretch between candidate sourcing and response. ## Being stored is not the same as being engaged Most talent teams have a clear process for an active requisition. The role opens, the team confirms the profile, searches the market and moves interested people into the recruiting process. The process becomes less clear when someone does not respond or says the timing is wrong. They may remain in the ATS or CRM. A recruiter may leave a note to follow up later. But the system remembering that a person exists does not create the next relevant interaction. Many strong candidates are not actively looking when an organization first finds them. A single outreach attempt tests whether the message and the moment aligned on one day. It does not fully test whether that person could become a strong candidate later. When the process ends after that attempt, sourcing has done its job. The relationship has not been given time to develop. ## Reach and follow-through require different fixes Talent pipeline gaps usually begin in one of two places. The first is reach. The organization is not consistently identifying and engaging people who match the work and are unlikely to apply on their own. The second is follow-through. The team found relevant people, but no repeatable process keeps the conversation alive until the timing changes. Both can produce a role that stays open too long. They should not produce the same response. If the problem is reach, the team may need a clearer market definition, better research or a stronger reason for someone to pay attention. If the problem is follow-through, adding more names creates a larger pool of people who receive one message and disappear from view. Ask four questions: - Are the right people failing to see the opportunity, or seeing it and not responding? - What happens after the initial outreach ends? - Who owns someone who says “not right now”? - When a recurring role opens again, does the team begin with known people or rebuild the market from zero? The answers reveal whether the team needs more sourcing capacity or a better way to carry relationships forward. ## A talent pipeline should outlive one requisition Some roles reopen regularly. Some capabilities remain difficult to find. Some talent markets matter even when no position is currently approved. If the team rebuilds those audiences each time, it pays the sourcing cost repeatedly and reaches people only when the employer urgently needs something from them. A stronger model separates the relationship from the requisition. That does not mean marketing jobs that do not exist or keeping people artificially “warm.” It means staying honest about recurring talent needs and offering contact that remains useful outside a specific opening. The standard should be simple: if the message would not be worth receiving without the employer’s immediate hiring need, it probably is not useful follow-through. ## What the system should carry A managed talent pipeline system gives this work continuity without asking recruiters to maintain every interaction manually. The team defines the roles, markets and legitimate job-related criteria. People approve who belongs in the audience. Outreach runs in the employer’s name and voice. Follow-up continues over an appropriate period, with a new reason to respond rather than the same message repeated. When someone expresses interest, the conversation moves into the organization’s existing recruiting process. The system sits beside the ATS, not in place of it. One manages people actively in process. The other maintains relevant contact with people who have not entered it yet. AI can support research, drafting, timing and coordination. It should not screen, rank or decide who is suitable for a role. People retain evaluation and every employment decision. Protected characteristics should never inform targeting or outreach. A Human in the Loop governs each handoff that requires judgment. LL Group runs this as SDRCloud, a managed talent pipeline system. AI carries repeatable work between moments of human judgment. It does not replace them. Start with one role that always seems to open cold. Look at the last search. Who matched? Who never replied? Who said the timing was wrong? Who reached a meaningful stage but did not become the hire? Which of them has heard from the organization since? If the next step is simply “search again,” the organization may not only have a sourcing challenge. It may have a continuity gap. Which is harder for your team today: reaching the right people, or staying relevant after you find them? If you would like to map it together, choose a time here: [https://calendar.google.com/calendar/appointments/schedules/AcZssZ2iLo42jxC\_QaCa5r\_wBX6isKN\_ADIZ7L\_UKU-c\_PE8oK0cp9fov0koICECQX600WMtYG\_t2R\_L](https://calendar.google.com/calendar/appointments/schedules/AcZssZ2iLo42jxC_QaCa5r_wBX6isKN_ADIZ7L_UKU-c_PE8oK0cp9fov0koICECQX600WMtYG_t2R_L)