These prompts are for HR Managers who have a workforce planning deliverable due this week and need a finished draft — not a framework to fill in themselves. Paste any prompt into ChatGPT or Claude, swap in your numbers, and walk away with a one-pager, a brief, a talking-points doc, or an email you can send with minor edits.
These prompts pair well with Jasper AI for HR Managers-specific tone control, or Copy.ai for fast iteration across multiple business units.
Headcount Gap Analysis and Forecasting
You are an HR Manager preparing a headcount gap analysis for a leadership review.
Business unit: {business_unit_name} Current headcount: {current_headcount} Approved headcount for end of {fiscal_year}: {approved_headcount} Roles currently vacant: {vacant_roles_listed_by_title} Roles at risk of attrition in the next 6 months: {at_risk_roles_and_reasons} Strategic priority this unit must deliver: {top_strategic_priority}
Write a 300 to 400 word headcount gap analysis. Open with a one-sentence summary of the gap. Use a structured narrative — current state, projected state, risk if gap is not closed. Close with three specific hiring or redeployment recommendations tied to the strategic priority. Tone: direct and data-led. No filler.
When to use it: Monday morning before a quarterly business review when your HRBP asks you to brief the VP on headcount status.
Pro tip: If your at-risk roles are based on gut feel rather than data, state that in the variable — the model will flag uncertainty in its output, which is actually more defensible in a leadership meeting than false precision.
You are an HR Manager writing a three-year workforce demand forecast for a business function that is expected to grow.
Function: {function_name} Current team size: {current_team_size} Projected revenue or output growth over 3 years: {growth_percentage_or_metric} Key capability gaps identified today: {two_to_four_capability_gaps} Known constraints (budget, location, talent market): {constraints} Hiring lead time for critical roles: {average_weeks_to_hire}
Write a 400 to 500 word demand forecast in narrative form. Year 1, Year 2, Year 3 as separate paragraphs. Each year should name how many net-new hires are needed, which capabilities are priority, and what the risk is if hiring lags behind growth. End with a one-paragraph executive summary the CHRO can read in 30 seconds.
When to use it: Before submitting a business case to finance for next fiscal year’s headcount budget.
Pro tip: Feed the growth percentage as a range (e.g. “12–18%”) rather than a single number. The model will produce a low-case and high-case scenario, which is exactly what finance will ask for anyway.
You are an HR Manager producing a skills gap brief for a department moving from manual processes to automated workflows.
Department: {department_name} Headcount affected: {number_of_employees} Current dominant skills: {three_to_five_current_skills} Skills required post-automation: {three_to_five_future_skills} Timeline for automation rollout: {rollout_timeline} Budget available for upskilling: {upskilling_budget_or_none}
Write a 350 to 450 word skills gap brief. Structure it as: current capability snapshot, future capability requirement, the specific gap, and options to close the gap (reskill, hire, contract). Be direct about which roles are most at risk of redundancy. Tone: factual and frank. This will be read by a Head of Operations who does not like HR jargon.
When to use it: When a tech implementation project lands on your desk and you need to brief the business on workforce impact before the project kicks off.
Pro tip: List current skills in plain language, not competency-framework language. “Builds Excel reports manually” is more useful than “data literacy Level 2” because the model produces more specific gap statements.
You are an HR Manager writing an internal briefing note on workforce supply risk for a specific geography.
Location: {city_or_region} Roles hardest to fill: {two_to_three_hard_to_fill_roles} Average time to fill those roles historically: {average_days_to_fill} Competitor activity in this market: {known_competitor_hiring_or_expansion} Your organisation’s employer brand strength in this market: {strong / moderate / weak} Any upcoming internal demand spikes: {upcoming_projects_or_growth_drivers}
Write a 300-word internal briefing note. Start with the risk level (high / medium / low) and the one-sentence reason why. Cover talent supply, competitor pressure, and your current brand position. End with two short-term actions and one longer-term recommendation. Tone: concise and honest. No HR buzzwords.
When to use it: When a hiring manager says “we can’t find anyone” and you want a written position to send them before the 1:1.
Pro tip: If you don’t have hard data on competitor activity, write “anecdotal — based on LinkedIn activity and candidate feedback” in the variable. The model will caveat accordingly, which protects you if the note gets forwarded.
You are an HR Manager preparing a workforce planning scenario analysis for a business that may need to reduce headcount.
Business unit: {business_unit_name} Current headcount: {current_headcount} Potential reduction range: {low_end_number} to {high_end_number} roles Functions most likely affected: {affected_functions} Timeframe for decision: {decision_timeline} Legal or consultation requirements in this jurisdiction: {consultation_requirements_or_none_known}
Write a 450 to 550 word scenario analysis covering three scenarios: minimal reduction, mid-range reduction, full reduction. For each scenario, state the headcount impact, the operational risk, the people cost (redundancy, morale, retention of key talent), and the timeline implication. Close with a recommendation on which scenario to model in detail first. Tone: measured, factual, no euphemisms about “restructuring opportunities”.
When to use it: When a CFO calls with a cost target and you have 48 hours to respond with a workforce impact assessment.
Pro tip: Always include the legal/consultation variable even if you write “unknown — check with employment counsel.” The model will surface the fact that this needs legal sign-off, which is a useful paper trail if the document is reviewed later.
Headcount Business Case Writing
You are an HR Manager writing a headcount business case to hire two net-new roles.
Role titles: {role_title_1} and {role_title_2} Business unit sponsor: {sponsor_name_and_title} Problem these roles solve: {specific_business_problem_in_one_sentence} Cost of not hiring (quantified if possible): {cost_or_risk_of_status_quo} Estimated fully-loaded cost per role: {annual_cost_per_role} Timeline to productivity for a new hire: {weeks_to_productivity}
Write a 400 to 500 word headcount business case. Format: problem statement, proposed solution, financial justification, risk of inaction, and a one-sentence ask. Write it so a CFO who has never seen the team’s work understands the ROI within 60 seconds. Tone: confident and commercially literate.
When to use it: Before any headcount approval gate — budget cycle, mid-year review, or ad-hoc request.
Pro tip: “Cost of not hiring” is the variable finance actually reads. If you don’t have a number, use a range or a qualitative risk statement. The model will structure it as a risk argument rather than an ROI argument, which is still effective.
You are an HR Manager writing a request to convert a contractor role to a permanent position.
Contractor name or role description: {contractor_role_description} Duration they have been contracting: {contract_duration} Monthly contractor cost: {monthly_contractor_cost} Equivalent permanent salary estimate: {estimated_permanent_salary} Strategic reason for conversion: {business_reason_for_permanence} Risks of staying on contractor arrangement: {two_risks_of_continued_contracting}
Write a 300 to 350 word conversion request memo addressed to the Finance Director. Lead with the financial comparison over a 12-month horizon. Follow with the strategic rationale. Close with a recommended conversion date and next steps. Tone: businesslike, no sentiment about the individual’s performance.
When to use it: When a hiring manager wants to lock in a contractor they’ve been extending every three months and you need finance to approve the conversion.
Pro tip: Calculate the 12-month cost comparison yourself before running the prompt — total contractor cost including agency margin vs total employment cost. The model will structure the argument; you need the numbers to be accurate before you paste them.
You are an HR Manager writing a business case to restructure a team from three specialist roles into two broader generalist roles.
Current team structure: {current_three_role_titles_and_headcount} Proposed structure: {proposed_two_role_titles} Reason for restructure: {strategic_or_operational_driver} Estimated saving: {annual_saving_if_known} Risk to service delivery: {specific_risk_and_mitigation} Consultation required: {yes_with_timeline / no}
Write a 400-word business case for the restructure. Sections: rationale, proposed new structure, financial impact, people risk and mitigation, and a recommended timeline. Write it for a joint HR-Finance sign-off meeting. Tone: measured and structured.
When to use it: When a business leader wants to restructure but hasn’t written anything down, and you need a document to anchor the conversation.
Pro tip: Put the consultation variable in even if the answer is “no legal requirement” — it signals to the reader that the HR Manager checked, which matters if someone challenges the process later.
You are an HR Manager drafting a justification to backfill a role that leadership has put on hold.
Role title: {role_title} How long the role has been vacant: {weeks_vacant} Work currently being absorbed by: {who_is_covering_and_how} Measurable impact of vacancy so far: {output_delays_or_quality_issues} Original reason leadership put it on hold: {stated_reason_for_hold} What has changed since then: {new_information_or_context}
Write a 300-word backfill justification email to the business unit Director. Open by acknowledging the original hold decision. Present two or three specific consequences that have occurred since then. Close with a request to reopen the approval, with a proposed start-to-hire timeline. Tone: assertive but not adversarial.
When to use it: Six to eight weeks after a backfill freeze when a hiring manager is escalating pressure on you to do something.
Pro tip: “What has changed since then” is the pivot point of the whole email. If nothing has genuinely changed, don’t use this prompt — it will produce a weak argument. Instead, reframe around cumulative cost of the vacancy.
You are an HR Manager writing a one-page workforce investment summary ahead of a board talent committee meeting.
Company size: {total_headcount} Total open roles: {number_of_open_roles} Roles classified as business-critical: {number_of_critical_roles} Year-to-date hiring spend: {ytd_hiring_spend} Average time to fill across all roles: {average_days_to_fill} One workforce risk the board should be aware of: {top_workforce_risk}
Write a 400 to 500 word board summary. Use three sections: Workforce Snapshot, Investment to Date, and Key Risk and Recommended Action. Write for a board member who reads HR updates in under two minutes. No HR jargon. Include numbers prominently. Tone: clear and strategic.
When to use it: The week before a board or talent committee meeting when your CHRO asks for “a one-pager on where we are with hiring.”
Pro tip: Board members respond to risk framing more than process framing. Put your one workforce risk front and centre in the variable — the model will open and close with it, which is where board attention lands.
Attrition and Retention Workforce Analysis
You are an HR Manager writing an attrition analysis summary for a specific department that has lost more staff than usual this year.
Department: {department_name} Attrition rate this year: {this_year_percentage} Attrition rate last year: {last_year_percentage} Roles that left most frequently: {two_to_three_roles} Exit interview themes (top 2–3): {exit_interview_themes} Cost estimate per departure (if known): {cost_per_departure_or_unknown}
Write a 350 to 450 word attrition analysis. Cover: what the data shows, the pattern by role or level, the likely root cause based on exit themes, and the financial exposure. Close with two targeted retention actions tied directly to the exit themes. Tone: evidence-led, direct. This will be read by the Head of the Department, not HR.
When to use it: When a business leader asks “why are people leaving my team” and you want a written answer before the meeting, not just a conversation.
Pro tip: If you only have one or two exit interviews, say so in the variable as “limited sample — n=2.” The model will caveat the root cause section appropriately, which is more credible than stating causes with false confidence.
You are an HR Manager writing a retention risk memo about a high-performing employee who has signalled they are considering leaving.
Employee role and level: {role_and_level} Tenure: {tenure} Signal received: {what_was_said_or_observed} What the employee values based on past conversations: {two_to_three_known_motivators} What the business can realistically offer: {retention_levers_available} Risk to the team if they leave: {operational_or_knowledge_risk}
Write a 250 to 300 word internal retention risk memo addressed to the employee’s direct manager. Be specific about the risk, realistic about the levers available, and suggest a concrete conversation approach the manager can use in their next 1:1. Do not write a script — write guidance the manager can act on immediately. Tone: candid and practical.
When to use it: When you hear through a manager that a key person is “looking around” and you need to get the manager moving before it becomes an exit.
Pro tip: Don’t overstate the retention levers in the variable if they don’t exist. If the honest answer is “we can offer a project change but not a pay increase,” write that. The model will produce a more realistic and credible memo than if you overstate options.
You are an HR Manager drafting a talking-points document for a manager who needs to have a stay conversation with a direct report at risk of leaving.
Employee role: {employee_role} Reason they may be at risk: {attrition_risk_reason} Manager’s relationship with this employee: {strong / neutral / strained} What the company can offer: {realistic_retention_offers} What the manager should avoid saying: {topics_or_phrases_to_avoid} Desired outcome of the conversation: {stay_and_engage / explore_options / mutual_clarity}
Write a set of 5 to 7 talking points for the manager to use in a 20-minute stay conversation. Each talking point should be a sentence or short paragraph the manager can say or paraphrase. Include