Candidate Submission: An Evidence-First Recruiter Guide

A candidate submission should let a hiring manager answer three questions quickly: which role is this person being considered for, what verified evidence supports the recruiter’s recommendation, and what needs human review next? A resume attachment alone does not answer those questions. A polished paragraph full of praise does not answer them either.

The useful middle ground is a concise evidence handoff. It connects one candidate to one approved role definition, separates confirmed facts from open questions, and gives the recipient a clear action. This guide is for agency recruiters submitting to clients and internal recruiters submitting to hiring managers.

Define the submission as a handoff, not a verdict

A practical working definition is simple: a candidate submission is the record a recruiter prepares when one candidate is ready for another person to review against a specific role. It may travel through an applicant tracking system, a client portal, or email. The channel can vary; the evidence responsibilities should not.

Current recruiting-system documentation shows the same operational pattern. Greenhouse’s agency recruiter guide, updated March 2, 2026, says invited agency recruiters can submit candidates, “view a candidate's stage information and receive feedback,” and add notes for the client. It also says the submitted profile details cannot be changed afterward, although the recruiter can add a note. That is a useful reminder to verify the record before it crosses the handoff.

The submission is not a final hiring decision. It is the recruiter’s case for why the candidate deserves the next review, grounded in available evidence and explicit about what remains unknown. The hiring manager or client still decides whether to advance, ask for clarification, or stop.

Keep four records distinct

Recruiting teams often use “submission” to mean several different artifacts. Separating them prevents repeated copy and mismatched expectations:

• Source record: the resume, profile, recruiter notes, and any other material the recruiter has actually verified.
• Candidate evaluation: the criterion-by-criterion review showing what is supported, partial, missing, or still unclear.
• Candidate submission: the concise, recipient-ready handoff for one candidate and one role.
• Shortlist presentation: the comparative view of several candidates and the recruiter’s ranked recommendation.

The submission should summarize and link to the first two records, not replace them. The candidate shortlist presentation guide covers the later comparative artifact. Keeping that distinction clear lets a recruiter submit a strong candidate promptly without pretending the whole pool has already been compared.

Start from the approved role criteria

Before writing, reopen the role definition used during screening. If the hiring manager changed a requirement after the candidate was reviewed, resolve that change first. Otherwise, the submission may confidently explain fit against a definition the recipient no longer uses.

Use a stable criteria version or a dated intake record. The recruiting intake form guide shows how to turn a role brief into required outcomes, evidence expectations, and unresolved questions. Those are the anchors for the submission.

Choose two to four signals that would materially affect the next review. Do not summarize the entire career history. For each signal, name the criterion, state the evidence, and identify the source. “Led a six-person implementation team across two launches, according to the resume” is inspectable. “Proven leader with exceptional delivery skills” is not.

Use a consistent candidate submission structure

A strong format is short enough to scan and complete enough to review without guessing. Use the same order every time so hiring managers know where to look.

1. Role and candidate identifiers

Name the role, candidate, recruiter owner, and submission date. If similar roles are open, include the stable role identifier. This prevents a compelling profile from being reviewed against the wrong requirement set.

2. One-sentence recruiter recommendation

State why the candidate is being submitted now. Keep it narrow: “Recommend an initial hiring-manager review because the resume documents direct ownership of the two required implementation outcomes, with one open question about scale.” The sentence signals support and uncertainty without turning either into a conclusion the evidence cannot carry.

3. Criterion-linked fit signals

List two to four bullets. Begin each with the role criterion, then the evidence. Prefer concrete scope, responsibility, result, and timeframe when the source provides them. If the source supports only part of a criterion, label it as partial rather than smoothing the gap away.

4. Material gaps and open questions

Name the few uncertainties that could change the next decision. Distinguish “not shown in the resume” from “candidate does not have it.” The first describes the record; the second is a claim about the person. A submission can recommend review while still saying that an important detail needs confirmation.

5. Source access and requested action

Attach or link the approved source record and the structured evaluation when the workflow allows it. End with one request: review by a given date, choose an interview step, or answer a named role question. Avoid a vague “thoughts?” that leaves ownership and timing unclear.

A copy-ready candidate submission example

Subject: Candidate submission — Jordan Lee — Implementation Lead

Recommendation: Recommend an initial hiring-manager review. Jordan’s resume supports the role’s two required delivery outcomes; team scope remains an open question.

Role evidence:

• Multi-site implementation ownership: the resume states that Jordan led planning and rollout for two regional platform launches.
• Cross-functional delivery: the resume names coordination across operations, engineering, and customer teams through launch.
• Post-launch improvement: the resume describes ownership of issue review and workflow updates after both releases.

Open question: The resume names project leadership but does not establish the size of the direct team or decision authority. Confirm scope during the next conversation.

Requested action: Please review the linked resume and criterion summary and confirm whether to schedule the hiring-manager conversation.

The example is intentionally restrained. It does not invent enthusiasm, infer personality, or hide the missing scope detail. It gives the recipient enough evidence to inspect and a clear question to resolve.

Build a review loop around the submission

A submission should create a trackable review state. Zoho Recruit’s hiring-manager submission documentation describes submission records linked to the candidate and job opening, with a review flow that can return a rating, remarks, and an approve-or-reject response. The durable workflow lesson is to keep the submission, recipient response, and next action connected to the same candidate-role record.

Define a small set of human-owned states, such as ready for review, under review, clarification requested, advance, or do not advance. Record who changed the state, when, and why. A state without the reviewer’s reason should not overwrite the evidence record.

When feedback reveals a changed requirement, do not quietly edit the submission as though the earlier review never happened. Record the change, update the role criteria, and decide whether other candidates need a new review under the revised definition.

Use AI as a drafting and checking aid

AI-assisted screening can help organize candidate evidence against the job description before a recruiter writes the handoff. A useful system can propose criterion-linked bullets, surface conflicts between an extracted field and the original resume, and flag an important requirement that lacks support. The guide to screening candidates against a job description explains the underlying evidence review.

Every generated statement remains provisional. The recruiter should compare it with the original source, remove unsupported interpretation, correct scope, and decide whether it belongs in the submission. AI should not infer an advancement decision, turn an unknown into a miss, or present a candidate claim as independently verified.

Avoid the common submission failures

• Resume forwarding: an attachment without a criterion-linked recommendation transfers the recruiter’s review work to the recipient.
• Generic praise: adjectives such as “excellent” or “impressive” do not show why the person fits this role.
• Evidence dumping: ten bullets make the recipient reconstruct priority. Choose the few signals that change the next review.
• Hidden uncertainty: omitting a visible gap makes the submission less trustworthy when the hiring manager finds it.
• Unsupported certainty: “not mentioned” is not proof that a capability is absent.
• Mixed roles: copied language from another opening can make accurate candidate evidence irrelevant.
• No review request: a strong summary can still stall when nobody owns the next action.

Candidate submission quality checklist

• Is the candidate tied to one role and one criteria version?
• Does the recommendation state why review is warranted now?
• Can every factual statement be traced to a named source?
• Are the strongest signals connected to actual role criteria?
• Are partial evidence, missing evidence, and confirmed misses kept distinct?
• Are material gaps visible without being overstated?
• Can the recipient open the underlying resume and evaluation?
• Is AI-generated language checked against the source?
• Does one person own the requested next action?
• Will the response remain attached to the candidate-role record?

Make the handoff easy to inspect

The best candidate submission is not the most persuasive-sounding message. It is the easiest one for a skeptical hiring manager to inspect. Tie the candidate to the approved role, use a small number of verified signals, expose the open questions, link the source record, and ask for one clear human-owned action. That gives the recipient a defensible basis for the next review without pretending the submission has already made the decision.