Candidate Communication

Candidate complaints are rarely about being rejected. They are about not knowing what was happening.

The principles in “Candidate Communication” become easier to maintain when ownership and time spent are visible. Teams evaluating online timesheet software 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 Acas recruitment guidance; the useful test is whether the local method remains job-related, proportionate and explainable.

Before they apply

The full process: how many stages, what each involves, how long in total.

The salary range. Withholding it wastes everybody's time and is increasingly required.

And what the role actually involves, which the job analysis has already produced.

At application

Confirmation that it arrived.

When they will hear, as a date rather than "in due course".

And what happens next if they progress.

Before an assessment

Format, length, what is permitted, who will be present.

The criteria, in general terms. Candidates who know what is being assessed perform closer to their actual ability, which is what you want to measure.

Any preparation material, offered to everybody.

And the adjustment question, asked in the same words every time.

After an assessment

When they will hear.

Then actually tell them on that date, including if the answer is "still deciding", which is a complete and acceptable message.

Silence after a candidate has spent hours on an exercise is the single most common complaint in candidate surveys.

Rejection

Promptly. A fast no is a kindness.

Specific to the stage: rejecting somebody after a three-hour exercise with a template used for unsuccessful applications reads as contempt.

And with feedback where they invested significant time, which the feedback note covers.

The tone

Plain and human.

Not "we were impressed by the calibre of applicants" if you were not.

Not "we will keep your details on file" unless you will.

Candidates detect both, and the ones you rejected today are customers, referrers and future applicants.

Who sends it

A person with a name, where volume allows.

Automated is acceptable early and reads badly late.

Nobody should receive a system-generated rejection after meeting four of your staff.

What it costs you

A template set and somebody watching the dates.

A few hours of setup, then minutes per round.

Against a reputation that takes years to repair, which is what a visibly careless process produces in a connected labour market.

What to check

Is the full process published before application?

Do candidates get a date, and do you meet it?

Does anybody receive an automated rejection after meeting people?

And when did you last read your own rejection email?

The point

Publish the full process and the time commitment before application, give a decision date, and meet it..

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.