These prompts are for HR business partners who need a finished draft, not a starting point. Each one targets a specific HRBP conversation — a difficult manager discussion, a leadership update, a reorg briefing, a performance escalation — and produces something you can use or send with minimal editing.
These prompts pair well with Jasper AI for HR Managers-specific tone control, or Copy.ai for fast iteration.
Difficult Manager Conversations
You are an HR business partner preparing to speak with a line manager about a performance concern raised by their direct report.
Manager name: {manager_name} Manager’s role: {manager_role} Department: {department} Nature of the concern: {concern_summary_in_two_to_three_sentences} Number of employees who have raised similar concerns: {number_of_employees} Tone: {neutral / direct / cautious} Desired outcome of the conversation: {specific_outcome}
Write a 250 to 300 word coaching script I can use in the meeting. Open by naming the pattern of concern without attributing it to a specific person. Use the SBI model (Situation, Behaviour, Impact) to structure the middle section. Close with one direct question that invites the manager to reflect and one proposed next step I can put on record. Do not produce talking points or a list. Write it as flowing speech I can follow.
When to use it: Monday morning before a 10am conversation you booked on Friday and haven’t prepared for yet.
Pro tip: Set {tone} to “cautious” only if the manager has a documented history of reacting defensively — the AI will soften the language enough that you lose the impact of the SBI section if the situation doesn’t warrant it.
You are an HR business partner. A senior manager has been flagged for micromanaging behaviour. You need to deliver feedback without triggering a grievance from the manager or losing their cooperation.
Manager name: {manager_name} Role level: {director / head_of / senior_manager} Specific observed behaviour: {behaviour_description} Who observed it: {peers / direct_reports / skip_level} Previous conversations on this topic: {yes_with_detail / no} Stakes if the behaviour continues: {business_impact_in_one_sentence}
Write a 200 to 250 word verbal script for the start of the feedback meeting only. Use the GROW model (Goal, Reality, Options, Will) to structure it. The opening sentence must name the reason for the meeting plainly. Do not use softening phrases like “I just wanted to” or “this is just a quick chat”. End with an open question that surfaces the manager’s perspective before I respond.
When to use it: Before any feedback meeting where the manager outranks you politically and you need to sound confident from the first sentence.
Pro tip: Paste the output into a notes app on your phone so you can glance at it without holding paper in the meeting — it signals less formality than a printed sheet, which matters with senior stakeholders.
You are an HR business partner writing a follow-up email after a difficult conversation with a line manager about a conduct issue in their team.
Manager name: {manager_name} Date of conversation: {conversation_date} Issue discussed: {conduct_issue_summary} Actions the manager agreed to: {agreed_actions_in_bullets} Deadline for first update: {deadline} Tone: {professional / firm / collaborative}
Write a 150 to 200 word follow-up email. Open with one sentence confirming the purpose of the email. Summarise the agreed actions in a short numbered list. State the deadline clearly. Close with one sentence that makes it clear this email forms part of the written record without using threatening language. No pleasantries at the top. Subject line included.
When to use it: Within two hours of the meeting ending, before either party’s memory of what was agreed starts to drift.
Pro tip: If the conduct issue is serious enough that it might reach an employment tribunal, replace {tone} with “firm” and ask your legal team to review before sending — the AI won’t flag legal risk, you have to.
You are an HR business partner. A line manager has come to you informally saying they want to dismiss a direct report but have not followed any performance management process. You need to slow this down and redirect them without damaging the relationship.
Manager name: {manager_name} Employee at risk: {employee_role_not_name} Reason manager wants to dismiss: {managers_stated_reason} Current documentation on file: {none / informal_notes / PIP_in_progress} Business urgency the manager is citing: {urgency_claim} Jurisdiction: {country_or_region}
Write a 200 to 250 word verbal script for the conversation where I redirect the manager toward a proper process. Acknowledge their frustration in the first sentence. Explain the legal exposure in plain terms without sounding like a compliance lecture. Propose a specific next step — either a PIP, a documented informal conversation, or a capability process — and name which one based on what’s already on file. Do not hedge. Give them a clear recommendation.
When to use it: The moment a manager calls you with “I just need to let someone go, can you help me write a letter.”
Pro tip: Fill {current_documentation} accurately — if you write “none” and the AI recommends jumping straight to a PIP, that’s actually correct advice and it will save you a step when you brief the manager.
You are an HR business partner writing a briefing note for yourself ahead of a mediation session between two managers in the same leadership team who have an ongoing conflict.
Manager A name and role: {manager_a_name_and_role} Manager B name and role: {manager_b_name_and_role} Nature of the conflict: {conflict_summary_in_three_sentences} Duration of the conflict: {duration} Attempts to resolve it so far: {previous_attempts} Business impact: {impact_on_team_or_output}
Write a 300 to 350 word internal briefing note I will read five minutes before the session starts. Structure it as: background (three sentences), my goals for this session (three bullet points), risks to manage (two bullet points), and two opening questions I will ask in the room to start the conversation without taking sides. Write it for me to read, not to share with either manager.
When to use it: When you have back-to-back meetings and the mediation session snuck up on you.
Pro tip: The “risks to manage” section is where the AI earns its keep — describe the conflict accurately in {conflict_summary} and it will often surface dynamics you haven’t consciously named yet.
Leadership Team Updates and Briefings
You are an HR business partner preparing a verbal update for a leadership team meeting on current people risks in the business.
Business unit: {business_unit} Key risks to cover: {two_to_four_risks_in_bullets} Relevant data points: {data_points_eg_attrition_rate_headcount_open_roles} Time available to speak: {minutes} Audience seniority: {C-suite / VP_level / director_level} Tone: {data-led / narrative / direct}
Write a spoken update script of exactly {minutes} minutes of speech (approximately 130 words per minute). Open with the most critical risk, not with context-setting. Use one data point per risk to anchor each point. Close with a single recommendation the leadership team can approve or reject in the room. No bullet points in the script — write it as continuous speech. Include a one-sentence transition between each risk.
When to use it: When you’ve been given a slot in ExCo and you need to sound like you’ve been doing this for years.
Pro tip: After generating the script, read it aloud and time it yourself — AI word counts and actual speaking pace don’t always match, and running 90 seconds over in an ExCo slot is a credibility hit.
You are an HR business partner writing a one-page people update for a business unit director ahead of their monthly board report.
Director name: {director_name} Business unit: {business_unit} Reporting period: {month_and_year} Headcount change this period: {headcount_change} Top hiring priority: {role_or_team} Attrition highlights: {attrition_data_and_any_notable_leavers} One people risk to flag: {risk_description}
Write a 350 to 400 word one-page people update in prose, not bullets. Write in the third person so the director can paste it directly into their board report. Open with headcount. Cover hiring progress in the second paragraph. Address attrition in the third. Flag the people risk in the fourth with a proposed mitigation in one sentence. Close with a forward look for next period in two sentences. Formal register throughout.
When to use it: When the director messages you at 4pm on a Thursday saying the board pack is due by noon Friday.
Pro tip: Set the register in the final output by reading the first sentence back — if it sounds like a news article, add “formal” to your {tone} override and regenerate just the opening paragraph rather than the whole thing.
You are an HR business partner writing a briefing email to a new executive joining the business in 30 days. The email introduces them to the current state of the people agenda in their function before their first day.
Executive name: {executive_name} Role they are joining: {executive_role} Function they will lead: {function} Team size: {headcount} Two strengths of the current team: {team_strengths} Two live challenges: {live_challenges} One open people risk you want them to know early: {early_risk}
Write a 300 to 350 word email from me as their HR business partner. Open by welcoming them and naming your role. Use one paragraph for team strengths, one for current challenges, one for the open risk. Close by proposing a 30-minute call in their first week and naming two specific agenda items for that call. Professional but warm tone. No HR jargon.
When to use it: When a senior hire is confirmed and you want to start the relationship before day one instead of scrambling to catch up in their first week.
Pro tip: The {early_risk} field is the most important one — be specific. “Low team morale” produces a useless paragraph. “Two high performers in the team have active conversations with competitors following last quarter’s bonus announcement” produces a paragraph the executive will actually remember.
You are an HR business partner writing talking points for a CEO who needs to address the leadership team about a restructure that will be announced next week.
CEO name: {ceo_name} Nature of the restructure: {restructure_summary} Number of roles affected: {number_of_roles} Key message the CEO wants to land: {core_message} What leadership team members are most likely to ask: {top_two_anticipated_questions} Tone: {confident / empathetic / direct}
Write 300 to 350 words of talking points structured as: opening statement (one paragraph), three key messages (each one sentence followed by two sentences of supporting rationale), anticipated questions with suggested responses (two Q&As). Write in the CEO’s voice, not mine. No bullet hierarchy — write each section as prose the CEO can read at a glance. Label each section clearly.
When to use it: The night before the leadership session when the CEO forwards you the calendar invite and says “can you prep me something.”
Pro tip: Fill {top_two_anticipated_questions} with the hardest questions, not the obvious ones — if you write “when will we know who is affected,” the AI gives a generic answer. If you write “why are we cutting this team when we just hired into it,” the AI has to work harder and the output is sharper.
You are an HR business partner writing an internal announcement for a department head to send to their team following an organisational design change that removes one layer of management.
Department head name: {department_head_name} Department: {department} Change being announced: {change_description} Effective date: {effective_date} Roles eliminated: {number_of_roles_eliminated} What stays the same for remaining employees: {continuity_points}
Write a 250 to 300 word all-team email from the department head. Open with the change and the date — do not bury the news. Use plain language. Acknowledge that this affects real people without making promises that haven’t been approved. Explain what stays the same for the people reading the email. Close with one clear action (e.g., attend a team meeting, expect a follow-up by a specific date). Do not use the words “exciting”, “journey”, or “opportunity” in any context.
When to use it: When the department head says “I don’t know how to write this” and sends you a blank draft at 8pm.
Pro tip: The instruction to avoid “exciting”, “journey”, and “opportunity” matters — paste the output into a word processor and search for those words before sending. AI occasionally ignores style rules when it generates long paragraphs.
Performance Escalations and PIPs
You are an HR business partner drafting a performance improvement plan (PIP) introductory letter for a mid-level employee who has been underperforming against measurable targets.
Employee name: {employee_name} Job title: {job_title} PIP duration: {duration_in_weeks} Specific performance gaps: {two_to_three_gaps_with_data} Targets to meet during the PIP: {measurable_targets} Review checkpoints: {checkpoint_dates} Consequence if targets are not met: {stated_consequence}
Write a 350 to 400 word formal letter opening a PIP. Use plain English throughout — no legalese. Open with the purpose of the letter. Describe each performance gap with reference to the data. State the targets and checkpoints clearly. State the consequence once, plainly, at the end. Do not soften the consequence or hedge it. The letter should be suitable to sign and send as-is. Include a space for the employee’s signature confirming receipt.
When to use it: When you’ve agreed the PIP with the manager and legal and you need the document drafted before the meeting tomorrow.
Pro tip: Run the output through your company’s standard letter template for formatting only — do not re-prompt the AI to “make it sound more like our style” unless you’ve defined that style precisely, or it will start hedging the consequence language.
You are an HR business partner writing a script for the meeting where a line manager will formally open a performance improvement plan with their direct report. You will coach the manager through the meeting structure.
Manager name: {manager_name} Employee name: {employee_name} Performance issue summary: {issue_summary} PIP duration: {pip_duration} Employee’s likely reaction: {defensive / emotional / disengaged / unknown} Previous informal conversations: {yes / no}
Write a 300 to 350 word meeting script for the manager to follow. Structure it as: opening (set context, 30 seconds), issue statement using SBI (90 seconds), PIP overview (60 seconds), employee response space (a pause instruction), and close (next steps, 30 seconds). Include a bracketed stage direction before each section. Write in the manager’s voice, not mine. Flag one phrase to avoid in a note at the bottom.
When to use it: When a manager tells you they’ve never opened a PIP before and the meeting is in two hours.
Pro tip: The phrase-to-avoid note at the bottom is worth reading carefully — the AI will usually flag something like “you need to improve” (too vague) or “this is just a formality” (legally problematic). Both are things managers actually say.
You are an HR business partner writing a mid-PIP progress review note