Recipes as Gantt charts
By Juan Buis, who builds RecipeTables — every rule below came out of a real bug report.
If you have seen a recipe drawn as a grid and thought “that looks like a Gantt chart” — you are in good company, and you are mostly right. The format has a real name and a twenty-year history, and the Gantt comparison is the fastest way to understand it.
The comparison, taken seriously
A Gantt chart puts tasks on rows and time on the horizontal axis; a bar shows when each task runs, and stacked bars show what happens in parallel. The recipe version, called a recipe summary table, maps almost the same way:
- Rows are ingredients instead of tasks, listed in the order they are first used.
- Left to right is sequence instead of calendar time: each column is a step.
- A cell spanning several rows is a merge — those ingredients are now one thing. Cream the butter and sugar, and their two rows share a cell from that point on.
- Parallel work reads as parallel rows: the sauce coming together in the bottom rows while the pasta cooks in the top ones, exactly like two workstreams.
The last column always spans every row. That cell is the finished dish, and the shape of the merging on the way there IS the recipe's structure — you can see at a glance which parts are separate components and where they join.
Where the comparison breaks down
Two honest differences, so the analogy doesn't mislead you. First, a Gantt chart's axis is real time — a two-week bar is twice a one-week bar. A recipe table's axis is sequence: a column is one step whether it takes thirty seconds or an hour, so column width says nothing about duration.
Second, Gantt bars end. Ingredients don't — they merge. A task chart tracks completion; a recipe table tracks combination, which is why its cells fuse into fewer, wider cells instead of finishing. It is closer to a flowchart read sideways than to a project plan, but “Gantt chart” is what everyone says, and it gets you 90% of the way.
Who drew recipes this way first
An engineer named Michael Chu, in 2004, at Cooking for Engineers. He drew every table by hand and called the format Tabular Recipe Notation. The format stayed rare for two decades because the hard part isn't the drawing — it is reordering the ingredients by first use and working out which cells span what, for every recipe, by hand. His originals are still the best-written ones.
Turn any recipe into one
The tedious part is now automated. Paste a link, the recipe text, or a photo of a cookbook page into RecipeTables and you get the Gantt-style table back in about fifteen seconds — ingredients reordered by first use, cells spanned correctly, ready to scale, translate or cook from.
Browse tables other people have made to see the format across hundreds of real recipes, or learn to read one in three rules.
See it on your own recipe.
Paste a link, the text, or a photo of a cookbook page — you get the whole recipe back as one table. Free, no account.