Candidate experience checklist for every hiring stage
Twenty-nine things that are either true of your hiring process or are not, from the job description to the first month in the job. Work down it, tick what you already do, and the gaps are your list. Part of the wider candidate experience platform.
Hari SContent MarketerBuilds narratives on employee engagement, and on the hiring experience that comes before it.What a candidate experience checklist is for
A candidate experience checklist is an operational list, not a strategy document. Its job is to turn a vague ambition, treat candidates well, into a set of specific things that are either true of your hiring process or are not.
Most hiring teams already know their process has weak points. What they usually cannot say is which weak point, at which stage, costing them which candidates. A checklist is the cheapest way to find out, because working through one takes an afternoon and needs no data at all.
The test for every item below is the same: could someone outside your team verify it from the candidate's side? If the answer is no, it belongs in a strategy deck rather than on a checklist. For the standard behind each item rather than the item itself, the candidate experience best practices set out what counts as doing it well.
The checklist, stage by stage
Twenty-nine items across five stages. Work down it and tick what is already true. The gaps are your list.
Before anyone appliesThe part candidates judge first and teams check last
Application and acknowledgementThe largest source of complaint in candidate feedback
Screening and interviewsWhere fairness scores are won or lost
Offer and decisionThe stage most often left unmeasured
From offer to day oneThe gap where accepted candidates quietly change their minds
Nothing here is stored or sent anywhere. Ticking is for your own use while you read. If you would rather take the list into a meeting, the printable version below has the same twenty-nine items with empty boxes.
Take the checklist with you
A one-page printable version to work through with your hiring team. No email, no form.
The four items almost everyone fails
Across candidate feedback the same gaps recur, and they are rarely the ones teams expect. What follows are the four clearest examples of a poor candidate experience, in rough order of how often they show up:
1. Silence after applying
The most common complaint in candidate feedback is not rejection. It is never hearing anything at all, the thing candidates call being ghosted. This is also the cheapest item on the list to fix, and it affects the most people, because most applicants never reach an interview.
2. The wait after the final interview
Candidates accept that decisions take time. What they do not accept is a week of silence at the exact point they are usually holding another conversation open. This is the stage where offers are lost to nothing more than slowness.
3. Interviewers who have not read anything
Being asked to repeat your CV to the third person in a process reads as disorganisation, and it is the single strongest driver of a poor fairness score.
4. The gap between acceptance and day one
Recruiting stops measuring at acceptance and onboarding does not begin until day one, so the weeks in between belong to nobody. They are also when a counter-offer lands, and a candidate who has heard nothing from you since the paperwork is much easier to win back.
How to audit your process against it
Reading the list tells you what your process is supposed to do. A candidate experience audit tells you what it actually does. Three passes, in order:
Apply for your own role
On a phone, with a personal email address, all the way to the confirmation screen. Time it. Note every field you have to fill twice. This takes twenty minutes and finds more than any workshop.
Read your own rejection email
Out loud. Most fail this immediately: they are addressed to nobody, explain nothing, and close a door that was never opened. If you would not want to receive it, do not send it.
Ask the people who went through it
The first two passes are your view of your process. Only the third is the candidate's. A short candidate experience survey at each stage, built from the candidate experience survey questions that stage calls for, turns the checklist from an opinion into evidence, and it covers the people you rejected as well as the ones you hired, which is where most of the honest answers are.
The third pass is the one you cannot do on your own
CultureMonkey runs the stage surveys and reads the results back by stage, recruiter and hiring manager, so the audit stops being your opinion of your process.
How to tell the checklist worked
A checklist without a measurement is a list of good intentions. Three things worth watching once you have made changes:
- One score, cut by stage. A single overall figure hides everything. The same score broken down by application, interview and offer is what shows you the stage that is dragging, and cutting it again by recruiter and by hiring manager shows you who owns the fix. The candidate experience metrics covers what to track.
- The same question, quarter after quarter. Changing the wording resets your history. Ask it identically, and a movement is a real movement rather than an artefact.
- Your own history, not an industry figure. There is no dependable external candidate benchmark, whatever a vendor tells you. The honest comparison is this quarter against last. candidate NPS explains why in more detail.
Change one thing at a time. Teams that fix five items at once, then see the score move, cannot say which fix did it, and so cannot repeat it.
Once you know which stage is weakest, improve candidate experience covers where to start, and the candidate experience software covers whether you need to buy anything at all.
Candidate experience checklists, answered
What should a candidate experience checklist include?
Items that can be verified from the candidate's side, at every stage: whether a job description says what the person will actually do, whether the application takes under ten minutes, whether every applicant gets an acknowledgement with a date, whether interviewers have read the CV, whether the offer decision arrives when it was promised, and whether contact continues between acceptance and day one. Anything that cannot be checked from outside your team belongs in a strategy document rather than on a checklist. The full list on this page runs to twenty-nine items across five stages.
How often should we run through it?
Once a quarter is enough for most teams, and it takes an afternoon. Run it more often than that and you are auditing faster than you can change anything; run it annually and process drift goes unnoticed for months. The exception is after a change to your ATS, your careers page or your interview loop, when it is worth re-checking the stages that change touched.
What is the single highest-impact item?
Acknowledging every application within a day, with a date by which the candidate will hear. It is the most common complaint in candidate feedback, it affects more people than any other item because most applicants never reach an interview, and it requires no change to how you interview or decide. It is close to free and it removes the largest single source of frustration.
Do we need to include candidates we reject?
Yes, and skipping them is the most common way this exercise misleads. Almost everyone who touches your hiring process is rejected by it, so the reputation your employer brand carries is mostly built by people who did not get the job. They also apply again and talk to other candidates. A process audited only against successful hires is an audit of your best case.
Is there a benchmark we can measure against?
Not a dependable one. Published candidate experience benchmarks vary widely by source, industry, hiring volume and how the question was asked, so a number lifted from a report is rarely comparable to your own hiring. The measure that works is direction against your own baseline: whether this quarter beats last, whether the offer stage trails the interview stage, whether one recruiter's cohorts differ from the team's.
How is this different from a candidate journey map?
A checklist asks whether specific things are true. A journey map records what the experience was like at each stage, drawn from what candidates reported. The checklist is what you work through to fix a process; the candidate experience journey map is what tells you which part to work through first.