How to Build a Company Handbook

What a Company Handbook Is (and What It Isn't)

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.

---

The Eight Sections Every Company Handbook Needs

1. Welcome and Purpose

A short section (500-700 words) that communicates:

• What the company does and why it exists (the mission)
• What kind of company it aspires to be (culture and values)
• What new employees should expect from the company and what the company expects from them
• Why the handbook exists and how it should be used

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:

• Working hours and flexibility (core hours, time zone expectations, flexibility policy)
• Remote/hybrid expectations (what determines who comes in, how remote work is evaluated)
• Communication norms (which channel for which type of communication, response time expectations)
• Meeting culture (what meetings are expected, how to decline or cancel, meeting-free windows)
• How decisions are made (who has authority for what, when to escalate)

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:

• Compensation and pay practices (when paid, how reviewed, bonus structures)
• Benefits overview (health insurance, retirement, equity, perks) with links to detailed benefits documents
• Time off policy (PTO, vacation, sick leave, parental leave, holidays)
• Performance management (review cycles, feedback processes, performance improvement process)
• Disciplinary process (how performance concerns are raised and addressed)
• Termination practices

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:

• Code of conduct (how to treat colleagues, customers, and partners)
• Conflicts of interest (what constitutes a conflict, how to disclose one)
• Confidentiality and data protection (what information must be kept confidential, how to handle company data)
• Social media and external representation (what can be said publicly about the company)
• Anti-harassment and anti-discrimination policy (definition, reporting process, non-retaliation)

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:

• Communication tools (Slack, email) and how they're used
• Project management tools and how work is tracked
• File storage and document management
• HR systems (benefits portal, payroll access, expense submission)
• IT and technical support
• Key contacts and who to reach for what

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:

• Career levels and ladders (or a link to the career framework)
• Performance review process (frequency, format, what to expect)
• Promotion criteria and process
• Professional development resources (budget, approved uses, request process)
• Learning and development programs

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:

• Workplace safety policies
• Emergency procedures (what to do in various emergency scenarios)
• Legal compliance requirements (data privacy, regulatory compliance relevant to the industry)
• Whistleblower and reporting policies

This section varies significantly by industry and jurisdiction. Consult legal counsel for industry-specific requirements.

---

Format Choices That Determine Whether the Handbook Gets Used

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.

---

The Living Handbook: Maintenance Practice

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.

---

Worked Example: A 50-Person Tech Startup's Handbook Project

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.

---

Key Takeaways

1. The handbook serves two audiences simultaneously: new employees reading for orientation (front-to-back) and existing employees searching for a specific policy (lookup); the structure should support both.
2. Culture sections with specific behavioral examples communicate more than value lists: "we value speed over perfection" followed by what that actually means in practice says something; a list of the word "speed" says nothing.
3. Employment policies must be specific to be useful: "generous PTO" is not a policy; "20 days per year accruing at X per month" is.
4. A digital, version-controlled handbook with a maintenance trigger is more useful than a printed one: it can be updated immediately; it can be searched; employees can acknowledge specific policies digitally.
5. The onboarding feedback loop is the most efficient quality control: new employees read the handbook fresh and notice gaps that long-tenured employees are blind to — build in a mechanism for their feedback.

---

Conclusion

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.

Related reading: Clip Articles for Later Reading.