Free template
Skills gap analysis: step-by-step guide and template
A copyable skills gap analysis template, a five-step method for running one and a worked example from a mid-size company, from required levels through to the development actions that close the gaps.
By the CLEAR Talent team
A skills gap analysis compares the skills a role needs with the skills the people in it have today, measures the difference on a shared scale and decides which differences are worth closing first. It can cover one person, a team, a job family or a whole organisation; the method is the same.
It sits between two pieces of work you may already have. A competency framework says what good looks like in each role; a development plan says what one person will do next. The gap analysis is the step that connects them, and it is the step most often skipped — which is why so much training is booked on instinct rather than evidence.
The template below is one row per skill: the level the role requires, the level assessed today, the gap, how much that skill matters to the role and a priority score that puts the list in order. Copy it into a spreadsheet, download it, or read the worked example first to see how the numbers come together.
The skills gap analysis template
Template
Skills gap analysis
Fill in the analysis details once, then one row per skill. Keep required and current levels on the same scale, or the gap column means nothing.
| Field | What to write |
|---|---|
| Analysis details | |
| Role or team | The role being analysed, or the team if you are analysing several people who share it. |
| People in scope | How many people hold the role. For an individual analysis, their name. |
| Proficiency scale | The scale for required and current levels, with what each point means. A common one: 1 awareness, 2 developing, 3 proficient, 4 advanced, 5 expert. |
| Evidence for current levels | Where the current levels come from: manager assessment, self-assessment, 360° feedback, work samples, certifications. Two sources are better than one. |
| Owner | Who runs the analysis and signs off the priorities. |
| Date of analysis | When the current levels were assessed. |
| Next review date | When the same skills will be re-assessed on the same scale to see whether the gaps are closing. |
| For each skill (up to 8) | |
| Skill or competency | One per row, named the way your competency framework names it. Five to ten rows cover most roles; many more usually means the list has not been prioritised yet. |
| Required level | The level the role needs, on your scale. Set it from the role, not from the person who holds it. |
| Current level | The assessed level. For a team, give the average and how many people sit below the required level — an average alone can hide a few large individual gaps. |
| Gap | Required level minus current level. Record zero where the current level meets or exceeds it. |
| Importance to the role | 1 useful, 2 important, 3 critical: how much the work suffers when this skill is missing. |
| Priority score | Gap × importance. Sort by this column; the top two or three rows are where to act first. |
| Development action | What will close the gap, who owns it and by when: training, coaching, a stretch assignment, a hire, or a deliberate decision to accept the gap for now. |
As a spreadsheet
One row per skill. Copy the grid below and paste it into the first cell of a spreadsheet, or download the CSV.
| # | Skill or competency | Required level | Current level | Gap | Importance to the role | Priority score | Development action |
|---|---|---|---|---|---|---|---|
| 1 | |||||||
| 2 | |||||||
| 3 | |||||||
| 4 | |||||||
| 5 | |||||||
| 6 | |||||||
| 7 | |||||||
| 8 |
Show the plain-text template
SKILLS GAP ANALYSIS Role or team: People in scope: Proficiency scale: Evidence for current levels: Owner: Date of analysis: Next review date: SKILL 1 Skill or competency: Required level: Current level: Gap: Importance to the role: Priority score: Development action: SKILL 2 Skill or competency: Required level: Current level: Gap: Importance to the role: Priority score: Development action: SKILL 3 Skill or competency: Required level: Current level: Gap: Importance to the role: Priority score: Development action: SKILL 4 Skill or competency: Required level: Current level: Gap: Importance to the role: Priority score: Development action: SKILL 5 Skill or competency: Required level: Current level: Gap: Importance to the role: Priority score: Development action: SKILL 6 Skill or competency: Required level: Current level: Gap: Importance to the role: Priority score: Development action: SKILL 7 Skill or competency: Required level: Current level: Gap: Importance to the role: Priority score: Development action: SKILL 8 Skill or competency: Required level: Current level: Gap: Importance to the role: Priority score: Development action:
Nothing here is gated: the spreadsheet and the text file hold exactly the fields shown above, with eight blank skill rows. Add rows as you need them.
How to conduct a skills gap analysis in five steps
The method is the same for one person or a hundred. The order matters: define the requirement before you look at anyone’s current level, so the standard is set by the role and not by whoever happens to hold it.
Define the skills each role requires
List the five to ten skills or competencies that matter most in the role and set a required level for each on a single proficiency scale. If you have a competency framework, take the skills and the level descriptions from it; if you do not, write a short behavioural description for each level so two assessors would read it the same way. Where the role is changing, set the level the role will need, not the level it needed last year.
Assess the current level of each skill
Rate each person against the same level descriptions, using evidence rather than impression: a manager assessment, a self-assessment, 360° feedback, work samples or certifications. Combining two sources, such as a self-assessment reconciled with the manager’s view in a one-to-one, catches most over- and under-rating. For a team, record both the average and how many people fall below the required level.
Quantify the gap
Subtract the current level from the required level for every skill. A gap of zero or less means no action for the role, although individuals may still need support. Because both numbers sit on the same scale, the gap is comparable across skills and can be re-measured the same way at the next review.
Prioritise the gaps
Not every gap deserves a programme. Score each skill’s importance to the role — 1 useful, 2 important, 3 critical — and multiply it by the gap to get a priority score. Sort by that score and commit to the top two or three. A small gap in a critical skill often outranks a large gap in a skill the role rarely uses.
Build the development plan
Turn each priority into an action with an owner, a date and a way of measuring success. Gaps shared by most of a team suit a group programme; gaps held by a few people belong in their individual development plans. Some gaps are better closed by hiring or by redesigning the role. Set the date on which the same skills will be re-assessed, so you can see whether the gap actually closed.
Skills gap analysis example: one mid-size company, three teams
A worked example from a 400-person software company that runs the analysis once a year after its competency reviews. Three teams show three different outcomes: a commercial gap in an established team, a leadership gap across a cohort of new managers, and a gap created by a change the business is about to make. Levels use the 1–5 scale above; current levels are team averages.
The company, teams and figures in this example were written for this page to show how the analysis works. They do not describe a real organisation or any CLEAR Talent customer.
Customer success
Team 1: customer success managers
An established team whose customers are happy but whose renewals depend heavily on two senior people. The analysis confirms what the renewal figures suggested and shows that product knowledge, the usual target for training spend, is not the problem.
- People in scope
- 12 customer success managers
- Evidence for current levels
- Self-assessment reconciled with the manager’s assessment in a one-to-one
- Next review date
- Twelve months, at the next competency review
| Skill or competency | Required level | Current level | Gap | Importance to the role | Priority score | Development action |
|---|---|---|---|---|---|---|
| Renewal and commercial negotiation | 3 | 2.1 (8 of 12 below 3) | 0.9 | 3 | 2.7 | Renewals workshop led by the sales director; everyone below level 3 shadows a strong renewer for two quarters. |
| Data-led account reviews | 3 | 2.5 (5 of 12 below 3) | 0.5 | 2 | 1.0 | A standard account-health report template and a half-day session on reading product usage data. |
| Product knowledge | 4 | 3.8 (2 of 12 below 4) | 0.2 | 2 | 0.4 | No team action; the two recent joiners are covered by onboarding. |
| Stakeholder management | 3 | 3.1 (2 of 12 below 3) | 0 | 3 | 0 | No team action; the two individual gaps go into those people’s development plans. |
First-line managers
Team 2: first-line people managers
Thirty managers across the business, most promoted in the last two years. Assessed against the leadership section of the company’s competency framework. The two largest gaps are shared by most of the cohort, so they become one programme rather than thirty separate plans.
- People in scope
- 30 first-line managers across all departments
- Evidence for current levels
- Manager assessment plus 360° feedback from each manager’s direct reports
- Next review date
- Twelve months; a pulse re-assessment of feedback skills at six months
| Skill or competency | Required level | Current level | Gap | Importance to the role | Priority score | Development action |
|---|---|---|---|---|---|---|
| Giving feedback | 3 | 2.4 (19 of 30 below 3) | 0.6 | 3 | 1.8 | Cohort programme: a feedback course, then practice in regular one-to-ones, with the manager’s own manager observing one session. |
| Delegation | 3 | 2.2 (20 of 30 below 3) | 0.8 | 2 | 1.6 | A delegation module in the same programme; each manager brings one live handover to work through. |
| Running performance conversations | 3 | 2.8 (9 of 30 below 3) | 0.2 | 3 | 0.6 | No cohort programme; the nine managers below level 3 get a goal in their individual development plans. |
| Budget and headcount planning | 2 | 1.6 (12 of 30 below 2) | 0.4 | 1 | 0.4 | A guidance note from finance before the next planning round; accepted for now. |
Finance operations
Team 3: finance operations ahead of a system change
A team of six that runs month-end close well today. The company will replace its finance system next year, so the required levels are set for the role as it will be after the change. That one decision turns a team with no visible problem into the highest-priority gap in the company.
- People in scope
- 6 finance operations staff
- Evidence for current levels
- Manager assessment and a short practical exercise in the new system’s trial environment
- Next review date
- One month after go-live, then at the annual review
| Skill or competency | Required level | Current level | Gap | Importance to the role | Priority score | Development action |
|---|---|---|---|---|---|---|
| Using the new finance system | 3 | 1.0 (6 of 6 below 3) | 2.0 | 3 | 6.0 | Vendor training for all six before go-live; two people trained to level 4 first so they can support the rest. |
| Process documentation | 3 | 2.0 (4 of 6 below 3) | 1.0 | 2 | 2.0 | Document each month-end process before migration, paired with the finance manager; the documents double as training material. |
| Spreadsheet analysis | 3 | 2.7 (2 of 6 below 3) | 0.3 | 2 | 0.6 | A goal in the two individual development plans; support from the two lead users. |
| Account reconciliation | 4 | 3.8 (1 of 6 below 4) | 0.2 | 3 | 0.6 | No team action; reviewed again after go-live, when the process changes. |
From spreadsheet to live data
How competency data automates the analysis in CLEAR Talent
The spreadsheet works, but it is rebuilt by hand every year and is out of date as soon as someone changes role. In CLEAR Talent the inputs already exist as competency data. Each role profile carries its required competencies and target levels, drawn from a central competency library in which every level has behavioural anchors. Ava, the platform’s AI assistant, can draft a role-specific framework from your role and organisation context; your team edits and approves it before it is used, every AI output is labelled and editable, and every edit is logged.
Current levels come from evidence-based competency assessments, so the gaps come from the assessments themselves rather than from figures copied into a sheet afterwards. Dashboards show capability coverage by individual, team, department and competency, flag the gaps and chart each competency over time, and reports at individual, team and organisation level export to PDF or Excel.
The last step is automatic too. Each assessment drafts an individual development plan from the competencies that matter most for the role, ranked by the size of the gap, and where someone has named the role they want next, the gap is calculated against that role. Learning impact dashboards then show whether the development activity closed the gaps it was meant to close.