How to create a flowchart from Excel

A worked example, stage by stage

1. Paste the steps

   One step per row in Box text and nothing else. This is what your existing spreadsheet already looks like: a list of boxes with no relationships between them, which is why it has never told anybody anything they did not know.

2. Fill in "Line to"

   Type the row number each step leads to and the arrows appear. Row 5 pointing at 6 and 7 forks the flow. This single column is the difference between a list and a process — and it is the column that reveals a step nobody could say what happened after.

3. Add shapes and branch labels

   Set the severity row's Shape to Decision and it becomes a diamond; put "Yes" and "No" in Line text and each exit says which case it is. Now the chart can be read by someone who was not in the room when it was written.

4. Add the lane columns

   Horizontal lane holds the phase, Vertical lane holds the owner, and the flat flowchart becomes a swimlane diagram — same rows, two more columns. The handoffs between Customer Service, Quality and the department owner were in the sheet all along; they just had nowhere to show.

How it works

1. Get your spreadsheet into one row per step

   Before anything else, make sure each row is a single action. Merged cells, a header block above the data, and one row holding three steps are the three things that turn a clean conversion into a cleanup job. Keep one sheet, one table, no blank separator rows.

2. Number the rows and add a "next step" column

   The row number is the step's identity, so add a column holding the number of the step that follows. Where a step forks, put both numbers separated by a comma. This is the only genuinely new information you have to supply, and filling it in is what surfaces the steps whose successor nobody actually knows.

3. Paste it into QueryChart

   Open a new chart and paste the rows into the spreadsheet editor: Box text for the label, Line to for the next-step numbers. The diagram renders as you paste, and the edges route themselves — there is no layout step and nothing to drag into place.

4. Mark the decisions

   Set the Shape column to Decision on every row that asks a question, and Start and End on the first and last. Then put the branch labels in Line text, comma-separated in the same order as the Line to numbers, so "6,7" with "No,Yes" labels the two exits correctly.

5. Add owners and phases

   Fill the Vertical lane column with the role that performs each step and the Horizontal lane column with the phase it belongs to. The flowchart becomes a swimlane diagram immediately, and any step whose owner you cannot name is worth a conversation before it goes any further.

6. Fix what the diagram exposes

   Converting almost always reveals two things: a step with no successor, and a decision with only one exit. Both were invisible in the spreadsheet and both are obvious on the canvas. Correct them in the rows, then share the chart so the fixed version is the one people work from.

Frequently asked questions

Can Excel create a flowchart by itself?

Only by hand. Excel can draw SmartArt and shapes on a sheet, but those are drawings that happen to sit on a grid — they are not generated from your data, and moving a step means redrawing it. Visio's Data Visualizer did generate diagrams from a table, but Microsoft retired the add-in in early 2026. Generating the diagram from the rows, and keeping it generated, is the part that makes the process maintainable.

What columns does my spreadsheet need?

Two are essential: a label for each step, and the row number of the step that follows it. Three more are worth having: a shape column so decisions and terminators render correctly, a branch-label column so each exit off a decision says which case it is, and an owner column that turns the flowchart into a swimlane diagram. Everything else — systems, timings, notes — can go in the comment on the step.

How do I handle a step that leads to more than one place?

Put both row numbers in the Line to cell, separated by a comma, and put the matching labels in Line text in the same order. That covers both decisions, where the branches are alternatives, and forks, where two things happen in parallel — a delivery producing both a goods receipt and an invoice, for instance. The order of the two lists has to match, because they are paired by position.

Will the layout be a mess if my process is complicated?

The routing is computed rather than drawn: edges are auto-routed around the boxes, and lane assignments place each step, so a twenty-step process across five lanes lays itself out. What produces a messy chart is not complexity but scope — a chart trying to cover two processes crosses lanes constantly. If it looks tangled, the usual fix is splitting the process, not moving boxes.