All articles
Business Analysis
5
min read
How to write an SOP from your process model

Thom Uffing
Process Innovation

A standard operating procedure (SOP) describes how a role carries out a process, step by step. If you already have a process model, most of the SOP is in it: the lanes give the roles, the tasks give the steps, the gateways give the decision rules and the data objects give the inputs and outputs. What remains is the practical detail of how each step is done, which you add with the people who do the work.
The request after validation
The process model has been through two validation rounds and the client agrees with it. Then the team lead asks: "Can we also get work instructions for the new people starting in January?"
In many projects, those instructions are then written separately in Word. They start from the same process, but they are maintained in a different place. After the next change to the model, the two no longer match, and nobody is sure which one describes the current way of working.
Deriving the SOP from the model keeps both on the same basis.
SOP, work instruction and process model
The terms are used differently between organizations, but a common distinction is:
Process model: what happens across roles, in which order and with which decisions. Usually in BPMN 2.0.
SOP (standard operating procedure): how a process or part of it is carried out, usually written for one role or one team.
Work instruction: the detailed how-to for a single task, sometimes with screenshots or field-by-field instructions.
This post uses SOP for the procedure per role. The same approach works for a work instruction at task level.
What an SOP usually contains
Purpose and scope: which process, where it starts and where it ends. If you made a SIPOC at the start, the scope is already written down.
Role: who carries out the procedure.
Trigger: what starts it, such as a request that comes in or a date that is reached.
Steps: numbered, in order, each starting with a verb.
Decision rules: what to do in each situation, with the condition stated.
Inputs, outputs and systems: which documents, data and applications each step uses or produces.
Exceptions: what to do when something deviates from the normal path.
Owner and version: who maintains the SOP and which version of the model it is based on.
From process model to SOP
Choose the unit. One SOP per lane (role) is a common choice, because a reader usually only needs their own part. For a short process, one SOP for the whole process can be enough.
Turn the tasks in that lane into numbered steps. Keep the task names from the model, so the SOP and the model use the same words.
Write out each gateway as a rule. An exclusive gateway with the conditions "amount below 500 euros" and "500 euros or more" becomes: "If the amount is below 500 euros, continue with step 5. Otherwise, send the request to the team lead for approval."
Add inputs, outputs and systems from the data objects and annotations. If the model does not contain them, note them as questions.
Mark the hand-offs. Where the flow moves to another lane, state who takes over and what they receive. The RACI matrix for the same process shows who is responsible and who is informed at that point.
Add the practical detail with the people who do the work. Screens, field names, thresholds and tips are usually not in a process model. A short process interview or a walkthrough at the workplace is a common way to collect them.
Validate and set a version. Have someone who does the work follow the SOP once, and record which version of the model it is based on.
An example: registering a refund request
For the customer service role in a refund process, the SOP derived from the model could look like this:
Trigger: a customer submits a refund request through the web form or by email.
Step 1, register the request: create a case in the customer system with the order number and the reason for the refund.
Step 2, check the order: confirm that the order exists and falls within the return period. If it does not, inform the customer and close the case.
Step 3, request the returned item: send the customer the return instructions and set the case to "awaiting return".
Hand-off: when the warehouse confirms receipt, finance takes over the payout.
Step 4, confirm to the customer: after finance reports the payment, send the confirmation and close the case.
Each step corresponds to a task in the customer service lane, and the condition in step 2 comes from the gateway after "Check order". If the model changes, for example because the return period check moves to the warehouse, the SOP changes with it.
Common pitfalls
Steps that are not in the model. If the SOP needs a step the model does not have, either the model is incomplete or the SOP describes a different process. Both are worth checking.
Decisions without conditions. "Check the request" without saying what to check and what to do with the outcome leaves the reader to guess.
No owner or version. Without them, it is hard to tell later whether an SOP still matches the current model.
Too much detail for the reader. An experienced team often needs a checklist, while a new employee needs the full instruction. It can help to ask who the SOP is for before writing it.
When you can skip it
For a small team that runs a stable, simple process every day, the process model plus a short checklist is often enough. A full SOP is most useful when new people join regularly, when the process is audited or when tasks move between teams or locations.
How ModelMatic does it
In ModelMatic the SOP is generated from the validated process model, together with the RACI matrix and the requirements. The model itself comes from your stakeholder interviews and documents, and every step points back to its source. When a validation round changes the model, you generate the SOP again from the new version instead of updating a separate document.
At one consultancy, working out a process went from about 8 hours to about 1 hour.
See all documentation outputs on the features page, or book a demo to see an SOP generated from an example interview.




