Employee Handbook Section

Employee Handbook Section

Before you start

Gather the following from the user. Items 1-3 are required:

1. What topic does this section cover? Name the specific policy area: PTO, remote work, code of conduct, expense reimbursement, performance reviews, etc.
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.
3. Who is the audience? All employees, managers only, specific departments, or contractors? This affects scope and tone.
4. What jurisdiction(s) apply? Employment law varies by country, state, and city. Identify where employees are located.
5. Does this replace an existing policy? If so, what is changing and why? This helps write the transition language.
6. Who has final approval? Legal, HR leadership, executive team — identify the review chain before writing.

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?"

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.

Handbook section template

1. Section Header

# [Policy Name]

Effective date: [Date]
Last updated: [Date]
Applies to: [All employees / Managers / US employees / etc.]
Supersedes: [Previous policy name and date, or "N/A"]
Owner: [Department or role responsible for this policy]

Every section needs these metadata fields at the top. They prevent ambiguity about when the policy took effect and who it covers.

2. Purpose Statement

Write 2-3 sentences explaining:

• Why this policy exists (the business or legal reason)
• What it aims to achieve (the outcome for employees and the company)

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."

Do not use legal jargon in the purpose statement. Save precise legal language for the policy details.

3. Scope

Define who this policy applies to and any exclusions:

• Included: Full-time employees, part-time employees (specify threshold), etc.
• Excluded: Contractors, interns, employees covered by a collective bargaining agreement, etc.
• Geographic exceptions: "Employees in [jurisdiction] should refer to Appendix A for jurisdiction-specific provisions."

4. Policy Details

Write the policy in numbered clauses. Each clause covers one rule or requirement.

Structure each clause as:

4.1 [Rule title]
[Clear statement of the rule]
[How to comply — specific steps or procedures]
[Exceptions, if any]

Writing rules:

• Use "employees must" for requirements, "employees may" for permissions, "employees should" for recommendations
• Define every term that could be ambiguous — "immediate family," "business day," "manager"
• 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."
• One rule per clause. Do not combine PTO accrual rates and blackout dates in the same clause.

5. Procedures

Step-by-step instructions for the most common actions under this policy:

How to [action]:
1. [Step with specific system, form, or person to contact]
2. [Step with timeline — "within 3 business days"]
3. [Step with expected outcome — "you will receive confirmation via email"]

Include procedures for both the employee and the manager/approver when applicable.

6. Frequently Asked Questions

Include 3-5 FAQs that address the most common points of confusion:

Q: [Common question] A: [Direct answer with reference to the relevant clause number]

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.

7. Related Policies

List other handbook sections that interact with this one. Cross-references prevent contradictions and help employees find related information.

• [Policy Name] — [How it relates]
• [Policy Name] — [How it relates]

Quality checklist

Before delivering the handbook section, verify:

• [ ] Section header includes effective date, audience, and policy owner
• [ ] Purpose statement explains why the policy exists in plain language
• [ ] Scope clearly defines who is included and excluded
• [ ] Every clause states one rule with clear compliance steps
• [ ] Language uses "must," "may," and "should" consistently and deliberately
• [ ] Ambiguous terms are defined (business day, immediate family, manager)
• [ ] Procedures include specific systems, timelines, and expected outcomes
• [ ] FAQs address genuine points of confusion, not restated policy
• [ ] A legal review disclaimer is included — this content requires attorney review before publication

Common mistakes to avoid

• 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.
• 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.
• 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.
• 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.
• No effective date or versioning. Policies without dates create disputes about which version was in effect. Always include effective date and superseded version reference.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: The-AI-Directory-Company
• Source: The-AI-Directory-Company/agents-and-skills
• License: MIT
• Homepage: https://ai-directory.company

Install and usage instructions live in the source repository linked above.