Process mapping
How to turn a written procedure (SOP) into a flowchart
To turn an SOP into a flowchart, extract the trigger and outcome, rewrite each instruction as one step with an owner, turn every "if" into a decision with labelled branches, and add the exceptions the document leaves implicit. Then check the chart against a real case.
Why convert an SOP
Written procedures are precise but hard to scan. A reader has to hold every condition in mind to know which paragraph applies. A flowchart shows the same logic as paths, so the reader only follows the branch that matches the situation. The two are complementary: the chart for orientation, the text for detail.
Step 1: find the boundaries
Identify what triggers the procedure ("a supplier invoice arrives") and every way it can end ("invoice paid", "invoice rejected", "escalated"). These become the start and end shapes.
Step 2: extract one step per instruction
Go through the document line by line. For each instruction, write a short step label (verb + object) and note who performs it. SOPs often use the passive voice ("the invoice is checked"); ask who checks it, because that is the lane it goes in.
Step 3: turn conditions into decisions
Every "if", "unless", "when" or "in case of" is a decision. Rewrite it as a question with explicit answers: "Is the amount above €10,000?" → Yes / No. Follow the rules in decisions and loops, especially for retries and waiting times.
Step 4: add what the SOP leaves out
Procedures describe the normal case well and the exceptions poorly. Ask:
- What happens if the information is incomplete?
- What if nobody answers?
- Who decides when the rule does not fit?
Missing answers are findings in their own right, worth reporting to the process owner.
Step 5: lay out and review
Organise the steps in swimlanes, one per role. Then walk through a real case with someone who applies the procedure. Differences between the chart and practice usually mean the SOP itself needs updating.
Using AI for the first draft
An SOP is already a text description of a process, which makes it a good input for an AI flowchart generator. Paste the relevant section into Flowchartio, check that every role and condition appears in the result, then refine it in conversation ("Add an escalation to the finance manager after 5 days"). The guide on describing a process for AI explains how to clean up the text first, for example by removing references to other documents.
Which one is the reference?
Decide explicitly. In regulated environments the written SOP usually remains the reference and the chart is an illustration. In smaller teams, a well-maintained flowchart can become the main document, with text only for details. Either way, update both together, and store the chart in the same place as the procedure. Text-based charts in Mermaid fit well in wikis.
Turn your process into a flowchart
Describe it in a few sentences. Flowchartio draws the flowchart, then you refine it in conversation.
Generate a flowchart