Skip to main content

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

Get the template

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.

Skills gap analysis template fields
FieldWhat to write
Analysis details
Role or teamThe role being analysed, or the team if you are analysing several people who share it.
People in scopeHow many people hold the role. For an individual analysis, their name.
Proficiency scaleThe 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 levelsWhere the current levels come from: manager assessment, self-assessment, 360° feedback, work samples, certifications. Two sources are better than one.
OwnerWho runs the analysis and signs off the priorities.
Date of analysisWhen the current levels were assessed.
Next review dateWhen 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 competencyOne 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 levelThe level the role needs, on your scale. Set it from the role, not from the person who holds it.
Current levelThe 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.
GapRequired level minus current level. Record zero where the current level meets or exceeds it.
Importance to the role1 useful, 2 important, 3 critical: how much the work suffers when this skill is missing.
Priority scoreGap × importance. Sort by this column; the top two or three rows are where to act first.
Development actionWhat 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.

Skills gap analysis template as a spreadsheet grid
#Skill or competencyRequired levelCurrent levelGapImportance to the rolePriority scoreDevelopment 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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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
Team 1: customer success managers
Skill or competencyRequired levelCurrent levelGapImportance to the rolePriority scoreDevelopment action
Renewal and commercial negotiation32.1 (8 of 12 below 3)0.932.7Renewals workshop led by the sales director; everyone below level 3 shadows a strong renewer for two quarters.
Data-led account reviews32.5 (5 of 12 below 3)0.521.0A standard account-health report template and a half-day session on reading product usage data.
Product knowledge43.8 (2 of 12 below 4)0.220.4No team action; the two recent joiners are covered by onboarding.
Stakeholder management33.1 (2 of 12 below 3)030No 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
Team 2: first-line people managers
Skill or competencyRequired levelCurrent levelGapImportance to the rolePriority scoreDevelopment action
Giving feedback32.4 (19 of 30 below 3)0.631.8Cohort programme: a feedback course, then practice in regular one-to-ones, with the manager’s own manager observing one session.
Delegation32.2 (20 of 30 below 3)0.821.6A delegation module in the same programme; each manager brings one live handover to work through.
Running performance conversations32.8 (9 of 30 below 3)0.230.6No cohort programme; the nine managers below level 3 get a goal in their individual development plans.
Budget and headcount planning21.6 (12 of 30 below 2)0.410.4A 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
Team 3: finance operations ahead of a system change
Skill or competencyRequired levelCurrent levelGapImportance to the rolePriority scoreDevelopment action
Using the new finance system31.0 (6 of 6 below 3)2.036.0Vendor training for all six before go-live; two people trained to level 4 first so they can support the rest.
Process documentation32.0 (4 of 6 below 3)1.022.0Document each month-end process before migration, paired with the finance manager; the documents double as training material.
Spreadsheet analysis32.7 (2 of 6 below 3)0.320.6A goal in the two individual development plans; support from the two lead users.
Account reconciliation43.8 (1 of 6 below 4)0.230.6No 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.

Frequently asked questions

What is a skills gap analysis?
A skills gap analysis compares the skills a role requires with the skills the people in it currently have, measures the difference on a shared proficiency scale and ranks the gaps so that training, hiring and development effort go where they matter most. It can be run for one person, a team or a whole organisation.
How do you conduct a skills gap analysis?
In five steps: define the skills and required level for each role; assess each person’s current level against the same level descriptions, using evidence; subtract current from required to quantify each gap; multiply the gap by the skill’s importance to prioritise; and turn the top two or three priorities into development actions with owners, dates and a re-assessment date.
What is an example of a skills gap?
A customer success team whose role requires level 3 in renewal negotiation, on a 1–5 scale, but whose members average 2.1, with eight of twelve below the required level. The gap is 0.9; because renewals are critical to the role, it outranks a smaller gap in product knowledge and becomes the team’s development priority.
What is the difference between a skills gap analysis and a skills matrix?
A skills matrix records who has which skills at which level. A skills gap analysis adds the required level for the role, measures the difference and decides what to do about it. In practice a matrix with a required-level column becomes the input to a gap analysis.
Should you analyse individuals or teams?
Both, for different decisions. Team-level analysis shows where a group programme, a hire or a change to the role is justified; individual analysis feeds each person’s development plan. Record both the team average and how many people sit below the required level, because an acceptable average can hide a few people with large gaps.
How often should you run a skills gap analysis?
At least once a year, usually straight after competency or performance reviews so the current levels are fresh, and additionally whenever a role changes materially — a new system, a new market, a restructure. Re-assess the same skills on the same scale each time, so you can see whether the gaps are actually closing.
Can software automate a skills gap analysis?
Much of it. In CLEAR Talent, role profiles hold the required competencies and target levels, assessments supply the current levels, and gap dashboards by individual, team, department and competency are built from those assessments. Each assessment also drafts a development plan from the largest gaps in the competencies that matter most. Deciding which gaps to act on, and how, stays with people.

See skills gaps measured, not guessed

Book a walkthrough of CLEAR Talent’s competency management: role profiles with target levels, evidence-based assessments and gap dashboards that draft development plans.