Most AI prompt lists for HR professionals are written by people who have never done HR. They are vague, structurally generic, and would produce outputs no HR manager could use without rewriting them entirely.
This library is different. Every prompt below is written for a specific HR task, includes the context variables that make AI output useful, and is formatted so you can copy it directly into ChatGPT, Claude, or Microsoft Copilot and get a working first draft.
The prompts are organised by workflow area. Fifty prompts across seven categories. Before you start, there is one important rule.
Never include real employee names, personal identifiers, employment IDs, health information, salary figures tied to individuals, or any data that could identify a specific person in a prompt you send to a public AI tool. Use role titles, anonymised descriptions, and generic department references instead. If your organisation has a private AI deployment or approved enterprise AI agreement, follow your IT and legal team's guidance on what is permissible. See our guide on what data you can put into ChatGPT at work for a full breakdown.
1. Job descriptions and recruitment
These prompts produce drafts you can edit — not finished documents. The value is eliminating the blank page and surfacing structural problems early.
What makes these prompts effective: Specificity about level, reporting structure, and competencies is what separates a useful JD draft from a generic one. Always include whether the role is individual contributor or people manager, the team size, and the primary success metric for the role.
Prompt 1 — Job description draft
You are an experienced HR business partner. Write a job description for a [SENIORITY LEVEL] [JOB TITLE] role at a [COMPANY SIZE, e.g. 200-person] [INDUSTRY] company. The role reports to [REPORTING LINE]. Key responsibilities: [LIST 3–5 RESPONSIBILITIES]. Required competencies: [LIST 4–6 COMPETENCIES]. The role is [INDIVIDUAL CONTRIBUTOR / PEOPLE MANAGER]. Do not include vague requirements like "strong communication skills" without a behavioural definition. Format: job title, one-paragraph summary, responsibilities (bullet list), required competencies (bullet list), nice-to-have skills (bullet list).
Prompt 2 — JD bias review
Review the following job description for gendered language, unnecessarily exclusive requirements, degree mandates where experience would suffice, and any phrasing that could discourage underrepresented candidates from applying. For each issue, explain why it is a concern and suggest a replacement. [PASTE JD]
Prompt 3 — Competency-based interview question bank
Generate a bank of 15 behavioural interview questions for a [JOB TITLE] role. Map each question to one of these competencies: [LIST COMPETENCIES FROM JD]. Include 2–3 questions per competency. Format as a table with columns: competency, question, what a strong answer would demonstrate.
Prompt 4 — Screening criteria scorecard
Create a structured screening scorecard for a [JOB TITLE] role. Use these must-have criteria: [LIST CRITERIA]. And these nice-to-have criteria: [LIST CRITERIA]. Format as a table with: criterion, weighting (must-have or nice-to-have), how to assess from a CV or application, pass/fail or scored 1–3.
Prompt 5 — Role brief for hiring managers
Write a one-page role brief for a hiring manager who will be interviewing candidates for a [JOB TITLE] position. Include: why we are hiring this role, what success looks like in the first six months, the three most important competencies to assess, what this role does NOT do (to avoid scope confusion), and suggested focus areas for the hiring manager's interview questions. Context: [BRIEF CONTEXT ABOUT THE TEAM AND ROLE].
Prompt 6 — Candidate rejection email
Write a professional, respectful rejection email for a candidate who applied for a [JOB TITLE] role and was not selected after [SCREENING STAGE / INTERVIEW STAGE]. Tone: warm but clear — no false hope. Length: 4–6 sentences. Do not invite them to reapply unless that is genuinely appropriate. Do not give specific feedback unless the process included a commitment to do so.
Prompt 7 — Job offer email
Write a job offer email for a [JOB TITLE] role. Include: a genuine congratulatory tone, the key offer details (role title, start date placeholder, reporting line, location/remote arrangement), a clear call to action for acceptance, and a contact name for questions. Do not include salary or compensation figures — those will be added manually. Tone: professional and welcoming.
Prompt 8 — Intake meeting agenda for a new role
Create a 45-minute intake meeting agenda for an HR business partner meeting with a hiring manager to kick off recruitment for a new [JOB TITLE] role. Include: role definition and success criteria, ideal candidate profile, deal-breakers and non-negotiables, interview process design, timeline expectations, and any known constraints. Format as a structured agenda with time allocations.
Always run a bias review (Prompt 2) on every JD before it is published — including ones you have written yourself. AI reflects the patterns in the language it was trained on, which means JD drafts can reproduce biased phrasing even when you have asked it not to. The review step is not optional.
2. Onboarding
Onboarding documentation is chronically underdeveloped in most organisations because it takes time to create and is role-specific. These prompts solve the blank-page problem for the most common documents.
What makes these prompts effective: Always specify the role, seniority level, team, tools, and key stakeholders. Generic onboarding content is useless. Role-specific content is the thing new hires actually need.
Prompt 9 — First-week checklist
Create a structured first-week checklist for a new [JOB TITLE] joining a [TEAM NAME] team at a [COMPANY SIZE] company. Include: day one priorities (access, introductions, tools), end-of-week goals, key people to meet, systems to set up, and any role-specific onboarding tasks. Format as a day-by-day breakdown for Monday through Friday.
Prompt 10 — Welcome email from the hiring manager
Write a welcome email from a hiring manager to a new team member starting as a [JOB TITLE] on [START DATE]. Tone: warm, genuine, and not corporate-sounding. Include: a genuine welcome, what their first day will look like, who to ask if they need anything, and one sentence about what the team is working on right now. Length: 150–200 words.
Prompt 11 — 30/60/90-day plan framework
Write a 30/60/90-day onboarding plan for a new [SENIORITY LEVEL] [JOB TITLE]. Structure each phase as: primary focus, key goals, success indicators, and relationships to build. The role is [brief description of the role's scope and context]. Make the goals specific enough to be measurable but flexible enough that a manager can adapt them to the individual.
Prompt 12 — Buddy programme guidance document
Write a one-page guidance document for an onboarding buddy at a [COMPANY TYPE] company. Include: what a buddy's role is and is not, four to five suggested activities for the first month, tips for being genuinely helpful versus just available, and how to flag if the new joiner seems to be struggling. Tone: practical and peer-to-peer — not formal HR policy language.
Prompt 13 — New joiner team announcement
Write a team Slack/email announcement introducing [NEW JOINER'S ROLE TITLE] who is starting on [START DATE]. Include: their role and what they will be working on, their background (written for me to fill in), their start date, and a warm welcome from the team. Do not include personal details. Length: 100–150 words. Tone: friendly and professional.
Prompt 14 — Onboarding survey questions
Write a set of 8–10 onboarding survey questions for new joiners to complete at the end of their first 30 days. Focus on: clarity of role expectations, quality of onboarding support, tool and systems access, sense of belonging, and any gaps in what they were told versus reality. Use a mix of rating scales (1–5) and one open text question. Avoid leading questions.
3. Performance management
Performance management generates a high volume of writing — templates, feedback frameworks, calibration guidance, and manager communications — most of which is done under time pressure and often inconsistently.
What makes these prompts effective: Specificity about competency, seniority level, and the direction of feedback (developmental vs. critical) is what separates useful output from performative boilerplate. Never include identifying information about a real employee in these prompts.
Prompt 15 — Performance review template
Write a performance review template for a [SENIORITY LEVEL] [JOB TITLE] role. Include sections for: overall performance rating context, achievements against goals, strengths with behavioural examples, development areas with specific observations, and goals for the next review period. Each section should include guidance notes for the reviewer on what to write and what to avoid. Format as a Word-style document template.
Prompt 16 — Constructive feedback framing
Help me frame a piece of constructive feedback for a [SENIORITY LEVEL] team member who [DESCRIBE THE PERFORMANCE ISSUE WITHOUT NAMING THE PERSON, e.g. "regularly misses deadlines on collaborative work items and does not flag blockers early enough"]. The feedback needs to be specific and actionable, not vague or punitive. Write three different versions: direct, coaching-oriented, and documentary (suitable for a formal record). Each should be 3–5 sentences.
Prompt 17 — Development plan draft
Write a professional development plan for a [SENIORITY LEVEL] [JOB TITLE] who is strong technically but needs to develop [DEVELOPMENT AREA, e.g. "stakeholder communication and influencing skills"]. Include: a clear statement of the development goal, two to three specific actions they can take in the next 90 days, a suggested resource or learning activity, and how progress will be assessed. Format as a structured one-pager.
Prompt 18 — Goal-setting framework for a new review cycle
Generate a goal-setting framework email for managers to send to their direct reports at the start of a performance review cycle. Include: the purpose of the goal-setting conversation, how to write a measurable goal, the number of goals recommended (3–5), the distinction between output goals and development goals, and a suggested deadline for the manager-direct report goal-setting conversation. Tone: clear and practical — not bureaucratic.
Prompt 19 — Underperformance conversation guide
Write a structured conversation guide for a manager preparing to have a formal underperformance discussion with a direct report who [DESCRIBE PATTERN, e.g. "has missed three consecutive delivery milestones and has not responded to informal coaching"]. Include: how to open the conversation, how to describe the performance gap factually, how to invite the employee's perspective, how to move to a plan, and how to close with clear next steps. Do not include names or identifying details. Note: this guide does not constitute legal advice — HR sign-off is required before any formal process.
Prompt 20 — Performance review calibration agenda
Write a calibration session agenda for a team of [NUMBER] managers reviewing [NUMBER] direct reports across [REVIEW PERIOD]. Include: pre-work instructions for managers, the calibration discussion format (how to present a rating, how to challenge a rating), time allocation per person, how to handle disagreement, and how to record outcomes. Timebox the session to [SESSION LENGTH, e.g. 2 hours].
Prompt 21 — Self-assessment prompt template for employees
Write a self-assessment prompt template for employees completing their own performance review. Include prompts for: key achievements and impact, how they have demonstrated [LIST 2–3 CORE COMPETENCIES], one area of growth they are proud of, one area they want to develop in the next period, and any context or challenges that shaped their performance. Tone: supportive — the template should encourage honest reflection, not defensive writing.
Prompt 22 — High performer recognition message
Write a recognition message from a senior leader to a team member who [DESCRIBE ACHIEVEMENT WITHOUT NAMING THEM, e.g. "led the delivery of a critical cross-functional project on time and under budget despite significant complexity"]. Tone: genuine and specific — not generic praise. Length: 100–150 words. The message will be shared internally. Do not include names or titles.
4. Learning and development
L&D professionals face a constant tension between the time it takes to design good training and the pace at which learning needs change. AI can significantly compress the design phase without reducing quality.
What makes these prompts effective: Be specific about the learner audience, their current level, the learning outcome, and the format. Vague L&D prompts produce generic content. Audience-specific prompts produce material that actually lands.
Prompt 23 — Training needs analysis summary
Write a training needs analysis summary for a [ROLE/TEAM] based on the following observations: [DESCRIBE PERFORMANCE GAPS OR SKILL GAPS, e.g. "managers are inconsistently applying the performance framework; three cases of poorly documented decisions in the last quarter"]. Include: a summary of the observed gap, the likely root cause (skill, knowledge, or motivation), recommended interventions, suggested priority level, and success metrics. Format as a structured brief suitable for presenting to a senior HR lead.
Prompt 24 — Workshop outline
Write a half-day workshop outline for [ROLE/TEAM] on the topic of [TOPIC, e.g. "giving effective feedback"]. Audience: [DESCRIBE, e.g. "line managers with between 1 and 5 years of management experience"]. Learning outcomes: [LIST 2–3 OUTCOMES]. Include: session objectives, agenda with timing, a mix of content delivery and practical activity, and a closing reflection exercise. Note any facilitation considerations.
Prompt 25 — Knowledge check questions
Write 10 multiple-choice knowledge check questions for a training module on [TOPIC]. Audience: [DESCRIBE LEARNER]. Difficulty: [BEGINNER / INTERMEDIATE / ADVANCED]. Each question should have four answer options, one correct answer, and a brief explanation of why the correct answer is right. Format as a numbered list.
Prompt 26 — Learning path recommendation email
Write an email from an L&D manager to a [ROLE TITLE] recommending a personalised learning path for the next quarter. The focus area is [DEVELOPMENT AREA]. Include: why this area matters for their role, three to four specific learning activities (courses, books, or stretch assignments — use placeholders where needed), a suggested timeframe for each, and a prompt to discuss with their line manager. Tone: encouraging and practical.
Prompt 27 — Post-training evaluation questions
Write a post-training evaluation survey for a [LENGTH] training on [TOPIC]. Include 8 questions covering: relevance to their role, quality of facilitation, pace and format, one thing they will apply immediately, one thing they are still unclear on, and an overall rating. Use a mix of 1–5 scales and open text. Keep it short enough to complete in under three minutes.
Prompt 28 — Case study for a management training module
Write a realistic case study scenario for a management training module on [TOPIC, e.g. "handling a team conflict between two senior individual contributors"]. The case study should: present a situation clearly without a clear right answer, include relevant context about the people involved (roles, not names), and end with three to four discussion questions that prompt reflection. The scenario should feel realistic for a [INDUSTRY/COMPANY TYPE] context.
Prompt 29 — Course description for an internal training catalogue
Write a course description for an internal training catalogue. Course: [COURSE TITLE]. Audience: [TARGET LEARNER]. Duration: [LENGTH]. Learning outcomes: [LIST 2–3]. Format: [E.G. VIRTUAL WORKSHOP / SELF-PACED E-LEARNING / IN-PERSON]. Write two versions: a short version (50 words) for a course tile, and a full version (150 words) for the course detail page. Tone: professional, clear, and benefit-focused — not academic.
5. Employee communications
HR communications often suffer from being either too formal (and therefore ignored) or too informal (and therefore not taken seriously). These prompts help you find the right register for each type of communication.
What makes these prompts effective: Always specify the audience, the tone, and what action (if any) you want the reader to take. The most common failure in HR communications is writing for compliance rather than for the reader.
Prompt 30 — Policy announcement email
Write an all-staff email announcing a change to [POLICY NAME, e.g. "the remote working policy"]. The key change is: [DESCRIBE CHANGE]. Effective date: [DATE]. Include: a clear explanation of what is changing and why, what employees need to do (if anything), where to find the full policy, and a contact for questions. Tone: clear and direct — not defensive or over-hedged. Length: 200–250 words.
Prompt 31 — All-hands update structure
Write a structured agenda and speaker notes framework for a company all-hands meeting focused on [TOPIC, e.g. "Q2 performance review and H2 priorities"]. Duration: [LENGTH]. Audience: [COMPANY SIZE AND COMPOSITION]. Include: opening, business update section, people and culture update, Q&A format, and close. Flag which sections typically generate the most questions and how to prepare for them.
Prompt 32 — Difficult conversation preparation guide
Write a preparation guide for a manager who needs to [DESCRIBE CONVERSATION TYPE, e.g. "tell a team member their role is being made redundant"]. Include: how to open the conversation, the key information to communicate clearly, what to expect emotionally, how to listen without dismissing, what not to say, and what happens immediately after the conversation. Note: this is a preparation guide only — any legally significant conversations require HR and legal sign-off before they happen.
Prompt 33 — Employee survey question set
Write a 12-question employee engagement survey for a [COMPANY SIZE] company. Include questions across: role clarity, management quality, collaboration, recognition, growth opportunities, wellbeing, and overall engagement. Use a combination of 1–5 agreement scales and two open-text questions. Avoid double-barrelled questions. Include a brief introductory statement for the survey that explains anonymity, purpose, and estimated completion time.
Prompt 34 — Change communication plan outline
Write a communication plan outline for [CHANGE INITIATIVE, e.g. "the introduction of a new performance management system"]. Include: key messages by audience (all staff, managers, senior leaders), the sequence of communications, the channel for each message, timing, and who is responsible. Format as a table. Also note any likely concerns from each audience and how the communications address them.
Prompt 35 — Recognition programme launch email
Write a launch email for a new peer recognition programme called [PROGRAMME NAME]. Include: what the programme is and how it works, why the company is introducing it, how to give recognition, what happens when you receive it, and a call to action for the first week. Tone: enthusiastic but grounded — not performative. Length: 200 words.
Prompt 36 — FAQ document for a policy change
Write a frequently asked questions document for employees following the announcement of [POLICY CHANGE]. Include at least 8 questions that employees are likely to ask, with clear, direct answers. Flag any questions where the answer is "we will update you on [DATE]" rather than giving a false certainty. Format: question in bold, answer in plain text below.
6. HR compliance and documentation
Compliance documentation must be precise, legally aware, and consistently applied. AI can produce useful draft frameworks, but every document in this category requires review by someone with employment law knowledge before use.
What makes these prompts effective: Always specify the jurisdiction (country, state, or employment framework) and the specific process you are following. Generic compliance documents are worse than useless — they create a false sense of coverage.
No AI-generated compliance document should be used without review by a qualified HR professional or employment lawyer familiar with your jurisdiction. These prompts produce draft frameworks — not legally approved documents. The prompts are designed to save drafting time, not to replace legal or HR expertise.
Prompt 37 — HR policy document draft
Draft an [POLICY NAME, e.g. "expenses and reimbursement policy"] for a [COMPANY SIZE] [INDUSTRY] company operating in [JURISDICTION]. Include: policy purpose, scope, definitions, the main rules and procedures, any exceptions, how to make a claim or request, escalation process, and a review date. Tone: clear and accessible — written for employees, not lawyers. Format in numbered sections. Flag any areas where jurisdiction-specific legal advice should be sought.
Prompt 38 — Disciplinary procedure letter — first written warning
Write a template letter for a first written warning under a formal disciplinary procedure. The letter should include: the nature of the concern, the date of the disciplinary meeting, the decision and its basis, what improvement is required, the timeframe for improvement, the consequence if improvement is not achieved, the right of appeal, and the appeal deadline. Leave placeholders for all case-specific details. Note: this template must be reviewed by your HR or legal team before use and adapted to your jurisdiction's requirements.
Prompt 39 — Grievance acknowledgement letter
Write a template acknowledgement letter for a formal employee grievance. Include: acknowledgement of receipt, the investigation process that will follow, the approximate timeline, who will be investigating, the employee's right to be accompanied at any meetings, and a contact point for questions. Tone: neutral and procedurally clear — not sympathetic in a way that implies a predetermined outcome.
Prompt 40 — Reasonable adjustments request process summary
Write a plain-language summary of the reasonable adjustments request process for employees. Include: what a reasonable adjustment is, how to request one, who reviews the request, what happens next, and the confidentiality of the process. Jurisdiction: [YOUR JURISDICTION]. Tone: supportive and accessible — this document is read by employees who may already feel vulnerable. Format: short numbered steps plus an FAQ section.
Prompt 41 — Compliance checklist for a new hire
Create a compliance checklist for onboarding a new employee in [JURISDICTION]. Include: right-to-work verification, required pre-employment checks, mandatory documents to issue (employment contract, policies), benefits enrolment deadlines, data protection notice requirements, and any mandatory induction training with legal basis. Format as a checklist table with: item, responsible party, due date placeholder, and done column.
Prompt 42 — Redundancy process checklist
Write a process checklist for a [INDIVIDUAL / COLLECTIVE] redundancy process in [JURISDICTION]. Include all procedural steps from the initial business case through to final payments, covering: notification requirements, consultation periods, selection criteria, appeals, and documentation requirements. Flag where legal advice is mandatory. Format as a numbered checklist with space for date completed and owner.
Prompt 43 — Data retention policy summary for HR records
Write a plain-language summary of HR data retention rules for [JURISDICTION]. Cover: how long to retain employee records post-exit, recruitment records, performance records, disciplinary records, and payroll records. Format as a table with: record type, retention period, legal basis, and destruction method. Include a note that this summary should be validated against current legal requirements and your organisation's DPA obligations.
7. Offboarding and exit
Exits handled well protect the organisation legally, preserve relationships, and ensure knowledge does not walk out the door. These prompts cover the full offboarding cycle.
What makes these prompts effective: Exit processes involve sensitive conversations. Prompts in this category should use role descriptions and scenarios, never real names or circumstances. The goal is to produce frameworks and templates that a manager or HR professional customises.
Prompt 44 — Exit interview question set
Write a set of 12 exit interview questions for a [ROLE LEVEL] employee leaving [VOLUNTARILY / FOLLOWING REDUNDANCY]. Cover: reasons for leaving, quality of management, what the organisation does well, what it could improve, how their role could be strengthened for the next person, and whether they would recommend the company to others. Include a mix of open questions and rating-with-explanation questions. Note: exit interviews should feel like a genuine conversation, not an interrogation — the question set is a guide, not a script.
Prompt 45 — Departure announcement — voluntary resignation
Write a team announcement for a departing [JOB TITLE] who is leaving after [APPROXIMATE TENURE] to [REASON IF SHAREABLE, e.g. "pursue an opportunity in a new sector" / "take time out" / simply "move on to their next role"]. Include: a genuine acknowledgement of their contribution, their last working day, what happens next for the team, and how to stay in touch if appropriate. Tone: warm and sincere — not formulaic. Do not include personal details. Length: 150 words.
Prompt 46 — Departure announcement — redundancy
Write a team announcement for a team member whose role has been made redundant. The announcement should: communicate the departure clearly without disclosing the private details of the process, acknowledge the person's contribution, state the effective date, and address any immediate team questions about workload or coverage. Tone: respectful and factual — this is a difficult message to receive. Do not include anything that could embarrass the departing employee or expose the company to legal risk.
Prompt 47 — Knowledge transfer template
Create a knowledge transfer document template for an employee who is [LEAVING / TRANSITIONING TO A NEW ROLE]. Include sections for: current responsibilities and how they are performed, key contacts and relationships, active projects and their status, recurring tasks and their cadence, access and systems, risks or open items that need immediate attention, and any unwritten rules or tribal knowledge worth preserving. Format as a structured document an employee can complete in a day.
Prompt 48 — Offboarding checklist
Create a comprehensive offboarding checklist for a departing [JOB TITLE] at a [COMPANY SIZE] company. Include tasks for: HR administration (final payslip, benefits, references), IT (access removal, device return, email forwarding), the line manager (knowledge transfer, team communication), and the employee themselves (documents to retain, personal files). Format as a table with: task, owner, due date placeholder, and status column.
Prompt 49 — Exit survey questions for volume analysis
Write a short 6-question exit survey designed to be completed by all departing employees, with responses that can be aggregated for trend analysis. Focus on: primary reason for leaving (multiple choice with categories), rating of management (1–5), rating of growth opportunities (1–5), one thing the company does well (open text), one thing it should improve (open text), and likelihood to recommend as an employer (1–10 NPS format). Keep it completable in under two minutes.
Prompt 50 — Post-exit reference framework
Write a reference framework template for managers providing employment references for former team members. Include: what information is factually safe to confirm (dates, title, responsibilities), how to handle requests that go beyond factual confirmation, how to decline requests you are not comfortable with, and a sample factual reference letter template. Note: reference policies vary by organisation and jurisdiction — check your HR team's guidance before providing any reference.
How to use this library effectively
Copy the prompt. Fill in the bracketed placeholders with your specific details. Run it. Edit the output.
The quality of what you get back is directly proportional to the specificity of what you put in. A prompt filled with real context — the actual role level, the specific competency, the genuine communication challenge — produces output you can use. A prompt left at the template level produces output that is technically correct but practically useless.
Treat every AI output as a first draft. Review it against your organisation's tone, policies, and employment framework. In categories like compliance, performance management, and offboarding, have a qualified HR professional review before anything is used in a formal process.
If you find yourself editing the same section of every AI output, that section belongs in your prompt. Add a line describing exactly what you want there and stop editing it manually. Good prompts get better over time as you refine them based on what you keep changing.
The AI for HR and People Managers course covers the underlying principles behind why some of these prompts work and others do not — including how to adapt them for more complex or sensitive HR tasks. The HR professionals path shows how to build and verify that competency with a credential employers can check.
For a broader view of how HR teams are integrating AI into daily work, see How HR Professionals Are Using AI in 2026.