Define the start and end first
State when the process begins and what condition means it is finished. A clear boundary prevents unrelated work from entering the diagram.
Use separate end nodes for outcomes such as completed and rejected.
Write one action per process node
Use short verb-based labels such as ‘Review request’ and ‘Save approval.’ Combining review and save hides where a failure happens.
When the chart becomes too detailed, split a subprocess into its own diagram and keep only the major step above.
- Start: entry point
- Process: one action
- Decision: a branching question
- End: an outcome
Make decisions answerable with yes or no
A question such as ‘Is the information complete?’ creates two clear paths. Assign the next node for both yes and no.
Loops can return a revision to review, but confirm that the process still has a reachable exit condition.
Choose direction and export format
Vertical layout often suits long approval processes, while horizontal layout can work for short presentation diagrams. Reorder nodes to reduce crossed lines.
PNG is convenient for documents and chat; SVG stays sharp for editing and print. Inspect every connection after export.