How to make a flowchart, step by step

1. Define the scope

Write down the trigger (what starts the process) and the outcomes (how it can end). "Starts when a customer submits a refund request; ends when the refund is paid or refused." Without this, flowcharts grow until nobody can read them.

2. List the steps

Write each step as a verb and an object: "Check the order", "Approve the refund". Do it as a plain list first, without shapes. Ask the people who do the work rather than relying on the official procedure: the gap between the two is often what you are looking for.

3. Mark the decisions

Every time the next step depends on a condition, you have a decision. Phrase it as a question ("Is the order less than 30 days old?") and list the possible answers. Each answer leads somewhere, possibly back to an earlier step. The rules are detailed in decisions and loops.

4. Assign owners

For each step, note who does it: a role, a team or a system. If more than one owner appears, organise the chart in swimlanes, one per owner. Hand-offs between lanes are where delays and errors usually happen.

5. Draw and connect

Place the start at the top, then the steps in reading order, using the standard flowchart symbols. Connect them with arrows, label every arrow leaving a decision, and make sure every path reaches an end.

6. Simplify

Merge steps that always happen together, move details into notes, and split very long charts into a main chart and sub-processes. A good rule of thumb is that one chart should fit on a screen without zooming out until the text is unreadable.

7. Review with the people involved

Walk through the chart with someone who does the work, using a recent real case. Every "actually, we also…" is a missing step. Then check the list of common flowchart mistakes.

Worked example

"A customer submits a refund request. Support checks the order date. If the order is older than 30 days, the request is refused and the customer is informed. Otherwise finance pays the refund and support confirms it to the customer."

That gives three owners (customer, support, finance), one decision (older than 30 days?), two outcomes (refused, refunded) and five steps. Drawn in lanes, the hand-off from support to finance becomes visible immediately.

Faster: start from a description

The paragraph above is already enough to draw the chart. With an AI flowchart generator, you paste it, get a first version in seconds, and spend your time on the review instead of on moving boxes. The guide to writing a process description for AI shows how to phrase it so the result is accurate. You can try it on your own process.