Candidate Sourcing for Recruitment & Staffing

Candidate sourcing is the research and identification stage that turns an approved role brief into a documented pool of potential candidates. It commonly includes search design, channel research, profile identification, source tracking, role-fit notes, duplicate checks and a recruiter-ready handoff. Formal screening, interviewing and hiring decisions remain separate unless they are explicitly added to scope.

A focused engagement can cover role-intake clarification, search criteria, Boolean and filter logic, multi-source research, candidate identification, approved profile enrichment, source documentation, duplicate checks, exception notes, a recruiter-ready longlist and a sourcing summary. The final scope is confirmed against role complexity, markets, tools and client access rules.

Useful inputs include the approved job description, must-have and preferred criteria, location or work-model rules, seniority, target or excluded companies where appropriate, compensation guidance where it affects search, work-authorisation constraints where lawful and relevant, existing candidate lists for duplicate checks, and a named recruiter or hiring stakeholder for feedback.

Yes. Multi-role sourcing can be scoped as a recurring pipeline or managed sourcing model. Pricing and timing depend on the number of roles, overlap between talent pools, role seniority, market scarcity, geographies, reporting cadence and the amount of recruiter feedback required.

The service can include a light evidence check against the agreed sourcing criteria so the longlist is usable, but formal resume screening, rejection decisions, interview assessment and hiring recommendations are distinct recruitment activities. Those should be separately scoped when required.

Outreach is not assumed in the standard sourcing scope. If you want message preparation, contact sequencing, response tracking or recruiter outreach support, that should be confirmed as an additional or custom workstream because it changes platform permissions, data handling, workload and quality checks.

Channel choice depends on the role and on the tools your organisation is licensed and authorised to use. Relevant environments may include professional networks, job boards, ATS or recruitment CRM databases, referral records, niche communities, technical portfolios and client-approved research sources. Named platform access is never assumed.

Potentially, when the agreed scope requires it and your organisation can provide appropriate access. The preferred approach is client-controlled, role-based access with only the permissions needed for sourcing, status updates or handoff. Platform configuration and integration work may require separate scope.

The handoff can include the candidate name or profile identifier, source reference, current role and employer as available, location, evidence against agreed criteria, recruiter notes, duplicate status, research date and any approved contact fields. The exact columns follow the client-approved format and data-handling rules.

Duplicate checks can be performed against client-provided lists or approved system records before handoff. When information conflicts or important fields are unavailable, the safer approach is to flag the exception rather than infer or manufacture missing data.

Candidate sourcing can involve personal information, so access, source use, storage, retention and sharing should follow the client's approved privacy and recruitment policies. Rudrriv can work within agreed handling instructions, but the client remains responsible for its legal basis, notices, hiring decisions and regulatory obligations.

A focused single-role sourcing sprint starts from USD 300. Broader engagements are quoted after review because cost changes with role scarcity, number of roles, geographies, channel access, outreach or screening requirements, reporting cadence, data handling requirements and ongoing replenishment needs.

The delivery schedule is confirmed after role intake. Timing depends on the clarity of the brief, seniority and scarcity of the role, geography, available sourcing channels, access readiness, required profile fields, duplicate-check volume and how quickly recruiter feedback is returned.

The entry sprint is best for one clearly defined role with an available job brief, a reachable talent market, a responsible reviewer and no complex outreach, multi-country compliance review or heavy ATS administration. Niche executive searches, confidential mapping, multiple roles or recurring demand are better treated as custom scope.

Unless separately agreed, standard sourcing does not include employment-law advice, background checks, reference checks, payroll, offer negotiation, interview decisions, guaranteed hires, executive-search representation, paid platform licences, job advertising spend or full recruitment process outsourcing.

Rudrriv reviews the role context, sourcing objective, required outputs, available tools, data-handling expectations and timing. Clarification may be requested before the scope, price and delivery approach are confirmed. Work proceeds after the agreed engagement terms and inputs are in place.