A recruitment market mapping report is a decision-ready account of a role's external talent market: what was searched, which companies and titles define the pool, how many people appear viable, what evidence supports that view, how reachable they are, what risks remain, and what the hiring team should do next.
This is a reusable report template, not another definition of talent mapping. Use it after or during the research process to make assumptions visible and enable a hiring leader to choose among changing the brief, widening the market, beginning direct sourcing, developing internal talent or using a specialist partner. For discovery techniques, use the existing step-by-step talent mapping guide.
The report should remain useful even when its conclusion is "the requested profile is not supported by current evidence". A polished list that hides uncertainty is less valuable than a short report that shows where the market estimate could be wrong.
Set the Report Header and Decision
Begin with control information: report owner, commissioning leader, role or capability, geography, source cut-off date, version, confidentiality level and next review date. Then state the decision required in one sentence. Examples include: approve a six-week sourcing pilot; relax the sector constraint; choose between London hybrid and UK remote; or fund an external search partner.
Add a three-line executive answer: the estimated viable pool range, the largest constraint, and the recommended next action. Keep claims proportional to the research. "We found 84 profiles" is an observed result. "The market contains 84 people" is almost certainly not.
Link the report to a workforce or hiring scenario. The CIPD workforce planning factsheet emphasises future demand, internal supply, external context and iterative action. A market map is one input to that process, not a decision to recruit by itself.
Reusable Recruitment Market Mapping Report Schema
Copy the following structure into the team's standard document or reporting system. Every section must contain evidence, an assumption label, or an explicit "not assessed". Empty cells should never be mistaken for favourable evidence.
| Report section | What to capture | Required output |
|---|---|---|
| 1. Role definition | Business outcomes, essential capabilities, level, location, compensation, right-to-work and agreed adjacencies | Calibrated search brief plus exclusions |
| 2. Target companies | Core, adjacent and excluded organisations with a reason for each segment | Company universe by priority tier |
| 3. Title synonyms | Exact, adjacent, seniority and regional title patterns; misleading titles to exclude | Search vocabulary with evidence |
| 4. Pool size | Raw discovered, deduplicated, reviewed, viable and reachable ranges by segment | Calculation, range and confidence |
| 5. Evidence | Sources, cut-off dates, sample method, capability evidence and unresolved gaps | Evidence register and quality rating |
| 6. Reachability | Permitted contact routes, prior relationship, data freshness, location and likely proposition constraints | Reachability bands, not assumed interest |
| 7. Risks | Market, brief, compensation, timing, source coverage, privacy, fairness and delivery risks | Risk owner, trigger and mitigation |
| 8. Next actions | Decision, owner, deadline, test cohort, stop rule and refresh date | Sequenced action plan |
Section 1: Define the Role as Evidence
Replace a generic job description with four to six outcomes and the capabilities required to deliver them. For every criterion, specify acceptable evidence. "Commercial" may mean owning a revenue target, influencing product pricing or negotiating enterprise contracts; without that definition, researchers and hiring managers will count different people.
Separate legal or operational constraints from preferences. Record location attendance, working pattern, compensation range, reporting scope, language needs and right-to-work position as currently known. Name plausible adjacencies and explicit exclusions. If the hiring team cannot agree, report the disagreement rather than averaging it away.
A skills vocabulary can reduce title dependence. Skills England's UK Standard Skills Classification links skills, knowledge, tasks and occupations and is a useful external reference when internal job families are inconsistent.
Sections 2 and 3: Map Companies and Title Synonyms
Divide organisations into core, adjacent and exploratory tiers. Core companies use comparable technology, regulation, customer model or operating scale. Adjacent companies offer transferable conditions but require an explicit hypothesis. Exploratory companies test a less certain route. Explain why each tier belongs; a famous competitor list without role logic is not a market map.
Build title synonyms from observed profiles, organisation charts, job adverts, professional standards and conversations with job experts. Include titles one level above and below only when scope evidence supports it. Record misleading synonyms. A "product lead" may be an individual contributor in one company and a department head in another.
Present a cross-tab showing company tier by title family and location. Gaps can reveal that a title is uncommon in the intended segment or that the work sits in another function. That insight should trigger a brief discussion before more names are collected.
Section 4: Estimate Pool Size Transparently
Use a funnel rather than one headline number. Start with raw profiles discovered across approved sources. Deduplicate them. Review a documented sample or the full set against essential evidence. Separate "plausible" from "verified enough to approach". Then report reachability as a different dimension. Do not apply an invented industry response percentage to turn profiles into candidates.
Show the formula and a range. For example: 310 raw records across sources; 248 after deduplication; 80 reviewed; 34 currently meet the evidence threshold. If the reviewed sample is reasonably distributed, it may support a broad viable-pool range, but explain the sampling and uncertainty. A small or convenience sample warrants low confidence.
Label source coverage. Professional profiles, internal records, member directories and public work may overlap and exclude people with limited online presence. The ONS vacancies and jobs bulletin provides national and sector context with published data-quality notes; it does not provide a count for a bespoke senior-role market. Keep those two evidence levels separate.
Sections 5 and 6: Grade Evidence and Reachability
Use a simple evidence scale. Grade A is current, directly relevant evidence from a reliable source. Grade B is relevant but incomplete or older evidence. Grade C is an inference that needs validation. Grade D means no usable evidence. Record the source and review date. A search score may help order review, but it is not itself evidence that a person can perform the role.
Assess reachability independently. "Known" means the organisation has a current, usable relationship record. "Contactable" means an appropriate route has been reviewed under the organisation's data rules. "Research required" means a profile exists but the contact route or data position is unresolved. "Suppressed" means no contact should occur. None of these labels means interested.
For candidates already in the database, include last meaningful interaction and stated preferences. For external records, include source, collection date and transparency action. The ICO draft recruitment and selection guidance includes prospective candidates identified through talent search, so the report needs data-protection controls even before outreach begins.
Sections 7 and 8: Turn Risks Into Actions
Write risks as a condition, consequence and trigger. "Compensation may be low" is vague. "Published and candidate evidence indicates the upper approved range may not reach the core segment; if fewer than five of the first fifteen reviewed conversations accept the range as discussable, return the proposition to the sponsor" is actionable. The numbers in a trigger should be chosen for the pilot, not presented as a universal benchmark.
Cover at least market, brief, delivery, source, privacy and fairness risks. Name an owner and mitigation. Then sequence next actions: decide the location policy, review an adjacent-company sample, validate compensation, launch a small outreach cohort, commission specialist research, or pause external hiring while internal development is assessed.
Every action needs a deadline, owner, expected evidence and stop rule. Add a report refresh date. A map without a next decision becomes an expensive archive.
Worked Example: Security Engineering Manager
Consider a fictional UK fintech planning a security engineering manager hire. The role definition requires evidence of leading engineers, improving cloud security controls and operating in a regulated environment. Core companies are comparable regulated digital businesses; adjacent tiers include cloud platforms and larger financial institutions. Observed synonyms include security engineering lead, cloud security manager and product security lead, with scope checked individually.
The report shows raw, deduplicated and reviewed counts rather than claiming a total market census. Candidate evidence is graded, and location is split between London hybrid, wider South East and UK remote. Reachability distinguishes existing relationships from externally sourced records. The principal risks are title ambiguity, a narrow office requirement, uncertain management scope and source undercoverage of candidates with limited public profiles.
The recommended action is a two-part test: review an adjacent-company sample with the security leader and run a small, human-reviewed outreach cohort after privacy checks. If adjacent evidence is strong, widen the company map. If location repeatedly blocks otherwise credible conversations, return that constraint to the sponsor. This example demonstrates report logic only; it makes no claim about actual pool size or hiring outcomes.
Quality-Control Checklist Before Sharing
- The requested decision is explicit and linked to a business scenario.
- Role outcomes and evidence are calibrated with a job expert.
- Target companies and title synonyms have reasons, not just labels.
- Raw, deduplicated, reviewed, viable and reachable counts are not conflated.
- Ranges, sampling, dates, sources and confidence are visible.
- Candidate interest is never inferred from contactability or profile activity.
- Privacy, accuracy, retention, suppression and fairness controls are recorded.
- Risks have owners, triggers and mitigations.
- Next actions have deadlines, stop rules and a refresh date.
- A second reviewer can reproduce the main conclusions from the evidence register.
What the Report Cannot Prove
A market mapping report cannot prove that every relevant person has been found, that a publicly described skill is current, that a contact route is accurate, or that someone will consider a role. It cannot remove bias from a poor brief, replace structured selection or predict quality of hire. It is a dated decision aid built from partial evidence.
Search tools can widen recall, cluster title variants and organise evidence, but humans must validate role logic, candidate relevance and the conclusions presented to leaders. Audit exclusions, correct inaccurate records and avoid sensitive inferences. Obtain data-protection or legal advice for the organisation's specific processing rather than treating this template as legal approval.
Sources and How to Use the Template
- CIPD: Workforce planning factsheet
- Skills England: UK Standard Skills Classification
- Office for National Statistics: Vacancies and jobs in the UK
- Information Commissioner's Office: Draft recruitment and selection guidance
Use the schema for one hard-to-fill role and require evidence or an uncertainty label in every section. Yena Sourcer can help assemble and rank the review cohort while the report remains owned by an accountable recruiter. For deeper research execution, continue with the candidate sourcing guide; for portfolio-level interpretation, connect the report to the talent intelligence framework.