How to diagnose a bake that went wrong

Most baking faults are established at one identifiable stage and only become visible at a later one. A cake that sinks in the oven often failed at the mixing stage; a loaf that is dense may have failed at shaping, long after fermentation went perfectly.

Working out the stage first narrows the candidates enormously, and it is usually easier than working out the cause directly. Ask when the last point was that everything looked right.

Once you have a handful of possible causes, do not evaluate them one at a time. Look for a single thing you can observe that divides them into groups.

For bread that did not rise, the question is whether the dough did anything at all — that one answer separates a dead-leavening problem from a time-or-structure problem, and the two have nothing in common. For cookies that spread, the question is whether later batches were worse than the first, which separates the tray from the recipe entirely.

This is what BakeHQ’s troubleshooting pages are built around, and it is a habit worth having regardless.

Once you have a candidate cause, change one variable and bake again. Changing three at once and getting a better result teaches you nothing about which one mattered, and the next failure starts from scratch.

Write down what you changed. Baking has long feedback loops and human memory is unreliable across a week.

Domestic ovens are frequently some way from their dial setting, and the discrepancy is invisible because it is consistent. It causes faults that look exactly like recipe problems: pale crusts, damp bases, cakes that sink, bakes that always need longer than stated.

An oven thermometer costs very little and eliminates an entire class of misdiagnosis. It is the first thing to check when several unrelated recipes all misbehave in the same direction.