The evidence review checklist for modern sourcing.
Before a source profile becomes a candidate conversation, separate what is known, what is public signal, what is assumed, and what still needs verification.
1. Public facts
Facts are things directly shown by a public source or a user-imported record you are authorized to use. Examples: a public repo URL, a publication title, a package maintainer page, a listed NPI record, or a profile headline.
2. Public signals
Signals are useful but not final. A clearance phrase in a public bio, an open-to-work phrase, a GitHub project, a conference talk, or a package contribution can point you toward fit. They do not verify identity, status, availability, or intent.
3. Assumptions
Assumptions are the quiet source of bad submissions. Label them. If two profiles have the same name, that is not a confirmed match. If a repo uses Kubernetes, that does not prove production ownership. If a person lists a company, that does not prove current employment.
4. Missing data
- Current role and employer.
- Location and work authorization.
- Clearance or license status, when relevant.
- Depth of hands-on experience.
- Contact path and outreach permission norms.
5. Verify-next checklist
Every result should end with the next verification step. That may be a second public source, hiring manager clarification, recruiter review, direct candidate confirmation, or a decision to stop pursuing the lead.
SourcingOS workflow
Candidate Search and Candidate 360 are designed around this checklist. Confidence means source relevance, not person verification.