How to use a cognitive test without making it exclusionary

A cognitive test is used without being exclusionary when it’s one input among several and not a filter that decides on its own. It measures reasoning aptitude at a given moment —not a person’s worth or their future performance— so treating it as an automatic cutoff makes it exclusionary for no reason. Calibrating it to the role, reading it in context, and combining it with other signals is what keeps it fair.

The risk is easy to see: turning a score into a closed door. “Below 70, out” looks efficient and objective, until you reject someone who would have been excellent because they had a bad day, didn’t understand the format, or took the test in their second language. The problem is almost never the test; it’s how it’s used.

Why an automatic cutoff is expensive

The appeal of a rigid threshold is convenience: it sorts a pile of candidates in seconds. But a cognitive score isn’t a clean measure of ability. It’s affected by things that have nothing to do with the role —nerves, language, familiarity with tests, conditions of the moment. When that number filters on its own, those factors slip into the decision disguised as objectivity.

What’s more, reasoning aptitude is an input, not a predictor of success. Plenty of capable people score average on a test and excel on the job, because real work depends on motivation, team fit, and experience as much as on fast reasoning. A blind cutoff sees none of that.

Four practices to keep it fair

1. Calibrate the level to the actual role. Ask yourself how much reasoning the position really demands. Asking for more than necessary excludes capable people for no reason.
2. Use the result to sort, not to reject. If you need to prioritize volume, let the score help sequence your reviews, not eliminate people unseen.
3. Always combine it. Read it alongside the role’s competencies, experience, and the interview. An isolated signal carries little weight; a coherent set carries a lot.
4. Apply it under even conditions. Same instructions, same time, attention to factors like language. Fairness starts with how you administer it.

The right role: inform, don’t decide

Read well, a cognitive test opens questions for the interview (“how would you approach this problem?”) instead of closing the door before you know the person. The result is usually expressed in percentiles, which place someone against a reference group —not a “how much they know”— and that already signals it’s a relative position, not a verdict. The final decision stays with the team, weighing all the evidence.

In short

A cognitive test becomes exclusionary when a score filters on its own: it rejects capable people based on factors unrelated to the role and confuses an aptitude with a prediction of performance. To use it without making it a wall, calibrate it to the level the position demands, use it to sort rather than reject blindly, combine it with competencies and the interview, and apply it under even conditions. It’s an input, not a verdict. At Kokoro, cognitive ability is combined with the role’s competencies in a single assessment to support the decision —see how it works— or browse the library to see which tests fit your roles.