VamimiOpen VamimiAI

Process mapping

SOP Flowchart: How to Turn a Procedure into a Flowchart

How to turn a standard operating procedure into an SOP flowchart, when a flowchart beats written steps, and how to keep the two in step.

By VamimiAI team · · 5 min read

An SOP flowchart is a standard operating procedure drawn as a diagram: each instruction becomes a step, each "if" becomes a decision with a line for every answer, and each way the procedure can finish becomes an end. To make one, mark the actions and the conditions in the written SOP, draw them in order, and check that every decision has all of its exits.

A flowchart does not replace the written procedure. It sits at the top of it and tells the reader where they are.

When an SOP needs a flowchart

Written steps work well for a procedure that runs in a straight line: do this, then this, then this. They work badly as soon as the procedure branches. A reader in the middle of step 7 who meets "if the reading is out of range, see section 4.2, unless the unit was serviced this month" has to hold the whole document in their head.

Draw a flowchart when the SOP has:

  • Decisions. Two or more places where the next step depends on a result.
  • Hand-offs. Work that passes between people, shifts or departments.
  • Loops. Steps that repeat until something passes.
  • Exceptions. A "what to do if it goes wrong" section that is longer than the main steps.

A five-step procedure with no conditions does not need one. A numbered list is clearer.

Step 1: Mark the actions and the conditions

Read the SOP with two highlighters. With the first, mark every action: a verb that someone carries out ("weigh the sample", "record the result", "notify the supervisor"). With the second, mark every condition: any sentence with "if", "unless", "when", "in case of", "otherwise" or "until".

The actions become the steps of the flowchart. The conditions become its decisions.

Step 2: Rewrite each condition as a question

A decision in a flowchart is a question with short answers. Turn "if the temperature exceeds 8 °C, discard the batch" into "Temperature above 8 °C?" with two lines: "Yes" to "Discard the batch", "No" to the next step.

Now look for the answer the SOP does not mention. Procedures are usually written by someone describing what to do when a check fails, or when it passes, but not both. Every missing answer is a gap in the procedure itself, and finding those gaps is the most useful thing the flowchart does.

Step 3: Draw the main path, then the branches

Put the steps of a normal, successful run in a straight line from the start to the end. Then add each branch to the side. This keeps the common case easy to follow and the exceptions easy to find.

If more than one role is involved, use a swimlane diagram: one lane for each role, each step in the lane of the person who does it. An operator should be able to read down their own lane.

Use the SOP's own step numbers in the labels ("4. Record the result") so that the reader can move between the diagram and the text.

Step 4: Give every path an end

Follow each line with your finger. Every path must reach an end: the procedure is complete, the batch is rejected, the supervisor takes over. A path that stops at a step with no line out of it is a place where someone will have to guess.

Mark the ends that mean a failure or a hand-over differently from the end that means success, so the outcome of each path is clear at a glance.

Making the flowchart from the document

If the SOP exists as a file, you do not have to redraw it by hand. VamimiAI's document to flowchart page describes how it works: attach the SOP as a PDF, Word, Excel, CSV or text file, ask for the flowchart, and the steps and decisions in the document are drawn in order. Logic checks then point at a decision with only one exit, a step that leads nowhere and a step nothing reaches.

Whichever way you draw it, read the result against the document once, line by line. The flowchart is a second view of the procedure, and both must say the same thing.

Keep the SOP and the flowchart in step

A flowchart that disagrees with the text is worse than no flowchart, because people follow the picture.

  • Give both the same version number and date, and change them together.
  • Put the flowchart on the first page of the SOP, not in an appendix.
  • When the procedure changes, change the flowchart first. It shows at once whether the change leaves a path without an end.
  • Keep the editable diagram, not only an image, so the next change takes minutes.

For the method behind all of this, see the process mapping guide.

Questions

What is an SOP flowchart?

An SOP flowchart is a diagram of a standard operating procedure. It shows the procedure's steps in order, its decisions with a line for each answer, and how the procedure ends, so that a reader can see the whole procedure on one page.

Does a flowchart replace the written SOP?

No. The flowchart gives the overview and the route; the written steps give the detail of how to carry out each one. Use the same step numbers in both.

What symbols does an SOP flowchart use?

A rounded shape for the start and the ends, a rectangle for a step, a diamond for a decision and arrows for the order. Label every line that leaves a decision with its answer.

How long should an SOP flowchart be?

One page. If it does not fit, the SOP probably covers more than one procedure. Split it, and let a single box in the main flowchart stand for each sub-procedure.

Can I make a flowchart from a PDF of our SOP?

Yes. In VamimiAI, attach the PDF and ask for the flowchart of the procedure it describes. Then check the result against the document.

Tools for this