Building a Referral-Plus-Sourcing Workflow

An employee recommends someone while the hiring manager searches public profiles for the same role. Without a shared workflow, the referral may skip review, the researcher may contact the same person, and nobody knows which record is current.

A referral-plus-sourcing workflow joins routes at the planning stage. It sets one role brief, record convention, handoff rule and review cadence before anyone compares people. The goal is equal, traceable review, not a promise of more names or a hiring outcome.

Agree the operating contract

Before inviting referrals or opening an outbound search, keep these decisions on one page:

• Role version: outcome, must-haves, preferences and genuine operating boundaries.
• Review standard: job-related evidence, unknowns and what a person must check.
• Route owners: the referral owner, outbound owner and hiring manager for the next decision.
• Record location: the approved system for source notes, contact history, corrections and stop instructions.
• Cadence: when owners reconcile new records, duplicates, blocked handoffs and brief changes.

Make the route a label, not a ranking. A referral is context, not an exception; an outbound profile is a lead, not proof of interest, availability or ability. Use the same review language and record approval for material changes.

Use one record with traceable handoffs

Create a shared record structure before the first name arrives. A minimum record can contain:

A handoff is a package, not a name. The referral owner records introduction context and requests an opt-in introduction; a passed name or number is not, by itself, permission to contact or retain. The outbound owner records source, date, reason and unresolved questions. The hiring manager receives both with a proposed action. Return a handoff missing its source, owner or reason.

Resolve duplicates before contact or review

Duplicates are normal when two routes find the same person. They become risky when copies have different owners, histories or dispositions. Use this merge process:

1. Search existing records before creating one, using permitted identity and professional context rather than sensitive attributes.
2. Mark the match confirmed, probable or uncertain. Similar names alone are not enough.
3. Keep one canonical record and link each route, date and source trace to it; do not delete provenance.
4. Assign one next-action owner. Hold conflicting statuses or contact instructions until that owner resolves the history.

Never let a referral override an opt-out or do-not-contact instruction. If identity needs guesswork, keep records separate and ask the responsible human owner. A duplicate decision controls records; it is not a judgement about the candidate.

Apply one evidence standard to both routes

Use an evidence note that separates source wording from interpretation:

Role version and criterion under review:
Route and source / capture date:
Job-related evidence and context:
What this supports:
Unknown or conflicting detail:
Verification question:
Owner / next action / review date:

For a referral, the referrer's description is conversation context, not independent proof. An outbound profile is selective and may be dated. Do not treat an omitted detail as absent or a familiar route as extra credit; ask the same focused question where the fact matters.

The UK's Information Commissioner's Office (ICO) says organisations considering AI recruitment tools should identify a lawful basis, document responsibilities, monitor fairness and accuracy, explain how information is used and limit collection to what is necessary. Its recruitment-AI considerations, published 6 November 2024, are general information rather than legal advice. Apply the rules for the organisation, candidates and location. NIST describes its AI Risk Management Framework as voluntary guidance for managing AI risks, not a hiring standard.

Set a review cadence that keeps ownership current

Choose a recurring review that matches the role and capacity; weekly is one possible starting point. Focus on exceptions and decisions:

1. Reconcile new referrals and outbound records against the shared role version.
2. Clear duplicates and confirm one owner for every live record.
3. Review missing evidence or conflicting contact history.
4. Decide progress, hold or close, and approve or defer brief changes while preserving the earlier version.

Trigger an extra review when a candidate asks not to be contacted, an owner or material boundary changes, or a record is wrong. Keep the cadence about decisions, not target referral or profile counts.

Where Talent Summoner fits

Talent Summoner is our product for role-based candidate discovery. 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 results with must-haves, nice-to-haves and plain-English reasoning. Use it as an outbound input, then apply your record controls. It does not merge referrals, assign ownership, resolve contact history, manage an application pipeline, send outreach or make the hiring decision.

When referrals include CVs, the separate candidate-ranking workflow supports up to 50 PDF, DOCX, MD or TXT resumes and shareable reports. Keep that output distinct from public-source discovery and check evidence, duplicates and next actions yourself. Neither workflow verifies a referral, establishes interest or replaces human contact and assessment.

Next step

Create the shared fields, name both route owners and agree who resolves duplicates and stop instructions. Test one referral and one outbound handoff. Then start a focused candidate-sourcing search under the same role version.