Most writing about AI screening is written for the people who buy it. It covers time saved, reach and cost per hire. The person on the other end of the process rarely gets a paragraph, even though they are the one filling in the form.

This post is about that person. It pulls together what applicants in high-volume hiring tend to run into, and what a screening process can do about each part. It is drawn from the research on candidate experience and from how Yardstick customers run their openings. It is not a survey, and there are no industry percentages in it.

The application starts on a phone, on a break

Picture the applicant for a warehouse picker role or a night care assistant shift. They are not at a desk. They found the ad on their phone, and they are applying in the fifteen minutes they have between tasks.

Three things break an application in that setting:

• A form that asks for a CV upload, when the applicant does not have one saved on their phone, or at all

• A session that times out and loses every answer when the break ends

• Questions written for an office role, asking about career goals rather than shifts and certificates

The first one matters most. Plenty of people who are good at shift work have never needed a CV. A form that demands one filters them out before anyone has read a word, and nobody on the hiring side decided that it should.

A structured screen can start somewhere else. The applicant answers a short set of questions about the work itself: which shifts they can cover, which certificates they hold, how they handled a specific situation on the floor. Harbourline Freight used five questions per role. That fits inside a break, and it describes the job instead of the paperwork.

Answering in the language you think in

A lot of high-volume work is done by people whose first language is not the language of the job ad. That is ordinary in logistics, care and hospitality, and it is often fine for the job itself. It is a problem for a written application, because the application measures fluency in writing whether or not the role needs it.

When the interview agents in Yardstick ask their questions, they ask in the language the applicant applied in. The answer is scored against the same rubric as everyone else’s. Vessik runs this across six markets with one rubric and one shortlist.

There are two limits worth stating. First, if the role genuinely needs a working language, say so in the brief and test it directly. Hiding a language requirement inside a writing test is unfair to the applicant and unclear to the reviewer. Second, answering in your own language only helps if the reviewer can see what was said. Every rating in Yardstick links to the answer it came from, so a reviewer can read the passage that earned the mark.

Hearing back at all

Ask applicants in volume roles what they remember about a bad process and silence comes up early. They applied, and nothing happened. There was no rejection and no date, only a quiet inbox and a job that was eventually filled by someone else.

Silence is rarely a decision. It is what happens when four hundred applications arrive for one role and the reading stops when the calendar runs out. The people at the bottom of the pile were never assessed, so there is nothing to tell them.

Reading everyone changes that. When every applicant has been read against the brief, every applicant has a status, and a status can be sent. Tarnow screened a thousand seasonal applicants and every one of them heard back in the first round. That was not true the year before.

Hearing back has a second half, which is hearing back in reasonable time. At Harbourline the median wait from application to first interview came down to two days. For someone choosing between three shift jobs this week, that is often the difference between accepting yours and accepting another.

A few habits make the reply worth receiving:

• Say what stage the application reached, in plain words

• Give a date for the next step, or say plainly that there will not be one

• Offer a route to ask why, and make sure someone answers it

Knowing a person decides

Applicants are increasingly aware that software reads their application. What worries them is not usually the reading. It is the idea that software made the decision, and that nobody could explain it if they asked.

Yardstick screens and recommends. It does not select, reject or decide. A named person on the hiring team approves every send and every decision, and that approval is recorded with the reviewer and the note they left.

That record matters to the applicant in two ways:

1. They can be told. Disclosure to the candidate is built into the flow, so the applicant knows a screening system was used before they answer a question.

2. They can ask. When a declined applicant asks why, the team can answer from the record: which criteria, which answers and which person. Harbourline answered those requests in writing within a day.

“People asked if a computer had turned them down. Being able to say no, and show who read their answers, ended most of those conversations kindly.”

Recruitment lead, Tarnow

What this asks of the team

None of this happens by switching a tool on. A screening process that treats applicants well is mostly a set of decisions the hiring team makes in advance.

Write the brief around the work, so the questions an applicant sees are about shifts and certificates rather than a CV they may not have. Decide which language the job needs, and test only that. Keep the reply templates short and honest. Make sure the person approving a shortlist has time to read the reasoning rather than just the rank.

Where law is involved, such as disclosure duties under the EU AI Act or local rules on automated decisions, take the specifics to your own counsel. This post describes practice. It is not legal advice.

The applicant never sees your pipeline or your scorecard. They see a form on a phone, a question in their language, a reply in their inbox and a name at the bottom of it. Those four moments are the whole of their experience, and each one is something you can design for.