Submit-to-interview ratio is the share of candidates a recruiter presents to a hiring manager who then get scheduled for an interview. It measures submission quality and how well recruiter and manager agree on the bar. Agencies, RPO teams and internal recruiters track it to catch a broken intake brief early.
Divide the number of submitted candidates who received an interview by the total number submitted in the same window, then read it as a ratio or percentage. The window matters: a candidate submitted late in a month may not be scheduled until the next one, so most teams measure by submission date and allow the cohort to mature before judging it. Define 'submitted' once and enforce it. In some teams a submission is a formal packet sent to the manager; in others it is any profile dropped in a chat thread. An [applicant tracking system](/ats) with a distinct submission stage removes that ambiguity, because the timestamp is created by the workflow rather than remembered afterwards. Segment by requisition and by manager before drawing conclusions.
A low ratio is almost always an intake problem, not a sourcing problem. The recruiter found people, wrote a case for them, and the manager said no before spending an hour in a room. That pattern points at a role brief that never got specific: must-haves that were really nice-to-haves, a title that maps to three different jobs, or a compensation band the market does not support. Before rewriting a search string, sit with the manager and score three rejected profiles out loud, asking what specifically disqualified each one. Those three conversations usually surface the real bar faster than another week of sourcing. Rebuilding the [job description](/job-descriptions) around that bar is the fix; more submissions against a wrong brief just repeats the loss.
Three things quietly wreck this number. Managers who interview nearly everyone push it toward the ceiling, which looks like excellent submissions and is actually an absent filter. Recruiters who only submit obviously safe profiles also push it up, while quietly holding back the unconventional candidate who would have been the strongest hire. And the definition of a submission drifts: profiles shared informally never enter the count, so the denominator shrinks and the ratio flatters everyone. Sample size compounds all three. A single requisition with twenty submissions can swamp a quarter, so a team ratio that moved sharply is often one manager's behaviour rather than a trend. Read it alongside interview-to-offer ratio and downstream quality, never on its own.
Use it to schedule a calibration conversation, not to grade a recruiter. When the ratio for one manager sits materially below the rest of the team, the action is a joint review of recent submissions: the recruiter presents, the manager rejects or accepts live, and both write down the reason in the same words. Repeat after ten profiles and the gap usually closes. When the ratio is high but offers are rare, the problem has moved downstream and belongs to the interview loop instead. Agency and RPO teams often contract on this number, which makes definition discipline commercial rather than academic. Practical guidance on running that first alignment meeting sits in the [hiring process guides](/how-to-hire), and structured question sets help managers explain rejections consistently.
Pitch N Hire unifies sourcing, screening and hiring decisions on one AI-native platform. Book a quick demo on your real roles.
Prefer to talk? Book a demo · View pricing
Free 1-user plan · No credit card · Talk to a real hiring expert
See your true cost-per-hire and how much Pitch N Hire could save you — our free Recruitment ROI Calculator gives you the numbers in under a minute. No signup required.
Open the free ROI calculatorPrefer a tailored walkthrough on your real roles? Drop your work email:
★ Free 1-user plan · No spam · Talk to a real hiring expert
