How to Write an Employee Handbook With AI and What to Check

Write the handbook from your own facts, not the AI's imagination. List how you actually handle hours, leave, pay, conduct and discipline, have an AI assistant draft one section at a time from those notes, then check every clause against your contracts and current employment law before an employment adviser signs it off.

The drafting is the easy part. The risk is that a chat assistant fills gaps with confident, generic rules: a statutory figure from another country, a probation length you never use, a promise to pay overtime you don't pay. Those sentences read well, which is exactly why nobody questions them until a dispute. For a firm of 10 to 20 people, budget two to three days of owner or manager time, most of it spent on facts and checking rather than writing.

Follow me on Instagram@sagnikteaches

What belongs in the handbook and what belongs in the contract

Before you open any AI tool, separate two kinds of document. The employment contract holds the terms: pay, hours, notice, holiday entitlement, where someone works. The handbook explains how things work day to day: how to book leave, how to report sickness, what counts as misconduct, how to raise a grievance, how to claim expenses. Many firms state that handbook policies are non-contractual so they can update them without renegotiating, but whether a particular clause is contractual changes how you can alter it later. That's a question for your adviser, not the AI.

Connect on LinkedInSagnik Bhattacharya

This split matters for drafting because the AI should never invent terms. If a number belongs in the contract, the handbook should point to the contract rather than restate it, which also stops the two documents drifting apart.

Subscribe on YouTube@codingliquids

Stage 1: write down how the business really runs

The single most useful document in this whole process is a plain fact sheet: short, blunt answers about how you operate now. The AI drafts from it, and you check the drafts against it. Without one, the model has nothing to anchor to and falls back on what an average handbook says.

You don't need to write it from a blank page. Ask the assistant to interview you, one topic at a time, and to record only what you say. Twenty minutes per topic is typical.

You are helping me build a fact sheet for our employee handbook.
Interview me about ONE topic at a time, in this order:
hours and on-call, holiday booking, sickness reporting, expenses,
devices and IT, conduct, discipline, grievances.
Ask one question at a time. Keep asking follow-ups until the rule
is specific enough that two managers would apply it the same way.
Record my answers as short bullet points in my words.
Do NOT add any rule, number or legal requirement I haven't stated.
If I say "I'm not sure", record it as UNKNOWN and move on.

Here's what a filled-in extract looks like for an illustrative 14-person IT support firm with six engineers on an on-call rota:

• Core hours: 08:30 to 17:30, Monday to Friday, one-hour unpaid lunch.
• On-call: six engineers, one week in six, covering 17:30 to 08:30 and weekends. Flat weekly on-call payment, plus the normal hourly rate for time spent on callouts, minimum one hour per callout.
• Sickness: phone (not message) the service desk lead before 08:00 on the first day. Message is fine from day two.
• Holiday: book through the HR app. More than two consecutive days needs two weeks' notice. No more than two engineers off at once.
• Laptops: company-owned, encrypted, no personal use on client networks.
• Mileage: claimed through the expenses app within 30 days of the visit.
• UNKNOWN: whether on-call staff who are ill during their week swap or are covered by the rota lead.

Those UNKNOWN lines are gold. Each one is a decision you'd otherwise let the AI make for you, usually by inventing something plausible. Settle them before drafting.

Stage 2: set up a private drafting workspace

Handbooks contain nothing secret, but the supporting material often does: contract templates, salary bands, notes about past disciplinary cases. Draft in a business account (ChatGPT Business, Claude Team, Microsoft 365 Copilot or Gemini in Workspace), where business content isn't used for model training by default. If you're a sole owner on an individual plan, switch off the model-training setting in privacy controls first.

Create a Project (ChatGPT and Claude both offer them) and upload the fact sheet, your contract template, any existing policies and one or two pages of writing whose tone you like. Don't upload anything about named individuals. Then add standing instructions so every section follows the same rules:

You draft sections of our staff handbook.
Rules:
1. Use ONLY facts from the uploaded fact sheet and contract template.
2. Never state a legal entitlement, minimum, deadline or percentage
   unless it appears in those files. Where the law might set a rule,
   write [LEGAL CHECK: what needs confirming] instead.
3. Where the fact sheet is silent, write [OWNER DECISION: question].
4. Plain English, second person ("you"), short sentences, no jargon.
5. Refer to the contract for pay, hours, notice and holiday entitlement
   rather than restating figures.
6. Don't invent roles or departments. We have: owner, operations
   manager, service desk lead, engineers, office administrator.

Rule 6 exists because assistants love to route things to "the HR department" or "your HR business partner". A 14-person firm has neither, and a grievance procedure that sends complaints to a department that doesn't exist is worse than no procedure.

Stage 3: draft one section at a time

Ask for one section per message, around 200 to 500 words each. Short requests keep the model close to the fact sheet; a request for "the whole handbook" invites padding. A good per-section prompt:

Draft the "On-call" section of the handbook using the fact sheet.
Cover: who is on the rota, how often, hours covered, what you're
paid, how to swap a week, what to do if you're ill while on call.
Maximum 350 words. Follow the project rules.

An illustrative draft that came back looked like this (shortened):

On-call runs on a six-week rota, so each engineer covers one week in six, from 17:30 to 08:30 on weekdays and all weekend. You'll receive a flat weekly on-call payment, set out in your contract, plus your normal hourly rate for time spent on callouts, with a minimum of one hour per callout. To swap a week, agree it with a colleague and tell the service desk lead at least 48 hours before the week starts. After a callout you are entitled to a minimum rest period before your next shift [LEGAL CHECK: confirm rest-period rules]. Staff will receive time off in lieu for all callouts. If you're ill during your on-call week [OWNER DECISION: does the rota lead cover, or does the engineer arrange a swap?].

Most of that is right, and the markers did their job. Three things still needed fixing. The 48-hour swap notice appears nowhere in the fact sheet; the model invented it because it sounded reasonable. "Time off in lieu for all callouts" contradicts the fact sheet, which says callouts are paid, and would have created a double entitlement. And "you are entitled to a minimum rest period" states an entitlement before the check has happened; the marker should replace the claim, not sit beside it. Fixing those took five minutes. Finding them is the real work, which is why the next stage exists.

Stage 4: what to check in every AI-drafted section

Run these checks on each section before it joins the master document. They're grouped by what goes wrong, with the quickest way to verify each.

Legal and jurisdiction checks

• Every number with a legal flavour. Holiday minimums, notice periods, sick pay, rest breaks, family leave, probation, record-keeping periods. Why: models blend rules from many countries. How to verify: list them in a table and have your adviser confirm each, or check them against the official guidance where you employ people.
• Legal concepts from another system. Terms such as "at-will employment" or "exempt and non-exempt staff" belong to particular legal systems. Why: they may be meaningless or misleading where you are. How to verify: search the draft for "at-will", "exempt", "statutory" and "by law", and question every hit.
• Discipline and grievance steps. Who investigates, who decides, whether staff can bring a companion, how appeals work. Why: a flawed procedure can undermine a fair decision. How to verify: adviser review, no exceptions.

Consistency checks

• Handbook against contract. Notice, probation, hours and the holiday year must match exactly or, better, not be restated. How to verify: search both documents for every number and date.
• Handbook against itself. A 30-day expenses deadline in one section and 60 days in another. How to verify: ask the assistant to list every number and deadline in the full draft, with section names, then read the list.
• Handbook against reality. Does the sickness section describe what the service desk lead actually does at 07:45? How to verify: show each section to the person who runs that process.

Promise and invention checks

• Absolute words. "Always", "will be paid", "guaranteed", "within 24 hours". Why: each one is a commitment someone can hold you to. How to verify: search for them and soften or delete.
• Things you don't have. An employee assistance programme, a wellbeing budget, a pension salary-sacrifice scheme, an HR department. How to verify: read with the question "do we actually offer this?"
• Monitoring claims. If you monitor email, calls or devices, say so accurately; if you don't, don't imply it. Check it matches your staff privacy notice.

Fairness and readability checks

• Assumptions about people. Gendered job references, assumptions that parents are mothers, "young and energetic team". How to verify: ask the assistant to list wording that assumes gender, age, family status or health, then decide yourself.
• Reading ease. Staff for whom English is a second language will read this too. Aim for short sentences and everyday words; ask the assistant to flag any sentence over 25 words.

Keep a search list handy and run it on the finished draft. It takes ten minutes and catches most of the dangerous sentences:

statutory | by law | legally | entitled | minimum | maximum
always | never | guarantee | will be paid | will receive
HR department | HR team | assistance programme | wellbeing
days | weeks | months | % | hours
at-will | exempt | discretion | immediately

Three errors that turn up in almost every draft

These came up in the illustrative IT support firm's first pass. You'll likely see versions of all three.

The imported number. The holiday section said "you are entitled to 20 days' paid holiday plus public holidays". The contract said 25 days including public holidays, with a different holiday year. The AI hadn't read the contract closely; it had reached for a common figure. Fix: delete the figure and write "your holiday entitlement is set out in your contract".

The accidental promise. The hours section said "overtime will be paid at time and a half". The firm's engineers are salaried and don't get paid overtime outside on-call. One sentence would have created an expectation for 14 people. Fix: "Your contract explains how extra hours are handled."

The missing step. The discipline section jumped from investigation to decision and never mentioned an appeal. The draft also said a manager "may dismiss without warning for any breach of this handbook", which is far broader than any adviser would accept. Fix: the adviser rewrote the procedure, and the AI was only used afterwards to tidy the wording.

Before and after: turning an old note into a clear policy

A lot of handbook work is rewriting scraps that already exist. The firm's expenses rule lived in an old email:

Guys, reminder: mileage has to go in the app, receipts too, don't leave it for months!! Anything over a hundred needs sign-off first. Parking fine = your problem.

Given that email plus the fact sheet, the assistant produced:

Claim mileage and expenses through the expenses app within 30 days of the cost. Attach a receipt for every item except mileage. Ask the operations manager before spending more than $100 on any single item; costs over $100 without prior approval may not be reimbursed. Parking and traffic fines are your responsibility and won't be reimbursed.

What changed: the 30-day deadline came from the fact sheet rather than "months"; "sign-off" became a named person; the unapproved-spend rule gained a consequence; the tone became neutral without becoming stiff. What was checked: that the operations manager agreed to be the approver, and that the $100 threshold matched the expenses app's settings.

The whole job for a 14-person IT support firm

Here's how the illustrative firm's handbook came together, with realistic time figures rather than best-case ones:

Total internal time was about 19.5 hours spread over three weeks, against an estimate of roughly 35 to 40 hours to write the same document by hand. Of the 23 markers, 9 were legal checks and 14 were owner decisions. The checking stage found 4 imported numbers, 2 contradictions with the contract, 3 invented roles or benefits and 1 promise the firm couldn't keep. None of those would have been caught by reading for style.

Sign-off, acknowledgement and version control

Send the adviser the draft with the list of legal markers at the top, so the review is focused and priced on a clear scope. Ask specifically about the discipline and grievance procedures, anything contractual, and any monitoring you describe.

Then test clarity with two staff who didn't write it. Give them five questions and time how long each answer takes to find: "You wake up ill on an on-call Tuesday. What do you do?" "How do you claim a $140 train fare?" If they hesitate or answer differently from each other, rewrite that section.

When you issue it, record who has confirmed they've read which version and when. A simple log at the front of the document keeps changes traceable:

Keeping it current without redrafting from scratch

Set one annual review date and a short list of triggers that force an earlier update: a change in employment law, a new benefit, a new tool that changes how people work, or a dispute that exposed a gap. Minor updates can go through the operations manager; anything touching discipline, grievance or pay goes back to the adviser.

AI is useful at review time for comparing versions. Paste the old and new text of a section and ask: "List every change in meaning between these two versions, ignoring wording-only changes." It surfaces the substantive edits so the approver reads those rather than the whole section.

Two sections deserve special attention each year. The IT and AI section dates fastest, so link it to your separate AI usage policy rather than copying rules into the handbook. And the health and safety summary must stay in step with the full policy; if you're rewriting that one too, follow the approach in writing a health and safety policy with AI, which has its own set of checks.

Once the handbook exists, it becomes a source for other work. It's the natural reference for a new starter's first fortnight, covered in planning AI-assisted onboarding, and it's the document an internal assistant should answer from if you set up an AI helpdesk for staff HR questions. Contract templates are a separate job with higher stakes; drafting employment contracts with AI covers the extra legal checks those need.

The pattern to keep: facts first, one section at a time, markers instead of guesses, and a human who knows the law signing off anything that could be argued over later.

Handbook questions owners ask next

Can I just ask AI for a complete handbook template?

You can, but you'll spend longer untangling it than you saved. A one-shot template is built from the average of thousands of handbooks, so it contains policies you don't run, roles you don't have and legal figures that may not apply where you employ people. Use a template only as a list of section headings, then draft each section from your own fact sheet.

Should our AI usage policy go inside the handbook?

A short summary should, with a link to the full policy. Staff read the handbook when they start and when something goes wrong, so it's the right place to say which AI tools are approved and what must never be pasted into them. Keep the detailed rules in a separate document so you can update them as tools change without reissuing the whole handbook.

Do employees have to sign the handbook?

Practice varies, and whether a signature matters depends on your contracts and the law where you employ people. Many small firms ask staff to confirm they've read the current version, recorded with a date, which proves they had access to it. Ask your employment adviser whether you need more than that, especially if any policy is meant to be contractual.

How long should a small-business handbook be?

Long enough to answer the questions staff actually ask, and no longer. For a firm of 10 to 20 people that's often 15 to 30 pages. If a section runs past two pages, it usually contains procedure that belongs in an SOP or a form. A good test is whether a new starter can find the sickness reporting rule in under a minute.

Further reads

• AI for HR in Small Businesses: 12 Tasks You Can Hand Over Safely — Other HR jobs you can hand to AI once the handbook is done.
• How to Write Fairer Performance Reviews With AI — Use the same evidence-first approach for fairer reviews.
• How to Roll Out an AI Policy So Staff Actually Follow It — Getting staff to follow the AI section, not just sign it.
• How to Write SOPs With AI: From Rough Notes to Clear Procedures — Move long procedures out of the handbook into proper SOPs.
• How to Classify Business Data Before Using AI Tools — Decide which HR documents are safe to upload to an assistant.
• How to Set Up Human Review for AI Work Without Slowing Down — A lightweight review routine for any AI-drafted document.
• How HR Consultants Use AI for Policies, Letters and Cases — Three workflows for HR consultants, with a client fact sheet, letter before-and-after, a grievance chronology prompt and the lines AI must never cross.
• AI Time Tracking for Small Teams: Hours Without Timesheets — Match the tracking method to the work, let AI draft the entries, and keep it on the right side of monitoring, with a seven-person brewery as the example.
• How to Run Staff Surveys and Exit Interviews With AI Analysis — A 12-question survey, an exit interview script, anonymity settings, a theme-coding prompt with checks, and an online clothing shop's first round of results.
• How to Build a Staff Training Matrix With AI — A skills-by-people grid with level definitions, expiry formulas and a gap score, built with AI prompts and filled in for an eight-person jewellery workshop.
• How to Automate Holiday Requests and Absence Tracking — Build a leave request process that checks balances, protects shift cover and records changes without repeated messages.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: OpenAI and Anthropic business plan pages for data-use defaults; general employment-practice guidance. No jurisdiction-specific legal figures are given; readers should confirm them with an employment adviser.