How to create a process flowchart in 5 steps
To create a process flowchart, list every step of the process on its own line, mark the start, end and any yes/no decisions, then paste the list into a tool that turns text into a chart. The whole thing takes about fifteen minutes and needs no drawing skills.
Before you start: a short checklist
Five minutes of preparation saves an hour of rework. Before you write the first step, confirm:
- The process has one clear trigger. If you cannot name the single event that starts it, you are probably charting two processes at once.
- The process has one clear owner. Somebody must be accountable for the outcome, even if many people contribute.
- You know the scope. Decide up front what is in and out. "Refund request to refund paid" is a scope; "customer service" is not.
- You have talked to at least one person who runs the process. Charting from memory is where fictional workflows come from.
- You have picked an audience. A chart for auditors looks different from a chart for new hires — pick one and write for them.
Step 1: List every step in plain language
Open a blank note and write one step per line, in the order the work actually happens. Use short verb phrases — 'Receive order', 'Check stock', 'Charge card'. Do not worry about shapes yet; the goal is to capture the sequence. If you get stuck, describe the process out loud to a colleague and transcribe what you say — spoken descriptions naturally follow the real order of events.
Step 2: Mark the start and the end
Add a line at the top for the trigger ('Customer submits order') and one at the bottom for the outcome ('Order shipped'). Every process needs an obvious beginning and end or the chart will feel vague. If you can name two possible endings (for example 'Order shipped' and 'Order refunded'), mark both — a chart with two clean end states is far more honest than one that pretends the unhappy path does not exist.
Step 3: Insert decisions as questions
Anywhere the process branches, add a line phrased as a yes/no question, like 'In stock?' or 'Approved?'. Follow it with the two possible next steps. Decisions become diamonds in the final chart. Keep the questions binary — if a decision has three or more outcomes, either split it into two decisions or accept that you need a switch-style branch and label each arrow clearly.
Step 4: Generate the chart from your list
Paste the list into a text-to-flowchart tool such as ProcessMapping.app. It converts each line into the right shape, connects them with arrows and lays out the chart for you — no dragging required. If the layout looks tangled, that is usually a signal the process itself is tangled: consider whether two steps can be merged or a decision moved earlier.
Step 5: Review with the people who do the work
Show the chart to whoever runs the process. They will spot the missing step, the wrong branch and the decision you glossed over. Update the list, regenerate and share the final version. Aim for at least two reviewers from different roles — the person who starts the process and the person who finishes it usually have very different mental models.
Common pitfalls to avoid
- Charting the ideal instead of the actual. Draw what happens, not what is supposed to happen. Fix the process after the chart makes the gap visible.
- Skipping the unhappy paths. A chart with only the happy path lies. Include the one or two failure branches that actually occur.
- Mixing levels of detail. Either every step is a single action, or every step is a sub-process — do not mix "Send email" with "Run entire onboarding" on the same chart.
- Never updating it. A chart that does not match reality is worse than no chart. Store the source text next to the image so updates take seconds.
People also ask
How long should a process flowchart take to make? For a process you already understand, ten to twenty minutes. If it takes longer, the bottleneck is usually alignment on what the process actually is, not the drawing.
Can I make a flowchart without any drawing skill? Yes. Text-to-flowchart tools generate the diagram from a list of steps, so the only skill you need is describing the process in order.
How often should I update it? Any time the process itself changes, and at minimum once a year. Put a review date in the file name so old versions are easy to spot.
Next: pick a symbol set and an example
Before you finalize, skim the symbol reference so reviewers see the shapes they expect, and browse worked examples for structure ideas. If you get stuck, the common mistakes post covers the fixes that make charts readable.
Create your process flowchart free
No signup, no drawing. Type your steps, get a chart.
Open the free flowchart maker →