How to turn spreadsheet data into a flowchart

A worked example, stage by stage

1. Rows in sequence

   Receipt, put-away, stock record, issue to a works order. Each Line to value points at the next row, which is all a straight-through process needs — and all most spreadsheets could represent even if they tried.

2. A number that points backwards

   The reorder branch ends with "Book receipt against the open order" pointing back to row 3. A loop is just a smaller number in the Line to cell, and it is the structure a spreadsheet is least able to express and most likely to contain.

3. A decision with two exits

   Cycle counting adds a variance check whose No route investigates and can recount. Two numbers in Line to, two labels in Line text, matched by position — get that pairing backwards and the chart is confidently wrong.

4. The lane columns

   Warehouse, inventory controller, production, procurement, finance. Those were columns in the original sheet doing nothing; as lanes they show that stock accuracy depends on four teams none of whom own it end to end.

How it works

1. Flatten the sheet

   One header row, one row per step, no merged cells and no blank separator rows. Anything that is not a plain rectangular table will paste badly, and cleaning it afterwards costs more than doing it first.

2. Make each row a single action

   Split any row whose text contains "and" or covers a phase rather than a step. Rows that describe stages rather than actions produce a diagram with four boxes that says nothing you did not already know.

3. Add the next-step column

   Number the rows and add a column holding the row number each step leads to, comma-separated where it leads to more than one. This is the only genuinely new data you have to create, and filling it in is what exposes the steps whose successor nobody can name.

4. Paste into the editor

   In QueryChart, paste the rows into the spreadsheet view: label into Box text, next-step numbers into Line to. The diagram renders as you paste and the edges route themselves, so there is no layout stage at all.

5. Add shapes, branch labels and lanes

   Set Shape to Decision on the rows that ask a question, put the answers into Line text in the same order as the numbers, and map your existing owner and phase columns onto Vertical lane and Horizontal lane. The columns you already had become the structure.

6. Retire the spreadsheet

   After conversion, work in the chart. Keeping the sheet as a parallel master reintroduces exactly the drift you converted to escape, and the sheet always loses because the chart is the one people are looking at.

Frequently asked questions

What does a spreadsheet need before it can become a flowchart?

Two things: one row per step with a usable label, and a column giving the row number of the step that follows. Everything else is optional but useful — a shape column so decisions render as diamonds, a branch-label column so each exit says which case it carries, and owner and phase columns that turn the flowchart into a swimlane diagram. If your sheet already has owners, you are one column away from a process map.

Can Excel or Google Sheets generate a flowchart from data?

Not natively in any maintainable way. Both can place drawing shapes on a sheet, but those shapes are not connected to your rows, so a change to the data does not change the diagram. Visio's Data Visualizer did generate diagrams from a table until Microsoft retired the add-in in early 2026. QueryChart keeps the table as the editor, so the diagram cannot fall out of step with the data — they are the same object.

How do I represent parallel steps rather than a choice?

The same way: two row numbers in one Line to cell. A decision and a fork look identical in the data and differ in meaning, which the shape carries — a diamond means choose one, a rectangle with two outgoing arrows means both happen. Label the arrows on a fork too, if the two arms are doing different things, because a reader cannot always tell from the destinations.

What if my process spreadsheet has thousands of rows?

Then it is not one process. Process sheets that large are almost always a log of instances rather than a definition of steps — one row per purchase order, not one row per step in the purchase order process. Pull the distinct steps out first; a process with more than about thirty of them should be split into a parent flow and linked sub-processes.