How to create a visual SOP
How to build a visual SOP: the diagram carries sequence, owners, decisions and handoffs, the text carries tolerances, criteria, warnings and records, and one approved version carries the training.
A visual SOP is a procedure whose primary representation is the diagram, with the written detail (tolerances, acceptance criteria, settings and records) attached to the individual steps that need it.
The short version
- Sequence, ownership and decisions go on the diagram; what a box cannot hold legibly goes in the text.
- Tolerances, settings and warnings sit on the step, not inside its label.
- A label longer than about a dozen words has taken over the text's job.
- Ownership drawn as a lane makes a handoff visible instead of merely described.
- Training is recorded against the approved version, not against the procedure in general.
Choosing documentation tools
What the boxes hold and what they cannot
A visual SOP is not a written procedure with a diagram added to the front of it. That version produces two documents describing one process, and the drawing is the one updated last. A visual SOP inverts the relationship: the diagram is the procedure, and the words survive as detail hanging off individual steps. Nobody reads a two-page narrative while holding an instrument they have been told to withdraw from service.
The diagram carries sequence, ownership, decisions and handoffs: the four things prose is worst at. The text carries what a box cannot hold at the size a box is read: tolerances, acceptance criteria, settings, warnings, and the record to be completed. Settle that division once and in writing rather than arguing it step by step. Push the criteria into the labels and the result is a wall of small print; leave them out altogether and it is a picture rather than a procedure.
The example below is an equipment calibration procedure across five owners. Most of it exists for one exit: "As-found reading within tolerance?" leaving on "Out of tolerance". Watch the recall loop as well, where "Needed on a live job" reaches "Authorise a dated calibration extension" and comes straight back to the same question, which is how an overdue instrument stays legal without anyone pretending it was calibrated.
The same procedure, with the words on the steps
Follow one instrument through the whole procedure, and watch a single out-of-tolerance reading open the entire Impact assessment phase behind it.
The diagram carries sequence
A due date, a recall notice, then "Instrument available for recall?", whose "Needed on a live job" exit buys "Authorise a dated calibration extension". The diagram owns the fact that the route exists; how long an extension may run, and who may sign one, are detail on that row.
Criteria belong beside the box
Booking in, then "Calibrate in-house or externally?" splitting to "In-house" and "Accredited laboratory". "Compare as-found against the standard" is one instruction in the label; the number of points across the range and the settling time are what you would put in that row's comment.
One exit does all the work
The gate the procedure exists for is "As-found reading within tolerance?". "Out of tolerance" raises a report and opens "Assess measurements since the last pass", after which "Is released product affected?" sends "Already shipped" to the recall process and "Still on site" to a re-inspection.
Every route reaches a record
Repair and retirement are separated by "Can it be adjusted into tolerance?": "Beyond adjustment" ends at "Instrument retired and replaced", while an adjustable instrument is re-verified. Both surviving routes then pass through the as-left reading, the certificate and the new label.
The procedure edits its own schedule
"Does drift history justify a change?" rewrites the procedure's own interval: "Shorten or extend" reaches "Reset the interval and re-label", three rows after the instrument went back to service, the one step reaching an instrument already in use, before "In service and in calibration".
How it works
Decide what the diagram is answerable for
Write the split down before starting: the chart owns sequence, owner, decision and handoff, and the text owns tolerance, criterion, setting, warning and record. Every sentence of the existing procedure then has a destination, and the argument about what to include stops being an argument about taste.
Cut every step back to one instruction
Compare the reading against the standard at five points across the range, allowing the instrument to settle first: that is one step and two pieces of detail. Keep the verb and its object in the label; the five points and the settling time go in the step's comment. A label somebody reads while working stays under a dozen words.
Type the steps in and shape the questions
Each row's Box text is a box. Any row that asks something gets Decision in its Shape column; the Line to column takes the row numbers a step leads to, and Line text carries the wording of each arrow in that same order. A tolerance decision wants the answer states ("Within tolerance", "Out of tolerance") rather than yes and no.
Attach the detail to the step it governs
Put the acceptance rule on the decision it decides rather than in a preamble: whether the reference uncertainty is subtracted before the call is made, how many points are checked, and who rules on a reading that sits on the line. Detail filed against a step is detail somebody reads at the moment it applies.
Put the owner of every step in a lane
The role that performs a step goes in its Vertical lane column and the phase in the Horizontal lane column, both plain text on the row, so ownership is data rather than a position. Filled in, the five rows from "Raise an out-of-tolerance report" onwards form one "Quality manager" band: the procedure has left the technician's hands entirely.
Run one real job from the chart alone
Hand the chart to a technician who has not run the procedure and watch them do one real calibration from it, without answering questions. Each question they have to ask names detail sitting in the wrong layer; each step taken out of the order drawn is a route to correct. The version that survives that run is the one to approve.
Mistakes to avoid
Small print inside the boxes
Once a label carries the tolerance, the settings and the warning, the diagram is a paragraph in a rectangle and the sequence has stopped being legible. The detail was not wrong: it was in the wrong layer.
Bolting the diagram onto the text
Keeping the narrative as the master and the chart as an illustration guarantees the two diverge, and the illustration is what loses. A diagram that is not the controlled document is decoration with a revision number on it.
No record named on the flow
A procedure that says what to do and never says what to write down produces work with no evidence behind it. Name the record on the step that creates it: the certificate, the out-of-tolerance report, the register entry.
Training against an unnamed version
A training record naming the SOP but not its version cannot show who was trained on the current one. Approve a version, train against that version, and re-train on the changes that alter what someone does.
Build your own visual SOP
Open the calibration example as your own chart, then move your own tolerances and acceptance criteria onto the steps that decide them.
Related guides
Frequently asked questions
What makes an SOP visual rather than illustrated?
Which is the master, the diagram or the text. In a visual SOP the diagram is the controlled document and the written detail hangs off individual steps; in an illustrated SOP the text is the procedure and the picture summarises it. The test is what happens when the process changes. If the edit is made to the diagram and the detail follows from it, the SOP is visual. If two documents both have to be edited, one of them is already out of date and there is no way to tell which.
How much text should a visual SOP still contain?
As much as the work needs, held per step rather than as a narrative. One step may carry a paragraph (the points across the range, the settling time, the uncertainty rule) while the three after it carry nothing at all. What should not exist is a continuous prose version running alongside the diagram, because it duplicates the sequence, and duplicated sequence is what drifts. Detail attached to a step cannot contradict the flow; a parallel narrative can, and eventually does.
Where do tolerances and acceptance criteria go?
On the decision they decide. "As-found reading within tolerance?" is only repeatable if the rule travels with it: which points were checked, whether the reference uncertainty is subtracted before the call, and who rules on a reading sitting on the limit. Filed in a specification chapter instead, the criterion is three clicks away at the moment it is needed, and the generous pass quietly becomes the local standard.
Is a visual SOP acceptable to an auditor?
Auditors are indifferent to format and specific about control. What gets asked is whether one authoritative version exists, who approved it and when, what changed since the previous revision, whether the people doing the work were trained on the version in force, and whether the records the procedure calls for were produced. A diagram answers all five as readily as prose, and it shows the branching an auditor would otherwise reconstruct from sentences.
