Your First Operations Manual: What to Document First
Why this matters
Most shops never build an operations manual because they imagine a three-ring binder nobody reads. That is the wrong picture. A working manual is a living set of short documents that answer "how do we do this here" so the answer does not live only in your head. The payoff is concrete: faster onboarding, fewer repeated mistakes, and the ability to take a week off without your phone melting. The mistake is trying to document everything at once. You document the highest-pain, highest-frequency things first.
The wrong order (what owners usually do)
Owners tend to start documenting whatever they touched last, or whatever feels impressive, like a polished company mission. That is backwards. The mission does not stop the dispatcher from booking two jobs into one slot. Start where the bleeding is, not where the writing is fun.
How to find your first ten documents
Rank candidate processes by two factors and start at the top:
- Frequency: how often does this happen? Daily beats monthly.
- Cost of getting it wrong: what breaks when it is done badly? A blown safety step or a botched invoice beats a misfiled email.
Multiply the two in your head. A daily task that causes real damage when fumbled is document number one. A rare task that rarely matters waits.
The starter set most service shops need first
These show up at the top of the list for nearly every trade:
- Phone intake / how we book a call. The single most leveraged document in the shop. What we ask, what we promise, what we never promise, how we capture the address and the problem.
- Dispatch / how a job gets assigned and confirmed. Who decides, how the customer is confirmed, what gets staged.
- On-site arrival standard. How a tech shows up: appearance, greeting, walk-through, where they park, how they protect the property.
- Quoting / pricing a job in the field. How we price, what needs approval, how we present options.
- Closing a job / collecting and getting it invoiced same day. The step that protects cash flow.
- Callback / warranty handling. How we respond when a customer says it broke again.
- Safety basics for our work. The non-negotiables that keep someone out of the hospital.
- New-hire first week. What the first five days look like so onboarding is not improvised.
Keep each document short and usable
A good operations document fits on one page or one screen. Use a consistent skeleton:
- Purpose: one line on why this exists.
- When it applies: the trigger.
- Steps: numbered, in order, plain language.
- Watch out for: the two or three mistakes people actually make.
- Owner and last-updated date: who keeps it current.
If a document grows past two screens, it is probably two documents. Split it.
Capture it the fast way
Do not sit down to write essays. Capture the process while it happens:
- Record yourself or a top tech doing the task and narrating. Transcribe the key steps later.
- Have the person who does it best rough out the steps, then you edit for clarity.
- Write the first draft ugly. Version one exists to be corrected, not admired. Real use will reveal what is missing faster than any planning session.
Make it the source of truth, not a shelf decoration
A manual only works if people are pointed to it. Three habits make that happen:
- When someone asks "how do I do X," answer by sending the document, then fix the document if the answer was not clear.
- Review the trigger documents whenever a process changes, and stamp the new date.
- During onboarding, the manual is the curriculum, not an afterthought.
What to do this week
Pick your two most frequent, most damaging-when-wrong processes. Draft each on one page using the skeleton above. Use them on the next real job and fix what was unclear. You now have an operations manual. Add to it one document at a time.
References
- See related: Document a Process at the Right Level of Detail
- See related: Checklist vs SOP vs Training: A Decision Matrix
- SBA guidance on standard operating procedures for small business
- Trade-standard practice for service-business documentation