Draft and Update HR Policies
Write clear, usable HR policy documents — from PTO and remote work to code of conduct — without the legal-department wall of text that no one reads.
The situation
You need to create or update a policy document. It might be a new PTO policy, a remote work framework, or a code of conduct that has not been touched since 2018.
After this guide you will have a draft policy that is clear, readable, and structured in a way employees will actually follow.
What you walk away with
A clear, readable policy draft in under 20 minutes
A structure that answers the questions employees actually have
Language that sounds human, not like a legal disclaimer
Decide what the policy actually needs to answer
Before writing, list the three to five questions employees most commonly ask about this topic. Those questions ARE the policy structure.
- For PTO: How much do I get? How do I request it? What happens if I don't use it? Can I take unpaid leave?
- For remote work: Who is eligible? What are the expectations around availability? What does the company provide?
- For code of conduct: What specific behaviors are in scope? What is the reporting process? What happens after a report?
Use the structured prompt for any policy type
Give Claude the policy topic, your context, and the key questions to answer.
Write a [policy type, e.g. "remote work policy"] for a [company size and type, e.g. "60-person B2B SaaS company, fully distributed across Europe"].
Key things this policy needs to address:
- [Question 1 employees ask]
- [Question 2 employees ask]
- [Question 3]
Context:
- [Any relevant constraints, e.g. "we have employees in 4 countries with different labor laws"]
- [Any decisions already made, e.g. "we've agreed on a core hours model of 10am-3pm CET"]
Tone: clear and direct, written for the employee reading it, not for legal protection. Use plain language. Structure with headers and short paragraphs. Include a one-paragraph "the intent behind this policy" section at the top.Add an FAQ section
After the main policy, an FAQ handles the edge cases that always come up. Ask Claude to generate it from the policy draft.
Based on the policy above, write a 5-question FAQ that covers the situations employees are most likely to ask about. Include one question about an edge case or grey area that the policy does not fully resolve, and give an honest answer about how to handle it.What's next?
Next: Write employee communicationsNew guides, when they ship
One email, roughly weekly. CLAUDE.md templates, workflows I actually use, and the cut-for-length stuff that does not make the public guides. One-click unsubscribe.
Or follow on Substack