One candidate appears as a referral, a job-board applicant, and a recruiter-sourced prospect because several systems wrote a source value at different stages. That is not merely an administrative delay. It changes what a candidate or hiring manager can reasonably rely on, and it leaves the recruiting team unable to distinguish a busy day from a broken control.
This guide narrows applicant source attribution to one operational question: Can an auditor reconstruct first touch, later touches, attribution rule, and any override without guessing? The answer should come from the recruiting system, the job-related standard, and the communication record;not from a retrospective explanation assembled after service fails.
Separate four meanings of source
Use the audit to repair collection and mapping. Do not rewrite historical records merely to make a dashboard total easier to explain.
Write separate definitions for first known source, latest touch, campaign, and credited source. One field cannot answer all four questions reliably.
Keep the raw event
Preserve the raw source event before applying attribution rules. A cleaned label without the original event makes disputes hard to reconstruct.
Map without manufacturing certainty
Map tracking codes, referral links, imports, recruiter entries, and career-site traffic to controlled values. Unknown should remain a valid value when evidence is absent.
Test duplicates before assigning credit. Merging records should preserve source history and should not silently replace an earlier application.
A worked operating exercise
Select ten hired records with mixed referral, campaign, import, and recruiter activity. Build the event sequence before viewing the dashboard's credited source. Compare raw capture, mapping, merge history, and manual overrides. Classify each result as confirmed, rule-based, disputed, or unknown. Use mismatches to repair future collection; preserve historical uncertainty instead of forcing every record into a clean channel total.
Inspect recruiter-created records and bulk imports separately. They fail in different ways: one may use a convenient default, while the other may flatten several source columns during mapping. Give each defect its own correction owner.
Attribution is defensible when event history survives the reporting rule. Preserve first source, timestamp, tracking code, imports, later touches, merges, rule version, and overrides. Consider a hire who clicked a campaign, later used a referral link, and was recreated after an integration delay. Reconstruct all three events before applying credit. If merging erased the first record, label the result disputed and repair future behavior instead of manufacturing a winner. Measure missing events, mapping failures, duplicate changes, overrides, and credited sources that cannot be reproduced. Publish confidence beside channel totals and audit imports separately from recruiter-created records because they fail differently. Historical uncertainty is evidence about collection quality; cleaning it away can misdirect spend and turn an arbitrary default into a precise-looking performance claim.
Assign every mapping defect to the collection point that can prevent recurrence: campaign parameters, career-site forms, integrations, bulk imports, duplicate logic, or manual entry. A reporting analyst can label the symptom but should not silently rewrite the source event. Retest with a controlled application and verify the event sequence before closing the defect. Keep the test identity excluded from production hiring metrics and remove it through the approved data process.
For this applicant source attribution exercise, record the tested condition, accepted owner, acceptance time, and precise message owed next. Preserve questions requiring policy, privacy, accommodation, labor, legal, or safety expertise and route them to the authorized specialist instead of improvising an answer.
Resolve duplicates before credit
Restrict manual overrides to named roles and require a reason. Free editing invites well-intentioned changes that favor a team or vendor.
Control manual overrides
Reconcile a sample from click or submission through ATS creation and hire. Look for dropped parameters, default values, and integration delays.
Evidence to retain and measures to challenge
For applicant source attribution, retain the trigger, controlling source, assigned owner, due point, exception, outward message, and resolution. Keep restricted facts in their approved system; the working record should contain a reference and status rather than a sensitive copy.
Review age and rework, not just throughput. For applicant source attribution, sample an ordinary case, the oldest open exception, and a recently closed case. Compare the promised update with the actual update, then inspect whether the underlying source and final system state agree. A fast closure that produces a reopened question is not a clean result. Neither is a large activity count that never reaches a qualified decision.
Do not use a small applicant source attribution sample to rank recruiters or claim a cause of turnover. Use it to find the broken handoff, unclear rule, access gap, or capacity constraint. Compare like periods and disclose changes in hiring volume, staffing, role mix, and tooling before treating movement as improvement.
Publish confidence with results
Report attribution confidence beside channel results. A precise percentage built on incomplete tracking can misdirect budget decisions.
Official boundaries and connected controls
Check current applicant source attribution requirements for the employer and jurisdiction using the first official source and the second official source, with qualified review where the facts require it. These sources establish boundaries; they do not make the employer's unsupported candidate decision.
Connect the applicant source attribution control to Candidate Source Quality Review and Ats Duplicate Candidate Merge Review. Let them share authoritative records while preserving separate owners and completion rules, so a broad dashboard state cannot conceal the unresolved promise addressed by this article.
StopHighTurnover helps employers make continuously open recruiting dependable. If weak applicant source attribution is producing avoidable delay or inconsistent follow-through, contact the team to build a practical operating system around the tools already in use.