← Back to Blog
October 19, 2026 · 10 min read · By Rezumz Team

How to Write a Candidate Submission Email to a Hiring Manager (With Template)

A candidate submission email gives the hiring manager what they need to say yes or no in two minutes: a subject line with the candidate and role, a two-line verdict, three to five points of evidence against the must-haves, any concerns, and the practical facts of pay, notice and availability. End with one clear request and a date.

What a submission email is for

A submission email is the moment a candidate stops being your opinion and becomes the hiring manager's decision. Most hiring managers are busy and read on a phone between meetings. If the email is long, vague or full of praise without evidence, they will forward the CV unread or reply later, and good candidates go cold in the meantime. A strong submission does three jobs. It tells the manager why this person is worth their time, using the criteria the manager agreed at intake. It is honest about gaps, which builds your credibility for the next candidate you send. And it makes the next step easy, so the manager can reply with one line. Think of it as a short brief, not a sales letter. The manager should finish reading with a view, not with questions you could have answered. It also protects the candidate. A clear, fair summary stops a good person being judged on a single line of a CV, and it gives the manager the language to explain a decision to others. Agree at intake how managers prefer to receive submissions: email, a shared document, a message in a chat tool, or a note inside your hiring system. Some managers want a shortlist of three with a ranking, and others want one candidate at a time. Asking once saves rewriting every email later, and it shows you respect how they work.

Before you write: get the inputs right

Open the job's must-haves and the notes from your intake meeting. Write down the three or four things the manager said matter most. Read the CV and your screening notes against only those points. Gather the practical facts: current or last employer, notice period or earliest start, location and work pattern, pay expectation if you have it, and any constraint such as a visa or relocation. Check that you have the candidate's permission to share their details with this employer, and that you are not sending anything you should not, such as a protected characteristic or a current salary where local rules restrict asking. If you are an agency recruiter, check the terms of business before sending. Spend your time on the evidence, because that is the part the manager cannot get from a CV alone. A useful habit is to write the verdict first, before the detail. If you cannot say in one sentence why you are sending this person, you are not ready to send them, and a further call with the candidate may be a better use of time than a longer email. Also decide what you will not say. Opinions about personality, guesses about motivation and second-hand gossip do not belong in the email. If you noticed something that worries you but have no evidence, raise it as a question for the interview rather than as a fact in the submission.

The subject line

Put the candidate, the role and the signal in the subject so the email can be found and triaged. Examples: Candidate for Senior Accountant: Priya Nair, strong match, available in 4 weeks. Submission: Daniel Okafor for Customer Support Lead. Shortlist of three for Payroll Analyst, one stands out. Avoid vague lines such as Great candidate or Quick note, and avoid all capitals. Use the exact role title from the requisition so the manager can match it to their open roles. If you send several candidates for one role, send one email per candidate unless the manager prefers a combined shortlist, because separate threads make replies and decisions easier to track.

The five-part structure

Part one, the verdict, in one or two sentences: who they are and why you are sending them. Part two, evidence against the must-haves: three to five short lines, each naming the requirement and the proof, such as managed a team of six in a retail setting, or ran month-end close alone for two years. Part three, concerns or gaps, stated plainly with your read on how serious they are. Part four, the practical facts: notice, location, pay expectation, motivation for moving. Part five, the request: ask for a decision on whether to interview by a date, and offer times. Keep the whole email under about 200 words. Attach the CV, but write so the email stands alone if the attachment is never opened. Use the same order every time so that managers learn where to look. Many will read only the first two lines and the request at the end, so make those two parts carry the decision. Write the evidence lines in the manager's own words from the intake, not in your agency's or team's jargon, because a line that echoes their requirement is easier to accept. Keep each evidence line to one sentence with a number or a named task where you have one. If the candidate has a result you can verify, such as a certification or a measurable outcome they described, include it. If you could not verify it, say what the candidate said and that you have not checked it.

Word-for-word template

Subject: Candidate for [Role]: [Name], [one-word signal], available [date]. Hi [Manager first name], I would like to put [Name] forward for the [Role] position. In short: [one sentence on current role and why they fit]. Against your must-haves: 1. [Must-have 1]: [specific evidence]. 2. [Must-have 2]: [specific evidence]. 3. [Must-have 3]: [specific evidence]. Points to weigh: [honest gap or concern, and what you think of it]. Practical details: notice period [x], based in [place], looking for [pay range or expectation if appropriate], moving because [reason in their words]. They have agreed to be put forward to you. Could you tell me by [date] whether you would like to interview them? I can offer [two or three time slots] and will arrange everything. CV attached. Best, [Your name, phone].

A worked example

Here is the template filled in for an invented candidate. Subject: Candidate for Warehouse Team Leader: Sam Ellis, strong match, available in 3 weeks. Hi Maria, I would like to put Sam Ellis forward for the Warehouse Team Leader position. In short: Sam has led a night shift of eight at a distribution centre for three years and wants a day role closer to home. Against your must-haves: 1. Team leadership: supervised eight pickers, ran daily briefings, handled rotas. 2. Safety: completed forklift certification and led two site safety walk-rounds a month. 3. Systems: used a warehouse management system daily, trained two new starters on it. Points to weigh: no experience with temperature-controlled stock. I think this is a short learning curve given the safety record, but you know the site better than I do. Practical details: three weeks notice, lives 20 minutes away, pay expectation within the advertised range. Could you tell me by Friday whether you would like to interview Sam? I can offer Tuesday or Wednesday afternoon. CV attached. Best, Jo. Notice what the example leaves out. There is no praise such as great energy, no guess about the candidate's ambitions and no pay history. The single concern is stated once and tied to the safety record, so the manager can disagree with it. The request names two time slots and a reply date, so the manager only has to say yes and pick one. Adapt the example to your own roles: swap in the must-haves from your intake and keep the same shape.

Concerns: how to state them without sinking the candidate

Hiding a weakness damages trust when the manager finds it in the interview, and over-apologising makes a decent candidate look weak. State the concern once, factually, then give your view. A gap in a skill: say what is missing and how the person might close it. A job-hopping pattern: say what the candidate told you about the reasons, if they were willing to share. A pay expectation at the top of the range: say so now rather than at the offer. Do not mention age, health, family plans, religion or other protected characteristics, and do not pass on information the candidate gave you in confidence. Rules about what you may collect and share differ by country, so check local rules. A concern that you present with a view invites a conversation. A concern you leave out creates a surprise. When you are unsure whether something counts as a concern, ask whether the manager would want to know before spending an hour of interview time. If yes, include it. If it is a matter the candidate told you privately or something unrelated to the job, leave it out. A balanced email, with strengths and one or two honest gaps, usually earns more trust than a spotless one, because managers know that real people have gaps.

Common mistakes

Sending a CV with no message. Writing adjectives instead of evidence: passionate, driven and a great culture fit tell the manager nothing. Burying the practical facts so the manager has to ask. Sending five candidates in one wall of text. Leaving out the deadline, so the email sits unanswered. Over-selling, so the manager discounts everything you say. Forgetting to check the candidate agreed to be submitted. Not following up: if there is no reply in two working days, send a one-line nudge offering to talk for five minutes. Using a different format every time, which makes it hard for a manager to compare candidates. If a manager keeps asking the same follow-up question, add that answer to your template. Another mistake is sending a submission before you have checked the basics the manager will ask about first, such as whether the candidate can work in the country or location. A third is describing the same strength three times in different words to make a short list look longer. A fourth is forgetting to tell the candidate what you sent and what happens next, which leaves them unsure whether to chase. Close the loop with a two-line message to the candidate once the manager replies, whatever the answer.

Follow-up and learning from replies

When the manager replies, answer the same day if you can, and book the interview or send a kind, specific decline to the candidate. If the manager passes, ask for one or two reasons in terms of the must-haves, and record them. Over several submissions, patterns show up: perhaps the manager cares more about industry experience than the intake notes suggested. Feed that back into your screening. If you often submit candidates who are declined, the problem is usually the brief, not the candidates, so go back to the intake. Keep each submission in the candidate record so that a colleague can see what was sent and when, and so that you can reuse the evidence lines later. If you work with several hiring managers, keep a note of how each prefers to receive submissions and what they care about most. One may want to see the pay expectation first, another the reason for leaving, a third the location. Tailoring the order of the evidence to the reader costs nothing and speeds up replies. Also tell candidates honestly when a submission has been declined, with the reason in neutral terms, so they are not left waiting. A quick, kind close keeps the relationship intact for the next role.

Submission checklist

Does the subject name the candidate, role and signal? Is there a one-line verdict at the top? Are there three to five evidence lines tied to the must-haves? Is any gap stated plainly with your view? Are notice, location, pay and motivation included where lawful? Has the candidate agreed to be submitted? Is there one clear request with a date? Is the email under about 200 words? Is nothing in it a protected characteristic or a confidence? If every answer is yes, send it. Keep a short library of your best evidence lines for common must-haves, so that writing the next email takes minutes. Review a few sent submissions every month and ask which ones got a quick yes, a slow reply or a no, and what the pattern says about your brief or your writing. Over time the email becomes a habit rather than a chore, and managers learn that your submissions can be trusted.

In Rezumz

In Rezumz, the job workspace holds the must-haves you confirmed, and CVs are ranked against them with the supporting evidence shown, so the evidence lines for your email are already in front of you. Interview scorecards keep your screening notes in one place, and you can email the manager from the candidate record, with every message logged. Rezumz does not write your submission or decide who you put forward, and people make each hiring decision.

Frequently asked questions

How long should a candidate submission email be?

About 150 to 200 words. Put the verdict first, add three to five evidence lines against the must-haves, state any concern, give notice and location, and end with one request and a date. Anything longer is likely to be skimmed or left until later.

Should I send the CV or a summary?

Send both. The email summary lets a busy manager decide in two minutes, and the CV holds the detail. Write the email so it works if the attachment is never opened, and check that the candidate has agreed to be submitted.

Should I mention salary expectations in the submission?

Often yes, so nobody wastes time on a mismatch, but check local rules first. Some places restrict asking about current or past pay. Ask about expectations rather than current pay, and share only what the candidate has agreed you may share.

How do I handle a candidate with a weakness?

State it once, factually, and give your view on how serious it is and whether it can be closed. Hiding it damages your credibility when it surfaces in the interview. Never include protected characteristics or confidences the candidate shared with you privately.

What if the hiring manager does not reply?

Send a short nudge after two working days offering a five-minute call. If delays are regular, agree a response time at intake and ask whether another person can decide. Record each attempt in the candidate record and tell the candidate honestly where things stand.

See it on a real hire

Open a private demo with fictional candidates and walk a hire from job description to offer. No sign-up needed.

Try the live demo →