Two words you've almost certainly used as synonyms in a briefing call or a job spec conversation. They're not the same thing.
Pre-screening and screening are different actions at different points in the funnel. Mixing them up costs you time, money and predictability in your pipeline.
Pre-screening is the eligibility filter. It runs at the point of application, checks non-negotiables, and answers one question: does this person meet the minimum criteria to be considered at all? Right to work, location, shift availability, required licences. A no on any of them ends the application there.
Screening is the depth check. It runs after the eligibility filter and asks whether a candidate who clears the basics is a good fit for the role. Skills validation, motivation, communication, availability for specific shifts or travel, and any role-specific capability questions.
Separate them by decision point. Pre-screening decides whether someone enters the process. Screening decides whether someone reaches an interview.
The NPSA describes the underlying job in its 2023 employment screening guidance: screening "seeks to verify the credentials of job applicants and to check that they meet preconditions of employment". Preconditions. That's the pre-screening layer.
Before. And most teams do it after.
The usual sequence is that a candidate applies, the full application lands in the ATS, and a recruiter then works through eligibility questions that should have been answered before the candidate hit submit. That's post-screening, whatever anyone calls it.
Put the eligibility check at the moment of application and reserve structured screening for candidates who have already cleared the basics. Fewer unqualified applications reach your recruiters. The work those recruiters do is worth more, because every candidate they see has already passed the minimum bar.
Which is where reducing time-per-hire actually begins. Not in the interview stage. In what you let through before it.
For most UK and European roles, pre-screening covers four things.
These are knock-out questions in the strict sense. A single no ends the process at that point. No scoring, no weighting, no judgement call.
On frontline and logistics roles, putting these questions in front of candidates before the full application changes what reaches the recruiter's desk.
Once a candidate clears the eligibility bar, screening decides whether they're worth an interview slot.
A human can sit in this stage. A short structured call, a video response, a scored questionnaire. Pick whichever format your team will run consistently, because consistency is what makes the output comparable: every candidate for the same role, assessed on the same criteria.
Screening automation handles the repeatable, binary work well. Knock-out questions, right-to-work flags, licence confirmations. None of it needs judgement and none of it needs a recruiter's time.
What automation cannot do is stand in for qualification. A candidate who clicks into a flow and abandons it hasn't been screened. A candidate who answers yes to a licence question without that licence being verified hasn't been qualified. Completion is the whole distinction.
Which is the catch with recruitment technology platforms priced per click or per application. You're buying traffic. If the traffic doesn't turn into interview-ready candidates, that cost is yours.
The Information Commissioner's Office sets a narrow gate. Its guidance, updated in November 2025, states that you "should only do pre-employment vetting where you are under a legal obligation (eg to perform right to work checks), or you can identify significant and particular risks to the employer, clients, customers, or others".
In practice that means four things.
Teams operating across several European jurisdictions get the same answer from GDPR. Purpose limitation and data minimisation govern everything you collect before a candidate is hired.
This is a summary of how the guidance reads, not legal advice. Have employment counsel review your question set before it goes live.
Stage one runs at the point of application. A short mobile-first flow, four to six questions, covering the knock-outs. Candidates who pass move forward, candidates who don't get an automated response, and your ATS never sees the second group.
Stage two runs after the eligibility pass. Structured screening questions or a short call covering capability, motivation and practical fit. Define the pass outcome before the campaign starts, so everyone who clears stage two has met the same bar.
The ATS only receives candidates who completed both. That's the difference between an application funnel that converts and one that generates inbox volume.
A two-stage process should move four numbers.
Track these per role type. The right criteria for a warehouse operative aren't the right criteria for a care worker or a retail supervisor, and an aggregate number hides that completely.
Qualify is the pre-screening layer described above, built as product. It replaces the traditional application form with a mobile-first screening flow that runs your knock-out questions before a candidate reaches the ATS, checking availability, intent and role fit. Only candidates who pass every check continue.
The flows come in two shapes. Apply Flows are gamified and mobile-first. Lead Forms sit inside the social channel itself, so the candidate never leaves the feed to apply.
Completion is what makes the difference, and it's the reason this sits before the ATS rather than inside it. Wonderkind puts drop-off on traditional forms above 70%, and reports five times higher completion through these flows.
Upstream, Attract turns your vacancy list into always-on job ads across Meta, TikTok and Snapchat, so the screening flow has traffic worth filtering.
For teams hiring at scale in logistics, manufacturing and retail, moving the filter to the point of application changes what reaches the recruiter, and changes what the recruiter's time gets spent on.
Depends what you ask on it. Right to work, location and shift availability make it pre-screening. Motivation, capability and fit make it screening. Most calls billed as pre-screening are doing both at once, which is the argument for putting the knock-out questions at the top of the call and keeping them separate.
Technically, in that it happens before recruiter review. In practice it's a weak substitute for structured knock-out questions, because it depends on candidates describing themselves in the right words rather than answering a specific eligibility question directly.
Before you make the hire. That's a legal requirement in the UK, and the civil penalty runs to £60,000 per worker. Asking a candidate at the point of application whether they have the right to work is reasonable for pre-screening purposes. The formal documentary check belongs before the contract is issued.
Background checks, meaning DBS, references and credit history, are a separate stage that usually follows a conditional offer. Screening as described here happens before the interview decision. ICO guidance covers both: collect only what's necessary and proportionate for the decision you're making at that stage.
Four to six. Beyond that you start losing candidates who would have passed, because every extra question costs you completions. If you're writing a tenth, some of them are screening questions rather than knock-outs.
Want to see what moving the filter forward does to your own numbers on a live role? Book a demo and we'll walk one of them through with you.
