It’s pretty common for employee handbooks (if you want to call them that) to live in shared documents on platforms like Google Drive. Perhaps the so-called handbook gets sent to every new team member, and is only ever reviewed right before each time it’s shared. There’s no real way to know who has seen it, or who has read the updated versions.

Maybe that’s not a huge deal for reference knowledge. For a handbook, it defeats the purpose of having one to begin with. Employee handbooks cover things that an organization should be confident was communicated to its employees. Things like policies, expectations, procedures, benefits, etc. If there’s ever a problem, “everyone said they read it” isn’t going to cut it. Confirmation is important.

What an employee handbook actually needs

Here’s what a useful handbook does that a static document can’t do.

• It separates required reading from reference information. A benefits overview and a code of conduct policy don’t carry the same weight. Treating them like they do makes the reference information a burden to read and dilutes the importance of the required information.
• It records acknowledgment instead of making assumptions. Someone has to actively confirm they’ve read a policy for that confirmation to mean anything later.
• It stays current without becoming a new document every time something changes. Changing one line in a PTO policy shouldn’t require building the whole handbook from scratch in a new document.

Building the handbook in WordPress

If your team runs WordPress, Keystone gives you the structure a handbook needs. It uses the accounts your team already has in WordPress. There’s no need for an external platform.

You’d start with a Section, something like “Employee Handbook.” Inside it, split content into Modules by function instead of sticking everything in one long document. A Required Module might hold your Code of Conduct and core policies. A separate Reference Module can hold a benefits overview, an org chart, or a PTO request how-to, content people look up as needed rather than read once and confirm.

For the policies that need to be acknowledged, Keystone’s Document item type is built for exactly this. Document items always require acknowledgment. There’s no plain “mark complete” option, only “I Acknowledge This Document.”

Reading items support acknowledgment too, for policies you’d rather present as formatted text than an embedded file. Either way, when a team member confirms, that confirmation is recorded against their account, and managers can see exactly who has and hasn’t acknowledged each policy from the Reports page or an individual’s Member Profile page.

Keeping the handbook current

Policies change, of course. Keystone’s re-completion setting handles the part that’s usually hardest to manage. When you update a policy’s content in a way that matters, you can flag it as requiring re-completion. Anyone who already acknowledged the old version shows as needing to review it again, without you having to track who saw which version or manually reassign anything.

What this looks like in practice

A 15-person company might build an Employee Handbook Section with two Modules.

• a Required Module called “Policies & Conduct” containing Document items for the code of conduct, an anti-harassment policy, and a safety procedure, each requiring acknowledgment
• a Reference Module called “Benefits & Resources,” containing browsable reading items and a PTO request Document with no acknowledgment required.

New hires are assigned the Required Module during onboarding, alongside whatever onboarding content already exists. When the code of conduct is revised eighteen months later, it’s flagged for re-completion, and the Reports page shows exactly who still needs to review it.

Getting started

If you already run WordPress, this doesn’t require a new platform, just structure inside the one you’re already using. Required modules handle the policies that need proof of acknowledgment. Reference modules handle everything else. See how the rest of Keystone’s features fit together, or check pricing to get started.