Short answer
Enterprise talent mapping connects the capabilities a business needs with the people, experience, and development options available to it. A useful map records the role requirement, supporting evidence, employee interest, gaps, and accountable reviewer. Start with one staffing or development decision, then expand the map when its information helps people make that decision more reliably.
Decide what the map is for
A map for opening new stores needs different information from one for developing future finance leaders. Write down the decision before choosing a taxonomy or buying software. For example: which internal development, external hiring, and operating changes could support three additional store openings?
CIPD's workforce planning guidance connects future business needs, existing workforce capacity, gaps, and actions. Talent mapping can supply part of the current-capability evidence within that process. It does not replace the demand forecast, finance assumptions, or decisions about how work should be organised.
Keep three tasks separate:
| Task | Question | Output |
|---|---|---|
| Workforce planning | What work and capacity will the business need? | Demand scenarios and resourcing choices |
| Talent mapping | What relevant capability, interest, and development options are available? | A reviewed evidence map |
| Software selection | Which systems support the required data and workflows? | Requirements and an implementation decision |
This guide covers implementation of the map. For software evaluation, use the talent intelligence platform guide.
Use a map with evidence behind each entry
Avoid starting with a global list of everyone marked high, medium, or low potential. The following template makes the specific work requirement visible instead.
| Field | What to record | What to avoid |
|---|---|---|
| Business need | Work to deliver, location, timing, and capacity | A role title without a defined requirement |
| Role requirement | Tasks, experience, qualifications where relevant | Treating every desirable skill as mandatory |
| Available evidence | Relevant work example, source, date, and reviewer | Treating a self-rating or inferred skill as verified |
| Employee interest | Expressed preference and constraints, with appropriate access | Assuming good performance means interest in promotion |
| Development gap | Experience or support still needed | An unexplained readiness label |
| Possible action | Development assignment, recruitment, role redesign, or further inquiry | Promising a move before approval |
| Owner and review | Who checks the entry and what change prompts another review | Updating dates without checking the evidence |
Keep source systems authoritative for formal facts such as role, employment status, or completed qualifications. Recent conversation evidence can add context, but it remains an account to examine. Recency and collection method are different: see live versus declarative HR data.
A fictional retail expansion example
A retailer plans to open three stores. The initial map lists four assistant managers as possible store managers. That count looks reassuring, but the review finds four different situations:
- One person wants the move and has already covered the relevant responsibilities.
- One wants a specialist route rather than people management.
- One is interested but needs experience handling opening operations.
- One has relevant experience but cannot move to the planned locations.
The map should preserve those distinctions. It should not turn four names into four available successors. HR and operations can now explore an opening assignment for one person, a local recruitment plan, and a specialist development path. The employees' expressed preferences remain part of the discussion, not a permanent prediction of future willingness.
The proposed actions still need budget, capacity, and individual agreement. The map improves the questions; it does not decide the moves.
Avoid counting the same capacity twice
Enterprise maps combine local views. The same person can appear in several development pools or store-opening plans, so adding those lists does not give an available headcount. Before using the map for coverage, reconcile proposed assignments for the same period with existing work, location constraints and confirmed availability. Keep employee interest separate from an approved allocation.
Extend the fictional retail example: one experienced manager can contribute two days a week to opening support after existing responsibilities are covered. Two sites each request those same two days in the same week.
| Proposed assignment | Requested support | Check before approval |
|---|---|---|
| Store A opening | Two days in week one | Confirm the specific days and required work |
| Store B opening | Two days in week one | The same person's two days are already requested by A |
| Combined request | Four days against two available | Resolve the overlap before calling both sites covered |
Splitting one day to each site provides two days in total but does not meet either original two-day request. The operating owner must change a date, agree a smaller scope or find additional coverage, then confirm the arrangement with the people involved. Any travel or handover time also uses capacity.
Record the selected scenario, the work displaced, the approver and the next review trigger. Keep alternatives visibly separate from approved assignments. For the underlying demand and available-hours calculation, use the workforce capacity worksheet. This is a planning check, not a feature claim about Lontra or a commitment that an employee will move.
Run a bounded mapping cycle
- Select one role family or operating decision and name its business owner.
- Agree the smallest set of role requirements needed for that decision.
- Reconcile existing records before asking employees to repeat information.
- Invite relevant work examples and aspirations with a clear explanation of use and access.
- Review uncertain entries with the people who can check them. Keep missing evidence visible.
- Choose an action, name the owner, and set a review trigger such as a completed assignment or changed requirement.
To reduce dependence on one manager's impressions, compare the evidence expected for the same role across teams. Record disagreements and what additional evidence would resolve them. A polished map with unsupported entries is less useful than an incomplete map whose limits are clear.
Check whether the map improves decisions
Track the share of in-scope requirements with reviewed evidence, unresolved gaps, agreed development actions completed, and entries awaiting employee confirmation. These measure progress in the mapping process. They are not proof that promotions will succeed or turnover will fall.
Review access before expanding the map. A regional capacity view does not require every manager to see personal aspirations or confidential notes. Decide what belongs in a restricted individual discussion and what can be reported as a broader capability gap.
Lontra can help prepare conversations about work examples and practical constraints. It does not operate a talent marketplace, verify qualifications, or make succession decisions. For a concrete conversation-preparation example, see the fictional manager brief.