Write your employee handbook

Creates a first version of your employee handbook from your existing documents and a short interview, with open decisions and legal sections marked.

This skill writes a first usable employee handbook in one session. It researches your company from the web and your connected tools, interviews you on the things nobody publishes, then writes the document with every fact sourced and every gap marked. Sections that depend on employment law are flagged for review in each country where you employ people.

When to use it

  • New hires keep asking the same questions and the answers live in people's heads.
  • You have policies scattered across emails, contracts and old documents, but no handbook.
  • You've grown past the size where the founders can explain how things work to everyone.
  • You opened a second country and the rules now differ.
  • Your handbook exists but has drifted from how the company works today.

What you get

A handbook saved where your team will read it: your wiki, a document in your drive, or a file. Its size follows the company:

  • Under about 30 people: 10 to 15 pages, 11 sections, reads like a letter from the founders.
  • About 30 to 300 people: 20 to 40 pages, shared rules plus per-country appendices.
  • 300+ or regulated: a plain-language layer over your formal policies, with a policy index.

Every section answers three things: what the rule is, how it works in practice, and who to ask. Anything undecided is written inline as [TO CONFIRM: what needs deciding]. The handbook ends with an Open items list and a Needs legal review list naming each section and the countries it applies to.

How it works

  1. It settles where the handbook will live. It checks what's connected and asks which place the team actually reads. Nothing is created yet.
  2. It researches the company. From your domain: what you do, roughly how many people and where, which countries, whether you're regulated. With your okay, it searches connected tools for existing policies, contract templates, onboarding documents and values. It reports back in five to ten sentences and waits for corrections.
  3. It interviews you. Up to ten questions in one message, chosen by gap. Where a document already covers a topic, it confirms: "Your 2023 PTO policy says 25 days. Still right?" It always asks about the things nobody publishes: how time off actually works, what happens when someone underperforms, how pay and promotion decisions get made.
  4. It proposes the structure. A table of contents with one line per section saying what goes in it and where the content comes from. It waits for a yes.
  5. It writes the whole handbook in one pass, in your company's voice, and saves it after confirming the location and title once more.

How it weighs evidence. A published or signed internal document counts most, then a recorded decision, then a rule stated by HR or leadership, then what you say in the interview. The public website is reliable for what the company does, not for how people work. When two sources disagree, it quotes both and asks which is right.

What it never does. It doesn't fill a gap with a plausible default: an invented notice period or leave allowance is worse than a blank, because someone will act on it. It doesn't lift policy values from other companies' handbooks. It doesn't rewrite decisions already written down. It keeps salary figures, ID numbers and health details out, and points to a role or channel, never a named person. It isn't a lawyer and says so: the sections marked (legal) need review by someone qualified in every country you employ people in.

If it finds an existing handbook, the job becomes an update: it summarises what has drifted, proposes what to add, rewrite or remove, and saves a new version without overwriting the original.

How to run it

Install the Effy AI plugin for Claude or ChatGPT. One install adds every Effy AI skill, this one included. Then connect the tools you want the skill to read from, such as email, calendar, your drive or your meeting notetaker, and ask for what you need in plain words: the assistant picks the right skill.

Before you start: you need your company domain. Connect your drive, wiki and email if you want it to find existing policies.

  1. Ask, for example: "Effy, write our employee handbook."
  2. Give your domain, correct its research, and answer the interview.
  3. Approve the structure.
  4. Work through the open items and send the legal sections for review.

It can also store the handbook as knowledge documents in Effy AI, so policy questions get answered from it.

Click. Try. Use.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.