Costs, Honestly

Assessment is usually discussed as a software purchase. Most of the cost is elsewhere.

The principles in “Costs, Honestly” become easier to maintain when ownership and time spent are visible. Teams evaluating the detailed reference can use it to coordinate the administrative work around assessment, identify stages that repeatedly expand and plan capacity, while keeping the hiring decision tied to job-relevant evidence instead of raw activity totals.

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 the visible costs are

Platform licences.

Test or instrument fees per candidate.

Background checks.

These are the ones that appear in a budget and they are rarely the largest.

What the invisible costs are

Assessor time, which is senior and expensive. Four interviewers times an hour times fifty candidates is a substantial figure nobody calculates.

Coordination and scheduling, which consumes more administrative time than anything else in hiring.

Time to hire, during which the work is not being done.

And dropout: candidates lost to slow or long processes, which shows up as a longer search rather than as a cost.

The cost of a bad process

A wrong hire: recruitment repeated, onboarding wasted, the work not done, and the effect on a team.

A rejected good candidate, which is invisible and probably more common.

And reputational cost in a connected market, where a process seen as careless reduces future applications from exactly the people you wanted.

What is worth paying for

Assessor time on calibration, which is the highest-return hour in the whole process.

Designing a work sample properly once, then reusing it.

Speed: compressing the process is cheap and reduces dropout substantially.

And feedback, which costs five minutes and buys goodwill disproportionately.

What is usually not worth paying for

Additional instruments beyond two or three, which add cost and little information.

Personality profiles used as scores.

Long assessment centres for ordinary roles.

And platform features that automate a stage you should have removed.

The build-versus-buy question

A work sample and a structured question set for a specific role can be built in a day and outperform generic products for that role.

Buy where you need volume scoring, scale, or validated instruments for a regulated purpose.

Build where the role is specific and recurring, which is most roles an organisation hires repeatedly.

Making the case internally

The argument that lands is rarely validity.

It is time saved, consistency, defensibility, and dropout reduced.

Bring your own audit figures rather than industry statistics, because your data is harder to argue with and more relevant.

What to check

Have you costed assessor hours for your last search?

Do you know your dropout rate and what it costs?

Is anything in your budget automating a stage you could remove?

And what did your last failed search actually cost?

The point

Most of the cost is assessor time, coordination and dropout, none of which appears in the budget that discusses platform licences..

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.