Employee Handbook Template and Tracker
Five documents and four sheets, including a coverage sheet that reports each policy against the employees who acknowledged a version actually containing it.
Free download · No account needed
What Effective Coverage Is
One number says 99.2 percent. Seven policies are under half.
Marloe Logistics, 240 employees across seven states. Handbook v5 effective 1 July 2026. The last company-wide re-acknowledgment campaign ran at v3 in March 2025, and v4 and v5 went out by email.
| What is being measured | Question it answers | Figure |
|---|---|---|
| Signed acknowledgment on file | Did this person ever sign something? | 238/240 99.2% |
| Acknowledged the current version | Did this person sign v5? | 22/240 9.2% |
| Effective coverage, per policy | For this policy as it reads today, did this person acknowledge a version that contained this text? | 0.0% to 100% |
The seven policies below half
| Policy | Applies to | Last amended | Covered | Coverage |
|---|---|---|---|---|
| Colorado paid sick leave | Colorado | v5 | 0 of 9 | 0.0% |
| Arbitration and dispute resolution | Every state | v5 | 22 of 240 | 9.2% |
| Remote work expense reimbursement | Every state | v5 | 22 of 240 | 9.2% |
| Anti-harassment and reporting | Every state | v4 | 41 of 240 | 17.1% |
| Washington paid family and medical leave | Washington | v4 | 1 of 5 | 20.0% |
| Pay transparency in postings | CA, NY, WA, CO | v4 | 12 of 44 | 27.3% |
| California meal and rest breaks | California | v4 | 7 of 18 | 38.9% |
Every one of the seven was amended in v4 or v5, and that is the finding rather than a coincidence: the most recently rewritten policy always has the lowest coverage, and it was usually rewritten because it was the exposure. Marloe's arbitration clause was rewritten in v5 because counsel had called the old one probably unenforceable. Twenty-two people are bound by the new one. Invoke it against any of the other 218 and the clause that governs is the one counsel already said would not hold.
The other 27 policies are the reason this is not just a re-sign
Most of a handbook does not change between versions. Twenty-seven of Marloe's 34 policies read identically in v3 and v5, so a v3 signature still binds on all of them. That is what makes the gap small enough to close: seven policies, not thirty-four.
Every handbook report ends at the same number. Some share of employees have a signed acknowledgment on file, it is nearly always above 95 percent, and it stays there because collecting it is on the onboarding checklist. That number answers whether somebody ever signed something. It does not answer the question a dispute asks, which is narrower: for the policy now being invoked, did this employee acknowledge a version that actually contained this text?
A handbook is a sequence of versions, and an employee is bound by the one they signed. Marloe Logistics, a fictional 240-person warehouse software company, reports 99.2 percent acknowledged. Per policy, coverage runs from 0.0 percent to 100 percent. Its arbitration clause was rewritten in v5 because counsel called the old one probably unenforceable, and 22 people are bound by the new one. Its Colorado sick leave policy was rewritten for nine employees, none of whom have acknowledged it.
The useful part is what that does to the fix. Most of a handbook does not change between versions, so 27 of Marloe's 34 policies read identically in v3 and v5 and a v3 signature still binds on all of them. The real gap is seven policies, and the ask differs by state: three in Ohio, four in New York, five in California. Scoping is a legal question, not a formatting one, which is also why pay range disclosure is not a national paragraph.
What is in the pack
Policy Register
One row per policy rather than per section, carrying the version that last amended it, what changed, and the states it applies to. A section cannot support a scoped acknowledgment, which is why the register is the unit everything else is computed from, the same unit the underlying policy set itself is maintained against.
Effective Coverage by Policy
Applicable employees, employees who acknowledged a version at or after the amending one, and the rate. Both of the numbers normally reported sit at the bottom of the same sheet so the gap between them is visible rather than argued about.
Acknowledgment Tracker
Grouped by state and by acknowledged version, because those two together decide what each person still owes. Same version in two states is a different ask, and the sheet names the policies rather than the count.
Review Calendar
Cadence set by what actually ages in each policy, with the coverage each amendment would reset in the last column. Reviewing the performance policy annually is different from reviewing a contribution rate that changes by rate year.
What Effective Coverage Is
Three pages to read before the coverage sheet. The three things that have to be joined, why the most recently rewritten policy always has the lowest coverage, and why amending a policy is a coverage decision as well as a legal one.
Handbook
The assembled handbook by section, with each policy stamped with the version that last amended it and its jurisdiction scope. State-scoped policies sit in their own part rather than being folded into a national paragraph.
Acknowledgment Form
Two forms. A full-handbook form for a new hire or anyone below the last campaign, and a scoped form naming specific policies and versions, which is what makes a three-policy request answerable rather than another whole-document click.
Change Summary and Campaign
What changed and why, written per policy so it can be attached to a scoped request. The campaign document runs the targeted ask, including chasing it, which is the same problem as collecting compliance documents.
Why the reporting policy is usually the least covered
Marloe's anti-harassment policy was rewritten in v4 to add a reporting channel that does not run through the manager, and 199 people are still bound by the routes it replaced. What that costs shows up in a live investigation rather than on a compliance report.
How it works
- 1
Send the handbook and its earlier versions
Every version you still have, not just the current one. The version history is what makes a v3 signature meaningful on 27 policies and worthless on seven, so a handbook with no history gets a coverage figure nobody can defend.
- 2
Send acknowledgments with the version, not the date
Which version each person signed. If your records only say signed, reconstructing the version history is the real first task and the space will say so rather than computing a number it cannot stand behind.
- 3
Scope each policy to the states it applies to
One row per policy, with the rows that need counsel left open rather than guessed. The applicable population becomes the coverage denominator, which is why a four-person state matters as much as the head office.
- 4
Coverage comes back per policy, then a targeted ask
Expect the policies you rewrote most recently to be the least covered. The campaign that follows names the specific policies each person owes, which is a request that gets returned rather than ignored.
Frequently asked questions
Is the acknowledgment rate not already the compliance number?
It answers whether somebody ever signed something. Marloe reports 99.2 percent while its arbitration clause is acknowledged by 22 of 240 people, because the clause was rewritten in v5 and most signatures are on v3. In a dispute the version the employee signed is the one that governs.
Why not just have everybody re-sign the whole handbook?
Because it is 240 people against 34 policies and it produces one more click on a document nobody reads. Coverage says the real gap is seven policies: three in Ohio, four in New York, five in California and Colorado. A three-policy request with the changes named gets returned.
Why does the same version mean a different ask in two states?
Because scope is per policy. FMLA is a floor and state or local law providing greater family or medical leave rights is not superseded by it, so an employer complies with both. Marloe's v3 employees owe three policies in Ohio and five in Colorado.
Does anything have to be in the handbook by law?
The FMLA general notice does, if you have one. An FMLA-covered employer with eligible employees must include that notice in employee handbooks or other written guidance, where such materials exist, or hand it to each new hire. Failing the notice requirements can itself be treated as interference.
Our records only say signed, with a date. Can we still use this?
Partly. A date plus your version effective dates usually reconstructs the version, and that reconstruction is the first task rather than a blocker. Where it stays ambiguous the policy is reported as uncovered, because a coverage figure built on a guess is worse than a gap you can see.
What does the coverage figure change about amending a policy?
It puts a number on the amendment. Rewriting a company-wide policy resets its coverage to zero for all 240 people, so a small clarification to something undisputed can wait for the next scheduled campaign while a clause counsel is worried about cannot. The review calendar carries that column.
What format are the downloaded files, and is it free?
Five Word documents and four CSV sheets in one zip, free and with no account. The documents open in Word, Pages and Google Docs, the sheets in Excel, Numbers and Google Sheets. Edit with AI installs the same pack as a private Space and computes coverage against your own roster.
Find out which policies your signatures do not cover
Send the current handbook, whatever earlier versions you still have, your acknowledgment records with a version rather than just a date, and where your employees work. What comes back first is the coverage figure per policy, and the group whose signatures predate your last campaign.
Edit with AI