Team Knowledge
How to build a company handbook — a practical guide for founders, operations leaders, and HR teams who want a handbook that communicates what the company values, how it works, and what employees can expect, without producing a bureaucratic document no one reads.
A company handbook is the document that answers the question every new employee has on their first day: "How does this place work?"
It's not a legal document, even though it contains policies that have legal implications. It's not a sales document, even though it communicates culture and values. It's not a database of HR procedures, even though it covers HR-related topics. It's a guide — written for people who are joining the organization and need to understand how it operates, what it values, and what they can expect.
The company handbook has two distinct audiences with different needs:
New employees in their first weeks: They need to understand the fundamentals: the company's mission and values, how work is organized, what the expectations are, what support is available. For this audience, the handbook is a orientation guide — it gives them the framework for understanding everything else they'll learn.
Existing employees with a specific question: "What's the policy on remote work?" "How do I request a leave of absence?" "What are the guidelines for expenses?" For this audience, the handbook is a reference — they need to find a specific answer quickly.
These two use cases require different structural choices: the new employee reads front-to-back (or follows an onboarding sequence); the existing employee searches. A good handbook serves both.
What a handbook is not: a substitute for manager relationships, team culture, or genuine leadership. A company that treats the handbook as its primary culture statement has a handbook problem. A company that uses the handbook to document what it actually practices and believes has a useful document.
1. Welcome and Purpose
A short section (500-700 words) that communicates:
This section sets the tone for the entire handbook. It's the only section that should be written in the company's authentic voice — not policy language, not HR-speak. It should sound like a person welcoming someone to the team.
2. Company Culture and Values
Not a list of values with definitions. A substantive explanation of what the company actually believes and how those beliefs shape how it works.
Effective culture sections include: specific behaviors that reflect each value, examples of decisions made in alignment with the values, and honest acknowledgment of the trade-offs the values involve. "We value speed over perfection" means something when it's followed by "that means we ship early and fix fast, and we accept that our first version will sometimes disappoint customers — we prefer that to not shipping at all."
Generic values lists ("integrity," "excellence," "teamwork") without specific behavioral examples communicate nothing. Specific descriptions of how decisions are actually made communicate a great deal.
3. How We Work
The operational norms of the organization: how work gets done, how decisions are made, how people are expected to communicate.
Typical content:
For remote-first companies, this section is significantly more detailed than for co-located ones. When working norms aren't visible by osmosis, they have to be documented.
4. Employment Policies
The policies that govern the employment relationship. This section is the one with the most legal implications and should be reviewed by employment counsel before publication.
Typical content:
This section should be factual and specific. Vague language in employment policies creates misunderstandings and legal exposure. "Generous PTO" is not a policy; "20 days of PTO per year, accruing at X days per month" is a policy.
5. Professional Conduct
The expectations for how employees treat each other and represent the company.
Typical content:
This section has the most legal weight. Every statement should be accurate and specific. "We take harassment seriously" is not a policy; "We investigate all harassment reports within 5 business days and retaliate against no one who reports in good faith" is a policy.
6. Tools, Systems, and Resources
The practical infrastructure of the work: what tools the company uses, how to get access, where to find resources.
Typical content:
This section has a short shelf life and should be maintained more actively than most. Tools change; access processes change; contact information changes.
7. Careers and Development
How employees grow within the company: what career paths look like, how performance is evaluated, what support is available for professional development.
Typical content:
This section is often sparse in early-stage companies and more detailed as the company matures. At minimum, it should explain how performance is evaluated and what advancement looks like.
8. Safety and Compliance
Legal and regulatory requirements the company is obligated to communicate.
Typical content:
This section varies significantly by industry and jurisdiction. Consult legal counsel for industry-specific requirements.
The readable handbook vs. the compliant handbook:
Handbooks written by lawyers read like contracts. They're complete, accurate, and unreadable. Employees sign to acknowledge receipt; they don't read.
Handbooks written for employees read like explanations. They explain the why behind policies, use plain language, and acknowledge that employees are capable of understanding nuance.
The practical compromise: write the handbook for employees, with footnotes or appendices that contain the legal-precise language where needed. "We expect employees to avoid conflicts of interest — situations where personal interests could conflict with the company's" is understandable. "Employees shall disclose material conflicts of interest as defined under [section] within 5 business days of discovery" is legally precise. Link the second to the first.
Digital vs. print:
Print handbooks become outdated the month after printing. A digital handbook (Notion page, company wiki, Confluence, or dedicated HRIS handbook module) can be updated immediately when policies change and can include links to supporting documents.
For companies that need employees to acknowledge receiving specific policies, digital handbooks with acknowledgment features (most HRIS platforms support this) are more practical than print versions.
Version control:
Every significant policy change requires a handbook update and communication to employees. Version the handbook (v1.0, v1.1, etc.) and maintain a changelog. Employees who remember an old policy and encounter a new one should be able to see when it changed.
A handbook written once and never updated becomes an accurate record of how the company worked when it was written and an increasingly inaccurate description of how it works now.
Maintenance mechanisms:
Policy change trigger: When any policy changes, the handbook update is part of the change implementation. The person implementing the change updates the handbook and notifies employees of the change. Not a separate process — part of the same action.
Annual review: Once per year, a designated person (usually HR or operations) reviews the entire handbook for accuracy, removes obsolete sections, and updates anything that has drifted from current practice.
Onboarding feedback loop: New employees, after completing their first month, are asked to flag any handbook sections they found inaccurate, unclear, or incomplete. This is the most efficient quality control mechanism — people encountering the handbook fresh notice gaps that long-tenured employees no longer see.
Setup: A 50-person B2B SaaS startup, 4 years old. They've been operating without a formal handbook. They have: a Notion workspace with scattered policy notes, several policies only in email history, and a culture document the founders wrote three years ago that no one has updated. They're preparing to scale to 100 employees over the next 18 months.
Their process:
Month 1 — Audit: The Head of People audits existing documentation. She identifies 40 discrete policy questions that employees have asked in the last year. She groups them into the eight sections above. She identifies 12 questions with no documented answer anywhere.
Month 2 — Drafting: She drafts the eight sections, with one dedicated week per section. She interviews the founders for the culture section. She reviews the employment law requirements for their jurisdiction with outside counsel.
Month 3 — Review: She sends each section to the relevant stakeholders for review. The employment policies section goes to legal and finance. The professional conduct section goes to the leadership team. The culture section goes to the founders for approval. She incorporates feedback.
Month 4 — Launch: The handbook is published in Notion and announced in an all-hands meeting. New employees are sent the handbook link before their start date with specific sections to read. Existing employees receive a summary of what's new with a link to the full document.
Ongoing: Policy changes trigger handbook updates on the same day. Quarterly review added to the Head of People's calendar.
A company handbook that employees use is readable, specific, and current. The readable part requires writing for people rather than for compliance. The specific part requires actual policy language rather than vague intent. The current part requires maintenance practices that connect policy changes to handbook updates at the moment of change. Teams that build these three properties into their handbook have a document that does its job — orienting new employees, answering questions for existing ones, and communicating authentically what the company believes and how it works. Teams that skip any of the three have a handbook that's signed but not read, or read once and never trusted again.
More WebSnips articles that pair well with this topic.
How to run a documentation audit — a practical guide for teams who want to systematically assess what documentation exists, what's accurate, what's missing, and what should be removed, producing a clear action plan for a knowledge base that's trustworthy and complete.
How to break down knowledge silos — a practical guide for teams and organizations where critical knowledge is trapped in specific people, teams, or systems, creating organizational brittleness, slowing decisions, and widening capability gaps between teams.
How to build a company knowledge base — a practical guide for teams and organizations who want to capture institutional knowledge, reduce repeated answering, and make organizational context accessible to every employee regardless of when they joined.
How to build a decision log — a practical guide for teams and organizations who want a permanent, searchable record of significant decisions that makes the reasoning behind current practices visible and prevents repeated debating of already-resolved questions.
How to capture knowledge from departing employees — a practical guide for managers and HR teams who want to systematically extract institutional knowledge before it leaves with an employee, rather than discovering the gaps after they're gone.
How to create a knowledge-sharing culture — a practical guide for teams and leaders who want knowledge sharing to be a natural part of how people work, not a program that requires constant top-down pressure to maintain.