Why does reading the recipe all the way through help?

Reading a recipe all the way to the end before you start cooking makes the steps that need waiting, and any missing ingredient, visible in the very first minute. The most expensive surprises are hidden in the middle of a recipe: a step that asks for an overnight soak, a rest or a cooling period leaves no way to rescue the dish once it is noticed after the burner is lit.

Why should a recipe be read from start to finish?

Recipes begin with an ingredient list, and that list is usually taken to be enough. Yet the list only says what is needed; it does not say when it is needed. Steps such as soaking, proving, resting and cooling do not appear in the list; they turn up inside the instructions.

When the instructions are read in order, these steps are only noticed when their turn comes. By then the kitchen is already set up, the burner is lit and the ingredients are out; going back means postponing the meal.

And a postponed meal usually does not get cooked. Something quick is put in its place that evening, the ingredients go back into the fridge and wait until the next attempt. So the cost of an unread recipe is not only the minutes lost but that meal changing entirely.

Which surprises hide in the middle of a recipe?

The most common are the steps that need waiting: soaking dried legumes in advance, resting dough, leaving meat in a marinade, cooling a dessert. None of these can be hurried; the time is part of the recipe.

Second come the tools. If a mold, a strainer or a tray mentioned in the middle of a recipe is not in the house, the decision made at that point changes the outcome of the dish. Third is the state of the ingredients: a recipe that asks for room-temperature butter, thawed meat or warmed milk pulls the preparation half an hour earlier.

How long does reading it take?

Reading a recipe from start to finish usually takes a minute or two, and that time does not extend the total time of the meal, because what it gains comes back at the stove. Once the instructions are known, it also becomes clear which jobs can be done at the same time as which.

Splitting the recipe in two while reading makes the job easier: steps that need waiting, and steps done without a break. The earlier the first group starts the better; the second group moves in order anyway.

That split also shows the real time the recipe takes. The time written is usually only the time at the stove; once the waiting steps are added, the total can get clearly longer. When you are working out which meal can be cooked on which evening, that total is the right number.

What if the recipe is incomplete or vague?

Some recipes do not write the waiting time, and some leave the measure vague. You only see this by reading to the end; an uncertainty noticed before you start cooking can be closed by looking at a second recipe.

Comparing two recipes for the same dish usually shows at a glance which one skipped a step. This is the cheapest check you can make before trying a recipe.

If the uncertainty is in the measure, staying on the lower side the first time you try a recipe helps; salt or liquid that is short can be added later, while too much cannot be taken back.

What can you do today?

You can read the recipe for tonight's meal to the end before you touch a pot; if there is a step that needs waiting, start it as the first job. If you note the missing ingredients and the equipment you will need while reading, no second check is required.

Adding your own note to the recipes you cook often gains you something lasting too: writing the waiting time at the top lets you cook that recipe in the right order without having to read it again.