How to Write a Candidate Submittal That Gets Callbacks

Knowing how to write a candidate submittal that gets callbacks is the difference between a recruiter who fills roles and one who sends resumes into the void. Your submittal is not a forwarded resume. It is a sales document that positions your candidate as the answer to your client's problem. If the client does not call you back, the submittal failed — not the candidate.

Here is the structure that consistently generates callbacks, the mistakes that kill submittals, and examples showing weak versus strong approaches.

What Clients Want from a Submittal

Before diving into structure, understand what the hiring manager is thinking when they open your submittal:

1. Does this person match what I asked for? They want to see a direct connection between their requirements and the candidate's qualifications.
2. Why should I interview this person over the other 10 submittals on my desk? They need a reason to prioritize your candidate.
3. Can I move fast? They want to know availability, compensation expectations, and whether there will be surprises.
4. Is this recruiter credible? A well-structured submittal signals professionalism. A sloppy one signals that you did not do your homework.

The Submittal Structure That Works

1. Subject line (the most overlooked element)

Your email subject line determines whether the submittal gets opened or buried. Most recruiters use: "Resume - John Smith - Software Engineer." That tells the client nothing useful.

Weak: Resume - John Smith - Software Engineer

Strong: Submittal: Senior Java Engineer | 8 yrs enterprise | Available 2 weeks | $140K target

The strong version front-loads three signals the client cares about: role match, experience depth, and logistics. The client can assess relevance without opening the email.

2. Executive summary (3-4 sentences)

Open with a brief that answers the four client questions immediately. This is what gets read. Everything else is supporting evidence.

Weak:

I am pleased to submit John Smith for your Software Engineer position. John has over 8 years of experience and is a strong candidate. Please review his attached resume.

Strong:

John is a senior Java engineer with 8 years building high-throughput transaction systems at JPMorgan and Capital One. He led the migration of a monolithic payments platform to microservices, reducing deployment time from 2 weeks to 4 hours. He is targeting $135-145K base, available in 2 weeks, and has no competing offers. I have vetted him thoroughly and believe he is a strong match for your distributed systems requirements.

The weak version could describe any candidate for any role. The strong version is specific, quantified, and directly tied to what this client needs.

3. Requirements match matrix

Map the candidate to the job requirements explicitly. Do not make the client figure out the match — show it.

| Job Requirement | Candidate Match | |---|---| | 5+ years Java/Spring Boot | 8 years Java, 6 years Spring Boot (JPMorgan, Capital One) | | Microservices architecture | Led monolith-to-microservices migration for payments platform | | AWS experience | AWS Certified Solutions Architect; daily AWS user for 4 years | | CI/CD pipeline experience | Built Jenkins → GitHub Actions pipeline; 50+ deployments/month | | Team leadership | Led team of 5 engineers; mentored 3 junior developers |

This table is the highest-value element in your submittal. Clients scan it in 10 seconds and immediately see the fit level.

4. Key achievements (2-3 bullets)

Select achievements that are most relevant to this specific role. These should be quantified and outcome-oriented.

• Reduced payment processing latency by 65% through architectural redesign, handling $500M+ in daily transactions
• Built automated testing framework that increased code coverage from 45% to 92%, reducing production incidents by 70%
• Mentored 3 junior engineers, two of whom were promoted to mid-level within 18 months

5. Logistics block

Clients hate surprises. Front-load the practical details:

| Detail | Information | |---|---| | Compensation target | $135,000 - $145,000 base | | Work arrangement | Hybrid preferred (3 days onsite) | | Notice period | 2 weeks | | Availability to interview | This week, flexible schedule | | Competing processes | None currently active | | Work authorization | US Citizen, no sponsorship needed | | Location | Dallas, TX (open to relocation) |

6. Recruiter's assessment

Add your professional opinion. This is where your value as a recruiter — not just a resume forwarder — comes through.

My assessment: John is a methodical engineer who thrives with complex system design challenges. His communication style is direct and low-ego — he presented his JPMorgan work by crediting his team, which suggests strong collaboration skills. His compensation expectations are within your stated range, and his 2-week availability means he could start by [date]. I rate this a strong match for your senior engineer opening.

This section differentiates a professional recruiter from a resume distribution service.

Before and After: Full Submittal

Before (weak — gets ignored):

Hi,

Please find attached the resume of John Smith for your Software Engineer role. John has good experience in Java and would be a great fit. Let me know if you'd like to schedule an interview.

Thanks, [Recruiter]

After (strong — gets callbacks):

Subject: Submittal: Senior Java Engineer | 8 yrs enterprise | Available 2 weeks | $140K target

Hi [Client Name],

John is a senior Java engineer with 8 years building high-throughput transaction systems at JPMorgan and Capital One. He led the migration of a monolithic payments platform to microservices, reducing deployment time from 2 weeks to 4 hours. Targeting $135-145K base, available in 2 weeks, no competing offers.

Requirements Match: [Matrix table as shown above]

Key Achievements: [Bullet points as shown above]

Logistics: [Details table as shown above]

My Assessment: [Professional opinion as shown above]

Full resume attached. Happy to set up a call to discuss further.

Same candidate. Night and day difference in presentation.

Common Submittal Mistakes

Forwarding the resume with no context

The number one mistake. A resume without a submittal is a commodity. The client has no reason to prioritize your candidate over anyone else's.

Generic summaries

"John is a great candidate with strong experience" tells the client nothing. Every submittal in their inbox says this. Specificity wins.

Missing compensation information

If the client learns about a compensation mismatch after investing interview time, you lose credibility. Include the target range upfront, every time.

Over-submitting

Sending 5 candidates for a role when 2 are strong matches dilutes your credibility. Submitting fewer, better-matched candidates positions you as a quality-focused partner, not a volume shop.

Not tailoring to the specific role

Using the same submittal summary for every job the candidate is submitted to is obvious and lazy. Adjust the emphasis, the requirements match, and your assessment for each submission.

Burying the logistics

If the client has to email you back to ask about compensation, availability, or work authorization, you have added friction. Put logistics where they cannot be missed.

Scaling Submittal Production

Writing a thorough submittal takes 30-45 minutes manually. When you are submitting multiple candidates per day, this becomes a bottleneck.

Build a template library. Create submittal templates for your most common role types. The structure stays the same — you customize the details.

Standardize your intake. During candidate interviews, collect information in the order your submittal uses it. If you ask about compensation, availability, and achievements during the call, the submittal writes itself.

Use AI assistance. Winnow's candidate brief generator analyzes a candidate's profile against a specific job and generates the requirements match matrix, key achievements, and executive summary automatically. You review, add your professional assessment, and send. The time drops from 30+ minutes to under 5.

The Bottom Line

Your submittal is your candidate's first impression with the client. A well-structured submittal with a clear match matrix, quantified achievements, upfront logistics, and your professional assessment gets callbacks. A forwarded resume gets filed. Invest the time in presentation — or use tools that compress that time — and your callback rate will reflect it.