25 Claude Prompts for HR Professionals

Most lists of claude prompts for HR professionals are wrong about where the actual time goes. They lead with the big documents — full policy manuals, complete employee handbooks — when the real daily time drain is smaller and more sensitive: the individual email about a policy exception, the performance conversation summary, the response to a tricky question from an employee that needs to be accurate, kind, and legally careful all at once.

Before: The Weak Approach

A typical HR-focused prompt list leads with something like "draft an employee handbook" or "write a company culture statement" — big, infrequent documents. Useful occasionally, but not what fills an HR professional's actual week.

Why It Fails

Big documents get written once and revised occasionally. The actual daily friction in HR work is the high volume of smaller, sensitive written communication: a rejection email that needs to be kind but clear, a policy explanation that needs to be accurate without sounding cold, a performance summary that needs to be fair and specific. A prompt list focused on rare big documents misses where HR professionals actually spend their time.

⚠️ Common mistake: treating HR prompt needs as document generation when most of the actual daily work is smaller-scale communication requiring tone, accuracy, and sensitivity all at once.

After: 25 Prompts Organized By What Actually Takes Time

Hiring and Recruiting (Prompts 1-7)

1. Write a job posting for [role], emphasizing [2-3 key selling 
   points about the role/company]
2. Draft 8 interview questions for [role] focused on [specific skill 
   or competency]
3. Write a rejection email for a candidate who interviewed but wasn't 
   selected, warm but not falsely encouraging
4. Turn this pile of resume notes into a structured comparison of 
   3 candidates: [paste notes]
5. Draft an offer letter email summarizing [role, salary, start date, 
   key benefits]
6. Write a follow-up message to a candidate who went quiet mid-process
7. Draft reference check questions specific to [role], beyond generic 
   "would you rehire" questions

⚡ Pro tip: for rejection emails specifically, ask for a version that names one genuine strength from the interview, if you can supply one. Generic rejections read as generic; specific one-line feedback reads as respectful, even in a two-sentence email.

Onboarding (Prompts 8-12)

8. Draft a first-week onboarding schedule for a new [role] hire
9. Write a welcome email to send before a new hire's start date
10. Turn this list of internal tools and processes into a new-hire 
    reference guide: [paste list]
11. Draft a 30-60-90 day plan template for [role]
12. Write an introduction email to send to the team before a new 
    hire starts

Performance and Feedback (Prompts 13-18)

13. Turn these manager notes into a structured performance review 
    summary: [paste notes]
14. Draft talking points for a difficult performance conversation 
    about [specific issue], direct but constructive
15. Write a performance improvement plan outline for [specific 
    performance gap]
16. Draft a promotion announcement highlighting [specific 
    accomplishments]
17. Write feedback on this draft performance review to make it more 
    specific and less vague: [paste review]
18. Draft a message recognizing a team's work on [project/milestone]

⚠️ Common mistake: asking Claude to write a full performance review from scratch with no input. The result reads generically because it has no actual specifics to draw from — always feed in real notes, examples, or manager input first, and use Claude to structure and sharpen, not invent.

Policy and Employee Questions (Prompts 19-23)

19. Draft a clear explanation of [specific policy] for an employee 
    FAQ
20. Write a response to an employee asking about [specific benefit 
    or policy exception], accurate and warm
21. Turn this legal/compliance summary into plain-language guidance 
    for managers: [paste summary]
22. Draft an announcement explaining a policy change and the 
    reasoning behind it
23. Write a response to a sensitive employee question about 
    [workplace situation], careful and non-committal on anything 
    requiring legal review

⚠️ Common mistake: using Claude output directly for anything touching legal or compliance risk (termination language, accommodation decisions, disciplinary action) without review from legal counsel or a compliance-trained colleague first. Use it to draft and structure, not to make the final call on legally sensitive language.

Culture and Communication (Prompts 24-25)

24. Draft an internal announcement about [organizational change], 
    direct and honest about what's changing and why
25. Write 3 discussion prompts for a team retrospective on 
    [recent project or quarter]

Actually, prompt 24 is worth using even for small changes — an HR manager at a 90-person company found that being upfront about a scheduling policy change, including the actual reasoning, generated far fewer confused follow-up questions than a vaguer announcement had for a similar change the previous year.

Variations for Different Contexts

For smaller companies without a dedicated legal team, it's worth adding an explicit instruction to every policy-adjacent prompt: "flag anywhere this touches legal risk and should be reviewed before sending." Claude generally will note this on its own for obviously sensitive topics, but naming it explicitly makes the flag more consistent across different types of requests.

For larger HR teams managing consistent tone across multiple HR business partners, it's worth building a shared voice reference the way a content team would for brand voice — a few paragraphs of past communications that represent the tone you want, so different team members' Claude-assisted drafts don't read as though they came from five different companies.

Save and Reuse This

The recurring theme across these 25 is that HR's real bottleneck is volume of sensitive small communications, not occasional big documents. If you're building your own list beyond these 25, look for the emails and messages you rewrite most often, not the documents you write least often — that's where a saved prompt actually earns its keep.

Once you've adapted a few of these to your company's specific tone and policies, save them in PromptABCD rather than rebuilding the context each time. HR communication carries real weight — having a consistent, reviewed starting point matters more here than in most other departments.