Take a week off. Not a working vacation with your laptop in the hotel room. A real one, phone off. Most owners know exactly what would break, and can name it in four seconds: the thing only they know how to do. The month end billing run. The one customer who only deals with them. Or something trivial, like which button to press when the payment terminal locks up.
That list is not proof you are indispensable. It is a list of undocumented procedures, and each one is a tax you pay forever: on hiring, on delegating, on being sick, and eventually on what your business is worth to a buyer. The reason most companies lack usable procedures is not laziness. They wrote them the wrong way once, watched nobody read them, and concluded the idea does not work.
Why the ones nobody reads fail
We have walked into businesses with a binder of procedures no employee had opened in three years. There are usually four reasons.
- They are too long. A fourteen page document covering a whole department is a policy, not a procedure. Nobody in the middle of a task reads fourteen pages. They ask the person next to them, which is what you were avoiding.
- They were written once, in a burst. Somebody spent a heroic weekend on it. Then the software changed and the steps stopped matching reality. One wrong step teaches everyone the whole document is unreliable.
- They live where nobody goes. The EPA’s guidance on preparing standard operating procedures is direct: current copies need to be readily accessible in the work areas of the people actually performing the activity, and otherwise SOPs serve little purpose.
- They were written by the wrong person. Usually the owner, from memory, describing the job as they believe it is done. The gaps show up when someone new tries to follow it.
The format that works
The definition in the EPA’s Guidance for Preparing Standard Operating Procedures, published as EPA QA/G-6 in March 2001, is plain: a set of written instructions that document a routine or repetitive activity followed by an organization. Written. Routine. Repetitive. No strategy, no philosophy, no explanation of why the department exists.
That same guidance sets the bar for detail, saying an SOP should contain enough detail that someone with limited experience or knowledge of the procedure, but with a basic understanding, can reproduce it unsupervised. That is the real test: could a competent person who has never done this get it right alone.
- One task per document. Not “accounts receivable.” Instead: “How to send the monthly statement run.”
- A one line purpose and a trigger. “Run on the first business day of the month” tells a new person more than a paragraph of context.
- Numbered steps, one action each. If a step contains the word “and” twice, it is two steps. Numbers let someone say “I am stuck on step seven.”
- Screenshots for anything on a screen. A picture of the actual button ends more confusion than three sentences describing where it is.
- The exceptions, at the end. What to do when the file will not upload, when the customer is on credit hold, when the total does not match. This is what makes a document survive reality.
- Who to ask when it goes wrong. A name, not a department.
Most good procedures run one to three pages. If yours runs longer, you are documenting a process, which is several procedures strung together. Write the procedures first.
Record yourself doing it, then edit
This is the tip that unblocks people. The obstacle is never the writing. It is starting from a blank page while trying to remember details of something you do on autopilot.
So do not start from a blank page. Next time the task comes up, start a screen recording and narrate as you go. Talk like you are training the person beside you, including the asides: “ignore this warning, it always does that.” Then get it transcribed, edit into numbered steps, and pull still images for screenshots. A task that would take ninety minutes from scratch takes about twenty this way.
There is a second reason it works, and the EPA guidance points at it: it recommends SOPs be written by individuals knowledgeable with the activity and the organization’s internal structure, meaning the people who do the work. Your bookkeeper documents billing. Your dispatcher documents scheduling. You edit. You do not author.
Where they live, and who keeps them alive
Storage sounds like the boring part and it is where the effort succeeds or fails. The rule: findable in under thirty seconds, from wherever the work happens.
- One home, searchable, on a company system. Not a personal drive. Somewhere search works and access survives an employee leaving.
- Reachable from a phone. Half your procedures get consulted by someone at a machine or in a truck.
- Named the way people talk. “How to set up a new customer” beats “AR Process Documentation v3 FINAL revised.”
- Version and date visible on the page. The EPA guidance recommends document control notation showing revision number and date, which lets a reader judge whether they are looking at something current.
- A named owner per document. Not “management.” One person whose job includes keeping that page true.
On staying current, the EPA guidance recommends SOPs be systematically reviewed on a periodic basis, giving every one to two years as an example, and that whenever procedures change the SOPs be updated and re approved. We would add a second trigger: when someone finds a wrong step, fixing it is part of the task, not a project to raise at a meeting. Documents anyone can correct stay alive. NIST’s small business guidance adds training, recommending you train employees immediately when hired and at least annually after that.
What this buys you: hiring, delegating, and one day selling
The EPA guidance describes SOPs as minimizing variation and promoting quality through consistent implementation, and lists benefits including reduced work effort along with improved comparability, credibility, and legal defensibility. That was written for laboratories. In an owner’s terms, four things.
- Onboarding stops eating your week. New hires get productive on their own instead of shadowing someone for a month.
- Delegation becomes real. Most owners do not fail to delegate because they are controlling. They fail because handing off an undocumented task takes longer than doing it. A written procedure changes that arithmetic.
- Quality stops depending on who is working. The customer gets the same result on a Tuesday when your best person is out.
- The business becomes sellable. A buyer is not purchasing your equipment. They are buying the ability to keep the revenue after you leave, and a company that lives only in the owner’s head is worth less.
The bottom line
Do not launch an SOP initiative. Those fail. Instead, pick the task that would cause the most trouble if you disappeared tomorrow, record yourself doing it this week, and turn the recording into two pages of numbered steps with pictures. Put it where people work, with a name and a date on it. Then do one more next month. Twelve procedures a year, written by the people who do the work, beats a binder nobody opens. Same principle as our article on why saving time takes priority over saving money.
Harrison Ward Technology works with small and mid sized businesses across Denton County on exactly this kind of unglamorous groundwork. We set up a place for procedures to live where they are searchable, current, and reachable from a phone. We document the technology procedures ourselves, from onboarding a new employee to what happens when the internet goes down. Our article on what to look for in an IT partner covers what else that relationship should include. Contact us today
Sources:
Comments are closed