Employee Handbook Template for Google Docs
Every section a growing company needs, what to write in each, and how to publish the handbook so people actually read it.

An employee handbook answers the questions every person in the company asks sooner or later: how we work, what we expect, what you're entitled to and who to ask. Below is a free template for Google Docs with every section a growing company needs, what to write in each, and how to publish it so people actually use it.
The template
| Section | What it covers |
|---|---|
| 1. Welcome | A short note from the founders: why the company exists and what this handbook is for |
| 2. Mission and values | What you're building, for whom, and the values that guide decisions, each with an example |
| 3. How we work | Working hours, remote and office setup, meetings, communication channels and response times |
| 4. Who's who | Teams, leaders and who to ask about what |
| 5. Your first weeks | Link to the onboarding checklist and the pages new hires read first |
| 6. Time off | Vacation, public holidays, sick leave, parental leave and how to request them |
| 7. Pay and benefits | Pay dates, expenses, equipment, learning budget, health and other benefits |
| 8. Tools and accounts | The tools we use, how to get access and the basic security rules |
| 9. Policies | Code of conduct, anti-harassment, equal opportunity, data protection, security, travel and expenses |
| 10. Growth and feedback | Reviews, promotions, one-to-ones and how feedback works |
| 11. Leaving the company | Notice periods, returning equipment, the last day |
| 12. Changes to this handbook | Who owns it, how changes are announced and the date of the last review |
Each section works best as its own short doc rather than one 40-page file. More on that below.
How to write it so people read it
- Write like you talk. "You get 25 days of vacation a year" beats "Employees are entitled to an annual leave allowance of twenty-five (25) working days."
- Lead with the answer. The first line of each section answers the most common question; details follow.
- Give examples. A value without an example is a slogan. Show what it looks like in a real decision.
- Link instead of repeating. The expense policy lives in one place; the handbook links to it.
- Keep it current. Add the owner and the last review date to each section, and review the whole handbook once a year.
- Ask new hires. Every new person reads the handbook with fresh eyes. Their questions show you what's missing.
One doc or many: publishing the handbook
A single long Google Doc is easy to start and hard to use. Nobody reads 40 pages front to back, a table of contents only helps so much, and one person editing the vacation policy shouldn't need to touch the whole file.
The better setup: one folder called Handbook in your shared drive, with one short Doc per section, numbered so they stay in order.
Handbook ├── 01 Welcome ├── 02 Mission and values ├── 03 How we work ├── 04 Who's who ├── 05 Your first weeks ├── 06 Time off ├── 07 Pay and benefits ├── 08 Tools and accounts ├── 09 Policies ├── 10 Growth and feedback ├── 11 Leaving the company └── 12 Changes to this handbook
The handbook is usually the first part of a wider company knowledge base in Google Drive, so give it a top-level spot next to onboarding and team docs.
Then connect the folder to Spaceli, and the handbook reads like a website, not a pile of files:
- A sidebar with every section, in the order you set.
- A table of contents on each page that follows the reader.
- Search across the whole handbook, titles and full text.
- Callouts for what matters most, like a Warning on the security rules, written right in Google Docs.
- Access for everyone on your domain, and a default space so new hires land on the handbook first.
- Edits in place. HR fixes a policy right inside Spaceli in the Google Docs editor, and the change syncs to Drive.
FAQ
What should an employee handbook include?
At minimum: mission and values, how the company works, time off, pay and benefits, tools and security, policies and how to leave. The table above covers the full set.
How long should a handbook be?
As short as it can be while answering the common questions. Split it into short sections that link to detailed policies, rather than one long document.
Who should own the handbook?
HR or operations owns it overall; each section has an owner who keeps it current, such as Finance for expenses and IT for security.
How often should we update it?
Update a section as soon as the policy changes, and review the whole handbook once a year.

Writes about wikis, documentation and how teams keep their knowledge easy to find.
Keep reading
All articles →Employee Onboarding Checklist Template for Google Docs
A free onboarding checklist for Google Docs: before day one, day one, week one and the first 90 days, with an owner for every task.
How to Write SOPs in Google Docs (with Template)
Write standard operating procedures people actually follow: a step-by-step method, a free SOP template for Google Docs, and how to keep SOPs current.
Help Center Article Template: How to Write Docs Customers Actually Read
Three copy-ready help article templates (how-to, troubleshooting, explainer), style rules and a checklist for writing docs customers actually read.
Your knowledge base is already in Google Drive.
Give your team a better way to organize, find, and share knowledge. Keep your documents right where they are.
Start for FreeFree during the beta. Get started in about a minute.
Spaceli only accesses the folders you choose.