← all playbooks

Write the candidate submission that goes to the client with the CV

A submission write-up ready to edit: why this person, the evidence against each must-have, motivation, notice and salary as the candidate stated them, and the concerns put plainly, with the candidate's own words quoted and anything inferred marked as inferred.

use when
you have interviewed a candidate you rate and the client is waiting for the CV and your reasons
starts from
A candidate

The prompt

Paste it into Claude Code or the Claude desktop app with Hyreflow connected. The first line tells your agent to use Hyreflow, so it reads the play, asks before it spends anything, and hands the work back to you.

paste this into Claude
Use hyreflow and write the submission that goes to my client with this
candidate's CV.

The candidate: <CV_FILE_OR_ATS_RECORD>. The role: <JOB_SPEC_OR_ATS_JOB>.
My interview notes: <PASTE NOTES, OR NAME THE RECORDED CALL AND ITS DATE>.

Write it in this order:
- Why this person, in three sentences at most.
- Each must-have from the spec with the evidence for it from the CV or the
  interview. If there is no evidence, say so. Do not argue around it.
- Motivation, notice period and salary exactly as the candidate stated
  them. Quote their own words where it matters.
- My concerns, stated plainly, with what the candidate said about each.

Mark anything you inferred as inferred. Leave out age, family, health,
nationality and any other protected characteristic, even if it is in my
notes. List what I still need to ask the candidate.

Do this one first and tell me what it costs. If I give you more, run one
first and tell me what the full run costs before you do the rest. Write it
to be edited. Stage it, do not send anything. If I want it on the record in
<ATS_NAME>, show me the changes before you write anything to the CRM.

Replace every <PLACEHOLDER> with your own detail. Everything else can stay as written.

What you need first

  • The candidate's CV, as a file, pasted text or their record in your connected ATS
  • The job spec with its must-haves, as a file or the job record in your ATS
  • Your interview notes, or the interview recorded in Fathom or Granola with your own account connected
  • A Hyreflow workspace with credits, since the drafting is metered

Tools it can reach for

The agent picks per step from what your workspace has. Nothing here is required by name.

What happens when you run it

Free steps are marked free. Anything that spends credits is marked, and the agent asks before the first paid run of any size.

  1. 1

    Gather the three inputs

    free

    The CV, the job spec and your interview notes. The candidate and the job can be read from their records in your ATS, and a recorded interview can be pulled as a full transcript from Fathom or Granola. All of it is a read of your own accounts.

  2. 2

    Fix the must-haves before judging anyone

    free

    The must-haves are listed from the spec and you confirm them, with the nice-to-haves kept apart. A write-up argued against a loose wish list convinces nobody.

  3. 3

    Set the evidence against each must-have

    credits

    For every must-have, the evidence from the CV's dated work history and from the interview, with where it came from. A must-have with no evidence is shown as a gap. It is not argued around.

  4. 4

    Record motivation, notice and salary as stated

    credits

    Why they would move, their notice period, current and expected salary, and other processes they are in, in the candidate's own words where the notes or the transcript have them. Anything that was not said stays blank and goes on the list of things to ask.

  5. 5

    Write the concerns down

    credits

    The gap, the short tenure, the salary distance, the commute. Each one is stated with what the candidate said about it, because the client will find it on the CV anyway.

  6. 6

    Check the draft against its sources

    credits

    Every claim is traced to the CV, the notes or the transcript, and anything inferred is marked as inferred. Anything about age, family, health, nationality or another protected characteristic is left out, and you are told what was removed.

  7. 7

    Edit it

    free

    You get the write-up as a draft in your voice, with the open questions at the top. It is written to be changed by you, and it is not sent to anyone.

  8. 8

    Note it on the candidate record, on approval

    free

    Where your ATS takes notes, you see the exact note and the record it will land on first. JobAdder, Recruiterflow and Atlas can hold it against the candidate. Elsewhere the write-up stays a file.

What a run costs

Nothing in this play spends credits.

Free before anything is charged

  • Gather the three inputs
  • Fix the must-haves before judging anyone
  • Edit it
  • Note it on the candidate record, on approval

What moves the number

  • How many candidates survive the free filters. Everything dropped before the paid steps costs nothing.
  • The scoring and drafting steps run on the metered agent, charged on what they read and write rather than per candidate, so they sit outside this table.
  • Providers you connect with your own key. Those calls bill your account, not your credits.

An estimate, not a quote, priced at the volume credit rate. Your agent sizes the run against your own workspace and tells you what it will cost before it spends anything.

The write-up is what the client is paying for

A CV on its own is something the client could have found. The paragraph that comes with it is the product: you met this person, you tested them against the brief, and this is what you concluded. Clients read that paragraph first, and sometimes only that.

It is also the work that gets written last, from memory, between calls. So it shrinks to three lines of praise, which is what every other agency sent too.

This play builds the write-up from material you already hold: the CV, the spec, and your interview notes or the recording. It sets evidence against each must-have, and where there is none it says so. It records motivation, notice and salary the way the candidate put them. And it writes the concerns down, because a client who finds the gap unaided stops trusting the rest.

What comes back is a draft in your voice. The judgement in it is yours, and you are expected to change it.

What you get back

A write-up in four parts: a short case for the candidate, the must-haves with the evidence and its source beside each, the candidate's motivation, notice period and salary position as stated, and the concerns with the candidate's answer to each. Quotes are marked as quotes and inferences as inferences. At the top sits a short list of what you still need to ask. At the bottom, a line listing anything left out because it concerned a protected characteristic.

Variations worth knowing

From a recorded interview. If the screening call was recorded, its transcript is pulled the same way as in turn a recorded briefing call into a search brief, and the quotes are exact.

A shortlist of three. The same structure across each candidate lets the client compare like with like. One is written first so you can fix the shape.

Before the interview. The must-haves with empty evidence beside them make a useful interview plan. Scoring candidates against a spec is covered in turn a job spec into a ranked shortlist.

Where this goes wrong

Thin notes. The write-up can only be as specific as what went in. Three lines of notes produce a write-up with many blanks, and the blanks are honest.

A quote nobody said. Notes paraphrase. Unless the words came from a transcript, or you marked them as verbatim, they are reported as indicated, not quoted.

Speaker labels. On some recordings the transcript separates speakers by label, not by name. A line credited to the candidate may have been you. Read the quotes before a client does.

Salary tidied up. "Looking for a step up, flexible for the right role" is not a number. It is recorded as said, and the number goes on your list of things to ask.

Sending it as it comes. The draft does not know what you thought in the room. Add that before it goes.

Questions

Why include the concerns when I am trying to win an interview?

Because the client will see the short stint and the missing qualification on the CV whether you mention them or not. A write-up that names the concern and gives the candidate's answer reads as judgement. One that skips it reads as a sales sheet, and the next submission you send is trusted a little less.

Where do the quotes come from?

From your interview notes, or from the full transcript if the interview was recorded in Fathom or Granola and that account is connected. Quotes are used where wording matters: motivation, salary, notice, the reason for leaving. Where your notes paraphrase, the write-up says the candidate indicated something. It does not put quotation marks around words nobody said.

What does it leave out?

Anything about protected characteristics: age, date of birth, marital or family status, health, nationality, religion and the like, even where it came up in conversation and sits in your notes. Nothing in the assessment rests on them, and the agent lists what it removed so you can see that.

Can it send the submission to the client?

No. It produces a draft for you to edit and send from your own inbox with the CV. The play has no step that emails a client, and a submission is your professional opinion under your name, so it should pass through your hands.

What does it cost?

Reading your ATS records and your meeting recorder runs on your own accounts and uses no Hyreflow credits. The drafting and the source check are AI work, metered on usage, and you are told the cost before it runs. With several submissions for the same role, one is written first so you can correct the shape before the rest.