TL;DR
Create a respectful process with clear instructions, relevant tasks, accommodations and human review.
Before you begin
This guide follows a candidate through an assessment-based hiring process, stage by stage, and asks what each stage looks like from their side of the screen. It covers the invitation, preparation, accessibility and adjustments, timing, the task itself, scoring, the outcome message and feedback. Each stage ends with something concrete you can change this week.
The most useful way to read it is with a fresh pair of eyes. Ask a friend or colleague who has never seen your process to go through it using only what a real applicant would receive. Note every point where they hesitate, ask a question or guess. Those moments are where good candidates drop out, and they are usually cheap to fix.
The examples are illustrative, and the legal and accessibility rules that apply to you depend on where you hire. Where a topic has its own detailed article, we summarise the decision it supports and link to it.
What makes a hiring process candidate friendly?
A candidate friendly hiring process is one in which applicants know what is being asked of them, believe the request is reasonable and can see a fair chance to show their ability. It is not about making assessments easy or removing standards. A demanding test can be entirely respectful if its purpose is clear, its length is honest and its conditions are the same for everyone.
Respect also produces better evidence. A candidate who understands the task, has the right equipment and is not worried about hidden rules performs closer to their real level. Confusion, anxiety about monitoring or an unexpected time limit adds noise to the result, which makes your decision harder rather than easier.
Four qualities run through every stage below: clarity about what will happen, relevance of each request to the job, access for people who work differently, and closure so nobody is left waiting. If a change you are considering improves one of these without harming the others, it is probably worth making.
Stage 1: the invitation
The invitation is the first real contact many candidates have with your process, and it sets their expectations for everything that follows. A short link with no context forces people to guess, and some will decide not to bother. A good invitation answers the obvious questions before they are asked.
What to include in an assessment invitation
- The role and why the assessment is part of the process.
- The tests involved, in plain words, and the total time including instructions.
- The deadline, with a date, time and time zone.
- The device and connection needed, such as a laptop for spreadsheet tasks.
- Which tools are permitted and which integrity settings are switched on.
- How to ask for an adjustment, with a named contact and a response time.
- What happens next and roughly when the candidate will hear back.
A hypothetical invitation
"Thank you for applying for the receptionist role. The next step is a 30-minute online assessment covering written English, scheduling scenarios and typing. Please complete it by 5 pm Eastern on Friday 14 March. A laptop or desktop works best. Please work alone; assistive technology is welcome. If you need extra time or another adjustment, reply to this email or contact Sam Lee before you start. We will let everyone know the outcome by Friday 21 March."
That message is under a hundred words and answers almost every question a candidate is likely to have. HireValid sends each candidate a signed, single-use invitation link that expires, so the message can focus on these details rather than on access instructions.
Stage 2: preparation and practice
Unfamiliar formats cause anxiety that has nothing to do with the skill being measured. Someone who has never seen a situational judgement question may spend the first few minutes working out how to answer rather than what to answer. A short chance to practise levels that difference.
Point candidates to a practice route in the invitation. The free sample test shows the HireValid question format, timer and navigation, and the practice tests section has longer sets for common test styles. The candidate information page explains what happens before, during and after an assessment, which helps people who are anxious about online testing in general.
Practice should be optional and should not use the real questions. Its purpose is to remove surprises about the format, not to let some candidates preview the content.
Stage 3: accessibility and adjustments
An accessible assessment measures the skill you care about rather than an unrelated barrier. A reasoning test that can only be completed with a mouse is partly a mouse test. A customer service scenario with a strict short timer is partly a reading speed test. Thinking about access early is cheaper than fixing it after a complaint.
Build accessible assessments by default
Several choices make a test usable by more people without any special request. Check that questions can be navigated with a keyboard, that text works with screen readers and magnification, that colour is never the only way information is shown and that instructions use plain language. Avoid time limits tighter than the job requires, and allow assistive technology unless there is a specific reason not to.
The HireValid accessibility statement describes how the candidate interface approaches these points. Review your own instructions and any custom questions with the same care, because the platform cannot fix an unclear question you wrote yourself.
Handle an adjustment request well
Some candidates will need something different: extra time, rest breaks, a different format or a conversation instead of a written task. In the United States, the United Kingdom and Canada, employers have legal duties around adjustments for disability, and the details depend on where you hire. Our guide to whether pre-employment tests are legal summarises the basics by country.
Operationally, three things matter. Publish the route where candidates will see it early, put a named person behind it who answers quickly, and decide in advance which adjustments you can offer without changing what the test measures. Ask only for the information you need to make the adjustment, and keep it separate from the hiring decision. Our help page for adjustment requests shows the route candidates see, and the glossary entry on accommodation explains the term.
When an adjustment is agreed, record it on the result so a reviewer does not misread extra time or breaks as unusual behaviour. An adjustment that is granted but then quietly counted against the candidate is worse than none.
Stage 4: timing
Time is the most concrete cost you ask candidates to pay, and they compare it with every other application they are making. A process that feels proportionate to the role keeps strong applicants engaged; one that feels excessive loses them, often without you ever knowing.
Set a total time budget per stage
Plan the time across the whole process, not test by test. The table below is a hypothetical budget for a mid-level administrative role.
| Stage | Candidate time | Who takes part | | --- | --- | --- | | Online assessment | About 30 minutes | Everyone meeting the basic requirements | | Structured interview | 45 minutes | A shortlist of five or six | | Short practical task | 30 minutes, live | Two or three finalists |
The early stage, which involves the most people, is the shortest. Longer requests come later, when each candidate has a realistic chance of an offer. If your first stage asks for more than about forty-five minutes, look hard at whether every part is needed then.
Give honest estimates and fair deadlines
Quote a time that includes reading instructions and moving between sections, not only the timed portions. Test the estimate yourself. Give a deadline of several days so people with jobs, caring responsibilities or different time zones can choose a good moment, and state the time zone explicitly.
Plan for interruptions
Connections drop and laptops restart. Decide in advance what a candidate should do if an assessment is interrupted, who they contact and whether you will offer a fresh attempt. Treat interruptions as practical problems to solve, not as suspicious events. Our guide to assessment integrity explains how to review integrity signals so that ordinary disruptions are not mistaken for misconduct.
Stage 5: a relevant task
Candidates are far more willing to invest time in a task when they can see why it matters. A scenario that resembles a real day in the job feels like a preview; a puzzle with no obvious connection feels like a hoop. Relevance is both a fairness question and a candidate experience question.
Start by describing the job in tasks, then choose the shortest assessment that shows the essential ones. The practical guide to pre-employment tests walks through that matching process, and the test library lists each test with its length and a sample question so you can check fit before inviting anyone.
For customer-facing roles, a good task blends accuracy with tone: does the candidate solve the problem and leave the customer feeling heard? Our article on designing a customer service assessment shows how to build a short written task around your own service standards and how to review responses consistently.
Scenario questions can be relevant or vague depending on how they are written. Useful ones supply enough context to make a real decision and offer options that differ in a meaningful way. Read our situational judgement examples to see how to write and score them.
Stage 6: consistent scoring and outcome checks
Candidates cannot see your scoring, but they experience its effects. Inconsistent review, where one reviewer is generous and another strict, or where rules change after results arrive, is unfair even if every individual decision seems reasonable at the time.
Decide before the round how scores will be used, how many people will move forward and how ties will be handled. Use the same criteria for everyone, and write down the reason for each decision in terms of the evidence rather than impressions. HireValid shows each candidate's results, percentiles and Integrity Score in one view, which helps reviewers compare like with like; the decision remains with a person.
After each round, check whether any group of applicants passed a stage at a noticeably lower rate than others. A common first screen is the four-fifths comparison of selection rates. With small numbers it is a prompt to look at the process, not a finding. Our article on the four-fifths rule explained walks through a hypothetical example and explains what to examine if a difference appears.
Stage 7: outcomes and feedback
Silence after an assessment is one of the most common complaints candidates make about hiring. They have given their time and want to know where they stand. A prompt, polite outcome message is the simplest way to show respect, and it costs very little.
Tell every candidate the outcome
Send outcomes on the date you promised, or explain the delay if you cannot. Unsuccessful candidates deserve a clear answer rather than an implied one. A hypothetical message: "Thank you for completing the assessment for the receptionist role. We have decided to move forward with other candidates whose results were a closer match for this position. We appreciate the time you gave, and we would welcome an application for future roles."
Decide what feedback you can offer
Some employers share a short summary of strengths and areas to develop; others offer a brief call to finalists. Whatever you choose, be consistent and do not promise detailed feedback you cannot deliver. Avoid sharing raw scores without context, because a percentile can be misread as a personal judgement rather than a comparison with a reference group.
Ask candidates about the process
Invite brief, optional feedback on clarity, length and any barriers, and keep it separate from the selection decision so people feel free to be honest. Two or three questions are enough: was the time estimate accurate, were the instructions clear, and was anything difficult for reasons unrelated to the skills being tested? Read the answers before the next round.
Candidate data and privacy
Candidates share personal information and work samples, and they want to know how both will be used. Tell them who can see their results, how long data is kept and how to ask for a copy or for deletion. The candidate privacy notice sets out how HireValid handles candidate data, and the help article on candidate data requests explains how those requests are handled.
Keep demographic information, where you collect it for fairness monitoring, separate from the information reviewers use to decide. Make it optional and explain why you are asking.
Bringing it together in a small team
A candidate-friendly approach does not need an HR department. In a small team, it usually comes down to three named responsibilities: one person owns candidate communication, one person reviews results against agreed criteria, and someone checks the process after each round. In a very small business these may all be the same person, which makes writing things down even more important.
If you are building the wider process from scratch, our guide to the hiring process for small businesses covers the stages before and after assessment, from the job advert to the offer.
Your candidate journey review
Draw the journey as seven boxes: invitation, preparation, adjustments, assessment, review, outcome and feedback. Under each box, answer the questions below. Complete it once before your first round and again afterwards, using what candidates told you.
- What does the candidate know at this point, and what are they likely to wonder?
- Who can they contact, and how quickly will that person reply?
- How long does this stage take them, honestly measured?
- What could stop someone with a disability, an older device or a busy schedule from continuing?
- What will the candidate hear when this stage ends?
Then ask your tester to go through the real process without help. Compare their experience with your boxes and fix the gaps, starting with anything that confused them more than once.
Final checks before inviting candidates
- Does the invitation state the time, deadline with time zone, tools allowed and adjustment contact?
- Is there an optional way to practise the format?
- Can the assessment be completed with a keyboard and common assistive technology?
- Is the total first-stage time proportionate to the role?
- Can every candidate see why the task relates to the job?
- Are scoring rules and shortlist size decided before results arrive?
- Will every candidate receive an outcome on a stated date?
If you can answer yes to each, your process is in good shape. Share the candidate information page with applicants so they know what to expect.
What is a respectful hiring process?+
One that tells candidates what to expect, asks only for relevant work, gives everyone the same conditions, makes adjustments easy and responds promptly with a clear outcome, whether or not the person is hired.
How do I make assessments accessible?+
Offer accommodations such as extra time, screen reader compatible formats and breaks; allow assistive technology; avoid unnecessary time pressure; and tell candidates how to ask for adjustments before they start.
How quickly should I tell candidates the outcome?+
As soon as the decision is made, ideally within a few days of their last stage. A short, polite message to unsuccessful candidates protects your reputation and helps them plan.
Does a candidate friendly process slow hiring down?+
Usually not. Clear instructions and short, relevant tests reduce drop-outs and repeated questions, and prompt communication keeps good candidates engaged, which often shortens time to hire.