Written procedures are widely recommended and widely ignored in small businesses, and the ignoring is often correct for a while. What changes is the number of handovers inside the work.
Shared memory works while everyone sees everything
In a firm where a few people work in the same space, coordination happens by overhearing. Nobody needs a document to know that an order changed, because they heard it change.
Writing procedures at that size costs real time and replaces a system that is functioning. The documents get created, then diverge from practice, then get ignored.
This is why process advice aimed at larger companies often produces nothing in a small one. The problem it solves has not appeared yet.
Handovers, not headcount, are the trigger
The moment work regularly passes between people who were not present for the earlier steps, information has to travel in some explicit form.
That can happen at eight people or at three, depending on whether the work is done in one place, across shifts, or by staff who are out with customers all day.
The symptom is repeated clarification questions and rework caused by something that was known but not passed on. That is the point where writing it down starts to save more time than it costs.
The useful artefact is smaller than a manual
Most firms do not need a procedures manual. They need the four or five sequences that break most often written in a form someone can follow while doing the job.
Checklists, standard quote templates and a defined order of operations for the common jobs carry most of the benefit at a fraction of the effort.
Documents that describe the ideal version of the work rather than the actual version get abandoned quickly, because the first person who follows them finds they do not match reality.
Processes decay unless someone owns them
Written procedures age as suppliers, tools and customer requirements change, and a stale procedure is worse than none because it is confidently wrong.
Firms that keep them alive usually attach updating to an existing event, such as reviewing the process whenever the job it describes goes wrong.
That makes maintenance a response to a real failure rather than a scheduled task nobody has time for, which is the form small businesses can sustain.
The clearest return shows up in training
The most visible benefit arrives when someone new joins, because every hour an experienced member of staff spends explaining is an hour not spent producing.
A firm with written sequences moves a new starter to useful output sooner and with fewer errors, and the people who already know the job are interrupted less often.
That return only materialises where the documents describe the current way of working, which is why maintenance rather than authorship is the part that decides whether the effort pays.