Guides

An employee handbook is not a set of procedures

5 minute read · Updated 2026-09-07

Small shops often end up with one document trying to be both. It covers holiday requests, phone use, dress code, and then somewhere on page nine it explains how to test a gas line. Neither part works well.

Different questions, different documents

A handbook answers questions about employment. Hours, pay, conduct, leave, what happens when things go wrong between people. It is a legal and HR document and it usually needs review by someone who knows your state's employment law.

A procedure answers a question about the work. How this task is done in this shop, in order. It is a technical document and it needs review by someone who knows the trade.

They change at different speeds

A handbook changes when the law changes or a policy changes, which is rarely. A procedure changes when someone finds a better way or a callback exposes a gap, which should be often. Binding them together means procedure improvements wait for a handbook revision, and they usually never happen.

They need different acknowledgements

A handbook acknowledgement is normally taken once at hire, sometimes re-taken after a substantial revision. A procedure acknowledgement is per procedure, per version, and per person doing that work. Rolling them into one signature at hire gives you a record that proves neither.

Which one gets asked for

After an injury, the question is about the procedure and the training on it. In an employment dispute, the question is about the handbook. Keeping them separate means you can produce the relevant one without handing over the other.

What to do if you have one merged document

Split it. Pull every how-to section out into standalone procedures, one per task, numbered steps. Leave the employment terms in the handbook. Take a fresh acknowledgement on both, because the old signature covered a document that no longer exists in that form.