Reassessment Over Time

Assessment produces a snapshot. Treating it as permanent is a mistake in both directions: people improve and skills decay.

Once the criteria described in “Reassessment Over Time” are fixed, the practical challenge is running them consistently across assessors. A coordinator can use the workflow note 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 U.S. OPM assessment resources; the useful test is whether the local method remains job-related, proportionate and explainable.

What decays

Specific tool and technology knowledge, quickly.

Regulatory and procedural knowledge, as rules change.

Practical skills not used, which degrade faster than people expect.

And currency in a field that moves, which is the general case.

What does not

Underlying reasoning.

Judgement built from experience.

And most of what a good job analysis identifies as distinguishing strong performers, which tends to be stable.

Which means reassessment should target the volatile things rather than repeating the whole exercise.

When it is warranted

After a substantial change to the role or the technology.

Before a move into a different role, as the internal promotion note covers.

Where regulation requires it.

Where safety depends on current competence.

And where somebody has been away from practice for a long period.

When it is not

Annually as a matter of routine, with no follow-up.

As a substitute for performance management, which is a different process with different purposes.

Or as a compliance ritual, which is how most skills matrices end up: filled in each year, read by nobody.

Returning from absence

Parental leave, long illness, career break.

Some reassessment may be genuinely necessary for safety-critical or fast-moving work.

It should be framed as identifying what needs refreshing rather than as proving fitness, and it should be accompanied by the refreshing rather than being a hurdle.

Getting this wrong is a common source of both unfairness and legal exposure.

The interval question

Set it by how fast the relevant knowledge changes, not by the calendar.

Some things need checking annually, most do not need checking at all.

And reassessing everything on the same cycle is administrative convenience wearing the appearance of rigour.

Making it worth doing

Tie it to something: training offered, a plan updated, a gap closed.

Tell people what will happen with the result before they do it.

And keep it short, because a long reassessment of people already doing the job well is a tax on your best staff.

What to check

Does anything in your organisation get reassessed annually out of habit?

Are volatile and stable capabilities treated differently?

Does anything follow from the results?

And is reassessment after absence framed as support or as a hurdle?

The point

Reassess the volatile capabilities rather than repeating the whole exercise.

Most things do not need checking at all.

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.