How Long an Assessment Should Take

Processes grow. Each stage was added for a reason and nobody removes any, so a role that was two interviews is now five rounds and a project.

Once the criteria described in “How Long an Assessment Should Take” are fixed, the practical challenge is running them consistently across assessors. A coordinator can use this useful page 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.

The diminishing return

The first well-chosen assessment gives you most of what you will learn.

The second, targeting a different requirement, adds substantially.

The third adds a little.

The fourth and fifth mostly add noise, fatigue, and dropout, and the candidates who complete them are disproportionately the ones with the most availability.

What a reasonable total looks like

For most roles: three to five hours of candidate time in total, across everything.

Two or three stages.

For senior or safety-critical roles, more is defensible — and should still be justified stage by stage.

Above about eight hours you are running a different selection than you think.

The cost to the candidate

Hours, which for employed candidates means annual leave or evenings.

Travel and its cost.

Childcare or care cover.

And the opportunity cost of a process that will probably end in rejection, which is the expected outcome for most applicants.

Its own note covers who this excludes, and the answer is systematic rather than random.

The cost to you

Assessor hours, which are senior and expensive.

Scheduling, which consumes coordinator time disproportionately.

And dropout: strong candidates with options leave long processes, which means length selects against exactly the people you wanted.

Trimming an existing process

List the stages. For each, ask what decision it makes and what it would take to change that decision.

Remove any stage that has never changed an outcome.

Organisations that audit this typically find one or two stages that have never rejected anybody, and those are pure cost.

Where length is genuinely warranted

Safety-critical roles.

Roles where a wrong hire is very expensive to unwind.

Senior roles with a small candidate pool, where both sides are investing in the decision.

Not: ordinary roles at volume, where the cost falls hardest and the information gained is least.

Telling candidates

Publish the total time commitment at the point of application.

It is a courtesy, it improves the quality of applications, and it forces you to look at the number, which is frequently the moment somebody notices it is unreasonable.

What to check

What is your total candidate time commitment, added up?

Is it published?

Has any stage ever changed an outcome?

And has anybody measured dropout by stage — and who drops out?

The point

Add up the total candidate time across every stage.

Above four or five hours you are selecting on availability rather than capability.

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.