Library Tracker Test build
Working document · v0.7 · test build

Partner Prompt Library

Workflows and paste-ready prompts for the embedded recruitment partner: on client kit, face to face with hiring managers, running a full requisition load from their own Excel tracker.

Audience On-site recruitment partners Floor tool Client Copilot, chat only, no plugins Data source Own Excel tracker, no ATS access Status 18 prompts drafted · 12 planned · 1 training module · 1 tool
Before the library

Foundations

Four things every partner learns once and uses in every prompt below. These are the transferable part: they work identically in Copilot, ChatGPT, Gemini or anything else with a chat box.

The brief pattern

Brief the tool the way you would brief a new team member on their first day. Five parts, same order every time. Partners already know how to brief; this just names it.

RoleWho it should be. "You are an experienced in-house recruiter supporting a financial services client."
ContextEverything it needs and cannot know: the brief, the notes, the tracker rows, the client's style. Paste it in.
TaskOne clear verb. Summarise, draft, rank, list, rewrite, challenge.
RulesLength, tone, what to leave out, what not to invent. "Do not guess salary figures."
FormatExactly what the output looks like: headings, a table, bullet count, word limit.
+ Ask first"Before you start, ask me up to three questions if anything important is missing." Turns a guess into a conversation.

The anonymisation routine

Nothing with a real person in it goes into a chat box until it has been through this. Thirty seconds in Notepad before pasting. It is non-negotiable in a personal or unsanctioned tool, and still good habit inside the client's own Copilot.

  • Names become Candidate A, B, C. Hiring managers become "the hiring manager" or a role title.
  • Delete email, phone, address, LinkedIn URL, photo references, date of birth, ID or passport numbers, nationality and visa status (unless the task genuinely needs work-rights, in which case keep only "has / needs sponsorship").
  • Current and past employers stay unless client policy says otherwise; if in doubt, generalise ("a regional bank", "a Big Four firm").
  • Keep dates, titles, responsibilities, skills, achievements. That is the substance the tool needs.
  • Never paste anything marked confidential by the client, whatever the tool.

Where can this go?

The client's AI policy governs on client kit, and it may be stricter than ours. This is the default until an account lead confirms otherwise for that client.

ContentClient's Copilot (inside their tenant)Personal or public AI tool
Job descriptions, hiring manager notes, process detailsYesNo, unless anonymised of client identity
Anonymised CV contentYesOnly if the client permits external tools at all
Named candidate data, contact detailsOnly if the client has confirmed Copilot is approved for candidate PIINever
Your own tracker rows (anonymised, no names)YesClient-identifying columns removed first
Client confidential or restricted materialNeverNever

Checking the output

Every prompt below has a "check before you trust it" line. The general rule: the tool is a fast, articulate junior. It drafts; you decide.

  • Any number (salary band, market size, days-to-fill) is a hypothesis until you have a source.
  • Any claim about a candidate must trace back to something in the CV or your notes. If you cannot find it, it was invented.
  • Anything going to a client or candidate gets read aloud once in your head, in your voice. If it sounds like a machine, edit it.
  • If the output is confidently wrong, fix the brief you gave it, not just the output. Usually a missing rule or missing context.
Training module 1 · 45 minutes

From "summarise this" to a brief

The session that sits in front of the library. Sixteen slides, built to be run live with partners trying each step in their own Copilot as they go. Use the buttons, or the arrow keys once the deck is focused; the frame resizes to each slide.

1 / 16
Prompt training · Module 1

From "summarise this" to a brief

Why the same tool gives one person a rough summary and another person a submission the manager reads on the train.

For embedded recruitment partners. Works in Copilot, ChatGPT, Gemini or anything with a chat box. Bring one real (anonymised) piece of work to use throughout.

45 minutes · one exercise per step · bring your own brief
The problem

Weak prompts get average answers, on purpose

The tool fills every gap you leave with the most average possible choice. Leave the audience blank and it writes for nobody. Leave the length blank and you get 400 words. Leave the format blank and you get bullet points you then reformat by hand.

What you typedSummarise this
What it heardSummarise this, for an unknown reader, at an unknown length, for an unknown purpose, and guess which parts matter
"Make this more professional" has the same problem: professional for whom?
The idea

You already know how to do this. It is a brief.

Brief the tool the way you would brief a new team member on their first day: who they are today, what they need to know, what to do, the rules, and what "done" looks like.

Recruiters live and die by the quality of a brief. A weak hiring manager brief costs three weeks of sourcing. A weak prompt costs you the same thing in miniature, several times a day.

Five parts, one add-on. The next six slides take one each.
Part 1 of 5

Role: who is answering

One sentence that sets the standard and the lens. It changes which knowledge the tool reaches for and how sceptical it is. It is not a costume; "you are a world-class genius" does nothing. "You are an in-house recruiter who has seen a thousand CVs and is hard to impress" does a lot.

WeakYou are a helpful assistant.
BetterYou are an experienced in-house recruitment partner supporting a financial services client, assessing a CV against a brief. Be evidence-based and sceptical.
Try it: take your piece of work and write the role line. Who would you hand this to if you had the perfect colleague?
Part 2 of 5

Context: what it cannot know

The tool knows recruitment in general and nothing about your client, your manager, your candidate or your last conversation. Everything that makes the task specific has to be pasted in. This is where most of the gain lives, and it is the part people skip because it feels like effort.

WeakMake this email more professional.
BetterThis email goes to a hiring manager who is a CFO, reads on his phone, dislikes fluff, and has just lost a candidate because his feedback took nine days. I need him to commit to 48-hour turnaround without feeling blamed. Here is my draft: [...]
Try it: write three lines of context for your task. Who reads it, what state are they in, what do you need to happen?
Part 3 of 5

Task: one verb, one output

Pick the verb carefully; they produce different things. Then ask for one output per prompt. "Summarise, then rank, then draft a message, then suggest questions" in one go produces four mediocre things. Four short prompts in a row produce four good ones, and you steer between them.

VerbWhat you get
SummariseShorter version of the same thing, same emphasis
ExtractOnly the items you name, in a list or table
Assess / rankA judgement against criteria you supply
DraftSomething new to send, in a voice you specify
RewriteSame content, different reader or tone
ChallengeThe holes in your thinking, before someone else finds them
Try it: which verb is your task actually? Most "summarise this" requests turn out to be "extract" or "assess".
Part 4 of 5

Rules: what not to do

Rules are where you stop the tool from being average. Length, tone, exclusions, and above all what it must not invent. Every prompt in the library carries a line like "do not invent salary figures" because, unprompted, it will.

  • Length. "Under 200 words" beats "keep it short". Numbers are obeyed; adjectives are interpreted.
  • Voice. Name the banned words. "No 'exciting opportunity', no 'reach out', no exclamation marks."
  • Boundaries. "Use only what is in my notes. If something is missing, say so rather than guessing."
  • Fairness. "Do not comment on age, nationality, gender or gaps for family reasons."
Try it: write two rules. Start with the thing the tool got wrong last time you used it.
Part 5 of 5

Format: draw the shape of the answer

If you can picture the output, describe the picture. Headings, a table with named columns, a fixed number of bullets, a word limit per section. This is the difference between an answer you reformat and an answer you paste.

WeakGive me a summary of this candidate.
BetterUse this exact format: HEADLINE: one sentence MUST-HAVES: one line each, Met / Partly / Not evidenced, with the CV line that proves it WATCH-OUTS: up to three LOGISTICS: notice, location, comp expectation Under 200 words in total.
Try it: sketch the format for your task in five lines. Then use it in the prompt verbatim.
The add-on

Ask first: turn a guess into a conversation

"Before you start, ask me up to three questions if anything important is missing."

One line, and the tool stops guessing at the gaps in your brief and starts telling you what they are. The questions it asks are also a diagnostic: if it asks who the audience is, you forgot context. If it asks how long, you forgot format. After a few weeks you stop needing it, because you have learned what it always asks.

Try it: add the line to the prompt you have been building and run it. Answer the questions in your next message.
Worked example 1

"Make this more professional", rebuilt

BeforeMake this more professional: Hi Mark, just chasing on the two profiles I sent Monday, any thoughts? Both have other things going on so would be good to move quick. Thanks
AfterYou are a recruitment partner writing to a hiring manager you sit near and work with daily. Context: Mark is a CFO, reads email on his phone, and lost a candidate last month when his feedback took nine days. Both candidates I sent Monday have other processes at final stage. Task: rewrite my draft below. Rules: under 80 words. Direct, warm, no "just", no "chasing". Make the deadline explicit and the consequence of missing it clear without sounding like a threat. Format: subject line, then the email. Before you start, ask me anything you need. My draft: [paste]
Notice: the "after" prompt is longer than the email. That is normal. The prompt is the work; the email is the output.
Worked example 2

"Summarise this CV", rebuilt

BeforeSummarise this CV: [paste]
AfterYou are an experienced recruiter assessing a CV against a brief. Be evidence-based and sceptical. Context: the brief's must-haves are [paste]. This is for a shortlist meeting tomorrow. Task: assess Candidate A against the must-haves. Rules: for each must-have write Met / Partly met / Not evidenced and quote the CV line that supports it. Never infer a skill from a job title. Do not comment on anything unrelated to the criteria. Format: MUST-HAVES, FLAGS, QUESTIONS TO PROBE (3 to 5), RECOMMENDATION (one line). CV (anonymised): [paste]
This is prompt 3.1 in the library. Every library prompt is built from the same five parts; once you see them, you can repair or write your own.
After the first answer

The second prompt is where the value is

Nobody gets it right first time, and you do not need to. The first answer is a draft to steer. Short, specific corrections work better than starting over.

  • "Too long. Cut to 100 words and keep the ask."
  • "You invented the salary band. Remove it and mark it as unknown."
  • "Give me three versions: one blunter, one warmer, one shorter."
  • "Be harsher. What would a sceptical hiring manager say about this candidate?"
  • "What did I not tell you that you needed? List it."
  • "Now do the same for the next one" (paste the next CV, same format, no need to repeat the brief).
Try it: send one correction to the answer you got on the last slide. Then one more.
Beyond drafting

Use it to think, not just to write

The most valuable prompts partners write are not documents at all. They are rehearsals and second opinions, five minutes before the conversation that matters.

  • Critique my draft. "Here is my submission summary. What would make the manager decline to interview? Be specific."
  • Argue the other side. "I think this brief is unrealistic. Make the manager's strongest case that it is not."
  • Predict the pushback. "I am about to tell the client their process is losing candidates. What are the three things they will say, and what do I answer?"
  • Find what I missed. "Here is my tracker for this manager. What looks like a problem I have not noticed?"
These need context more than anything. Paste the situation, not just the question.
Anti-patterns

Six habits that quietly waste the tool

  • Politeness padding. "Could you possibly help me to maybe..." spends the words that should have been context. It is not rude to be direct with it.
  • Five tasks in one prompt. Four mediocre outputs. Split them.
  • No format. You will reformat by hand every time.
  • Trusting the numbers. Salary bands, market sizes, totals from a pasted table: check every one.
  • Pasting names. Anonymise first, always. Thirty seconds.
  • Accepting the first answer. The tool is a fast, articulate junior. It drafts; you decide.
Which of these did you do this week? Most people find two.
Practice

Three exercises for this week

  • Rebuild one. Take the last prompt you typed that started with "summarise" or "make this". Rebuild it with the five parts. Keep both versions and both outputs.
  • Run a library prompt on real work. Pick 1.1, 4.1 or 7.1. Use your real (anonymised) brief or tracker. Note where the output was weak and what rule would have fixed it.
  • Rehearse one conversation. Before your next difficult hiring manager conversation, run 4.2 and send one correction to the answer.

Bring the before-and-after from exercise one to next week's fifteen-minute session. The good ones go into the library with your name on them.

Submission format: the two prompts, the two outputs, and one line on what changed.
Take-away

The whole module on one card

RoleWho is answering, and how sceptical
ContextEverything it cannot know. Paste it.
TaskOne verb, one output
RulesLength, voice, what not to invent
FormatDraw the shape of the answer
+ Ask first"Ask me up to three questions if anything is missing"

Then: anonymise before you paste, check every number, steer with the second prompt, and keep the good ones.

Next module: sourcing and screening prompts in depth, with live iteration on a real search.
Workflow 1

Intake and brief clarification

The highest-leverage moment in the cycle. A brief that is wrong by ten percent costs three weeks of sourcing. These prompts turn a rushed hiring manager conversation into something you can actually recruit against, and give you the questions to go back with.

Fires whenA new requisition lands, a manager sends three lines by email, or you walk out of an intake meeting with a page of scribbles.

1.1 Notes to structured brief

Draft
Paste inYour raw intake notes, the manager's email, or a Teams transcript. Plus the existing JD if there is one.
You are an experienced in-house recruitment partner. I have just come out of an intake conversation with a hiring manager and my notes are rough.

Turn my notes into a structured recruitment brief with these headings:
1. Role summary (2 sentences, plain language)
2. Must-haves (skills or experience without which we would not submit)
3. Nice-to-haves
4. Dealbreakers the manager mentioned
5. Compensation and level (only what was actually said; write "not discussed" if not)
6. Team, reporting line and why the role exists now
7. Interview process and decision makers (as stated)
8. Gaps: everything a recruiter would need to know that is not in my notes

Rules: use only what is in my notes. Do not invent requirements, salary figures or process steps. Where the notes are ambiguous, put the item under Gaps rather than guessing. Keep each section short; bullets are fine.

Before you write the brief, ask me up to three questions if anything critical is unclear. Otherwise go ahead.

MY NOTES:
[PASTE NOTES HERE]

EXISTING JOB DESCRIPTION (if any):
[PASTE OR WRITE "none"]
Good looks likeA one-page brief you could hand to a colleague to source from, with a Gaps section long enough to be useful. If Gaps is empty, be suspicious.
Check firstRead the must-haves against your memory of the conversation. The tool will sometimes promote a nice-to-have because the manager mentioned it twice.
If you have moreCopilot in Teams: ask it to draft this directly from the meeting recap instead of pasting. Copilot in Outlook: select the manager's email thread and run the same prompt with "from the email above".

1.2 Clarifying questions, ranked by cost

Draft
Paste inThe brief from 1.1 (or whatever you have).
You are an experienced recruitment partner preparing to go back to a hiring manager after intake.

Below is the brief as it stands. Produce a list of clarifying questions I should ask the manager, ranked by how expensive it would be to get the answer wrong (for example, sourcing the wrong seniority for three weeks is expensive; not knowing the desk location is cheap).

For each question give:
- The question, worded so I can ask it as-is in a 10-minute call
- Why it matters in one line
- What I will do differently depending on the answer

Rules: maximum 8 questions. Do not ask things the brief already answers. Prefer questions that expose hidden assumptions about level, comp, or what "good" looks like.

BRIEF:
[PASTE BRIEF HERE]
Good looks likeThe top two questions are ones you would be embarrassed not to have asked. The list makes a 10-minute follow-up call worth the manager's time.
Check firstCut anything you already know from account context. The tool does not know this client's norms; you do.

1.3 Reframing an unrealistic brief

Draft
Paste inThe brief, plus what you actually know about the market for this role (your own view, previous searches, recent comp data). No market knowledge in, no market knowledge out.
You are a senior recruitment partner who has to have a diplomatic but direct conversation with a hiring manager.

The brief below is unrealistic in the ways I describe. Help me prepare for the conversation.

Give me:
1. A one-paragraph opening that acknowledges what the manager wants and why, before raising the problem
2. The core message, stated plainly in two sentences
3. Two or three options I can put to the manager (for example: adjust comp, flex a must-have, accept a longer timeline, consider a different level), with the trade-off of each in one line
4. The likely pushback and a calm response to each
5. A closing that asks for a decision, not agreement

Rules: British English, conversational, no jargon. Do not exaggerate the market difficulty beyond what I have told you. Do not invent statistics. Keep the whole thing under 350 words so I can rehearse it.

THE BRIEF:
[PASTE BRIEF HERE]

WHY IT IS UNREALISTIC (my view and evidence):
[E.G. "Asking for 8 years' experience at a comp band that attracts 4-year candidates in this market. Last two searches at this band took 11 and 14 weeks."]

WHAT I KNOW ABOUT THIS MANAGER:
[E.G. "New to the company, under pressure from their director, responds well to data"]
Good looks likeSomething you would actually say, that lands the problem without making the manager defensive, and ends with options rather than a complaint.
Check firstEvery market claim in the output must be one you supplied. If it added "typically takes 12 to 16 weeks", it made that up.

Planned for this workflow

  • 1.4 JD rewrite — turn a description copied from the last incumbent into one that describes the actual role, in the client's house style.
  • 1.5 Intake meeting agenda — a 20-minute intake structure for a manager who has never hired before.
Workflow 2

Sourcing strategy and market intelligence

Where the tool is strongest at generating options and weakest at knowing the truth. Use it to widen your thinking about where candidates sit and how to reach them, then verify against what you actually see in LinkedIn Recruiter.

Fires whenA brief is agreed and you need a search plan, or an existing search has gone stale and the same forty profiles keep appearing.

2.1 Candidate persona and talent map

Draft
Paste inThe brief (client name can stay if using the client's Copilot; generalise it otherwise) and the market location.
You are an experienced talent sourcer in [MARKET, E.G. SINGAPORE / SYDNEY / MANILA].

From the brief below, build me a sourcing plan:
1. Candidate persona: a short description of the person most likely to succeed and be interested, including their likely current title(s), what they are doing day to day now, and what would make them move
2. Title variations: 10 to 15 job titles this person might actually hold, including adjacent and non-obvious ones
3. Feeder organisations: types of company (and specific companies if you are confident) where this profile is common, grouped by direct competitors, adjacent industries, and unexpected sources
4. Step-up and step-across candidates: who could do this role that is not doing it today
5. Where they spend time: communities, events, certifications or groups relevant to this profile

Rules: be specific to the market I named. Where you are guessing about a company, mark it (guess). Do not pad the list; fewer good items beat more weak ones.

BRIEF:
[PASTE BRIEF HERE]
Good looks likeAt least three title variations or feeder sources you had not thought of. The persona reads like a real person you have met.
Check firstCompany lists are the least reliable part: firms merge, rename and leave markets. Treat as leads to confirm, not a target list.

2.2 Boolean string set

Draft
Paste inThe must-haves and the title list from 2.1.
You are a sourcing specialist writing search strings.

Build me Boolean search strings for the role below. Give me:
1. A broad string for LinkedIn Recruiter (titles OR'd together, core skill AND'd, exclusions with NOT) to see the size of the pool
2. A tight string that should return under 200 highly relevant profiles
3. A "step-across" string for adjacent titles who could do the role
4. A plain keyword version for a basic search box that does not support Boolean operators

For each, note in one line what it is designed to catch and what it will miss.

Rules: use standard operators (AND, OR, NOT, quotes, brackets). Keep each string under 500 characters. Include common abbreviations and local title conventions for [MARKET].

ROLE TITLE AND MUST-HAVES:
[PASTE HERE]

TITLE VARIATIONS TO INCLUDE:
[PASTE LIST FROM 2.1, OR LEAVE FOR THE TOOL TO SUGGEST]

EXCLUDE:
[E.G. "recruiters, students, our own client's employees"]
Good looks likeStrings that paste straight into Recruiter and run. The broad and tight versions give meaningfully different result counts.
Check firstRun the string. Bracket errors and unsupported operators are common; the tool cannot test its own output. Iterate by pasting back the result count and asking it to widen or narrow.

2.3 Outreach message set

Draft
Paste inThe role's genuine selling points (from the manager, not the JD) and anything about the persona's likely motivations.
You are a recruitment partner writing first-touch messages to passive candidates. These people receive many recruiter messages and delete most of them.

Write me an outreach set for the role below:
1. Three first messages, each under 90 words, in three tones: direct and factual; warm and curious; peer-to-peer (as if from someone in the same field)
2. Two follow-ups (day 4 and day 10), each under 50 words, that add something new rather than "just checking in"
3. One version suitable for an InMail subject line plus opening line only

Rules: lead with something specific to the role or the person, never with our company. No "exciting opportunity", "perfect fit", "reach out", or exclamation marks. Do not mention salary unless I give you a figure. Leave a [PERSONALISE] marker where I should add one line about the individual's profile. British English.

ROLE AND WHY SOMEONE WOULD ACTUALLY WANT IT:
[E.G. "Head of FP&A. Rebuilding the function from scratch, reports to a CFO who was previously a COO, business is 18 months from IPO."]

WHO I AM WRITING TO:
[E.G. "FP&A managers at listed companies, probably feeling stuck below a long-tenured director"]
Good looks likeMessages you would reply to yourself. The three tones are actually different, not the same message with adjectives swapped.
Check firstFill the personalise marker every time. A template that is visibly a template performs worse than no message.

Planned for this workflow

  • 2.4 Thin-market summary — a one-page talent market note for the manager when the pipeline is short: pool depth, competing employers, comp friction, drawn from your own search evidence.
Workflow 3

Screening and assessment

Structured evaluation against the brief, fast. The gain here is consistency across forty CVs on a Tuesday afternoon, not cleverness. Every prompt in this workflow assumes the anonymisation routine has been run.

Fires whenApplications or sourced profiles are stacking up, a screening call is in 15 minutes, or you have finished a call and need to write it up before the next one.

3.1 CV against the brief

Draft
Paste inThe must-haves and nice-to-haves from the brief, and one anonymised CV. One at a time keeps the output honest.
You are an experienced recruiter assessing a CV against a brief. Be evidence-based and sceptical.

Assess Candidate A against the criteria below. Use this exact format:

MUST-HAVES
For each must-have: Met / Partly met / Not evidenced, followed by the specific line in the CV that supports your answer (quote it). If nothing in the CV supports it, write "Not evidenced" and do not infer.

NICE-TO-HAVES
Same format, briefer.

FLAGS
Anything a careful recruiter would notice: unexplained gaps, short tenures, title inflation, a mismatch between claimed seniority and scope described.

QUESTIONS TO PROBE
Three to five questions for a screening call that would resolve the "Partly met" and "Not evidenced" items.

RECOMMENDATION
One line: Progress / Hold / Decline, and the single biggest reason.

Rules: only use what is in the CV. Never assume a skill from a job title alone. Do not comment on age, nationality, gender, gaps for family reasons, or anything unrelated to the criteria.

CRITERIA:
[PASTE MUST-HAVES AND NICE-TO-HAVES]

CV (anonymised):
[PASTE CV TEXT]
Good looks likeEvery "Met" has a quoted line beside it. The Questions to Probe are ones you would actually ask.
Check firstThe recommendation is the tool's opinion, not a decision. Where it says "Partly met", read the CV yourself; that is usually where the interesting candidates live.
If you have moreWith file upload, attach the anonymised CV rather than pasting. Do not batch multiple CVs in one prompt even if the tool allows it; quality drops sharply after the second.

3.2 Screening call guide

Draft
Paste inThe brief and, if you have it, the output of 3.1 for this candidate.
You are a recruitment partner preparing for a 25-minute screening call.

Build me a call guide for the role below:
1. A 30-second opener that explains the role and the process honestly
2. Five core questions that test the must-haves, each with what a strong answer and a weak answer sound like
3. Three motivation questions that reveal whether this person would actually accept and stay
4. The practical checks: notice period, location, work rights, compensation expectations, other processes, worded naturally
5. A closing that sets expectations on next steps and timing

Rules: open questions, no leading. Keep it to one page. If I have included candidate-specific notes, weave targeted probes into the core questions.

ROLE BRIEF:
[PASTE BRIEF]

CANDIDATE-SPECIFIC NOTES (optional):
[PASTE 3.1 OUTPUT OR LEAVE BLANK]
Good looks likeA guide you can glance at during the call. The strong/weak answer examples are specific to this role, not generic.
Check firstRemove any question that touches a protected characteristic or that the client's process would not permit. Local employment law varies by market.

3.3 Screen notes to submission summary

Draft
Paste inYour rough call notes (anonymised) and the brief's must-haves. Note the client's preferred submission length if they have one.
You are a recruitment partner writing a candidate submission for a busy hiring manager who will read it on their phone.

Turn my screening notes into a submission summary:
- Headline: one sentence on why this candidate is worth 30 minutes
- Fit against must-haves: a short line per must-have, evidence-based
- What they bring beyond the brief: 2 to 3 points
- Watch-outs: anything the manager should know before interviewing, stated neutrally
- Logistics: notice period, location, compensation expectation, other processes, availability for interview
- Suggested interview focus: 2 questions the manager should ask

Rules: under 250 words. No adjectives like "excellent" or "impressive" without evidence beside them. Do not include anything from my notes that I have marked "private". Refer to the candidate as Candidate A; I will add the name.

MUST-HAVES:
[PASTE]

MY CALL NOTES:
[PASTE NOTES]
Good looks likeThe manager can decide whether to interview in under a minute. Watch-outs are present; a summary with none reads as a sales pitch.
Check firstCross-check the logistics line against your notes. Notice periods and comp expectations are exactly the details that get transposed.

Planned for this workflow

  • 3.4 Interview question bank — structured or competency question sets calibrated to level, with a scoring guide, so the partner improves the client's interviewing rather than just feeding it.
  • 3.5 Interview debrief synthesis — turn three interviewers' scattered feedback into a consistent picture and a decision recommendation.
Workflow 4

Stakeholder and client management

The workflow that separates an embedded partner from an agency recruiter. You are managing the manager as much as the search, and the hard conversations happen in person, two desks away. These prompts prepare you; they do not replace the conversation.

Fires whenA pipeline review is on the calendar, a manager's process is losing candidates, or you need to say something the manager does not want to hear.

4.1 Hiring manager meeting prep

Draft
Paste inThe tracker rows for this manager's roles (copied from Excel with the header row; names removed), plus what has changed since the last meeting.
You are a recruitment partner preparing for a 30-minute pipeline review with a hiring manager.

Using my tracker data and notes below, prepare me:
1. The narrative: what is the honest one-paragraph story of where these searches are
2. Per role: status in one line, the single most important thing to say, and what I need from the manager (a decision, feedback, time, a change to the brief)
3. Risks I should raise before the manager raises them
4. The objection I am most likely to get, and a calm response
5. An agenda in five bullets, ordered so the most important decision comes first, not last

Rules: be direct about problems. Do not soften a stalled search into "progressing". The Status column is calculated (Stalled = no activity for over 7 days; Blocked on client = the next action sits with the manager or client HR and is overdue; At risk = under 7 days to the 40-business-day due date, or past it); where Override differs from Status, ask me why before the meeting. Where the data is thin, say what I should find out first.

TRACKER (paste-ready block, filtered to this manager, header row first):
[PASTE THE PASTE-READY BLOCK FROM THE TRACKER]

WHAT HAS CHANGED SINCE LAST TIME:
[E.G. "Two candidates withdrew after second round; manager took 9 days to give feedback"]

WHAT I KNOW ABOUT THIS MANAGER:
[E.G. "Prefers numbers, dislikes surprises, tends to over-index on brand names"]
Good looks likeYou walk in knowing what you want to walk out with. The agenda front-loads the decision.
Check firstThe tool reads your tracker literally. If your status column is out of date, the narrative is wrong. Update the tracker first; it takes two minutes and the prep gets much better.

4.2 The difficult message

Draft
Paste inWhat needs saying, the evidence, and how the message will be delivered (in person, email, Teams).
You are a senior recruitment partner who needs to tell a hiring manager something they will not want to hear, and keep the relationship intact.

Help me prepare the message described below. Give me:
1. The message in 3 to 4 sentences: what is happening, why, what I recommend
2. The evidence, in a form I can show (a short list or a two-column before/after)
3. Two ways to open, one for in person and one for written
4. What I should NOT say (things that would sound like blame or excuses)
5. The specific ask: what I need the manager to do, by when

Rules: own our part where we have one. Never blame the candidate or the market as a way of avoiding the real point. British English, calm, no hedging phrases like "I just wanted to". Under 250 words in total.

WHAT NEEDS SAYING:
[E.G. "Your process has lost two strong candidates because second-round feedback is taking over a week"]

EVIDENCE:
[E.G. "Candidate A withdrew day 9 after round 2; Candidate B accepted elsewhere day 11; both cited timing"]

HOW I WILL DELIVER IT:
[IN PERSON / EMAIL / TEAMS]
Good looks likeReading it, you feel slightly uncomfortable but not anxious. The ask is concrete enough that the manager can say yes or no.
Check firstSay it out loud. Anything that sounds like a corporate template will undermine you with someone who sits next to you.

4.3 Candidate feedback the manager can hear

Draft
Paste inWhat candidates actually said about the role, the manager or the process (anonymised, paraphrased).
You are a recruitment partner relaying candidate feedback to a hiring manager. The feedback is partly about the manager themselves.

Turn the raw feedback below into something the manager can act on:
1. Themes: group the feedback into 2 to 4 patterns, with how many candidates mentioned each
2. For each theme: what candidates said (neutral paraphrase, no quotes that could identify anyone), what it probably means, one concrete thing we could change
3. What is working: at least one genuine positive, because there always is one
4. A suggested opening line for the conversation

Rules: describe behaviour and process, never personality. Frame changes as experiments ("we could try") not verdicts. Do not attribute any comment to an identifiable candidate. Keep the whole thing under 300 words.

RAW FEEDBACK (anonymised):
[E.G. "Candidate A: interviewer seemed distracted, checked phone twice. Candidate B: couldn't explain why the role is open. Candidate C: great conversation but heard nothing for 8 days."]
Good looks likeThe manager finishes reading it wanting to fix something rather than defend themselves.
Check firstWith a small number of candidates, even a paraphrase can identify who said what. If only one person interviewed last week, this needs holding until there is more.

Planned for this workflow

  • 4.4 Stakeholder map — for a new account or manager: who decides, who influences, who blocks, and how to work with each.
  • 4.5 Process improvement proposal — turn a recurring problem into a one-page change proposal for the account lead or client HR.
Workflow 5

Candidate experience and offer management

The candidate is the client's future employee and your reputation in the market. The tool is good at volume communication that still feels personal, and at rehearsing the offer conversation before it happens.

Fires whenA shortlist is decided and everyone else needs telling, an offer is about to go out, or a candidate has gone quiet during a slow client process.

5.1 Rejection messages that do not sound automated

Draft
Paste inThe role, the stage each person reached, and one honest line per person about why (anonymised, letters not names).
You are a recruitment partner declining candidates with respect. Some of these people will be candidates again, or will one day be clients.

Write a decline message for each candidate below. Each should:
- Be under 120 words
- Open with something specific to what they brought, not a generic thank you
- Give the honest reason at the level of detail I have marked as shareable
- Say clearly what happens next (nothing, or we will stay in touch, and mean it)
- Leave a [NAME] marker for me to fill

Rules: no "unfortunately", no "at this time", no "we were impressed by your background" without saying what impressed us. Different structure for each so they do not read as a template. British English. Do not promise future roles unless I have said to.

ROLE:
[ROLE TITLE]

CANDIDATES:
[E.G. "A: interviewed round 2, strong technically, other candidate had sector experience (shareable). B: screened only, comp expectation 30% above band (shareable as 'compensation alignment'). C: applied, no relevant experience (keep brief)."]
Good looks likeEach message could only have been written to that person. You would be comfortable receiving it.
Check firstClient policy may restrict the feedback you can give in writing. Check the shareable level against the account's rules before sending.

5.2 Offer and counter-offer preparation

Draft
Paste inWhat you know about this candidate's motivations, current situation and stated expectations, plus the offer parameters the client has approved.
You are an experienced recruitment partner preparing to make a verbal offer and to handle a possible counter-offer from the candidate's current employer.

Using my notes, prepare me:
1. Acceptance risk: Low / Medium / High, with the three factors that drive it
2. How to position the offer verbally: an opening that connects the offer to what this person told me they want, not just the number
3. The questions to ask before I state the figure, so I hear their current position first
4. Counter-offer rehearsal: what their current employer is likely to offer, what the candidate will be tempted by, and how I should respond to each, without disparaging their employer
5. Gaps: anything I should have found out and have not

Rules: be honest about risk. Do not suggest we increase the offer; that is not my decision. Frame everything as helping the candidate make a good decision, because that is also what closes.

CANDIDATE NOTES (anonymised):
[E.G. "Motivated by broader scope and a shorter commute; current employer has counter-offered once before; expects base of X; partner is cautious about change"]

APPROVED OFFER:
[BASE, BONUS, START DATE, ANYTHING FLEXIBLE]

PROCESS CONTEXT:
[E.G. "Has another process at final stage; our client took 3 weeks between rounds"]
Good looks likeYou go into the call with a sequence, not a script. The counter-offer section anticipates something you had not considered.
Check firstDo not let the tool talk you into a risk rating. If your instinct and the rating disagree, your instinct has more data.

Planned for this workflow

  • 5.3 Keep-warm sequence — three short, genuinely informative touchpoints for a candidate stuck in a slow client process.
  • 5.4 Pre-close conversation — a checklist conversation to surface acceptance risks before the offer is formally requested from the client.
Workflow 6

Workload and self-management

The workflow that addresses "complex workload" directly. Fifteen requisitions, forty stakeholders and a client on your shoulder. The tool cannot do the work, but it can be the ten-minute planning conversation you never get to have.

Fires whenMonday morning, after a meeting that generated more actions than you can hold in your head, or before leave and account changes.

6.1 Triage the day from the tracker

Draft
Paste inYour tracker rows for all open roles (header row first, candidate names removed; role titles, stage, days open, last action, next action and owner are the useful columns), plus what is in your inbox and calendar.
You are an experienced recruitment partner helping me plan my day. I have more to do than I can do.

From my tracker and the noise below, give me:
1. The three things that, if I do nothing else today, keep the most important searches moving. For each: what, why it is top three, how long it should take
2. Everything that is waiting on someone else, grouped by who, so I can chase in one message per person
3. Things I can safely leave until later this week, with the date they become urgent
4. Anything in the data that looks like a problem I have not noticed (a role open too long with no activity, a stage where candidates keep stalling)
5. One thing I should say no to, or push back on, today

Rules: prioritise by impact on time-to-fill and client relationship, not by who is shouting loudest, but tell me where those conflict. Use the Owner column to build the "waiting on" groups and the Hygiene column to list rows I should fix before anything else (under two minutes each). Be concrete; "follow up on Role X" is not an action, "send HM-02 the two profiles and ask for a decision by Thursday" is.

TRACKER (paste-ready block, all managers, header row first):
[PASTE THE PASTE-READY BLOCK FROM THE TRACKER]

INBOX AND CALENDAR NOISE:
[E.G. "Manager Z wants an update by lunch; 3 new applications on Role X; offer approval for Role W stuck with client HR; pipeline review at 3pm"]
Good looks likeA plan you disagree with in one place, which means it made you think. Item 4 finds something real about once a week.
Check firstRows copied from Excel come across as tab-separated text, which works well. Include the header row or the tool will guess what the columns mean.
If you have moreCopilot in Excel can be asked these questions directly against the tracker. If the tracker is in the client's OneDrive, check that is permitted before opening it in Copilot.

6.2 Meeting notes to actions

Draft
Paste inRough notes or a transcript. Works for intake meetings, pipeline reviews and internal account calls.
Turn my meeting notes into a clean record I can send to attendees and add to my tracker.

Format:
DECISIONS: what was agreed, one line each
ACTIONS: a table with columns Action / Owner / Due / Which role it relates to. Where I did not capture an owner or date, write "confirm" rather than guessing
OPEN QUESTIONS: things raised but not resolved
FOR MY TRACKER: for each role discussed, the one-line status update I should paste into my tracker's notes column
FOLLOW-UP MESSAGE: a 3-line message to the attendees confirming actions, ready to send

Rules: keep the attendees' words where they matter. Do not add actions that were not discussed. British English.

MEETING NOTES:
[PASTE NOTES OR TRANSCRIPT]

ATTENDEES AND THEIR ROLES:
[E.G. "Me; hiring manager for Roles X and Y; HRBP"]
Good looks likeThe tracker updates paste straight in. The follow-up message goes out within ten minutes of the meeting ending, which is when it changes behaviour.
Check firstOwners and dates. The tool will confidently assign an action to the wrong person if the notes were ambiguous.
If you have moreCopilot in Teams produces a meeting recap; paste that into this prompt for a better-structured result than the recap alone.

Planned for this workflow

  • 6.3 Handover document — from tracker rows and notes to a handover a colleague can pick up cold, for leave or account moves.
  • 6.4 Weekly reflection — a short structured review: where time went, what to push back on, what to raise with the account lead.
Workflow 7

Reporting and account value

Partners rarely have ATS access on site, so reporting starts from the Excel tracker and their own notes. That is fine: a clear narrative from good tracker data beats an ATS dashboard nobody reads. These prompts turn rows into a story the client will act on.

Fires whenThe weekly or fortnightly client update is due, a QBR is coming, or the account is up for renewal or scope discussion.

7.1 Tracker rows to client pipeline update

Draft
Paste inTracker rows for the reporting period (header row first, candidate names removed), the client's preferred format if they have one, and last period's update so the tool can show movement.
You are a recruitment partner writing the regular pipeline update for a client stakeholder who has five minutes and wants to know: are we on track, where are the problems, what do you need from me.

From my tracker data, produce:
1. Summary: three sentences maximum. Overall health, the biggest risk, the most important ask
2. Movement since last update: roles opened, filled, offers made, offers accepted or declined, withdrawals, as a short line each with numbers
3. Per-role table: Role / Days open / Stage / Candidates active / Next milestone / Status (On track, At risk, Stalled, with a one-line reason for anything not on track)
4. Asks of the client: specific decisions or actions we need, with the role and the date
5. Watch-list: anything that will become a problem in the next two weeks if nothing changes

Rules: use the Status column as given (it is calculated from the data); where Override is filled, use the Override and note that it is the partner's judgement. Count roles per status and per stage from the rows and show your working for every total. Movement figures come from comparing with last period's update; if I have not included it, say "movement not available" rather than guessing. Match the tone and structure of last period's update if I have included it. No adjectives, no "great progress".

THIS PERIOD'S TRACKER (paste-ready block, all managers, header first):
[PASTE THE PASTE-READY BLOCK FROM THE TRACKER]

LAST PERIOD'S UPDATE (optional, for format and comparison):
[PASTE OR LEAVE BLANK]

CLIENT FORMAT PREFERENCES:
[E.G. "Table first, narrative after; they track days-to-offer not days-to-fill"]
Good looks likeThe client replies to the Asks section. The table matches your tracker exactly, because it came from it.
Check firstRecount the totals yourself. Arithmetic from pasted tables is the most common error in this whole library, and it is the one a client will notice first.
If you have moreCopilot in Excel can build the per-role table and counts directly from the tracker; then paste that table into this prompt for the narrative and asks.

7.2 QBR talking points

Draft
Paste inThe quarter's headline numbers from your tracker (fills, time-to-fill or time-to-offer, source mix, offer acceptance, withdrawals), the SLA targets if any, and your own honest view of what happened.
You are a recruitment partner preparing talking points for a quarterly business review with a client. The audience is the client's HR director and two hiring leaders. They respect candour and dislike being sold to.

From the numbers and notes below, prepare:
1. The quarter in one paragraph: what we set out to do, what happened, what it means
2. What went well: 3 points, each with a number and the reason behind the number
3. What did not: 2 or 3 points, stated plainly, with our part in it and what we have already changed
4. What we need from the client: process, decision speed, brief quality, whatever the data supports, framed as joint improvements
5. Next quarter: three commitments we can be measured against
6. Anticipated hard questions from the client, with a direct answer to each

Rules: every claim has a number or a specific example beside it. Do not describe a missed target as "nearly achieved". Under 500 words so it fits on two slides or one page.

QUARTER NUMBERS:
[PASTE OR TYPE: FILLS, TIME-TO-FILL, SOURCE MIX, ACCEPTANCE RATE, WITHDRAWALS, SLA TARGETS]

WHAT ACTUALLY HAPPENED (my honest view):
[E.G. "Strong on volume roles, weak on two senior searches where the briefs changed twice; client feedback times averaged 6 days against a 2-day target"]
Good looks likeSection 3 is the strongest part. A QBR that owns its problems is what earns the renewal.
Check firstPercentages and averages: verify each against your tracker. Then have the account lead read it before it goes near the client.

Planned for this workflow

  • 7.3 Value story — for a renewal or scope conversation: what we changed for this client beyond the fills, with evidence.
  • 7.4 Tracker hygiene prompt — superseded by the Hygiene column in the role tracker, which 6.1 now reads directly.
Tool · Demo

Role tracker

One row per requisition. The partner types six things; everything else is calculated, and the column names are exactly what prompts 4.1, 6.1 and 7.1 ask for. This copy runs in the page so you can edit it live in a demo: change a stage or a date, watch the status recalculate, then copy the anonymised paste-ready block straight into a prompt. Edits stay in this browser only; Reset restores the sample.

The tracker runs as its own full-width view so all columns are visible at once. Open it from the tab above or the button below; it keeps the same data in this browser.

Open the tracker →

Design notes

  1. Deliberately no candidate sheet. Candidate counts are typed as numbers, so names never enter the tracker at all and there is nothing to anonymise except the manager column. The cost is that feedback lag per candidate is not measured; if that becomes the argument you need to win with a client, add it then.
  2. Every free-text field is one line. The prompts quote Last action, Next action and Notes verbatim, so they should read as actions: "send two profiles to HM, ask for decision by Thu", not "chased".
  3. Status is calculated, with an override. The paste carries both, so a prompt can see where the partner disagreed with the data. Frequent overrides are a sign the rules need tuning for that account, not that the partner is wrong.
  4. Hygiene flags missing next action, overdue next action and no activity date, so 6.1 can point at rows to fix before it plans the day. That replaces the planned 7.4 hygiene prompt.
  5. Due date is not typed. It is the open date plus 40 business days, the time-to-offer KPI on almost every programme, so it cannot drift and every partner measures the same thing. If a programme runs a different KPI, that is one number to change.
  6. The Excel version is the same columns with data validation lists, the calculated columns as formulas (WORKDAY for the due date), and a locked Paste-Ready sheet. Open question: one tracker per client or per partner, which decides whether Client becomes a column.
Working notes

Open questions and next steps

To decide

  1. Which three prompts go into the pilot? Suggested: 1.1, 4.1 and 7.1, because they touch the brief, the manager and the client, and all three run off inputs partners already have.
  2. Tracker adoption. The role tracker is now the standard 4.1, 6.1 and 7.1 assume. The realistic risk is that partners do not keep it current; the design bets on six typed fields and a Friday ten-minute ritual. Watch the Hygiene column in the first month as the adoption signal.
  3. Client-policy sign-off. The "Where can this go?" table needs confirming per account before anything with candidate data goes into a client's Copilot, even anonymised.
  4. Language. Drafted in British English; some markets will want variants, and some prompts (outreach, rejections) should exist in local languages where partners work in them.
  5. Voice. The prompts ban a handful of recruiter clichés. Worth agreeing that list with the team so the outputs sound like us.

Next build steps

  1. Test each drafted prompt in a plain Copilot chat with a real (anonymised) brief and tracker extract; record where the output is weak and tighten the rules line.
  2. Add one worked example per workflow: real input, real output, annotated with what was kept and what was changed. These do more teaching than the prompts themselves.
  3. Draft the 12 planned prompts, prioritising 1.4, 3.4, 6.3 and 7.4.
  4. Then the training layer: a 45-minute foundations session (brief pattern, anonymisation, where-can-this-go, checking), followed by weekly 15-minute "bring a prompt" sessions per account.

For IT and testers

This page is a single self-contained file. It runs entirely in the browser, makes no network requests after loading (fonts and images are embedded), sets no cookies, and transmits nothing. Tracker edits are kept in this browser's local storage on this machine only; clearing site data removes them. No candidate, client or personal data is included or collected. Prompts are copied to your clipboard only when you press Copy.

Partner Prompt LibraryWorking draft — feedback welcomev0.7 · test build
Tool

Role tracker

One row per requisition. Type the open date and the due date follows at 40 business days (the time-to-offer KPI). Everything in blue is calculated. Edits stay in this browser; Reset restores the sample.

Partner typesStage · Active candidates · At interview or beyond · Last activity · Next action, owner and due · Notes
Set once at intakeRole title · Hiring manager · Priority · Date opened (due date = 40 business days later, the TTO KPI)
CalculatedDue date · Days open · Days to due · Days since activity · Status · Hygiene
Role IDRole titleHiring managerPriorityStageStatusOpened → due (40 BD)Days openDays to dueActive candidatesAt interview+Last activityDays since activityNext actionOwnerDueOverrideNotesHygiene
Status rules Stalled no activity for more than 7 days Blocked on client next action sits with the manager or client HR and is overdue At risk under 7 days to the 40-business-day due date before Offer, or already past it On track otherwise On hold / Filled excluded from the rules

Paste-ready block — manager names replaced by codes, tab-separated, header row first. This is the only thing that leaves the tracker.

Use it with 4.1 Hiring manager meeting prep (filter to one manager first), 6.1 Triage the day and 7.1 Client pipeline update.