Can You Trace Where Every Candidate in an Offshore Sourcing Pipeline Came From?

Research question

Candidate provenance is the record of how a person entered a sourcing pipeline, which approved search produced the lead, what information was collected, and what happened before the profile reached a hiring decision. Can a buyer reconstruct that path for every candidate handled by an offshore sourcing team?

A name in a spreadsheet is not enough. It may have come from a public professional profile, an employee referral, a prior application, an agency submission, an event list, or an unapproved data vendor. Those routes carry different promises, duplicate risks, privacy questions, and commercial terms. Without provenance, the buyer cannot reliably honor an opt-out, explain a contact, resolve candidate ownership, or audit whether the sourcer followed the brief.

Define provenance at the point of discovery

The first record should identify the approved requisition or talent-pool purpose, source channel, source URL or stable reference where appropriate, discovery date, search version, sourcer, and status. It should distinguish information observed in the approved source from information inferred by the sourcer. An inferred skill, location, or availability should never be stored as a fact.

The search version matters because criteria change. If a manager widens the location, adds a required certification, or removes an industry preference, later candidates should not be judged against an invisible earlier rule. Preserve the approved criteria and effective time. Do not rewrite old records so they appear to have been sourced under the latest brief.

Capture only what the purpose requires. A sourcing record normally needs enough information to assess a defined occupational criterion and make an approved contact. Copying a person's full profile, photograph, unrelated posts, family information, or every listed connection increases risk without improving the handoff.

Separate discovery, contact, and application

These stages are often collapsed into one status, but they have different evidence:

A person who appears in a search result has not applied. A reply asking not to be contacted is not a cold lead for another campaign. A referral still needs an approved candidate experience and privacy process. Keeping these states distinct prevents reporting from inflating the active pipeline.

Reconcile duplicates before outreach

Duplicate profiles are common because people use different emails, change names, appear through several sources, or previously applied. The deduplication rule should use the minimum attributes needed and route uncertain matches for review. Do not merge records solely because names resemble each other.

The authoritative system should preserve source history rather than replacing the first source with the most recent one. Commercial ownership disputes may depend on agency or referral terms. Privacy requests may need every linked record. At the same time, access to that history should be limited. A sourcer does not automatically need confidential notes from an earlier application.

Before sending outreach, check the buyer's approved suppression records, prior contact status, application state, and channel rules. The check should return a usable decision without exposing why someone is suppressed when that detail is sensitive. Record the check time and rule version, not a copied suppression list.

Make the sourcing brief testable

An effective brief distinguishes required evidence, useful indicators, prohibited assumptions, and unresolved questions. For example, a recruitment coordinator search may require experience maintaining candidate records and coordinating calendars. A profile that says "talent acquisition" does not prove either task. The sourcer can record the visible evidence and flag the gap for screening.

Avoid proxy criteria that are not tied to the work. School prestige, employment gaps, profile photography, name, age signals, and native-language assumptions can distort the pool and create legal risk. The hiring owner approves job-related criteria. The offshore sourcer applies them and reports where the available record is incomplete.

Build a small calibration sample before scaling. Give two sourcers the same approved search and compare which profiles they include, exclude, or flag. Review the evidence attached to each decision. Disagreement may reveal an ambiguous criterion, a platform filter interpreted differently, or a hidden preference from the manager. Fix the brief before adding volume.

Control outreach without pretending one law fits every audience

Outreach rules depend on the buyer, candidate location, channel, platform terms, and applicable privacy and communications law. The buyer should approve the lawful basis or authority, notice, message, sender identity, frequency, opt-out mechanism, and suppression process. The sourcing provider should not invent these rules.

The Philippines Data Privacy Act and its implementing rules require legitimate, declared purposes and proportional processing. National Privacy Commission guidance on legitimate interests describes a balancing analysis rather than a blank permission. Other jurisdictions may use different terms and tests. A buyer sourcing internationally should obtain advice for the actual campaign.

Operationally, the sourcer needs a clear answer for each approved audience. If the policy is silent, the record stays in a research state and outreach stops. This boundary is healthier than allowing individual sourcers to make legal judgments from a generic template.

Messages should identify the sender and purpose honestly. Track the approved template version while preserving the actual sent content where required. If personalization uses a profile fact, it should be job relevant and accurate. A fabricated compliment or implied prior relationship is poor candidate experience and weak evidence.

Handoff to screening

The sourcing handoff should contain the requisition, current stage, source history, job-related evidence, contact status, candidate-stated preferences relevant to the process, unresolved questions, and the authoritative record link. It should not include speculative personality judgments or copied personal material unrelated to the role.

The screening owner confirms that the candidate is in the correct workflow and that required notices or application steps are complete. The sourcer remains responsible for correcting provenance errors found during handoff. The hiring manager owns any change to criteria or selection status.

For talent sourcing support, buyers can make this handoff the acceptance unit. Sample ten records from different sources and ask whether another authorized reviewer can reconstruct the search, evidence, contact, response, and next owner without consulting private messages.

Metrics that expose process quality

Raw profiles found and messages sent mostly measure activity. Better controls include the share of records with a complete source path, duplicate rate before outreach, contacts blocked by suppression, profiles returned for unsupported criteria, response-status aging, and handoffs missing an authoritative link.

Interpret conversion rates carefully. Channels serve different roles, and small cohorts fluctuate. A high response rate does not excuse missing authority or deceptive messaging. A low rate may reflect the role, timing, employer proposition, or search design rather than sourcer effort. Keep facts and hypotheses separate in the report.

Review errors by cause. If multiple records lack search versions, the workflow may not make that field easy to capture. If sourcers repeatedly infer required skills from titles, the brief may need examples. Correct the system before treating every failure as an individual performance problem.

Retention and removal

Provenance does not justify permanent storage. Tie each record to the buyer's approved applicant or prospect retention schedule. When the purpose ends, delete or de-identify data as required across exports, messages, integrations, and reporting copies. Preserve suppression information only to the extent and duration approved for honoring contact choices.

If the source removes or corrects information, do not treat an old copied profile as timeless truth. Candidate-provided corrections should flow to the authoritative record under the buyer's procedure. Reports should use stable identifiers and aggregate results without republishing unnecessary personal details.

Method and limitations

This report reviewed privacy, fair-selection, and recruiting guidance, then applied it to the operational chain from sourcing search to screening handoff. It does not decide the lawful basis for a campaign, interpret platform contracts, or prescribe a universal candidate notice.

Provenance improves traceability but does not make a source accurate or a criterion fair. Buyers still need job analysis, approved selection rules, privacy review, and qualified legal advice for the places where they recruit.

Conclusion

A sourcing pipeline is auditable when each candidate can be traced to an approved purpose, search version, source, contact rule, status, and next owner. That record lets a buyer correct mistakes and respect candidate choices. It also gives the offshore sourcing team a fairer standard than a volume target detached from process quality.

Sources

Sources checked October 5, 2026.

1. Republic Act No. 10173, Data Privacy Act of 2012, Official Gazette
2. Implementing Rules and Regulations of the Data Privacy Act, National Privacy Commission
3. Advisory Opinion No. 2020-006 on legitimate interests, National Privacy Commission
4. Best Practices of Private Sector Employers, U.S. Equal Employment Opportunity Commission
5. Employment Tests and Selection Procedures, U.S. Equal Employment Opportunity Commission
6. Recruitment and selection factsheet, Chartered Institute of Personnel and Development
7. NIST Privacy Framework
8. Fair Information Practice Principles, U.S. Federal Trade Commission
9. OECD Guidelines on the Protection of Privacy and Transborder Flows of Personal Data
10. Principles for the Validation and Use of Personnel Selection Procedures, Society for Industrial and Organizational Psychology

FAQ

Is a public profile free to copy into any recruiting database?

Public visibility does not remove the need for an approved purpose, proportional collection, applicable notice, secure handling, and a retention rule.

Who owns candidate provenance?

The buyer owns the recruiting policy and systems. The sourcing team records the path accurately, while privacy, legal, and hiring owners decide the governing rules.