A company expanding a team, a leader announcing a new remit or a public role opening can help a recruiter decide where to look next. None of those signals proves that a person wants to move. The useful question is not “who will accept?” but “which research deserves a careful human check today?”
What is signal density in recruiting?
Signal density is a practical way to group several current, relevant and reviewable indicators around a search target. It helps a recruiter prioritise research while preserving uncertainty about the person’s intentions, availability and fit.
Examples include a recent role change, an approved public hiring announcement, a new team responsibility or a company expansion that matches the client brief. Each signal needs a source, date and relevance explanation. One noisy data point should not decide outreach.
Signals are research prompts, not consent, candidate intent or a hiring decision. Yena does not make unattended hiring decisions and should not be presented as predicting who will move.
Define a signal before collecting it
A signal earns attention only when it connects to the search question.
Start with the role and market. A company announcement about a new facility might matter for an operations search, while a generic funding headline may add little to a specialist mandate. Write down why the signal could change research priority before adding it to the record.
Use public or approved sources and note what they actually say. “Company announced expansion in Berlin” is different from “this person is hiring” and very different from “this candidate is ready to move”. The last claim needs direct evidence that a public signal cannot supply.
Freshness matters. Label the source date and the date your team reviewed it. A signal can become stale quickly, especially after an announcement, role change or hiring campaign ends.
- Name the search decision the signal supports.
- Record source, date and exact observation.
- Describe the relevance without inferring intent.
- Set a review or expiry point.
Use density to prioritise, not to automate contact
Several independent observations may justify research time, but they do not authorise a message.
A useful density view can combine recency, relevance and source quality. It should also show missing evidence. A person linked to a relevant function and a current company change may deserve a closer look; the recruiter still checks the profile, contact basis, role fit and communication context.
Avoid counting duplicated syndication as several signals. Ten sites repeating one press release are not ten independent observations. Group the source family and preserve the primary reference where possible.
A low-density profile should not automatically disappear. Public visibility varies by sector, privacy preference and language. Treat density as a queue-management aid, not a measure of human value.
- Independent source or clear source family.
- Current enough for this search.
- Relevant to the role or market.
- Uncertainty visible to the reviewer.
Verify before outreach
The final step between a signal and a message is a human evidence check.
Check that the person is the same person, that the role or organisation is current and that the signal supports the proposed context. A name match is not identity proof. A public profile is not permission to collect every detail available about someone.
Use a clear professional introduction and explain why you are contacting the person. Keep the message relevant and proportionate. If the person declines or asks not to be contacted, record the preference and respect it according to the process that applies.
GDPR principles such as transparency, accuracy and data minimisation remain relevant when a recruiting team uses public information. Signal tooling does not remove those responsibilities.
A fresh signal can tell you where to look. Only a human can decide whether a respectful, relevant conversation makes sense.
Separate company signals from candidate signals
Business activity can inform market research without becoming a statement about an individual.
An organisation opening a new office may create a useful target-company hypothesis. It does not prove that every employee is hiring, leaving or interested in the opportunity. Keep company-level evidence and person-level evidence in separate fields.
For a retained search, the client may care about a competitor’s capability or a scarce skill cluster rather than a single public announcement. Signal density can help map the market, but the recruiter must assess whether approaching a person is appropriate under the assignment and confidentiality expectations.
Make the distinction visible in client reporting. Say “research priority based on public company activity” rather than “candidate likely to move”. Precise language protects trust and makes the recommendation easier to challenge.
Handle uncertainty as part of the result
A signal workflow is stronger when it shows what is unknown.
Record whether the source is direct, secondary, dated, incomplete or contradicted. If a role announcement is public but the person’s current remit is unclear, leave the question open. Do not fill gaps with a confident generated summary.
Ask the recruiter to review high-priority signals before they appear in a client-facing shortlist. The review can downgrade a signal, add context or remove it. A system that allows correction is more useful than one that presents a polished but untraceable ranking.
Keep access and retention proportionate. Not every research note belongs in a permanent candidate record. Decide what the team needs for the assignment and what should expire when the work ends.
- Mark the evidence level.
- Write the unresolved question.
- Assign a human reviewer.
- Set a retention or expiry decision.
Build a signal-led research rhythm
Signals become useful when the team knows how they enter and leave the work queue.
Set a short review cadence that fits the market. A recruiter might review new signals at the start of a sourcing block, then work through a small prioritised queue. The goal is not to watch every public change; it is to spend attention where the current mandate makes it valuable.
Compare the signal queue with recruiter outcomes. Did the research produce a relevant conversation, a useful market insight or simply more noise? Use that reflection to adjust source quality and definitions. Do not convert a handful of conversations into a universal performance claim.
A 10-day free trial is enough time to test a bounded workflow with one live search. Agree what will be reviewed, who owns the human checks and how candidates can correct or challenge information.
Signal review record
This table keeps prioritisation separate from candidate intent and hiring decisions.
| Field | Example question | Reviewer action |
|---|---|---|
| Search relevance | Why could this matter to the current mandate? | Keep, downgrade or remove |
| Source and date | Where did the observation come from, and when? | Check primary source and freshness |
| Identity | Is this the same person or organisation? | Verify before using |
| Uncertainty | What does the signal not establish? | Write the open question |
| Contact basis | Is an appropriate professional approach permitted? | Follow the applicable process |
| Expiry | When should this observation stop guiding research? | Review or delete as required |
Limits of live hiring signals
Public activity is incomplete and can be misunderstood. It cannot establish candidate intent, availability, suitability or consent. Signal density is a research-priority aid, not a predictive score.
Yena does not make unattended hiring decisions. Recruiters must review sources, check accuracy, respect contact preferences and make recommendations through their own accountable process.
Hiring-signal questions
Use these answers to keep signal-led sourcing grounded and respectful.
Does a hiring signal mean someone is open to work?
No. It means a recruiter has a reason to research the market or profile. Only the person can express their interest, and even that can change.
How many signals should make a profile high priority?
There is no universal threshold. Use relevance, freshness, source quality and the assignment context. A count without those explanations creates false precision.
Can we scrape every public profile connected to a signal?
No assumption like that is safe. Consider purpose, transparency, accuracy, minimisation, lawful basis and the applicable platform or source terms before collecting or using information.
What should we tell a client about the ranking?
Explain that it prioritises research based on reviewable observations and uncertainty. Do not describe it as a prediction that a person will move or as an automated hiring decision.
Official sources and scope
These sources support the human-oversight, data-protection and multilingual principles in this guide. They do not certify a particular signal workflow.
- European Commission: AI Act rules for high-risk employment systems and human oversight
- EUR-Lex: GDPR principles for transparency, accuracy and data minimisation
- European Commission: ESCO skills and occupations in 28 languages
Turn research signals into a careful workflow
Explore Yena candidate sourcing · See the recruiting CRM workflow · Review Yena pricing · Talk through your search process · Compare established talent-sourcing strategies
Test signal-led sourcing with your team
Start a 10-day free trial and review one real search with fresh evidence, visible uncertainty and a human approval step before outreach.
Start your 10-day free trial