Short answer
Employee skills mapping is a reviewed map of the work an organisation needs, the evidence of capability it already has and the questions that remain open. It is useful for a defined staffing, mobility or development decision. Start with roles and work outcomes, retain the source and date of each entry, and let people correct their context. Do not turn mixed evidence into an automatic individual score.
What a skills map is for
Mapping is broader than checking whether one person can complete one task. It answers a coverage question: where is capability available, where is it thin, and what needs a closer review before a business decision? A skills gap analysis worksheet is the better next step when the team needs to test one work requirement and select development, sourcing or process action.
The US Department of Labor's sponsored O*NET database separates occupation data into tasks, skills, knowledge, work activities and work context. That is a helpful prompt: a good map should not treat a job title or course completion as proof of every part of the work. The CIPD workforce-planning factsheet similarly frames capability alongside future demand and action planning.
Build a map around one decision
Choose a decision with a real owner. Examples include opening a new service line, covering a seasonal peak, moving work between sites or identifying internal candidates for a development programme. Then define the smallest useful scope: a job family, site, shift or programme rather than every skill in the company.
| Map element | Record | Why it matters |
|---|---|---|
| Decision and owner | The decision, deadline and accountable reviewer | Stops the map becoming an inventory with no use |
| Work requirement | Observable task, conditions and acceptable output | Makes a vague label such as leadership reviewable |
| Coverage | Relevant roles or teams, including exclusions | Shows what the map can and cannot represent |
| Evidence | Source, date, context and reviewer | Keeps a declaration separate from demonstrated work |
| Employee context | Interests, constraints, correction or disagreement | Prevents a record becoming a silent verdict |
| Next action | Confirm, develop, redeploy, source or redesign | Connects the map to a human decision |
Use evidence in layers
Employee self-report can identify experience, confidence and examples worth examining. A manager may add local context. A work artifact, work sample or formal qualification can answer a narrower question. None alone proves all future capability.
Keep the evidence state visible instead of averaging it into a single proficiency number:
- Declared: the employee describes relevant experience or interest.
- Described: a conversation gives a specific example and conditions.
- Demonstrated: a recent comparable work output has been reviewed.
- Verified record: a qualification or formal requirement has been checked for relevance and date.
- Unknown or disputed: evidence is absent, old, incomplete or challenged.
This distinction is especially important when maps inform opportunity. The UK ICO's employment-record guidance covers accuracy, transparency, minimisation, access and retention. A map needs a defined purpose, proportionate access and a way to correct factual errors.
A fictional coverage exercise
This example is fictional. A UK service organisation plans to add a weekend support rota. The decision owner needs four people who can diagnose a common issue, explain the next step to customers and hand unresolved cases to the weekday team.
The mapping team does not search for people labelled "advanced support." It records the three work requirements and reviews recent case notes, employee examples and training records. Two employees have recent accepted cases and are marked demonstrated. One employee has relevant experience but no current case because she works another channel, so her state remains declared pending a comparable work sample. Another employee completed training but lacks the required system access, which is an access issue rather than a capability conclusion.
The resulting action is clear: confirm interest, availability and working arrangements with the two employees whose examples were reviewed, resolve access for one, offer one fair work sample and decide whether additional coverage requires sourcing or changing the rota. The map exposes the decision without claiming to rank people or predict performance.
Refresh when the decision changes
Refresh evidence after a role redesign, new tool, material change in work conditions or before a decision that depends on it. Do not set an arbitrary refresh interval for every record. A map is current only in relation to the work it represents.
A focused conversation can add employee examples, blockers and local practice to a defined mapping question. Lontra's product can be evaluated with one campaign of up to 30 invitations over 60 days, without a card. Its output should support human review: managers receive a brief, not raw conversations. It is not an automated skills inventory, system of record or decision-maker.
