The Bench / Playbooks / 002
Playbook 002
Tailoring your contract CV to a live role
A role goes live on Tuesday and submittals close Friday. Or the phone rings: a recruiter found you, a position description is in your inbox, and they want to submit by Thursday. Either way your CV is honest, aimed at nothing in particular, and there's no time to rebuild it. This is the playbook for that window.
Playbook 001 called tailoring a later playbook's job. This is that playbook. One sequence, one real role carried start to finish, two time-boxes: the thirty-minute version and the half-day one. If your CV has been through 001's probes, the sequence runs faster – but it works on any CV that tells the truth. A vague CV is the one thing tailoring can't rescue; Playbook 001's probes are the fix for that.
One promise, stated carefully. Tailoring re-weights the truth you already have. It can't manufacture fit – and finding that out costs ten minutes on this page, which is the cheapest outcome here.
The window
Contract roles run on submittal windows: three to five days is common, shorter happens. The recruiters holding the role are racing each other to put candidates forward first, so the shortlist is often drawn from what arrived early, not what arrived perfect. The role reaches you through one of two doors: an ad you found, or a desk that found you, with a quick screening call and the PD attached. The window runs the same either way, and it changes the job. A full rebuild loses to the clock; a scattergun application loses to the recruiter's read. Disciplined tailoring is the move that fits the window – and it starts before the CV is even open.
The two time-boxes, made concrete: the thirty-minute version is steps 1 to 4 plus the final read in step 6. The half-day version adds step 5 and a deeper pass through the body – reserve it for a role genuinely worth it.
The job
One role and one CV, carried through every step. Both are composites of real patterns with details changed.
Position: Senior Business Analyst (Discovery)
Engagement: 6-month contract, full-time
About the role: A state government department is scoping the replacement of a legacy case-management platform with limited CRM capability. The successful candidate will lead the discovery phase.
Key responsibilities: deliver the current-state assessment; lead the options analysis; develop the business case; support the market scan with the procurement team; engage stakeholders across business and technical teams.
Essential: demonstrated business case development; demonstrated options analysis; strong stakeholder engagement across business and technical teams.
Desirable: government experience; procurement exposure; CRM or case-management domain knowledge.
One honesty note before the CV: this release is clearer than plenty that reach the market – the deliverables name the phase. Step 2 shows two of the worse kind, and how to read them.
the university engagement, written up for the delivery role it won last year.
- Led the project through discovery, design and delivery across three release cycles, chairing weekly governance and maintaining the RAID log
- Coordinated vendor onboarding and managed the procurement schedule to plan
- Ran stakeholder workshops across business and technical teams
Buried at bullets four and five: "Completed options analysis across three build-and-buy paths" and "Drafted the business case for the student-management platform replacement, endorsed by the investment committee."
The evidence the new role decides on – the options analysis, the endorsed business case – is real and already on the page. It sits last, behind the delivery-and-governance framing that won a different role. Nothing needs inventing. It needs re-aiming.
Step 1 · Ring the recruiter
Every ad is a lossy compression of a conversation the recruiter had with the client. Every PD has the opposite problem: it lists everything and weights nothing, and plenty are stale or just badly written. Either way the paper isn't the brief. Titles get genericised, the real problem gets sanded down, and the requirement that will actually decide the shortlist sits in the recruiter's head, not the fourth bullet. So the first move in the window is a call, and it asks three questions in this order: What does ideal look like? What's actually must-have? What would you still put forward as a fallback?
Those three words – ideal, must-have, fallback – map onto the categories recruiters already sort with. Ask in that vocabulary and something shifts: you stop being an applicant to sort and start being a candidate doing the qualification work with them. Recruiters cover candidates they can represent confidently, and confidence comes from exactly this conversation. It also gets you the uncompressed brief in ten minutes.
The job. The call reveals what the PD couldn't. The business case is the whole mandate – it goes to Treasury, and the last attempt at this replacement stalled there. "Stakeholder engagement" means one specific thing: a business unit that fought the last attempt, and an enterprise architect who owns the standards gate. And the recruiter is thin on detail about the department itself, because the department keeps recruiters at arm's length. Hold that last one; it matters in step 2.
When the desk rang you, step 1 is already underway: the quick screening call recruiters open with is this conversation. Ask the three questions before it ends, while the brief is fresh in their head, and the screen becomes a briefing.
And sometimes you ring and learn little – the recruiter is new to the client, or the client keeps them at arm's length. That's a finding, not a wasted call. When the context can't reach you through the call, the paper has to carry it, and step 2 reads what the paper is doing in that silence. Thin call, heavier paper.
Sometimes there's no human to ring – a portal, a panel, an inbox. Then step 2 runs on the paper alone, and the paper-reading below is the fallback, not the spine.
Before the CV opens: ring, and ask the three questions. Write the answers down in their words, not yours.
Step 2 · Weigh what the paper can't say
The paper sorts requirements into must-have and desirable, and the sorting says nothing about weight. A bloated PD makes it worse: forty listed requirements can't all matter, and the paper won't say which five do. Some requirements weigh exactly what they say. The business case here is concrete: it's the mandate, and nothing adjacent substitutes for having built one that survived scrutiny.
Others get their weight from the environment. Stakeholder engagement, procurement exposure – phrases like these can mean anything until someone tells you what they mean here. That's context, and context is expensive to transmit. When an organisation can transmit it – a good briefing, an open hiring manager – the recruiter hands it to you in step 1.
When an organisation holds recruiters at arm's length by design, the paper does something quieter: "sector experience desirable" becomes the heaviest line on it. It reads as a preference. It's actually a proxy for every piece of context the paper couldn't carry – the processes, the approval gates, the way decisions actually move. A recruiter who can't tell you much about the client is itself a signal that the proxy is doing real work.
Reading cold, the tells are ordinary: what's listed first, what's repeated, "demonstrated" versus "familiarity with", and which desirable line is really a must wearing manners. Out of all of it, name the three to five requirements that will decide the shortlist. The rest is boilerplate.
One more tell, because it decides aim: the headline names the destination, and the deliverables name the stage. Replacement or implementation in a title means little when the deliverables are an options analysis and a business case – that work is discovery, whatever the title says. Weight against the stage, because the stage is what's being bought now.
Two worse papers, read quickly
Business Analyst · 6-month contract
Our government client seeks an experienced BA to support a high-profile transformation initiative. Strong communication and stakeholder engagement skills essential. CRM experience highly regarded.
No phase, no deliverables, no problem named. Every weight here is a question for the call – and if the call can't happen, the desirable line is carrying the whole release: CRM.
Senior Business Analyst · CRM Implementation · 6-month contract
A government department requires a Senior BA for the implementation of a new case-management solution. Deliverables: current-state assessment, options analysis, business case for the preferred approach.
The title says implementation. The deliverables say the decision hasn't been made yet. Weight it as discovery, and raise the mismatch on the call – whoever wrote the deliverables scoped the money; the title came later.
The job. The weights, after the call: the Treasury-grade business case carries the most. Government experience – listed desirable – carries nearly as much, because the department transmits nothing and having lived it is the only substitute. The named stakeholder terrain is third. Procurement is fourth. "Requirements gathering" barely registers; every BA claims it.
Write the paper's requirements in one column and your weights in another. Circle the three to five that decide it.
Step 3 · Qualify in or out
Now the gate, and it runs on the weights, not the paper. Take the deciding three to five and map what's true against them – not what's arguable, what's true. Hold most, and the gap has a name you can say out loud: qualify in, and tell the recruiter the gap yourself before the client finds it. A named gap with an adjacency beside it reads as judgement. A hidden gap reads as the thing that ends the interview.
Hold none of them, and the answer is a different role, not a bolder CV. This is the step most people skip, and skipping it is how the same week gets spent tailoring toward five roles that were never really open to you. Chasing everything is how nothing gets caught. Ten minutes of honesty here buys the hour back.
The job. The contractor holds the business case cold – built, endorsed, committee-tested. Options analysis, same engagement. Procurement, genuinely. Stakeholder resistance – the university's registrar fought that replacement too; the pattern transfers. The gap is government itself. The adjacency is real: a public institution, an investment committee, procurement thresholds. Qualify in, gap named.
Map the deciding requirements against what's true. In, or out. If it's out, close the file and spend the window on a role you can actually win.
Step 4 · Re-aim the top third
The recruiter's first read is fast, and it spends its seconds on the top third of the page: the title line, the summary, the most recent role, the nouns it can match against the brief. That's where the fit call gets made, so that's where tailoring concentrates. The work is re-voicing and re-ordering what's true into the words the brief uses – the market's words and the PD's words, because those are the search terms of that fast read and the vocabulary of the client's own head.
- Led the project through discovery, design and delivery across three release cycles, chairing weekly governance and maintaining the RAID log
- Built the endorsed business case for replacing a legacy student-management platform at a university – options analysis across three build-and-buy paths, market scan run with procurement, presented to the investment committee twice.
What changed: the lead swapped for the buried line, re-voiced in the PD's own nouns – platform replacement, options analysis, procurement, committee scrutiny – carried by work that was already on the page. Nothing was added. Everything was re-weighted.
The summary gets the same treatment: two or three lines that answer the brief's deciding requirements in order, gap included where it earns trust. And the title line under the most recent role gets checked against the market's name for the work – your org's dialect translated, exactly as 001's probe three taught.
Rewrite your summary against the deciding three to five, then re-aim the two or three bullets the fast read will hit first: their nouns, your evidence.
Step 5 · Context lines and the cut
Playbook 001 put the mandate in a context line, the single line above an engagement's bullets. Tailoring is where that structure pays twice. The context line is where phase, driver and environment live – and phase, driver and environment are what this role is buying. One line above the relevant engagement, tuned to those three, does more aiming than three rewritten bullets below it.
The other half of this step is the cut. Relevance is relative: the engagement that carried your last application may be dead weight in this one. Compress what the brief has no use for – older roles to a line or two, adjacent detail out entirely. The page the desk receives should read like it was always about this kind of work, because for this submittal, it is.
The job. The university engagement's context line becomes: Brought in at discovery to scope the replacement of a legacy student-management platform – options, business case and market approach for a public institution's investment committee. The retail loyalty-platform engagement two roles back compresses to two lines. It was the hero of a different application.
Tune the context line on your most relevant engagement to the brief's phase, driver and environment. Then cut or compress everything the brief has no use for.
Step 6 · The consistency pass, then stop
Two failure modes live at the finish. The first is the tailored top on the untouched body – a summary that promises the brief's world sitting above bullets still aimed at the old one. The fix is one read-through as the recruiter: does the page agree with itself, top to bottom, in tense and voice and vocabulary?
The second is version sprawl. Keep one master CV and one tailored copy per live role, named so you can tell them apart in six weeks. Agencies keep what you send them, and two conflicting versions of you reaching the same desk reads as a problem neither version can fix.
Then stop. The evidence on tailoring is clear that the gains concentrate early – the call, the weights, the top third – and thin out fast after that. Half a day is the ceiling for a role that's genuinely worth it. Past that, the window is spending you.
One full read as the recruiter. Fix what disagrees. Save as the role-named copy. Send inside the window.
What the numbers actually say
The careful studies – the ones that vary one thing on otherwise-identical CVs – put the lift from genuine relevance in the range of real but modest. Worth having, worth the thirty minutes, and nothing like the numbers the software industry quotes. The ten-times-this and doubled-that figures are platform marketing measuring their own users. And the famous claim that the machines auto-reject three-quarters of CVs traces back to a company that folded over a decade ago. Most systems rank; humans decide. Write for the human, in the market's words, and the searches find you too.
What this can't do
Tailoring re-orders and re-voices what happened. The moment it invents, you've written a cheque your references get asked to cash – and this market calls references. The bright line never moves: if the evidence exists, aim it; if it only nearly exists, the gap gets named, not papered. And if the deciding requirements find nothing true to map against, the page was never the problem – the aim was, and The Bench exists to tell those apart.
The checklist
The pre-submittal gate, six lines and two laws. Lines 1 to 4 and 6 are the thirty-minute version; line 5 is where the half-day goes.
- The call – ideal, must-have, fallback, in the recruiter's words.
- The weights – the three to five that decide it, named.
- The gate – in or out, gap named if in.
- The top third – summary and first bullets in their nouns, your evidence.
- The context lines – phase, driver, environment, tuned; the irrelevant cut.
- The consistency pass – one read as the recruiter, then stop.
Law one: nothing invented, ever. Law two: one master, one tailored copy per live role.
Playbook 003 takes the evidence into the room: the interview is the bullet, spoken. One email a month when a playbook drops. Take a seat →