Three Kinds of No Go, and the Sentence Each One Leaves

The message I get most often from hiring managers during a pilot is not about speed or cost. It is some version of “why did we reject this one?” It usually arrives on a Friday evening, with a candidate’s name and a line about a good college or a strong last employer. The answer that manager wants is not “the AI decided.” It is a sentence they can repeat to their own boss on Monday.

Every AI screening rejection reason in HireQwik comes from one of three routes, and each route leaves a different kind of sentence behind. Once your team can tell the three apart at a glance, the Friday message takes two minutes instead of a lost weekend. This post goes through each route, what its reason looks like in the product, how to turn it into a reply for three different audiences, and the few cases where a No Go should make you reopen the file rather than close it.

What a No Go reason looks like in HireQwik

A No Go reason in HireQwik is the recorded cause behind a post-call reject: a failed knockout question with the candidate’s quoted answer, a communication score under the job’s floor with the threshold named, or an overall score below the job’s On Hold line. Each is stored with the verdict and visible to the recruiter.

The verdict engine checks those routes in a fixed order, knockout first, which the verdict tier explainer covers in full. Here the question is narrower. Once a candidate is No Go, what exactly is written down, and what can you honestly say about it?

Knockout No Go: the reason is the candidate’s own answer

Knockout questions run first in the call. They check hard facts that the job description marks as non-negotiable: shift timing, work location, notice period, a required licence. If an answer fails, the agent wraps up the call politely right there, and the verdict is No Go.

What makes this route easy to defend is what gets stored alongside it. The reason reads “Knockout failed”, then the question identifier, then the candidate’s own words, trimmed to about 80 characters. In the inbox that appears as a small “KO” chip; hover over it and the quote shows. So a reply to the Friday message might be: “She was asked whether she could join within 30 days and said her notice period is 90 days and cannot be bought out.” That is a fact about the role’s needs, not an opinion about the person.

Two cautions. First, a knockout is only as fair as its question. If “must relocate to Pune” was one manager’s preference rather than a real requirement, the knockout is enforcing a preference. Review the knockout list whenever a job description changes. Second, the quote has to exist in the transcript. Since August 2026, when the quoted answer cannot be found in what the candidate actually said, the engine does not issue a No Go at all; it holds the candidate for review. That safeguard has its own story, told in the hallucination check post. The candidate’s side of the same moment is in the knockout rejection explainer.

Communication-floor No Go: the reason names a threshold

The second route only exists on jobs where HR switched it on. A communication floor says: below this communication score we will not move forward, whatever the other dimensions show. For a voice-heavy role such as inside sales, customer support or admissions counselling, that is usually a rule the hiring manager asked for in the first place.

When the floor fires, the verdict carries a plain line stating that communication fell below the campaign threshold, with the number in brackets. The default threshold is 4.0 out of 10, and each job can raise or lower it.

The defensible reply here starts with the rule and then moves to evidence. “For this role we set a minimum communication score of 4 out of 10 before launch. Her score was 3.5. The scorecard notes say her answer to the objection-handling question trailed off without a clear point.” Then offer the recording. A manager who listens to 90 seconds of the call almost always either agrees or tells you the floor is set wrong for this role, and both outcomes are worth having.

The communication score blends two halves: what the transcript shows and how the voice sounded. To see which half pulled a score down, reviewing an AI interview communication score shows where to look.

Score-band No Go: the reason is spread across the job’s dimensions

The third route is the least dramatic and the most common. No knockout failed and no floor fired; the candidate’s overall score simply landed under the job’s On Hold line. On the default weighted path that line is 4.5 out of 10. On the points rubric it is 6.0 out of a 10-point total.

This reason is harder to put in one sentence, because it is a sum. The honest reply names the weakest dimensions rather than the total. “He scored low on the two role questions, especially the one about a delayed customer delivery, where he described how he would feel but not what he would do.” The per-dimension notes on Interview Details are written to support exactly that kind of sentence.

A worked example makes this concrete. On a points job, the ten available points split as 3, 3 and 2 across the core questions, with the final 2 reserved for communication. Suppose an invented candidate earns 1.5 on the first question, 1 on the second, 1.5 on the third and 1.5 on communication. The total is 5.5, under the 6.0 line, so the verdict is No Go. Read the breakdown and one number stands out: 1 out of 3 on the second question, the weakest share of any budget. That is where the reply starts. “His answer on handling an angry customer stayed general; he said he would stay calm but gave no example or steps.” Two sentences, one piece of evidence, and nothing about the total.

What you should avoid is “he scored 4.2, so he is a weak candidate.” The score describes 15-20 minutes on a given day against a given rubric. It is evidence about one conversation, not a judgement on the person, and the words you choose should respect that line.

Turning each HireQwik No Go reason into a reply

Different people ask “why?” for different reasons. Here is how I would phrase each route for the three audiences who ask most:

HireQwik does not message the reason to the candidate. That call belongs to the employer, made by the recruiter running the drive. If a hiring manager wants to see the evidence without a login, a read-only scorecard link is safer than forwarding screenshots around.

The legal column is not theoretical. The EU AI Act treats AI used in recruitment as high-risk and, in Article 86, gives people affected by such decisions a right to a clear explanation of the system’s role in them. The UK’s data regulator sets out similar expectations for automated decision-making. Even where neither law applies to a drive in India, both describe what a good explanation contains, and your own legal team will ask along the same lines. The fuller list of what they tend to request is in AI hiring audit trail questions.

When a No Go reason should make you reopen the file

Most No Go rows can close on the reason alone. A few patterns deserve a short listen first:

1. A floor reject on a call with an audio flag. When a recording is flagged for low signal-to-noise or mostly silence, speech analysis is dropped from communication scoring and the evaluator is told to prefer On Hold over No Go on communication grounds. But a job with the floor enabled can still produce a No Go from the transcript-only score. If you see both together, listen. What happens to the score with poor audio explains the switch.
2. A score reject a fraction under the line. A 4.4 against a 4.5 cut-off is a coin toss, not a finding.
3. A sharp split between resume and call. On jobs using the newer decision matrix, a lightning chip warns that what the resume promised and how the call went point in opposite directions. Read the summary before deciding.
4. A role where you later hired someone the screen rejected. HireQwik’s outcome report counts that miss on its own line, the hired No Go, because one of those says more about your rubric than a hundred correct rejects.

A regular spot check of the reject pile, the habit described in the No Go audit, catches what this list misses. Calls that stopped early for technical reasons should not be in the No Go pile at all; the incomplete interview guide covers how those are flagged instead.

Before launch: make every future No Go explainable

The easiest rejection to explain is one you planned for. Most of the Friday messages I see could have been answered in a line if someone had spent twenty minutes on the job before the first invite went out. Here is the checklist I walk pilot teams through:

1. Tie each knockout to a sentence in the job description. If a knockout checks night-shift availability, the JD should say the role works nights. A knockout with no matching line is the hardest reject to defend, because the candidate was never told.
2. Decide on the communication floor per role, in writing. Turn it on for roles where speaking is the job, leave it off where it is not, and note who agreed. When the floor fires later, “the hiring manager asked for this on 12 September” is a much better start than “it was on by default”.
3. Read the bands out loud. Know where On Hold ends and No Go begins for this job, and whether it uses the weighted average or the points rubric. You will be quoting these numbers.
4. Name who answers the “why” messages. One person per drive, usually the recruiter running it. Replies from three different people in three different styles are how inconsistent explanations start.
5. Agree the candidate reply template before you need it. Short, job-related, no scores. Writing it calmly in advance beats drafting it under pressure after a complaint.

None of these steps changes how the AI scores a single call. They change whether the reason it records is one your team can stand behind.

What a No Go reason will not tell you

It will not tell you the candidate is unemployable, or even weak in general. It will not give you an accuracy percentage, because we do not publish one; we are still calibrating, and one headline accuracy number for screening hides more than it shows. And it will not replace the recruiter’s own decision, which HireQwik records separately from the AI’s verdict, as described in how the recruiter’s call is stored.

What it will do is give you a traceable cause for every reject. That covers most Friday messages. The ones it does not cover are exactly the ones a human should be answering anyway.

Practise on your last drive

Sign in to HireQwik, open the Screened tab for your latest role and filter the verdict to No Go. For ten rows, write the one-sentence reason you would give a hiring manager, using only what is on screen. If a row stumps you, that is the row to listen to, and possibly a sign the job’s rubric needs work. We are happy to go through it with you: get in touch.