How to Create an Employee Handbook for a UK Startup in One Day (Without a Lawyer on Speed Dial)
You don't need a 50-page document. You don't need a £3,000 legal bill. And you definitely don't need to spend three weeks agonizing over whether to call it a "handbook" or an "employee guide."
This guide walks you through exactly how to do it — with plain English, practical examples, and zero fluff. If you're a founder, head of people, or the person who's somehow inherited "HR stuff," this is for you.
Let's build your handbook.
Step 1: Decide What This Handbook Is For
Before you write a single word, answer this question:
Most founders think the answer is "legal compliance." And yes, that's part of it. But handbooks do three jobs:
Job #1: Avoiding Disputes
When someone says "you never told me that," you can point to the handbook. It's your evidence that you communicated expectations clearly.
Job #2: Onboarding Speed
New hires shouldn't have to ask 47 questions about how things work. The handbook answers them: remote work policy, how to book holiday, who to talk to if something's wrong.
Job #3: Culture Clarity
Your handbook is a culture document. It tells people what you value, how you work, and what "good" looks like. This is how you scale culture as you hire.
Step 2: Start with UK Legal Basics
Let's get the compliance stuff out of the way first. These are non-negotiable policies for any UK employer:
What Must Be Covered
What Must NOT Be Contractual
This is where founders mess up.
Your employment contract should cover individual terms (salary, notice period, job title). Your handbook should cover collective policies (how we all work).
If you put a policy in the handbook and call it "contractual," you've just made it much harder to change. And startups need flexibility.
"This handbook is for guidance and does not form part of your employment contract. We may update policies at any time, and will notify you of changes."
Now you can update policies without renegotiating contracts.
Where Founders Usually Mess This Up
Mistake #1: Copying a US template that references "at-will employment" or "401k plans." Fix: Use a UK-specific template or adapter framework (like ours). Mistake #2: Writing a 40-page handbook that tries to cover every possible scenario. Fix: Start with the essentials. You can always add sections later. Mistake #3: Using legal jargon that nobody understands. Fix: Use plain English. More on this next.Step 3: Write in Plain English (Seriously)
Employment law is complicated. Your handbook doesn't have to be.
Compare these two versions of the same policy:
❌ Bad (Legal Jargon):
"The Company reserves the right to invoke disciplinary proceedings in circumstances wherein an employee's conduct or capability falls below the requisite standard as determined by management in its sole discretion."
✅ Good (Plain English):
"If your behavior or performance doesn't meet expectations, we'll talk to you about it. We follow a fair process (detailed below) and you'll always have a chance to improve before any formal action."Why plain English matters:
- Use "you" and "we" instead of "the employee" and "the company"
- Break up long sentences
- Use bullet points for lists
- Include real examples
- Avoid "herein," "aforementioned," and other Victorian nonsense
Step 4: Make It Accessible
Your handbook shouldn't live in a PDF that someone emailed in 2022 and nobody can find.
Best Options for Startups:
Notion (most popular)- Free, easy to update, searchable
- Version history built-in
- Can lock pages so only admins can edit
- Employees can comment and ask questions
- Simple, familiar, collaborative
- Easy to share via link
- Version history in "File → Version history"
- Works for teams already living in Google Workspace
- If you're already paying for HR software, use it
- Usually includes acknowledgment tracking
- May have UK-compliant templates built-in
Versioning and Timestamps
Every policy should have:
- Version number: e.g., "v2.1"
- Date last updated: e.g., "Last updated: January 2026"
- Change log: Brief summary of what changed (at the front of the handbook)
v2.1 (January 2026)
- Updated remote work policy to clarify expense reimbursement
- Added flexible working request process (new legal requirement)
>
v2.0 (June 2025)
- Major rewrite for ACAS Code 2024 complianceAction: Add a version number and "last updated" date to every policy page today. Even if it's v1.0.
Step 5: Sanity-Check (Without Paying a Lawyer Yet)
Before you roll this out, do a quick sanity check:
ACAS References
For disciplinary, grievance, and flexible working policies, check them against the ACAS guides. ACAS is your free, government-backed resource. If your policy contradicts ACAS, fix it.
Peer Review
Get someone outside your company to read it. Ideally another founder or head of people. Ask:
- "Is this clear?"
- "Would you know what to do if X happened?"
- "Does this sound like us, or like a corporate law firm?"
Fresh eyes catch ambiguity.
Compliance Tooling
Use a compliance checker (like ours) to flag obvious gaps. We'll tell you if:
- Your disciplinary policy doesn't mention ACAS
- You're missing a flexible working policy (required since April 2024)
- Your equality policy references US law instead of the Equality Act 2010
- Your sick pay policy confuses SSP with company sick pay
Step 6: Roll It Out Properly
You've written the handbook. Now you need to actually implement it.
Acknowledgment
Employees need to confirm they've read and understood it. This is your proof of communication.
- Email: "We've updated the handbook (link). Please confirm you've read it by replying to this email."
- HR software: Most tools have built-in acknowledgment tracking (checkbox + timestamp).
- In-person: If your team is small, do it in a team meeting. "Everyone good? Any questions?"
Change Communication
When you update a policy, don't just silently change the doc.
Subject: Updated Remote Work Policy
>
Hey team,
>
We've updated our remote work policy to clarify expense reimbursement (you can now expense coworking up to £50/month).
>
You can see the updated version here: [link]
>
What changed: Section 5 (Expenses) now includes coworking spaces.
>
Why it changed: A few people asked, and it makes sense to support focus time outside the home.
>
Any questions, ask in #people-ops.
Transparency builds trust.
Where Most Startups Fail
Failure mode #1: Writing a handbook and never mentioning it again. Fix: Reference it regularly. "Check the handbook." "That's covered in our remote work policy." Failure mode #2: Writing policies that contradict how the company actually works. Fix: If your handbook says "9-5 office hours" but everyone works remotely on Fridays, update the handbook. Don't let policies fossilize. Failure mode #3: Not updating when things change. Fix: Set a calendar reminder every 6 months: "Review handbook." It takes 30 minutes.Step 7: When to Bring in a Lawyer
You don't need a lawyer to write a handbook. But you should get one to review it if:
Your One-Day Handbook Schedule
If you're time-blocking this, here's how to structure your day:
You'll have a draft that's 90% ready. The final 10%? A legal review (optional but recommended) and team rollout.
Already Written Something? Check It.
If you've already got a handbook (even a rough one), don't start from scratch. Check what you've got and fix the gaps.
Upload your current handbook to our free compliance checker. We'll tell you what's missing, what's risky, and what needs updating.
Related Resources
Found this article helpful?
Check Your Handbook Compliance
Use our free compliance checker to identify gaps, outdated information, and common mistakes in your employee handbook.
Run Free Compliance Check