Writing procedures employees actually use

Standard operating procedures that employees actually use are short, written by the people who do the work, tested by someone else and kept where they're needed. One page, action verbs, an owner, checkpoints. Everything else is what turns a good intention into a binder nobody opens.

Why so many procedures sit in a drawer

Plenty of small businesses have procedures. Few use them. Ask an employee where the receiving procedure is, and there's a good chance they'll shrug, then explain how they do it themselves.

The causes are always the same:

• Too long. A 20-page document for a 15-minute task. Nobody rereads it.
• Written for an auditor, not an employee. The text exists to prove it exists, not to guide anyone.
• Impossible to find. It lives on one computer, under a file name only its author knows.
• Out of date. The software changed, the supplier too, but the procedure didn't. After one mistake, nobody trusts it again.

A useful procedure fixes all four problems at once. It's less about writing than about format and habit.

Six rules for a procedure people use

These rules apply to every procedure in step 5 of the path, from customer service to payroll.

1. One page, one task

If a procedure runs past one page, it probably covers two tasks. Split it. Technical detail can go in an appendix or a short video linked at the bottom.

2. A verb at the start of every line

"Check the purchase order." "Enter the lot number." "Call the client if the gap exceeds the threshold." A busy employee should be able to read just the start of each line and know what to do.

3. An owner and a backup

Each procedure names one person who keeps it current, and another who knows how to do it. That's what stops know-how from becoming one person's business again, the trap described in our article on key employee dependency.

4. Clear checkpoints

At certain steps, you check before going on. These checkpoints replace the "show me before you send it" that pushes so many small decisions up to the owner. They let you delegate decisions without losing control.

5. Kept where the work happens

A shop procedure can be posted at the station, with a QR code to the current version. An office procedure lives in a shared folder, organized by department. The test is simple: can a new hire find it in under a minute?

6. Tested before it's approved

Before calling it final, give the procedure to someone who doesn't do that task, and watch them do it without helping. Every time they hesitate, mark the line. Fix it, then approve it.

An example in Montérégie

Picture a welding supply and industrial gas distributor in Saint-Jean-sur-Richelieu. The company is invented, but the story is common. Nine million dollars in sales, 40 employees, a counter for welders and shops, a gas cylinder warehouse and a sales team on the road. The owner is 64.

The company has a 120-page procedures manual, written eight years ago for a certification project. Nobody uses it. At the counter, when a welder needs a part for an old welding machine, everyone turns to Gilles, who has 30 years of seniority.

The owner decides to start over. She lists the 20 tasks that cause the most mistakes or calls to Gilles: part returns, cylinder exchanges, special orders, warranties, receiving, cycle counts. Each task becomes a one-page procedure, written by the employee who does it best, then tested by a coworker.

Gilles sits for three recorded interviews on hard-to-find parts: which suppliers to call, which substitutes work, which customers have special needs. His answers become a reference sheet at the counter.

Six months later, the old manual is archived. The 20 procedures are posted or two clicks away. New hires learn faster, and Gilles takes his July vacation without daily phone calls.

A filled-in procedure to copy

Here's one of this fictional distributor's 20 procedures. Copy the shape, not the content.

Process a part return

• Purpose: credit the right customer and restock only what can be resold.
• Trigger: a customer comes to the counter or calls with a part to return.
• Owner / backup: Nadia (counter) / Marc (warehouse).
• Tools: management software, return form, "to inspect" labels.

Steps:

1. Find the original invoice in the software, by number or customer name.
2. Check the purchase date. Past the deadline: go to the checkpoint.
3. Inspect the part: original packaging, no sign of use.
4. Fill out the return form and have the customer sign it.
5. Issue the credit using the original payment method.
6. Label the part "to inspect" and put it on the returns shelf.
7. Notify the warehouse in the software before the end of the shift.

• Checkpoint: late return or part already used: the counter manager decides, not the owner.
• Special case: part special-ordered for this customer: follow the "Special orders" procedure.
• Common mistake: crediting the wrong account when a welding contractor buys for several job sites. Check the project number on the invoice.
• Review: March 2026, Nadia. Next: March 2027.

Notice what isn't there: no explanation of the return policy, no history. That lives elsewhere. The page is for the person with a customer in front of them.

This week, take the task that interrupts you most often. Have the person who does it write it up in this shape, then have someone else test it.

Five traps that kill a good procedure

Even with a sound method, these five come up often.

• Starting everything at once. Twenty procedures in progress, none finished. Work on three at a time, through to the test.
• Writing the ideal procedure instead of the real one. If the team works differently, the procedure gets ignored the next day. Write what actually happens, then improve it together.
• Forgetting the exceptions. The client who always pays late, the rush order on Friday afternoon: those are what get the boss called. A "special cases" line is often enough.
• Never reviewing. A wrong procedure is worse than none, because it destroys trust in all the others. Put the annual review on the calendar, like the inventory count.
• Keeping approval for yourself. If every procedure has to cross your desk before it's published, you rebuild the bottleneck you set out to remove. Hand approval to the department head.

What a buyer concludes

During due diligence, a buyer isn't looking for a handsome manual. They're looking for proof the business runs the same way no matter who's at the station. Short, current procedures that are visibly in use are the best proof there is.

They're also the raw material of your Transition Document: the "how it works" section a successor reads first. If you're starting from scratch, begin with our method to document business processes in a few weeks.

Do it with a pro

Alone, rewriting procedures takes months of evenings, and it's easy to rebuild the big manual you meant to avoid. With us and our regional partner, the interviews, recordings and formatting are handled for you, and your employees validate the result. See how it works.

Owner independence