Somewhere in your company's history, someone decided that new hires get two weeks of PTO. Someone else decided that remote work is fine on Fridays. A third person established that expense reports need to be submitted within 30 days. And the dress code? That was a Slack message from the CEO three years ago that said "just don't wear pajamas to client meetings."

These policies exist. They're real. People follow them. But they're not in a handbook -- they're scattered across emails, Slack threads, meeting notes, Google Docs, and the collective memory of long-tenured employees. Every new hire discovers them piecemeal, usually by accidentally violating one.

You know you need a handbook. You've been meaning to write one for months (or years). The task feels enormous because it requires gathering every policy decision your company has ever made from dozens of sources. But what if most of the raw material is already in your notes?

The Scattered Policy Problem

Growing companies generate policies organically. A situation arises -- someone asks about parental leave, a vendor asks about procurement approval thresholds, two people want the same week off -- and a decision gets made. That decision becomes policy, even if it's never formally documented.

Over time, these informal policies accumulate. The people who were there when the decisions were made know the rules. Everyone else has to ask around, search Slack, or learn by doing. This is manageable with ten employees. It's chaos with fifty.

The handbook isn't a creative writing project. It's an assembly project. The content already exists in your organization's notes, messages, and documented decisions. The challenge is finding it and organizing it.

Mining Your Notes for Policy

If you've been using Mem (or any notes app) to capture meeting notes, decisions, and operational discussions, you already have a substantial portion of your handbook raw material.

Start by asking Mem Chat:

"What decisions have I captured about company policies, benefits, remote work, time off, expenses, hiring, or employee guidelines?"

Chat searches across all your notes -- leadership meeting minutes, team sync notes, HR conversations, onboarding discussions -- and surfaces every policy-adjacent decision you've documented. The results might surprise you: a note from the Q1 offsite where the team agreed on a four-day summer schedule, a meeting note where expense limits were set at $500 for pre-approved purchases, a 1:1 where someone asked about professional development budgets and you said "up to $2,000 per year."

These fragments are your handbook's raw material. Each one is a policy that's been decided but never formally documented.

Assembling the First Draft

Once you have the fragments, ask Chat to assemble them:

"Based on all the policy decisions and guidelines I've captured, create a first draft of an employee handbook organized by section: company overview, employment basics, benefits, time off, remote work, expenses, conduct, and professional development."

Chat takes your scattered notes and produces a structured document. It won't be perfect -- some sections will be thin, others will have conflicting information from different time periods. But it's a first draft, and a first draft is infinitely more useful than the blank document that's been sitting in your to-do list for a year.

Review the draft section by section. Where information is missing, you know exactly what questions to answer. Where information conflicts, you know which decisions need to be re-made. The handbook stops being an overwhelming project and becomes an editing project.

Filling the Gaps

The first draft will reveal what you haven't documented. Common gaps include:

• Benefits details -- health insurance specifics, 401(k) match percentages, enrollment periods

• Leave policies -- how PTO accrues, what happens to unused days, how sick time works

• Performance processes -- review cycles, promotion criteria, improvement plans

• Legal requirements -- anti-discrimination policies, harassment reporting, accommodation procedures

For each gap, you have two options: check if the information exists in notes you haven't searched yet ("Do I have any notes about our health insurance plan details?"), or recognize that this policy hasn't been established and needs a decision.

The second option is valuable because it forces explicit decisions on things that have been operating on assumption. "We don't actually have a policy on whether unused PTO rolls over" is better to discover now than when an employee asks in December.

Voice Capture for Policy Decisions

Going forward, when policy decisions happen in meetings, capture them explicitly. A 15-second voice note after a leadership discussion: "Decided today that employees can expense co-working space memberships up to $200 per month. Starts next quarter. Applies to fully remote employees only."

These captures become automatic handbook updates. Quarterly, ask Chat: "What new policy decisions have I captured since the last handbook update?" and you have a change log ready to incorporate.

This is the handbook that maintains itself -- not through a dedicated HR process, but through the meeting notes and decision captures that are already happening. For the broader approach to capturing organizational knowledge, see our guide on documenting institutional knowledge.

The Living Handbook

Traditional handbooks are PDFs that get updated once a year (if ever). By the time they're published, they're already outdated. A notes-based handbook is a living document -- always current because it's built from the same system where new decisions are captured.

Keep the handbook as a note (or a set of notes) in Mem. When a policy changes, update the relevant section. When someone asks a question the handbook doesn't answer, add the answer. When Chat reveals a new policy fragment from meeting notes, incorporate it.

The handbook becomes less like a legal document and more like a company wiki -- a practical reference that evolves with the company. New hires get the current version. Existing employees can query it: "What's our policy on conference attendance and travel expenses?" gets an answer drawn from the handbook content, supplemented by any related meeting notes.

From Notes to Culture

Here's the unexpected benefit: the process of assembling a handbook from scattered notes reveals your company culture in practice, not just in principle.

The decisions you've documented -- the four-day summer schedule, the co-working stipend, the emphasis on professional development -- tell a story about what your company values. Reading them together, organized into a coherent document, often surprises founders. "I didn't realize we'd made so many employee-friendly decisions" or "We have more structure than I thought" are common reactions.

This is culture documentation in reverse. You didn't start with values and derive policies. You made policies based on situations, and the patterns reveal your values. For more on this approach, see our guide on documenting company culture.

Mem Chat helps with the synthesis: "Based on the policies in our handbook, what values do they collectively reflect?" can produce a values statement that's grounded in actual behavior rather than aspirational language.

Getting Started

1. Ask Mem Chat to surface all policy-related decisions from your notes

2. Review what comes back -- you'll be surprised how much is already documented

3. Ask Chat to assemble a first draft organized by standard handbook sections

4. Identify gaps and either find missing information in your notes or make the missing decisions

5. Keep the handbook as a living document -- update it when new decisions are captured

The employee handbook you've been putting off writing is hiding in your notes. The AI just needs to find it and put it in order.

Try Mem free →