Time to screen

Time to screen is a narrower cousin of time to hire. It measures just the first stretch of the process: how quickly you find out whether an applicant is worth a closer look. It’s less widely tracked, but it’s often where the most time is lost.

What it includes

• Waiting to be reviewed. The application sits in a queue.
• Waiting to be invited. Someone has to decide to screen them.
• Scheduling. Finding a time that suits both sides.
• The screen itself. The call or interview.
• Write-up. Notes, a rating, a decision to move forward or not.

A worked comparison

Assume a candidate applies on Monday morning.

Phone screen path: The recruiter reviews applications on Wednesday, emails to schedule, and the candidate replies on Thursday. The first open slot is the following Tuesday. The call happens, and notes are written that afternoon. Time to screen: about eight days.

Asynchronous path: An invite goes out automatically on Monday. The candidate takes the interview on Monday evening after work. The recruiter reviews the result on Tuesday morning. Time to screen: about one day.

The interview is similar length in both paths. The difference is almost entirely waiting.

Why it matters most in volume

For hourly, retail and support roles, candidates often apply to several employers at once and take the first reasonable offer. A week-long screen can mean losing the best applicants before you’ve spoken to them. In high-volume hiring, time to screen is often the single biggest lever on time to hire.

How to measure it

• Record the application time and the time a screening result exists.
• Use the median, not the average. A few candidates who take a week to respond will skew an average.
• Track it per role and per month, so you can see whether changes help.

Pitfalls

• Counting only interview time. A 15-minute call that takes eight days to arrange is an eight-day screen.
• Fast screen, slow next step. Getting results in a day doesn’t help if they sit unreviewed for a week. Track the handoff too.
• Rushing reviews. A fast result is only useful if someone reads it properly.