Skills Gaps and What Assessment Reveals

A process that rejects most applicants is telling you something, and it is not always about the applicants.

Once the criteria described in “Skills Gaps and What Assessment Reveals” are fixed, the practical challenge is running them consistently across assessors. A coordinator can use the original source to plan review time, compare the effort spent at each stage and spot avoidable delays, without confusing administrative efficiency with the quality of the evidence collected from candidates.

For an independent benchmark, compare the process with O*NET occupational information; the useful test is whether the local method remains job-related, proportionate and explainable.

What high rejection rates might mean

The requirements exceed what the market supplies at the salary offered.

The job description is describing two roles.

The assessment is measuring something the role does not need.

Your sourcing is reaching the wrong people.

Or the market genuinely lacks this skill, which is the least common explanation and the first one people reach for.

Diagnosing it

Look at where candidates fail, by criterion.

If everybody fails on the same requirement, that requirement is the constraint — and the question becomes whether it is genuinely necessary or whether it could be trained.

If failures are scattered, you have a sourcing problem rather than a skills problem.

The train-or-hire decision

For each requirement, ask how long it takes a competent person to acquire it.

Anything under about three months is an onboarding item, not a selection criterion, and treating it as one shrinks your pool for no benefit.

This calculation, done honestly, usually moves two or three requirements out of selection.

What the data tells you about the role

A role nobody can fill as specified is a role that needs redesigning.

Splitting it, reducing the seniority, or accepting a training period are all legitimate answers.

Running the same search for nine months is not, and it is the common one.

Aggregating across rounds

Individual rounds are noisy. A year of data shows patterns.

Which requirements consistently eliminate candidates. Which sources produce people who pass. Where the process loses people.

This is the same audit described in its own note, read for a different purpose.

Feeding it into workforce planning

Assessment data is the most direct evidence you have about what the market supplies.

It should reach whoever decides on training, on role design and on salary bands.

In most organisations it reaches nobody outside recruitment, which wastes the most useful output of the whole process.

The uncomfortable finding

Sometimes the data says the role is unfillable at the offered salary.

That is a finding about the offer rather than about candidates.

Organisations that will not hear it run searches indefinitely and conclude there is a skills shortage.

What to check

Do you know which criterion eliminates most candidates?

Have you asked how long each requirement takes to learn?

Does anybody outside recruitment see the assessment data?

And has a failed search ever led to the role being redesigned?

The point

Look at which criterion eliminates most candidates.

If everybody fails the same one, that requirement is the constraint and may not be necessary.

Underlying all of this

Almost everything in this collection reduces to one discipline: write down what the job requires, assess that thing directly, record the evidence, and look at your own outcomes afterwards. None of it requires buying anything, and organisations that do those four things consistently outperform ones running longer processes built from instruments chosen before the requirements were known.

The recurring pattern

The recurring failure across every section here is the same: measuring what is convenient rather than what matters, then never checking whether it predicted anything. The check is an afternoon of work once a year, and it is the step that separates a process that improves from one that merely persists.