Every founder asks me: "Do I need an employee handbook?"

My answer is always the same: "I don't know. Let me ask you some questions."

Because the truth is, some 3-person startups desperately need a handbook, and some 15-person companies can still get away without one. It's not about the number on your org chart. It's about what's actually happening in your business.

Here are the questions you need to answer honestly.

Question 1: How Many States Do Your Employees Work In?

If your answer is "one" → You might not need a handbook yet.

If your answer is "two or more" → You probably need a handbook.

Why this matters:

Different states have wildly different employment law requirements. What's legal in Texas is illegal in California. What's optional in Florida is mandatory in New York.

A handbook creates a single source of truth for policies that comply with the most restrictive state you operate in. Without it, you're making up policies on the fly and hoping you're not accidentally violating someone's state law.

Example: You have employees in Colorado and Texas. Colorado requires paid sick leave. Texas doesn't. Without a handbook, your Colorado employee might not know they have sick leave rights, and you might forget to track their accruals. That's a violation waiting to happen.

Question 2: Do You Have Any Managers?

If your answer is "no, everyone reports to founders" → You can probably wait.

If your answer is "yes, some employees manage others" → You need a handbook.

Why this matters:

Managers make decisions that create legal liability. They approve time off, handle performance issues, decide who gets raises, and respond to employee complaints.

Without a handbook, every manager is making up their own rules. One manager lets people work from home Fridays. Another doesn't. One manager is strict about PTO requests. Another approves everything.

That inconsistency is how discrimination lawsuits start.

A handbook gives managers clear policies to follow, so they're all treating employees the same way. It protects you AND them.

Question 3: Have You Ever Said "Let Me Get Back to You on That" to an Employee Question?

If your answer is "rarely, our policies are clear" → You might be fine without one.

If your answer is "all the time" → You need a handbook.

Why this matters:

When employees ask questions and you don't have clear answers, you're making policy on the fly. That's dangerous for two reasons:

Common questions that mean you need written policies:

If you're answering these differently for different people, or if you're not sure what your answer should be, you need a handbook.

Question 4: Have Any Employees Left Your Company?

If your answer is "no, we're all still here" → You can probably wait a bit longer.

If your answer is "yes, we've had turnover" → You need a handbook.

Why this matters:

When employees leave, they ask questions:

If you don't have written policies, you're vulnerable to:

A handbook documents what happens when employment ends. Before you have any turnover, this seems unnecessary. After your first messy departure, you realize why it matters.

Question 5: Are You Offering Benefits?

If your answer is "no, just salary" → You might not need a handbook yet.

If your answer is "yes - health insurance, 401k, PTO, equity, etc." → You need a handbook.

Why this matters:

Benefits require policies. When do employees become eligible? How much do you contribute? What happens if they leave before vesting? Can they carry over unused PTO?

Without written policies, you're creating confusion and potential legal issues:

The more complex your compensation package, the more you need it in writing.

Question 6: Have You Ever Had an Awkward Conversation About Employee Behavior?

If your answer is "no, everyone's professional" → You might not need a handbook yet.

If your answer is "yes, and I didn't know what to say" → You need a handbook.

Why this matters:

Startups attract informal cultures. That's great until someone crosses a line.

Scenarios I've seen:

Without a handbook, you have no documented standards of conduct. You're having uncomfortable conversations based on "vibe" rather than policy.

A handbook doesn't have to be corporate and stifling. It can say "we trust you to be professional, here's what that means" and give clear examples.

Question 7: Are You Subject to State-Specific Compliance Requirements?

If your answer is "I don't know what you're talking about" → Research this immediately, you might need a handbook.

If your answer is "yes - we have to provide [specific leave/notice/policy]" → You need a handbook.

Why this matters:

Many states require employers to provide specific notices and policies:

Colorado: Must notify employees of paid sick leave rights (HFWA), FAMLI benefits, wage payment policies

California: Must provide policies on meal breaks, rest breaks, sick leave

New York: Must provide sexual harassment policy, wage notices, sick leave policy

NYC: Must provide earned sick time policy, freelance isn't free act notices

You can provide these as standalone notices, but most employers incorporate them into a handbook because it's easier to keep track of one document than 15 different policy sheets.

Question 8: Could You Confidently Defend Your Policies in Court?

If your answer is "we don't really have policies" → This is a problem whether or not you have a handbook.

If your answer is "yes, but they're not written down" → You need a handbook.

If your answer is "yes, they're documented" → You basically already have a handbook.

Why this matters:

When (not if) an employee claims discrimination, harassment, or unfair treatment, you need to show:

"We told everyone verbally" doesn't hold up. "It's just how we do things" isn't a defense. "We treat everyone fairly" means nothing without documentation.

A handbook is your evidence that you had reasonable policies and communicated them clearly.

Question 9: Are You Hiring People Who've Worked at "Real" Companies?

If your answer is "no, mostly early-career people used to startup chaos" → You can probably wait.

If your answer is "yes, we're hiring experienced people from corporate backgrounds" → You need a handbook.

Why this matters:

People coming from established companies expect written policies. They're used to knowing:

Without a handbook, you look unprofessional and disorganized. You'll lose good candidates or create frustration with new hires who don't understand "how things work here."

Question 10: What Would Happen If a Founder Got Hit by a Bus Tomorrow?

If your answer is "the other founder/early employees know all our policies" → You might not need a handbook yet.

If your answer is "honestly, nobody would know what our policies are" → You need a handbook.

Why this matters:

Right now, all your HR knowledge is in founders' heads. That's fine when you're 3 people. It's a disaster when:

A handbook is institutional knowledge. It ensures policies survive beyond whoever created them.

The Scoring Guide

Count how many of these apply to you:

0-2 "yes" answers: You can probably wait on a handbook. Focus on having written policies for critical items (PTO, expense reimbursement, remote work) even if they're not in a formal handbook.

3-5 "yes" answers: You're in the gray zone. Start working on a handbook now, aim to have it done in the next 2-3 months.

6-10 "yes" answers: You needed a handbook yesterday. This is your top priority.

What to Do If You Don't Need a Handbook Yet

Just because you don't need a full handbook doesn't mean you need zero documentation.

At minimum, have written policies on:

These can be simple Google Docs. They don't need to be a 50-page handbook.

The Bottom Line

A handbook isn't about company size. It's about complexity.

If you have:

You can probably wait.

If you have:

You need a handbook.

The right time to create a handbook is before you need it in court.

Need help figuring out what should actually be in your handbook? That's what I do.