HR leads tend to put the employee handbook in the “no” pile by reflex. It feels personal. Read it again, though, and most of it is not about any one person. It sets out leave rules, conduct standards, how expenses are approved and what happens when someone resigns. That is company policy, written by the company.
The harder questions are about what sits around the policy text, and what the handbook promises employees.
Is a handbook the company’s to license?
The parts your company wrote, usually yes. Copyright in text written by employees as part of their job generally sits with the employer, which is the same reason the company can license its SOPs.
Three kinds of content in a typical handbook are not yours:
- Template text. Many handbooks start from a model bought from an HR publisher, a payroll provider or an employment law firm. The license that came with it may not allow reuse outside your company. Check it, or rewrite those sections.
- Benefit summaries. Plan descriptions supplied by an insurer or benefits provider belong to them.
- Quoted law. Statutory text is free to use, but long passages of it add nothing a buyer cannot already get.
What personal data does a handbook hold?
Less than most HR documents, but not none.
| Section | Personal data | What to do |
|---|---|---|
| Welcome letter | Founder or CEO name and signature | Replace with a role, drop the signature |
| Contacts page | HR names, emails, phone extensions | Replace with roles |
| Policy sections | Usually none | Check examples for real incidents |
| Acknowledgment form | Signed copies with employee names | Exclude every signed copy |
| Org charts | Names and reporting lines | Exclude |
The signed acknowledgment pages are the trap. If the handbook lives in an HR system, each employee’s signed copy may sit next to the master. License the master only.
What does the handbook promise employees?
This is the confidentiality question that actually matters. Many handbooks include a section on how the company handles employee information: who sees personnel files, what is monitored, what is shared with third parties. A license should sit comfortably inside those promises.
If the handbook says employee information is never shared outside the company, licensing the handbook’s own text does not break that, because the policy text is not employee information. Licensing performance reviews or investigation notes would. That is why HR case files belong in the “no” pile for real, even though Scale AI’s page lists HR records among what it takes. Scale also lists employee and customer identities among its exclusions, but de-identifying a performance review well is hard, and the promise to staff may rule it out anyway.
Have your own lawyer read both the handbook’s privacy section and the proposed license side by side.
What about the confidentiality clause in the handbook?
Most handbooks ask employees to keep company information confidential. That clause binds employees, not the company. The company is the owner of its confidential information and can choose to license it.
Two things are worth checking, though. First, whether the handbook or offer letters promise anything specific about employee data, as above. Second, whether any customer or client contract treats your internal procedures as their confidential information, which is rare but happens in some outsourcing deals.
Do buyers want handbooks?
Handbooks do not appear by name on any buyer page we read. The nearest headings are micro1’s SOPs and process documentation and Scale AI’s documents and files with metadata. A handbook fits under those, but it is rarely the most valuable item in a set. It is short, similar across companies, and often template-based.
Where a handbook helps is as part of a linked whole: the handbook’s leave policy, the HR runbook for processing leave, and the wiki pages that answer staff questions about it. That set shows a policy, its process and its exceptions together.
How should you prepare a handbook for licensing?
- Take the current master version, not the HR system’s per-employee copies.
- Remove or rewrite template and provider sections whose license you cannot confirm.
- Replace every named person with a role, including the welcome letter.
- Drop org charts, signed forms and appendices that list staff.
- Read the privacy section against the license terms with your lawyer.
- Note what you removed, in a line or two, for the buyer’s review.
A clean handbook takes an afternoon. The redaction guide covers the documents around it. If you are weighing whether to sell company documents at all, the handbook is a fair test: if it comes through cleanly, most of your policy folder will too.
A handbook tells staff how the company treats them, so the license should honor that before it honors anything else.