How to read a recipe table

A recipe table is a whole recipe in one glance: every ingredient, every step, and — the part prose can't do — how they combine. Here's one, followed by the three rules for reading it.

The left column lists what you need — but not in the order the source wrote it. Ingredients are sorted by when they enter the recipe, top to bottom. That ordering is what makes the rest of the table possible, and it's the tedious part nobody did by hand, which is why these tables were rare for twenty years.

It has a practical side effect at the counter: your mise en place is just the column read downward. The first thing you'll touch is the first thing listed.

Every box to the right of the ingredients is one action — “cream”, “fold in”, “bake 60 min” — and its height tells you exactly which ingredients it involves: the rows it touches. A box spanning butter and sugar means cream the butter and sugar. No re-reading the paragraph to find out what “the mixture” refers to; the geometry says it.

Wide full-width rows above the table are prep — oven temperature, pan greasing — things you do before anything combines.

Later steps sit further right, and a step's box also covers everything behind it: when a box spans rows that earlier boxes already combined, it means take those results and combine them. By the rightmost column, every row has merged into one box — the finished dish. If a recipe has two components (a batter and a glaze, a dough and a filling), you'll see them as two separate stacks of boxes that only meet near the end, which is the structure of the recipe made visible.

That's the whole grammar. The useful consequence: you can see before you start that steps 2 and 4 never interact, that the sauce can be made while the oven works, that everything converges at the fold — the shape answers questions prose makes you reconstruct in your head.

Michael Chu introduced tabular recipes at Cooking for Engineers in 2004 and hand-built a few hundred of them. The format was admired, discussed — and then mostly ignored for twenty-two years, because producing one meant manually re-deriving ingredient order and step spans for every recipe. That's the part that finally got automated, which is why you can now make one from any recipe instead of reading about the idea.

On RecipeTables the format picks up a few live extras the paper version can't do: tap a step to check it off while cooking, scale every quantity, switch cups and grams, and build a shopping list from the rows.