How to Document Business Processes: Simple SOP Template

This guide shows what to capture, gives you a ready-to-use SOP template and explains how to keep documentation alive.

Why documenting processes pays off

Process documentation is often seen as bureaucracy. For a small business, it solves very practical problems:

• Holidays and sick days: someone else can step in without guessing.
• Onboarding: new colleagues learn faster and ask fewer repetitive questions.
• Consistency: customers get the same quality regardless of who handles their request.
• Improvement: you can only simplify what you can see.
• Automation: a documented process is the blueprint for any automation. Without it, automations are built on assumptions.

Which processes to document first

You do not need to document everything. Prioritise:

1. Processes that customers notice directly: enquiry handling, quoting, order processing, invoicing, support.
2. Processes that only one person knows.
3. Processes where errors are expensive.
4. Processes you plan to automate or change.

A list of 10–20 core processes is a realistic start for most SMEs.

What to capture for each process

Element	Question it answers	Example
Name and purpose	What is this process for?	"Handle new web enquiries so every prospect gets an answer within one business day"
Trigger	What starts it?	A web form submission or a phone enquiry
Roles	Who is involved?	Office manager, salesperson
Inputs	What is needed?	Contact details, request type, preferred callback time
Steps	What happens, in which order?	Numbered list
Tools	Which systems are used?	CRM, email, calendar
Decisions and exceptions	What varies?	If the request is outside our service area, send the standard referral email
Output	What is the result?	Qualified lead in CRM with next step scheduled
Quality check	How do we know it was done right?	Every new enquiry has an owner and a next-step date
Owner and review date	Who maintains this document and when is it checked?	Office manager, every six months

A simple SOP template

Copy this structure into your shared documentation tool:

SOP: [Process name]

**Purpose:** [One sentence: why this process exists]
**Owner:** [Name / role]   **Last reviewed:** [Date]   **Next review:** [Date]
**Trigger:** [What starts the process]
**Result:** [What is true when the process is complete]

## Roles
- [Role A]: [responsibility]
- [Role B]: [responsibility]

## Steps
1. [Role] – [Action] in [Tool]. ([Time target, if any])
2. [Role] – [Action]. If [condition], go to step 5.
3. ...

## Exceptions
- [Situation]: [What to do]
- [Situation]: [What to do]

## Quality check
- [How to verify the process was done correctly]

## Related documents and tools
- [Links to templates, checklists, system instructions]

In your documentation tool, make the first line the page title. Keep the template short; long SOPs tend not to be read.

Example: handling a new web enquiry (hypothetical)

Purpose: every web enquiry gets a personal answer within one business day. Trigger: contact form submission. Result: enquiry recorded in the CRM with an owner and a next step.

Steps:

1. Office manager checks the shared inbox for new form submissions twice a day (9 am and 2 pm).
2. Office manager creates or updates the contact in the CRM and selects the request type.
3. If the request is outside the service area, the office manager sends the referral template and closes the enquiry.
4. Otherwise, the office manager assigns the enquiry to the salesperson responsible for the region.
5. The salesperson calls or emails the prospect within one business day and logs the result in the CRM.
6. The salesperson sets the next step (quote, site visit, follow-up date).

Exceptions: spam is deleted without a CRM entry; existing customers are forwarded to customer service.

Quality check: weekly, the office manager checks that all enquiries from the past week have an owner and a next-step date.

Steps 1, 2 and 4 are typical candidates for automation. Our article on business processes to automate explains how to evaluate such candidates, and the process automation ROI calculator estimates the time and money an automation would save.

Swimlanes: when several roles are involved

A swimlane diagram shows a process as a flow chart divided into horizontal or vertical lanes, one per role or department. It makes handovers visible, which is where delays and errors often occur.

Use swimlanes when:

• Three or more roles are involved.
• Work moves back and forth between people or departments.
• You want to discuss improvements with the team.

You can draw them on a whiteboard, with sticky notes or in any diagram tool. Keep the written SOP as the main reference and use the diagram as an overview.

RACI: clarifying responsibilities

For processes where responsibilities are unclear, a RACI table helps. For each step, it lists who is:

• R – Responsible: does the work.
• A – Accountable: makes the final decision and answers for the result (only one person).
• C – Consulted: gives input before or during the step.
• I – Informed: is told about the result.

Step	Office manager	Salesperson	Managing director
Record enquiry	R/A	I	–
Qualify and contact	I	R/A	–
Approve special discount	–	R	A
Weekly quality check	R/A	C	I

In small teams, a full RACI is not necessary for every process. Use it for the steps where people regularly ask "Who decides this?"

Keeping documentation current

Outdated documentation is worse than none, because people stop trusting it. Simple rules:

1. One owner per process. The owner updates the document when the process changes.
2. Review dates. Put the next review date in the document and in a calendar.
3. Change at the source. When someone finds an error, they report it immediately or fix it directly.
4. One central place. All SOPs live in one shared location with a clear structure, not in personal folders.
5. Link from the tools. Where possible, link the SOP from the place where the work happens, for example in the CRM or the team chat.

Common mistakes

Writing for auditors instead of colleagues. Documentation should help people do the work.

Too much detail. Describing every click makes documents long and fragile when software changes. Focus on steps, decisions and checks.

Documenting the ideal instead of reality. Capture how the process actually works first, then improve it.

No owner. Without an owner, documents decay.

Hidden storage. If people cannot find the SOP in seconds, they will ask a colleague instead.

How documentation fits into digital transformation

Documented processes are the foundation for every improvement step: simplifying, automating and choosing new systems. In our digital transformation roadmap for SMEs, documentation is part of the first phase, because it makes the current state visible and gives you a baseline to measure progress against.

Summary

Knowing how to document business processes is less about methods and more about habit. Capture purpose, trigger, steps, roles, tools, exceptions, result and owner for your 10–20 core processes, using a short SOP template. Add swimlanes where several roles hand work over and a RACI table where responsibilities are unclear. Store everything in one place, review it regularly and let the people who do the work keep it accurate. The result is a business that runs more consistently and is ready for automation.