← Back to articles

Why a week (and not a quarter)?

Most skills audits stall because the people running them try to boil the ocean. They start with "let's catalogue every skill across the whole company" and the project dies in spreadsheet meetings. The 5-day method exists because we have watched it succeed where the quarterly version failed: it constrains scope so hard that progress becomes the only option.

You can always run another, deeper audit later. The first one earns the right to do so.

Day 1, Define the scope and the scale

Two artefacts come out of day one: a scope statement and a scoring policy. Without them, every later day will reopen settled questions.

The scope statement (10 lines)

Write down, in plain English:

The 0-5 scoring policy

Use the 0-5 scale (full descriptors in our competency policy guide). Write a one-sentence definition of each level in your team's language. A "3" in cybersecurity reads differently from a "3" in CNC programming; let the words reflect that.

Days 2-3, Gather ratings

Use the template's pre-built data-entry sheet or PulseAI's bulk-import. The mechanics matter less than the social structure:

  1. Self-rating first. Each person rates themselves before they see the manager's view. Self-rating done first reduces deference effects.
  2. Manager rating second. The line manager rates without seeing the self-rating, then both numbers are placed side by side.
  3. Conversation on disagreements. Where the two numbers differ by more than one level, a 15-minute conversation reconciles them. Most of the time, the conversation surfaces hidden capability or unspoken expectation, both gold.
  4. Date every cell. Without a date, the matrix decays into "what we thought once".

Day 4, Calibrate across managers

This is the step most teams skip. It is also the one that separates trustworthy data from theatre.

Pick three or four skills that several managers have rated. Look at the distributions. If Manager A's team is mostly 4s and 5s while Manager B's team is mostly 2s and 3s on the same skill, you have a calibration problem, not necessarily a capability gap.

Resolve it by tightening the descriptor (the words at each level), not by overruling the ratings. Re-rate only where the descriptor genuinely changed.

Day 5, Read the heat-map; build the plan

Open the heat-map view. Three patterns will jump out:

Pick the three biggest gaps weighted by business impact. For each, write a 90-day plan with named owners and dates. That document, not the matrix, is what the audit was for. The full reading method is documented in Reading your skills heat-map.

Five mistakes that kill a skills audit

  1. Trying to score 80 skills on day one. Keep it under 25. Add skills on the second audit.
  2. Letting the highest-paid person in the room decide every contested score. Defeats calibration.
  3. Hiding the matrix from the people in it. Trust collapses; data quality follows.
  4. Treating the audit as a one-off. Quarterly is the minimum useful cadence.
  5. Measuring without a plan. The plan is the only output that produces ROI.

What does a first skills audit really cost?

For a team of 25 people and 20 skills, plan on roughly:

Estimate the upside against your own numbers in the ROI calculator, typical teams find their first audit pays back inside 90 days.

Run your first audit this week

The award-winning template ships with the scope sheet, 0-5 policy, calibration worksheet, and heat-map all pre-built.

Get the template, £199 →