leadershipbusiness

Employee Handbook Section

Write employee handbook sections — covering policies, benefits, expectations, and procedures with clear language, legal compliance awareness, and consistent formatting across the handbook.

HRhandbookpoliciesemployee-experiencecompliance

Works well with agents

Compliance Officer Agent Engineering Manager Agent People Ops Manager Agent

Works well with skills

Compliance Assessment Onboarding Plan

employee-handbook-section/

SKILL.md

Markdown

1
2	# Employee Handbook Section
3
4	## Before you start
5
6	Gather the following from the user. Items 1-3 are required:
7
8	1. What topic does this section cover? Name the specific policy area: PTO, remote work, code of conduct, expense reimbursement, performance reviews, etc.
9	2. What is the company's stance? Every policy section needs a clear position. "We offer unlimited PTO" vs. "We offer 20 days per year" produces fundamentally different content.
10	3. Who is the audience? All employees, managers only, specific departments, or contractors? This affects scope and tone.
11	4. What jurisdiction(s) apply? Employment law varies by country, state, and city. Identify where employees are located.
12	5. Does this replace an existing policy? If so, what is changing and why? This helps write the transition language.
13	6. Who has final approval? Legal, HR leadership, executive team — identify the review chain before writing.
14
15	If the user says "write a PTO policy," push back: "What is the PTO structure — unlimited, accrual-based, or fixed allowance? What jurisdictions do you operate in?"
16
17	Important: Always include a disclaimer that the output requires legal review before publication. AI-generated policy language should never be published without review by qualified legal counsel familiar with applicable employment law.
18
19	## Handbook section template
20
21	### 1. Section Header
22
23	```
24	# [Policy Name]
25
26	Effective date: [Date]
27	Last updated: [Date]
28	Applies to: [All employees / Managers / US employees / etc.]
29	Supersedes: [Previous policy name and date, or "N/A"]
30	Owner: [Department or role responsible for this policy]
31	```
32
33	Every section needs these metadata fields at the top. They prevent ambiguity about when the policy took effect and who it covers.
34
35	### 2. Purpose Statement
36
37	Write 2-3 sentences explaining:
38	- Why this policy exists (the business or legal reason)
39	- What it aims to achieve (the outcome for employees and the company)
40
41	Example: "This policy establishes clear guidelines for time-off requests to ensure fair and consistent treatment across all teams. It balances employee wellbeing with operational continuity."
42
43	Do not use legal jargon in the purpose statement. Save precise legal language for the policy details.
44
45	### 3. Scope
46
47	Define who this policy applies to and any exclusions:
48
49	- Included: Full-time employees, part-time employees (specify threshold), etc.
50	- Excluded: Contractors, interns, employees covered by a collective bargaining agreement, etc.
51	- Geographic exceptions: "Employees in [jurisdiction] should refer to Appendix A for jurisdiction-specific provisions."
52
53	### 4. Policy Details
54
55	Write the policy in numbered clauses. Each clause covers one rule or requirement.
56
57	Structure each clause as:
58
59	```
60	4.1 [Rule title]
61	[Clear statement of the rule]
62	[How to comply — specific steps or procedures]
63	[Exceptions, if any]
64	```
65
66	Writing rules:
67	- Use "employees must" for requirements, "employees may" for permissions, "employees should" for recommendations
68	- Define every term that could be ambiguous — "immediate family," "business day," "manager"
69	- State what happens, not what does not happen. "Requests require 5 business days' notice" is clearer than "Requests should not be submitted with less than 5 business days' notice."
70	- One rule per clause. Do not combine PTO accrual rates and blackout dates in the same clause.
71
72	### 5. Procedures
73
74	Step-by-step instructions for the most common actions under this policy:
75
76	```
77	How to [action]:
78	1. [Step with specific system, form, or person to contact]
79	2. [Step with timeline — "within 3 business days"]
80	3. [Step with expected outcome — "you will receive confirmation via email"]
81	```
82
83	Include procedures for both the employee and the manager/approver when applicable.
84
85	### 6. Frequently Asked Questions
86
87	Include 3-5 FAQs that address the most common points of confusion:
88
89	Q: [Common question]
90	A: [Direct answer with reference to the relevant clause number]
91
92	FAQs are not a substitute for clear policy language — they supplement it. If an FAQ reveals that the policy itself is unclear, fix the policy.
93
94	### 7. Related Policies
95
96	List other handbook sections that interact with this one. Cross-references prevent contradictions and help employees find related information.
97
98	- [Policy Name] — [How it relates]
99	- [Policy Name] — [How it relates]
100
101	## Quality checklist
102
103	Before delivering the handbook section, verify:
104
105	- [ ] Section header includes effective date, audience, and policy owner
106	- [ ] Purpose statement explains why the policy exists in plain language
107	- [ ] Scope clearly defines who is included and excluded
108	- [ ] Every clause states one rule with clear compliance steps
109	- [ ] Language uses "must," "may," and "should" consistently and deliberately
110	- [ ] Ambiguous terms are defined (business day, immediate family, manager)
111	- [ ] Procedures include specific systems, timelines, and expected outcomes
112	- [ ] FAQs address genuine points of confusion, not restated policy
113	- [ ] A legal review disclaimer is included — this content requires attorney review before publication
114
115	## Common mistakes to avoid
116
117	- Legalese that employees cannot understand. "Pursuant to the foregoing provisions" communicates nothing. Write in plain language. Legal precision and readability are not mutually exclusive — they require more effort, not more jargon.
118	- Policies without procedures. A policy that says "employees must submit expenses within 30 days" but does not say where, how, or to whom is incomplete. Every requirement needs a corresponding procedure.
119	- Inconsistent obligation language. Mixing "must," "shall," "should," and "is expected to" within the same section creates ambiguity about what is mandatory vs. recommended. Pick a convention and follow it throughout.
120	- Missing jurisdiction awareness. Employment law varies dramatically. A PTO policy that works in Texas may violate California law. Flag jurisdiction-specific provisions explicitly and recommend legal review.
121	- No effective date or versioning. Policies without dates create disputes about which version was in effect. Always include effective date and superseded version reference.
122