Almost every small business intends to write its procedures down properly one day. Almost none does, and the reason is the size of the task as it is usually imagined: a handbook, organised by department, complete, reviewed, and therefore never started.
Here is a version you can finish this week.
Start from the questions, not from a template
Do not start with a list of what a handbook ought to contain. You will write forty pages, most of it about situations that have never arisen in your business, and skip the three questions you are asked weekly.
Instead, spend twenty minutes writing down every question your staff have asked you more than once in the last month. That list is short, it is real, and it is already ordered by what is actually costing you time.
For most businesses it comes out looking something like this:
- What can I approve without asking? The single most asked question in any business with money moving through it.
- A customer is unhappy. What can I offer? The one where two members of staff giving different answers does real damage.
- Something is late or short. What now? Supplier problems, missing parts, short deliveries.
- How long should this take? The standard for your core process – a recon, a service, a turnaround, a callback.
- I am ill, or I need time off. Who do I tell, and when? Asked rarely by each person and constantly across the team.
Five pages. One question each. You can genuinely do this in an afternoon.
Write to the question, in their words
Make the heading the question people actually ask, phrased how they say it. Not “Expenditure Authorisation Policy” but “What can I approve without asking?”
It feels informal. It is also how somebody scanning on a phone finds their answer in four seconds, and it forces you to write an answer rather than a description of a policy area. A useful test: if a heading is not something a member of staff would say out loud, rewrite it until it is.
Put the number in the sentence
The most common failure in a written procedure is not vagueness about process. It is vagueness about figures.
“Managers may authorise reasonable amounts at their discretion.”
That reads like a policy and answers nothing, so the question gets asked out loud anyway and the document has failed. Compare:
“Up to $500 without asking. Above $500, ask a manager. Above $2,000, ask the owner.”
Write the figure. If it depends on something, write the figure and the condition. And if you are reluctant to write it down, that reluctance is worth examining – it usually means the rule has never actually been decided, and everybody has been guessing. Deciding it is the real work; writing it down takes thirty seconds.
One page per question
Shorter and more numerous beats longer and better organised. Put the answer in the first sentence, before any context. Add the exceptions underneath, not before. Keep each page to a screen or two on a phone – if it needs scrolling three times, it is two pages.
Then date it, so a reader can tell whether to trust it.
The hardest part: knowing what is missing
You do not know which questions your procedures fail to answer, because when a document fails, nobody reports it. They ask a colleague and get on with their day. The gap is invisible by nature.
There is a manual way to see it: for one month, write down every question you or your managers answer out loud, and check each one against your documents afterwards. It is tedious and it works.
The other way is to have whatever answers questions record the ones it could not. This is the part of our own product that owners most often say surprised them – Bosun records every question your procedures failed to answer, counts the repeats, and ranks them. “We should write things down properly one day” becomes a specific list, ordered by what is actually costing time. See answers from your procedures.
Either way, the list is the point. Writing procedures without knowing which ones are missing is how businesses end up with a handbook nobody needed.
The longer method, including how to keep them alive once written, is in writing procedures staff will use.