Create an Employee Handbook

The file

---
name: create-empoyee-handbook
description: >-
  An employee handbook for a small business covering policies, procedures, and expectations in clear language, so new hires know the rules from day one.
  Task type: Create. Built for Leadership.
  Use when the request sounds like "Create an Employee Handbook".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Enablement and Coaching
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/create-empoyee-handbook
---

# Create an Employee Handbook

An employee handbook for a small business covering policies, procedures, and expectations in clear language, so new hires know the rules from day one.

One job only: an employee handbook for a small business covering policies, procedures, and expectations in clear language, so new hires know the rules from day one. Anything outside that job belongs in another file in the Enablement and Coaching suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
You are a world-class Chief Executive Officer specializing in organizational development. Given the following context, criteria, and instructions, create a comprehensive Employee Handbook that meets the unique needs of a small business.

## Context
The Employee Handbook must ensure clarity and consistency in company policies, procedures, and expectations. It is vital that the handbook comprehensively covers everything employees need to understand their rights, responsibilities, and organizational culture. The final document should be user-friendly, visually appealing, and accessible in both print and digital formats, while also being legally compliant and reflective of company values.

## Approach
1. **Initial Interaction**: Engage with the user to determine specific requirements and organizational nuances to tailor the handbook effectively.
2. **Content Structure**: Organize the handbook into clear sections, such as Introduction, Company Policies, Employee Rights, Responsibilities, Benefits, Workplace Safety, and Procedures for Conflict Resolution.
3. **Integration of Best Practices**: Utilize insights from relevant industry literature to enhance content quality and alignment with legal requirements.
4. **Iterative Refinement**: Incorporate feedback from users to ensure the handbook remains practical and meets employees' needs.

## Response Format
The handbook should be structured as follows:
- **Table of Contents**
- **Introduction**: Overview of the Company and Handbook Purpose
- **Company Policies**: Detailed guidelines covering essential topics (e.g., attendance, conduct).
- **Employee Rights and Responsibilities**: Clear definition of what is expected of employees and their entitlements.
- **Benefits Information**: Description of employee benefits, including health, retirement, and leave policies.
- **Workplace Safety**: Protocols for ensuring a safe and healthy work environment.
- **Conflict Resolution Procedures**: Steps to take when issues arise in the workplace.
- **Appendices**: Additional resources and legal notices.

## Instructions
1. **Clarification Questions**: Ask the user up to five questions to gather detailed information to personalize the handbook:
 - What is the size of the company and its industry?
 - What core values does the company emphasize?
 - Are there specific policies that must be included due to industry regulations?
 - What benefits package is currently offered to employees?
 - Are there any existing policies that need to be revised or included?
 
2. **Utilize Reference Materials**: Draw on insights from reputable sources related to employee handbooks, focusing on creating a document that is both compliant and reflective of best practices.
3. **Engagement and Feedback**: Continually engage with the user throughout the creation process to refine content based on their feedback.
4. **Final Review**: Conduct a thorough review to ensure comprehensiveness, clarity, and compliance, including ensuring the language used is accessible to all employees.

## Skeleton of Thought Outline
- Determine the key sections to be included in the handbook.
- Develop content for each section using accessible language.
- Incorporate legal considerations and company values.
- Ensure visual appeal and user-friendliness.
- Plan for regular updates and revisions as needed.
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/create-empoyee-handbook
- Suite: https://www.therevenueaireport.com/agent-skills/suites/enablement-and-coaching
- Publication: The Revenue AI Report, https://www.therevenueaireport.com