Process Documentation: How to Document a Process Your Team Will Follow

Every team has processes that live only in someone's head, like how a refund gets approved or how a new hire gets set up. They work until that person goes on vacation, changes roles, or leaves.
Process documentation gets that knowledge out of people's heads and onto a page others can use. This guide explains what it is, how it relates to SOPs and work instructions, and how to document a process in seven steps. A template you can copy is included.
What is process documentation?
Process documentation is a written description of how a recurring piece of work gets done from start to finish. It covers what triggers the work, who is involved, what goes in and comes out, the order of the steps, and how to tell it was done right. It's the shared reference a team works from.
In business process documentation, a good document answers the questions a new team member would ask: Where does this start? Who does what? What do I need before I begin? What does "done" look like?
Process documentation vs. SOPs vs. work instructions
These terms overlap. It helps to think of them as levels of detail:
| Level | Answers | Example |
|---|---|---|
| Process document | What happens, in what order, and who is involved, end to end | Customer refund process, from request to closed ticket |
| SOP | The required, controlled way to carry out the process | Refund SOP with approval limits and records to keep |
| Work instruction | Exactly how to do one task inside it | How to issue a refund in the billing system |
The process document gives you the overall flow. The SOP sets the rules, and work instructions cover individual tasks. Small teams often combine the first two into one page, and that's fine as long as the flow is clear.
Why process documentation matters
The U.S. Environmental Protection Agency's guidance on standard operating procedures (EPA QA/G-6) sums up the benefits well. Documented procedures minimize variation and keep work consistent even through temporary or permanent staff changes. They also double as training material, and inspectors often use them as checklists during audits.
In practice, that means fewer "how do we do this again?" interruptions for your most experienced people, faster onboarding, and easier audits. It also gives you something concrete to improve: lean practitioners treat standardized work as the baseline for continuous improvement.
The timing also matters for quality teams. ISO published ISO 9001:2026 on 16 September 2026, and certificates issued against the 2015 edition stop being valid after 30 September 2029, according to certification body DNV. The new edition reinforces the requirements for managing changes to the quality management system. If you're certified, the transition is a natural moment to review your process documents.
How to document a process in 7 steps
1. Pick one process and set its boundaries
Start with a process that's frequent, error-prone, or known by only one person. Write down the trigger (what starts it) and the end point (what "done" means). "Customer submits a refund request" to "refund issued and ticket closed" is a clear scope. "Customer support" is not.
2. Bring in the people who do the work
The EPA guidance recommends that procedures be written by people who know the activity and actually perform it. For processes that span several roles, it suggests a team approach, which also builds buy-in from the people who'll use the document. An hour with two or three practitioners beats a week of guessing.
3. Sketch the big picture with a SIPOC
Before you write the steps, capture the process at a high level with a SIPOC: Suppliers, Inputs, Process, Outputs, Customers. The U.S. Agency for Healthcare Research and Quality describes it as a high-level flowchart, useful when inputs, suppliers, outputs, or end users aren't clearly identified.
For a refund process, that might look like this:
- Suppliers: customer, support agent, finance
- Inputs: refund request, order record, refund policy
- Process: review, approve, issue, notify
- Outputs: refund payment, customer confirmation, updated ticket
- Customers: the customer, finance (for reconciliation)
4. Map the flow
Turn the "Process" column into a simple flowchart showing each step, decision point, and handoff between roles. Swimlanes, where each role gets its own row, make handoffs easy to see. The EPA guidance recommends a flowchart alongside the written steps because it breaks up long text and summarizes the sequence at a glance.

5. Write the steps
Now write the steps in order. The first three rules come from the EPA guidance:
- Be concise and step-by-step. One action per step.
- Use the active voice and present tense. "Finance approves refunds over $500," not "Refunds over $500 should be approved."
- Write for a capable newcomer. Include enough detail that someone with basic knowledge could follow the process unsupervised.
- Name the role, not the person. "Support lead," not "Maria," so the document survives a reorganization.
- Link out instead of repeating. If a step needs detailed tool instructions, link to the work instruction.
6. Test it, then get it approved
Hand the draft to someone who didn't write it and ask them to follow it. The EPA calls out testing by people other than the original writer as especially helpful. Every point where they hesitate or ask a question shows you what's missing. Fix those gaps, then route the document for review and approval by the process owner and, where relevant, your quality or compliance lead.
7. Publish it where the work happens
The EPA guidance also says that procedures serve little purpose unless current copies are readily accessible where the work is done. A shared drive folder with five versions named "final" doesn't count. Publish one current version in a place people already look, and make it searchable and readable on a phone.
Process documentation template
Copy this structure for each process. Leave out what you don't need, but keep the control fields at the top. They're what make the document trustworthy.
Process name: Customer refund
Process ID / version: FIN-007 · v1.2
Owner: Support operations lead
Last reviewed / next review: (date) / (date)
Purpose: Why this process exists, in one or two sentences.
Scope: Trigger → end point. What's in and what's out.
Roles: Who does what (support agent, support lead, finance).
SIPOC summary: Suppliers, inputs, outputs, customers.
Flowchart: The visual map from step 4.
Steps: Numbered, one action each, with the responsible role.
Records and checklists: What gets saved, and where.
Related documents: Policies, SOPs, and work instructions this links to.
Change history: What changed, when, and who approved it.
The control fields reflect what the EPA recommends for every procedure: a clear title, an ID, a revision number and date, and approval signatures. For a deeper look at numbering and versioning, see our guide to document control.
Process documentation examples
The same template works across very different teams:
- Employee onboarding (HR and IT): The trigger is a signed offer and the end point is the new hire's first productive week. Roles include HR, IT, and the hiring manager. The flowchart shows account setup running in parallel with paperwork.
- Purchase approval (finance): The trigger is a purchase request. Decision points branch by amount, and the records section lists the approved request and the invoice.
- Machine changeover (manufacturing): The process document shows the sequence and the handoffs between operators and quality. Each step links to a work instruction with the exact settings.
Process documentation best practices for keeping it current
A process document is only useful while it matches reality. The EPA recommends updating a procedure whenever the process changes and reviewing all procedures on a regular schedule, for example every one to two years. If a procedure describes something no one does anymore, withdraw and archive it.
A few habits help:
- Give every process an owner who is accountable for keeping it accurate.
- Put the review date on the page, so readers can see how fresh it is.
- Make feedback easy. The people following the process spot drift first.
- Keep old versions archived, not deleted, so you can show what was in force at any point.
How Sonat helps
Sonat is built for exactly this kind of documentation. Teams draft in the editor or in Google Docs, send each change through review and approval workflows, and publish one current version with full version history behind it. Readers can open it on any device and leave feedback right on the page. Sensitive processes can stay private to your team. See how it works for policies and procedures.
Conclusion
Good process documentation doesn't need to be long. It needs a clear scope, input from the people who do the work, a simple map, steps a newcomer can follow, and an owner who keeps it current. Start with one process this week, test it on a colleague, and publish it where your team will find it.