Passive sourcing becomes strategic when it verifies evidence of work before outreach, and keeps domain context attached to the candidate from first signal to final submission.
Active markets are a filtered market
A job board shows you the people currently looking. That is a real population, and it sometimes contains exactly who you need. But it is a filtered slice, and the filter has nothing to do with capability.
For scarce production skills — the ones where an environment punishes weakness immediately — the relevant population is largely not in that slice.
Evidence before outreach, not after
The discipline that makes passive sourcing work is looking at the evidence first. Public technical signals, project history, the shape of someone's actual contributions, the domains they have operated in — assembled before the first message, not requested afterwards.
That ordering matters for the candidate too. A passive engineer with no active search has little patience for a generic approach about a role that does not fit, and rightly so.
Approach someone about the work they actually do, or do not approach them.
Keeping context attached
Signal degrades as it travels. A candidate found for a specific reason often arrives at the client stripped of that reason, reduced to a resume like any other — and the insight that justified the outreach is lost.
Prism keeps the domain context attached through SME review and into the submission, so the client sees not just who the candidate is but why this person surfaced for this environment.
What to ask a vendor about sourcing
Ask where the last three placements came from, and what the vendor knew about each person before making contact. A partner working the passive market can answer specifically. A partner working the active market will answer in tooling.