Free Skill Matrix Template for Excel & Google Sheets | HR Gap Analysis Tool
Free Skill Matrix Template for Excel & Google Sheets | HR Gap Analysis Tool
A project management skills matrix is a grid that maps your project people against the competencies each role needs, then rates every person 0–4 on each one. It turns a vague "who's good at what" into a decision-ready view of gaps, cover, and readiness — so you staff projects, plan development, and promote from Coordinator to PMO on evidence, not gut feel.
The free Excel and Google Sheets template below is built for the full delivery ladder — Coordinator → Project Manager → Program Manager → PMO — with role-specific competency weighting and a calibration process most guides skip. In this article you get:
- What actually belongs in a PM skills matrix (and what to leave out)
- A role-ladder weighting table with real starting numbers
- A step-by-step assessment and calibration process to kill rating bias
- How to scale the matrix from a single team to an enterprise PMO
- The free download in Excel and Sheets
What belongs in a project management skills matrix
Every useful matrix has three axes: the people (rows), the competencies (columns), and a proficiency rating in each cell. The mistake most teams make is dumping fifty micro-skills into the columns. Keep it to a handful of competency families that genuinely predict project outcomes.
These seven families cover the vast majority of PM delivery roles. You can map them onto PMI's Talent Triangle (Ways of Working, Power Skills, Business Acumen) if your PMs already work inside that language — it makes adoption faster.
| Competency family | What it measures |
|---|---|
| Planning & scheduling | WBS, critical path, baselining, dependency management, realistic estimates |
| Stakeholder & communication | Steering-group management, status reporting, expectation setting, escalation |
| Risk & issue management | Identifying, quantifying, mitigating and tracking risks and open issues |
| Budget & commercial | Cost planning, forecasting, change control, vendor and contract handling |
| Leadership & people | Motivating a team without line authority, conflict handling, coaching |
| Methodology & governance | Waterfall/agile/hybrid fluency, gate reviews, quality and compliance |
| Tools, data & reporting | PM software, dashboards, portfolio data, PowerBI/Excel reporting |
Rate each person on a short, defined scale so ratings mean the same thing to everyone:
- 0 — None: no exposure, needs full support
- 1 — Aware: understands the concept, works under supervision
- 2 — Working: applies it independently on routine work
- 3 — Proficient: handles it under pressure, on complex projects
- 4 — Expert: sets the standard, coaches and reviews others
The non-negotiable rule: every rating needs evidence. "I feel like a 3" is not a rating. "Led the SAP rollout steering group for six months" is. This single discipline separates a matrix that drives decisions from one that quietly rots.
The role ladder: Coordinator → PM → Program Manager → PMO
A single competency profile for "project people" is the most common reason matrices fail. A Project Coordinator and a Program Manager need almost inverse strengths. The value of a role ladder is weighting: the same competency counts differently depending on the level.
The table below shows a starting weighting (each column sums to 100%). Treat it as a baseline to adapt, not gospel — the point is that the emphasis visibly shifts as you climb the ladder.
| Competency family | Coordinator | Project Manager | Program Manager | PMO |
|---|---|---|---|---|
| Planning & scheduling | 25% | 20% | 10% | 10% |
| Stakeholder & communication | 15% | 20% | 25% | 15% |
| Risk & issue management | 10% | 15% | 20% | 15% |
| Budget & commercial | 5% | 15% | 20% | 15% |
| Leadership & people | 5% | 15% | 20% | 10% |
| Methodology & governance | 10% | 10% | 5% | 25% |
| Tools, data & reporting | 30% | 5% | 0% | 10% |
Read down each column and the role tells its own story. A Coordinator lives in scheduling and reporting — the operational backbone. A Project Manager is deliberately balanced across delivery. A Program Manager loads onto stakeholder, risk and leadership because they orchestrate people and dependencies across projects. A PMO role tilts hard toward methodology and governance — they own the standard, not the delivery.
To get a readiness score, multiply each person's rating by the target-role weight and total it. Someone scoring 3.4 out of 4 against the PM profile is ready; a 2.1 shows exactly which families to develop before promotion. This is what makes the matrix a promotion and staffing tool, not a wall poster.
Building the assessment and calibration process
The single biggest failure mode is rating drift: two assessors score the same competency completely differently, so the numbers stop being comparable. A skills matrix that isn't calibrated is just a collection of opinions. Run this five-step process.
- 1. Define levels with behaviour anchors. For each competency, write one concrete sentence per level ("Level 3 in Risk = independently ran a risk register on a €1M+ project"). This is the guardrail against "I feel like a 3."
- 2. Self-assessment first. Each person rates themselves with evidence. Doing this before the manager rating surfaces where perceptions diverge and gives you a real conversation, not a verdict.
- 3. Manager rating, independently. The lead rates the same person without seeing the self-score, then the two are compared.
- 4. Calibration session. Managers sit together and reconcile ratings across people. This is the step everyone skips — and it's the one that makes the data trustworthy. Anchor to evidence, not likeability.
- 5. Set a refresh cadence. Re-rate after every major project close and at least twice a year. Skill data goes stale fast; an un-refreshed matrix is worse than none because people trust numbers that are no longer true.
Why bother with the rigour? PMI's 2026 Pulse of the Profession found project success rises to 72% when leads deploy a formal, structured framework, versus 61% without one. A calibrated skills matrix is one of the most concrete structured frameworks a PMO can actually put in place — but only if the ratings are consistent enough to act on.
Adapting the matrix by company size
The same template scales, but how you run it should change with the size of your project organisation.
| Organisation | How to run it | Refresh |
|---|---|---|
| Small (<50, one delivery team) | One tab, one competency set, no formal PMO. The team lead owns ratings. Focus on cover for critical skills, not on career ladders. | Quarterly |
| Mid (50–500) | Full role ladder, per-team owners, readiness scoring feeds promotion talks. One consolidated matrix per department. | Every 6 months + project close |
| Enterprise (500+) | PMO owns the standard and the weighting; matrices roll up to a portfolio view; integrate with the HR system so it isn't a parallel spreadsheet island. | Continuous, with biannual calibration |
The moment you pass roughly a hundred project people, the spreadsheet starts to strain — version conflicts, stale tabs, no history. That's the natural point to look at dedicated skills and competency management software. If you want to compare options before you decide, our skill management software comparison and RFP checklist walks through the practical criteria.
Common pitfalls (and how to fix them)
| Pitfall | Why it hurts | Fix |
|---|---|---|
| Too many columns | 50 micro-skills means nobody keeps it current | Cap at 7–10 competency families that predict outcomes |
| Activity-focus ratings | Rating "did the task" instead of "delivered the outcome" inflates scores | Anchor every level to a result, not an activity |
| No calibration | Ratings aren't comparable across teams | Run the manager calibration session (step 4) |
| Set and forget | Data decays within months; people trust stale numbers | Fixed refresh cadence tied to project close |
| Same profile for every role | Coordinator and PMO get judged on the wrong things | Use role-ladder weighting |
| Used punitively | People game their self-ratings if it feeds only discipline | Frame it as development first, assessment second |
Keeping the matrix current with AI
The honest weakness of any spreadsheet matrix is decay. A PM finishes a demanding program, levels up three competencies — and the matrix still shows last year's numbers because nobody re-rated them. Within a couple of quarters the file is quietly wrong, and stale skill data is what pushes teams to abandon the exercise entirely.
This is where an AI layer earns its place — not as hype, but as maintenance. An AI coworker like Sprad's approach to skill management can pick up skill signals from real work (project closeouts, tools used, feedback) and prompt a re-rating, so the matrix stays close to reality instead of drifting. Treat it as one option for the maintenance problem, once the spreadsheet stops keeping up.
Free download: PM skills matrix template
The template ships in Excel and Google Sheets, pre-built with the seven competency families, the 0–4 rating scale with anchors, the four role-ladder weighting columns, and an automatic readiness score. Drop in your people, rate against evidence, and you have a working matrix in an afternoon.
If you're weighing a spreadsheet against a proper system for the long run — especially past ~100 project people — start with the software comparison and RFP checklist so you buy on criteria, not on a demo.
FAQ
What is a project management skills matrix?
A grid mapping project people (rows) against the competencies each role needs (columns), with a 0–4 proficiency rating in each cell. It shows skill gaps, coverage risk and promotion readiness across your delivery team at a glance.
What competencies should a PM skills matrix include?
Seven families cover most delivery roles: planning & scheduling, stakeholder & communication, risk & issue management, budget & commercial, leadership & people, methodology & governance, and tools, data & reporting. Keep it under ten columns so it stays maintainable.
How do you rate proficiency in a skills matrix?
Use a short defined scale — 0 None, 1 Aware, 2 Working, 3 Proficient, 4 Expert — with a behaviour anchor per level and evidence for every rating. Combine self-assessment, an independent manager rating, and a calibration session so scores are comparable.
How is a competency matrix different from a skills matrix?
In practice the terms are used interchangeably. If you want a distinction: a skills matrix leans toward specific, observable abilities, while a competency matrix bundles skills, knowledge and behaviours into broader families. The template here works for both.
How often should you update a PM skills matrix?
Re-rate after every major project close and at least twice a year. Skill data decays within months, and a stale matrix is worse than none because decisions get made on numbers that are no longer true.
Next step
Download the template, run one honest calibration round with your leads, and score every project person against their target-role profile. You'll see your real gaps within a day — and know exactly who's ready for the next rung on the ladder.
Jürgen Ulbrich
Jürgen Ulbrich has more than a decade of experience in developing and leading high-performing teams and companies. As an expert in employee referral programs as well as feedback and performance processes, Jürgen has helped over 100 organizations optimize their talent acquisition and development strategies.
