On this page: Key takeaways · What are knockout questions, and where do they go wrong? · How should each knockout answer be routed? · How do you audit your knockout rules in an hour? · What is the difference between missing and failed? · Which knockout questions are safe to automate? · What are the most common knockout mistakes? · What does routing to a person cost, and how do agencies handle it? · How Radius helps · The rule to take away · FAQ
Key takeaways
- Missing, unclear, an adjustment request and a technical failure are separate states from "no", and each needs a person.
- Audit one role's knockout rules in about an hour, then count how many routed candidates are hired.
- This blog covers configuration; the law on automated rejection is in our blog on human oversight in hiring.
What are knockout questions, and where do they go wrong?
Knockout questions screen out applicants who miss an essential requirement. The form asks "Do you hold a valid reach truck certificate?", and a rule in the applicant tracking system (ATS) moves anyone who does not answer "yes" to a rejected stage, often with an automatic email. At high volume that saves real time.
The problem is that "reject unless yes" treats a blank field, a failed upload, a dropped call and a confused answer exactly like a clear "no". Those candidates leave without anyone deciding that they should, and nobody knows how many could have done the job. Our view at Radius Hire is that the fix belongs in the design of the ATS, not in each recruiter's judgement.
How should each knockout answer be routed?
Route each answer by its state, not by whether it says "yes". Only a clear "yes" moves on without a human step.
| Answer state | What it looks like | Route | Owner and deadline (illustrative) |
|---|---|---|---|
| Clear yes | "Yes, I hold a valid reach truck certificate." | Next step: interview or document check | None needed here |
| Clear no on a written requirement | "No, I cannot work nights" for a role with nights in the job request | "Does not meet" list; a recruiter confirms and tells the candidate which requirement was not met | Recruiter, two working days |
| Missing | Blank field, failed upload, error, timeout or a call dropped before the question | "Needs a person": ask again by message or phone; report technical errors to the system owner | Recruiter, one working day |
| Unclear | "I had one, it expired, I am renewing it" | "Needs a person": one clarifying question | Recruiter, one working day |
| Adjustment request | The candidate asks for another format, more time or help | "Needs a person": offer the adjustment, then ask the same question | Recruiter, before any other step |
Set your own deadlines and give the "needs a person" stage a named owner, or it becomes a second rejected pile. To see a pipeline where nobody is rejected automatically, look at the Radius ATS.
How do you audit your knockout rules in an hour?
Take one high volume role and test every rule in four steps, with the vacancy, the job request and admin access to the ATS.
- List every rule (15 minutes). Include filters on distance, keywords and "years of experience". Note whether each one sends an email.
- Match each rule to a written requirement (15 minutes). If no line in the job request supports it, or the supervisor would hire someone who fails it, remove it.
- Test the other states (20 minutes). Submit test applications with a blank answer, a failed upload and an answer that is neither yes nor no. Any of these that ends in a rejection is a defect.
- Add the route and the count (10 minutes). Create the "needs a person" stage with an owner, then count each week how many candidates enter it, reply and are hired.
We know of no published figure for how many qualified candidates knockout rules lose, so your own count is the answer. For the rest of the process, use our one hour recruitment process audit. The principle behind this routing, that a person decides and can see the evidence, is set out in The Radius Papers 03: What CVs Miss.
What is the difference between missing and failed?
Failed means a clear "no"; missing means you do not know yet. A candidate whose certificate photo did not upload has told you nothing about the certificate, and rejecting her turns a gap in your data into a judgement about a person.
Gaps are routine in automated steps. In a field experiment with 70,884 applications for entry level customer service jobs in the Philippines, 7% of interviews run by an AI voice agent were aborted because the agent failed technically (Jabarian and Henkel, 2026). That is one firm, one type of job and interviews rather than forms, in a working paper not yet peer reviewed, but it shows that a process at volume produces incomplete records.
Registers have gaps too. The Dutch diploma register run by DUO does not include foreign diplomas, and covers diplomas from state funded MBO schools only from 2007 (DUO, checked 21 October 2026). A candidate who is not found may still hold the qualification: "not found" means "not checked yet".
Which knockout questions are safe to automate?
Let a rule sort only on questions that are clear, job related and actually answered. That means one question about one fact, tied to a written requirement the supervisor would not waive, with an answer you can read. Anything else is missing.
Never knock out on nationality (right to work is the question you need), and avoid proxies such as "native Dutch speaker". Under the Dutch Equal Treatment Act, a neutral looking criterion that particularly disadvantages people of a certain nationality or race is allowed only if it is objectively justified by a legitimate aim, with appropriate and necessary means (Algemene wet gelijke behandeling, articles 1 and 2). Ask about the task instead.
| Weak knockout question | Why it fails | Stronger version |
|---|---|---|
| "Do you have at least three years of warehouse experience?" | Drops someone with two and a half strong years | "Where have you driven a reach truck, and for how long?" Read by a person, never a knockout |
| "Are you flexible with working hours?" | Almost everyone says yes | "Can you work nights from 22:00 to 06:00, starting in November?" |
| "Upload your VCA certificate" as a required field | A failed upload becomes a rejection | "Do you hold a VCA certificate?" Yes, no, or "yes, but I cannot upload it now", routed to a person |
| "Are you a native Dutch speaker?" | A proxy, not a task | "Can you follow safety instructions given in Dutch on the floor?" with "not sure" routed to a person |
For the evidence on experience, see three years on reach trucks tells you less than you think; for shift questions, also tell candidates about the 05:30 start in the advert.
What are the most common knockout mistakes?
Most knockout mistakes turn a gap in the data into a rejection.
- Rejecting on a failed upload. Ask the question first and make the upload a separate step, so a failure creates a task.
- Rejecting on a register miss. Ask for the document; see checking certificates before you say yes.
- Counting an unasked question as "no". If the session ended first, the state is missing.
Illustrative example. At 22:00 a candidate applies for a reach truck role and answers "yes" to the certificate question, but her photo upload times out. Under a "reject if no file" rule, a rejection email reaches her at 22:01 and she applies elsewhere. Under a routed rule, her application waits in "needs a person", marked "certificate: upload failed", and at 08:30 a recruiter asks her to try again or bring the card. She is interviewed that afternoon. She holds the same certificate in both versions; only the second process finds out.
Under a “reject if no file” rule
- 22:00She answers “yes” to the certificate question; her photo upload times out
- 22:01A rejection email reaches her
- She applies elsewhere
Under a routed rule
- 22:00The same answer, the same failed upload
- Her application waits in “needs a person”, marked “certificate: upload failed”
- 08:30A recruiter asks her to try again or bring the card
- She is interviewed that afternoon
She holds the same certificate in both versions; only the second process finds out.
What does routing to a person cost, and how do agencies handle it?
It costs recruiter time, so keep the queue small and measured. Fix the causes: clearer wording, uploads that can be retried, fewer knockout questions. A growing queue tells you about your form; it is not a reason to switch automatic rejection back on.
Staffing agencies should agree the routing with each client at intake, because a rule copied from one client's role can enforce a requirement the next client never set. Record which requirements are essential and whether the agency or the client handles the "needs a person" stage.
How Radius helps
Radius Hire is the AI hiring platform for frontline roles. Radius never rejects a candidate on its own: a recruiter reviews the evidence, can overrule anything Radius presents and makes every hiring decision.
For each requirement, Match shows whether it is backed by a document or a check, rests only on what the candidate said, or is still missing, so a gap stays visible. Where the employer uses Radius Passport, the Passport checks identity and right to work with a trusted verification partner and records certificates with their expiry dates. Candidates are told at the start that the AI Interviewer is automated and that a person reviews the result. Radius is new, so this describes how the product works rather than claiming results.
The rule to take away
Knockout questions save time when they act only on a clear answer to a written requirement. Everything else is missing information that goes to a person with a deadline. Audit one role this week, add the "needs a person" stage and count what comes out of it.
