How to improve your submittal-to-interview ratio

The submittal-to-interview ratio is interviews scheduled divided by candidates submitted, and it tells you whether your submittals are converting — but it does not tell you why they are not. The fastest way to improve it is to break it down by stage (intake, screen, submittal, client) and fix the specific stage that is failing, rather than writing better submittals across the board when the real problem is somewhere else in the funnel.

Recruiting agency metrics defines this ratio and several others with formulas; this page assumes you already know the formula and focuses only on diagnosis and fixes. If you have not yet defined how you count "submitted" and "interview" the same way every time, start there first — a ratio measured inconsistently cannot be improved reliably.

What the ratio measures, and its blind spot

A submittal-to-interview ratio answers "of the people I sent, how many got a conversation." It cannot tell you on its own whether the problem is the candidates you chose, how you presented them, how fast the client responds, or the client's own bar being unclear. Two desks can post the identical ratio for opposite reasons — one because submittals are weak, the other because the client is simply slow and disorganized — and the fix for each is completely different. Break the number down before acting on it.

Diagnose before you fix: break the ratio down by stage

Tag each non-interview outcome with the stage it traces back to for a month. A pattern will usually emerge fast — most desks find one stage accounts for the majority of stalled submittals, not an even spread across all four.

Segment by client and by recruiter before you segment by stage

Run the stage breakdown separately for each client and each recruiter before drawing conclusions about the desk as a whole. A single unresponsive client can pull a desk-wide average down while every other client converts normally, and a single recruiter working an unusually hard search can look like a performance problem when the real cause is the search's difficulty. Look at the distribution, not only the average — one client at 5% and four clients at 35% is a very different situation from five clients all sitting around 20%, even though both can produce the same overall number.

The five most common causes and the fix

Worked example: the cost of a low ratio

This is why the ratio is worth tracking even though it is not a client-facing number: every percentage point improvement is recruiter time recovered, not just a better-looking report.

Fixing it at intake

Most submittals that stall trace back to an intake gap, not a submittal-writing problem. Before the next round of submittals on a role that has already produced one or two non-interview outcomes, go back to the hiring manager with the specific candidates who did not convert and ask directly: "what was missing." Their answer, repeated across two or three candidates, is usually more precise than the original intake notes and should update your must-have list for the rest of the search. See intake meeting questions for the fuller list to run at the start of a search.

Fixing it at the submittal itself

A submittal that restates the resume instead of adding what the screen learned is the single most common quality problem behind a low ratio. Each candidate reason needs to answer a specific must-have with evidence from the call, not an adjective — a tool like Interview Signal that produces a submittal summary with quotes checked against the transcript removes the guesswork of which detail to include. If your submittals do not already follow this structure, start with the candidate submittal template, which includes a filled example and a pre-send checklist.

Fixing it on the client side

When the submittal quality is solid and the ratio is still low, the bottleneck is often the client, not you. Track median time from submittal to any client response, per client. A client who reliably takes two weeks to open a submittal needs a different cadence: a heads-up call before submitting ("I'm sending you someone strong today, can I get five minutes on Thursday"), rather than relying on email alone. If a client's non-response rate is high across several recruiters at your agency, that is a service-level conversation, not an individual performance issue — see how to present candidates to clients for handling that conversation and for when to call instead of email.

Setting an expectation with a new client early

For a client you have not worked with before, agree a response-time expectation before the first submittal goes out, not after the third one stalls. A short line in the intake meeting — "when I send someone strong, when can I expect to hear back, even if it's a no" — sets a benchmark you can refer back to later without it sounding like a complaint. Clients who resist naming any timeframe at all are worth flagging early as likely slow responders, so the desk can plan submittal pacing accordingly rather than being surprised by it three roles in.

A tracking template

Submittal tracker — [Client / Role]
Date submitted: ____   Candidate: ____
Must-haves mapped in submittal: [ ] Yes  [ ] No
Follow-up call/email at 48 hrs: [ ] Done
Outcome: [ ] Interview scheduled  [ ] Declined — reason: ____
          [ ] No response by [date]

Monthly rollup
Submittals sent: ____   Interviews scheduled: ____   Ratio: ____%
Stalled at: intake ___  screen ___  submittal ___  client ___
Top cause this month: ____
One change to make next month: ____

The "stalled at" line is the part most trackers skip, and it is the part that turns a lagging indicator into something you can act on before the next batch of submittals goes out.

Checking that a rising ratio isn't hiding a new problem

A ratio that improves because submittals got more conservative is not actually an improvement. Watch fill rate and average time-to-fill alongside the ratio: if the ratio rises while fill rate falls or searches take longer to close, the likely cause is that only "safe" candidates are being submitted, and harder-to-place but strong candidates are being held back. The ratio is one signal among several, not the only measure of whether the desk is performing well.

A simple guard against this: once a month, pull the two or three candidates each recruiter chose not to submit on a competitive role and ask why. If the reasoning consistently points at genuine must-have gaps, the ratio improvement is real. If it increasingly points at "probably fine, but I didn't want to risk the number," the ratio is being managed instead of the outcome, and it is worth saying so directly before the habit sets in across the desk.