When a bake goes wrong: troubleshooting by symptom, and high altitude baking adjustments
A failed bake diagnosed from its symptom in a fixed order, fixed one change at a time and logged, and a recipe changed with the high altitude baking adjustments from the extension tables.
- Start here: the essentials
- The order of checks
- The tables: symptoms and their causes
- The oven as a cause
- One change at a time
- When a sourdough starter goes wrong
- Baking at altitude
- See it: flat cookies and a gummy loaf
- Practice: one failed bake, one change
- Your kitchen
- Check your work
- Knowledge check and scenario
Start here Essentials
For a first pass, take one bake that went wrong, read its likely causes, check the two most common ones, and plan one change. One line in the log is enough.
- Find the symptom on the symptoms page and read its likely causes. How the tables work is under the tables.
- Check the two causes that come up most often first: how the flour was measured, and the oven's real temperature (the order of checks, the oven).
- Change one thing for the next bake, and keep everything else the same (one change at a time).
- Write the symptom, the cause you suspect and the change on the bake log.
Minimum time: about 15 minutes, plus the next bake. Done when: the bake log has one failed bake with a suspected cause and one planned change.
The order of checks Understand
A failed bake usually has more than one possible cause, and the published tables list several for each symptom. Flat cookies, in the University of Nebraska-Lincoln Extension's 4-H judging guide, can come from dough that was too warm, a sheet that was still hot, the wrong oven temperature, flour or liquid measured wrong, or melted fat. A table cannot tell you which one happened in your kitchen. A fixed order of checks can narrow it down.
Our order puts first the causes the tables name most often, and the ones you can check without baking again. It is our method, built from the extension tables cited in this chapter; no source we found gives an order. Convention
| Check | What to ask | Where it is explained |
|---|---|---|
| 1. Measuring | Was the flour weighed, spooned and leveled, or scooped? Was anything left out or doubled? | Measuring |
| 2. The oven | What does an oven thermometer say when the dial reads the recipe's temperature? Which rack, which pan? | The oven and the pan |
| 3. Ingredient temperature | Was the butter soft or melted? The dough warm or chilled? The yeast water too hot? | Temperature |
| 4. Mixing | Overmixed, undermixed, creamed too little? | Cookies, muffins and biscuits |
| 5. Leavening and freshness | Is the baking powder or yeast in date and active? Was soda matched to an acid? | Leaveners |
| 6. Time and doneness | Was it taken out by the clock, by look, or by a test? Cooled in the pan or on a rack? | Temperature |
Why measuring and the oven come first
Measuring and oven temperature appear as causes in nearly every section of the Nebraska and Utah 4-H tables: cookies, cakes, quick breads, muffins, pies and yeast bread. Both are also invisible in the finished bake and easy to check. A cup of flour can weigh anywhere from about 106 g to 160 g depending on the publisher and how it got into the cup (Measuring), and appliance makers let owners offset an oven by up to 30 or 35 °F because ovens drift (The oven and the pan). Neither error shows on the recipe card. Both can be ruled in or out in a few minutes with a scale and an oven thermometer.
Read the whole bake, not just the symptom
Before you open the table, write what you saw: the color of the top and the bottom, the height, the texture of the inside, how it came out of the pan, how long it baked. Two symptoms together often point to one cause. A cake that is dark outside and wet in the middle points to heat; a cake that is pale all over and sank points elsewhere. The bake log has a column for what you saw and a separate one for the cause you suspect, so the observation does not get rewritten by the guess.
The tables: symptoms and their causes
Three extension tables and two practitioners' pages give the causes this manual relies on. The Nebraska guide's tables pair "what happened" with "because of" (Nebraska Extension, 4-H Foods Judging Guide). Utah State University Extension's 4-H fair judges' manual pairs common defects with probable causes (Utah 4-H, Fair Judges' Manual). USU's yeast bread bulletin FN 283 adds bread faults. Red Star Yeast's troubleshooting guide covers yeast doughs, and King Arthur Baking's cheesecake trial covers cracks. The symptoms page carries every row, filterable by bake, with its source.
| Symptom | Causes the tables name | Source |
|---|---|---|
| Cookies spread flat | Dough too warm; dropped on a hot sheet; wrong oven temperature; flour or liquid mismeasured; melted, whipped or oil fat; too much fat, sugar, leavening or liquid | Nebraska; Utah |
| Cookies flat and pale | Expired baking powder | Nebraska |
| Cookies too dark | Baked too long or too hot; a dark nonstick or glass pan without lowering the oven 25 °F | Nebraska |
| Cake fell in the middle | Too much shortening, sugar or baking powder; door opened or cake moved; oven too low; too much batter; underbaked | Nebraska; Utah |
| Cake peaked or humped | Oven too hot at the start; too much flour; batter too stiff; pan too high or too small | Nebraska; Utah |
| Cake dry or crumbly | Overbaked; too much leavening or flour; oven too hot | Nebraska |
| Quick bread center dipped | Oven not hot enough; underbaked | Nebraska |
| Quick bread soggy or gummy | Wrapped before cool; underbaked; too much fruit | Nebraska |
| Muffins with tunnels and peaks | Overmixed (all sources); too much flour (Utah); too much liquid, too little fat or sugar (Nebraska) | Nebraska; Utah |
| Pie crust shrank | Stretched into the pan; handled too much | Nebraska; Utah |
| Pie crust tough | Too much water; overhandled; dough too warm when rolled; too much rolling flour | Nebraska; Utah |
| Soggy bottom crust | Shiny pie pan; pie baked on a cookie sheet; undermixed | Nebraska |
| Fruit filling ran over | Top crust not sealed; too little thickener; too much sugar; oven too low | Nebraska; Utah |
| Yeast bread did not rise, or rose slowly | Too little or expired yeast; liquid too hot; ingredients too cold; too much salt; rise too cool | Red Star |
| Yeast bread fell in the oven | Overproofed; flour too weak; oven too low | Nebraska; Red Star |
| Yeast bread with large holes | Poor shaping; rise too long | Red Star; Utah |
| Bread cracked along one side | Uneven oven heat or crowded pans (the crack on the cooler side) | USU FN 283 |
| Cheesecake cracked | Overbaking, chiefly | King Arthur Baking |
Sources: Nebraska and Utah 4-H tables, as linked; USU Extension, FN 283 (1976 to 2000, used for fault descriptions only); Red Star Yeast, Tips and Troubleshooting Guide; King Arthur Baking, How to keep cheesecake from cracking.
Reading a row
A row is a list of suspects, not a verdict. Read the whole row, cross out the causes your notes rule out, and the shortest list left is where to start. Nebraska adds one useful "not a fault": a crack down the center of a quick bread loaf is normal, because a large mass of batter heats slowly. Convention
Where the tables point in opposite directions
Two common symptoms have causes that pull opposite ways. Both are shown here, because the fix depends on which one happened.
- Dense yeast bread. Red Star says a dense, gummy loaf can come from an oven that is too hot, which sets the crust before the loaf reaches full volume, or from taking it out too soon. Nebraska and Utah trace heavy, coarse bread to an oven that is too cool. The oven thermometer settles which. Test it
- A cracked cake top. Nebraska traces it to an oven too hot at the start, a batter too stiff, or a pan too narrow or deep. Utah lists too much sugar. Check the oven first, because it is quicker to rule out than a recipe.
A published table lists causes that judges and bakers have seen. It cannot say which one happened in your kitchen, and a bake can fail for two reasons at once. This chapter gives you causes to check, in an order. Your own log, one change at a time, is what settles it.
The tables compared, where they differ
| Symptom | Nebraska | Utah | Red Star or USU FN 283 |
|---|---|---|---|
| Dense or heavy bread | Oven too cool, among many | Coarse: oven too cool | Red Star: oven too hot; taken out too soon |
| Cracked cake crust | Oven too hot at start; batter stiff; pan narrow or deep | Too much sugar | |
| Muffin tunnels | Over-stirring; too much liquid; inaccurate measuring; too little fat or sugar | Overmixing; too much flour | |
| Cake tunnels | Too many eggs or too little sugar; poorly mixed; butter overbeaten | Coffee cake: oven too hot; dark or glass pans; extreme overbeating | |
| Large holes in bread | Poor molding; over-raised | Red Star: poor shaping; rise too long. FN 283: a gas bubble left at shaping, or a dried surface |
All agree on overmixing as the main cause of tunnels; they differ on the ingredient causes. On dense bread and cracked cakes, they name causes that need opposite fixes, which is why the oven check comes before any recipe change. King Arthur's cheesecake trial ranked crack prevention from least to most effective: a plain bake, a steam pan on a lower rack, soaked cake strips, and a water bath; it calls overbaking the chief cause, and gives a doneness check of no more than 175 °F (79 °C) about 1 inch from the edge and at least 150 °F (66 °C) in the center. Cakes and frosting covers cheesecake.
The oven as a cause
An oven's dial is a request, not a reading. The thermostat switches the heat on and off around the set point, and appliance makers say ovens drift as they age. New Mexico State University Extension's high-altitude circular says oven regulators vary, and advises checking with an oven thermometer, then having the regulator adjusted or learning the setting that gives the temperature you need (NMSU Extension, Circular 293).
The check itself, with where to put the thermometer and how many readings to take, is in The oven and the pan. What matters here is the order: check the oven before you change a recipe. A recipe change made to cover a hot oven fails again the day the oven is fixed or you bake somewhere else.
What an oven error looks like
| Oven runs | Signs the tables connect to it |
|---|---|
| Hot | Cookies too dark or hard; cakes peaked, humped or cracked; dry, crumbly cake; quick bread cracked; dense, gummy bread whose crust set early (Red Star) |
| Cool | Cakes that fall or run over; quick bread center dipped; pie filling runs over; pale bread crust; heavy, coarse bread; a compact layer at the bottom of a loaf (Utah) |
| Uneven | A cake higher on one side; a bread loaf cracked along one side; muffins with peaks |
Sources: Nebraska and Utah 4-H tables; Red Star; USU FN 283.
The pan and the rack are part of the oven
Nebraska's guide traces too-dark cookies to a dark nonstick or glass pan used without lowering the oven 25 °F, and a pale top with a burned bottom to a rack not in the middle. Whirlpool says the middle rack suits most baked goods and that pans should not touch each other or the oven walls. The oven and the pan covers pan materials and racks.
If you have no oven thermometer, Whirlpool publishes a bake test: a can of refrigerated biscuits on a shiny sheet, middle rack, at the package temperature; the oven is right if they are done and evenly browned within the package time. It also says to change a calibration by no more than 10 degrees at a time and retest. Product-specific
One change at a time
When a bake fails, the urge is to fix everything at once: more flour, a cooler oven, a new pan. If the next bake works, you will not know which change did it, and if it fails, you will not know which change made it worse. Change one thing, bake again, and compare. The University of Wyoming Extension gives the same rule for altitude adjustments: one change at a time, smallest first (UW Extension, B-1310). Test it
How to run a test
- Write the failed bake in the log. What you saw, separately from what you suspect.
- Pick one suspect, the first in the order of checks that you have not ruled out.
- Change only that. Same recipe, same pan, same rack, same measuring method, same doneness test, everything but the one thing.
- Bake and write the result in the same words you used the first time.
- Decide: fixed, better, the same or worse. If the same, the suspect is probably cleared; go on to the next.
A small batch is enough for a test: half a recipe of cookies, six muffins, a single layer. Bake it on a day when nothing depends on it. The bake log has columns for the oven setting and offset, the minutes baked, the doneness check, what you saw, the suspected cause and the next change.
What counts as one change
Correcting the oven to its true temperature is one change, even though it affects time and color, because it removes an error rather than adding a new variable. Switching from scooped to weighed flour is one change. Chilling the dough is one change. "Use a different recipe" is many changes at once; keep it for when the tests run out.
King Arthur Baking says to throw a sourdough starter out and start over if it shows mold (often fuzzy, in various colors) or any pink or orange tint or streak. We found no extension or agency guidance on spoiled starters; this is a practitioner's rule, and we follow it.
When a sourdough starter goes wrong Go deeper
King Arthur Baking's troubleshooting page is the only source we found on starter problems (King Arthur Baking, Sourdough starter troubleshooting). Its point is that a mature starter is hardy, and most worrying signs are not failures.
| What you see | What King Arthur says it means | What to do |
|---|---|---|
| Liquid on top (hooch), clear, gray, brown or black | Alcohol from fermentation; the starter is hungry. Color alone does not mean spoiled | Pour it off or stir it in, and feed |
| A new starter not rising after a few days | A new starter takes 6 to 10 days to mature | Keep feeding; keep it at about 70 °F (21 °C) |
| Rising slowly after a missed feeding | Missed or uneven feedings do not kill it | Feed every 12 hours until it doubles reliably |
| A few days in the freezer | Survivable; long freezing damages yeast | Thaw and feed |
| Left somewhere hot | Yeast dies at 140 °F (60 °C) | If it does not revive with feeding, start over |
| Mold, or pink or orange streaks | Spoiled | Throw it out and start over |
A starter that rises but makes a dense loaf is usually being used before or after its peak. Yeast bread has the peak times by feeding ratio.
Baking at altitude
Above about 3,000 feet, recipes written at sea level start to fail in predictable ways: cakes rise too high and fall, batters dry out, cookies spread. Colorado State University Extension puts the start of high elevation at 3,000 feet, and USDA's Food Safety and Inspection Service says most cookbooks do too (FSIS, High Altitude Cooking).
Why
- Lower air pressure. CSU gives 14.7 pounds per square inch at sea level, 12.3 at 5,000 feet and 10.2 at 10,000 feet. With less pressure on it, the gas from leaveners expands more and faster, so a batter rises further and its bubbles can grow too large and collapse. Physical principle
- A lower boiling point. FSIS says water boils just under 1 °F lower for each 500 feet, about 198 °F (92 °C) at 7,500 feet. Water leaves a batter at a lower temperature and faster, so batters dry out and sugar concentrates. Physical principle
- The oven is not affected. FSIS and CSU both say oven temperatures do not change with altitude. The increase in the tables below is a recipe adjustment, to set the structure before it over-expands, not a correction to the oven.
The adjustment table
Our default is Colorado State University Extension's table, the most recently reviewed extension source (revised 2023, reviewed October 2025) (CSU Extension, High Elevation Food Preparation Guide). It is written for cakes, and CSU applies it to cake-like quick breads too.
| Adjustment | 3,500 to 6,500 ft | 6,500 to 8,500 ft | 8,500 to 10,000 ft |
|---|---|---|---|
| Baking powder: for each teaspoon, reduce by | 1/8 tsp | 1/8 to 1/4 tsp | 1/4 tsp |
| Sugar: for each cup, reduce by | 0 to 1 Tbsp | 0 to 2 Tbsp | 1 to 3 Tbsp |
| Liquid: for each cup, increase by | 1 to 2 Tbsp | 2 to 4 Tbsp | 3 to 4 Tbsp |
| Oven temperature | Raise 15 to 25 °F; the baking time may shorten | ||
Source: CSU Extension. The oven increase is in CSU's text rather than its table. CSU says most one-bowl cakes need no change up to 3,000 feet. The altitude calculator applies this table to a recipe and shows Wyoming's banding beside it.
Beyond the table, CSU says rich cakes may need 1 to 2 tablespoons less shortening and an extra egg; foam cakes need their whites beaten only to shiny, slightly drooping peaks. FSIS adds that at high altitude, extra-large eggs add moisture and structure, and smaller eggs make a batter more likely to fall. For cookies, CSU says results often improve with slightly less leavener, fat or sugar and slightly more liquid, flour and oven heat. Pie crust may need slightly more liquid. Yeast bread rises faster, and Yeast bread carries CSU's advice for it.
Applying it to one recipe
A cake recipe calls for 2 1/2 teaspoons baking powder, 1 1/2 cups sugar and 1 cup milk at 350 °F (177 °C). At 5,300 feet, CSU's first band:
- Baking powder: 2 1/2 × 1/8 = 5/16 teaspoon less, so about 2 1/4 teaspoons (2 3/16, rounded to the nearest measuring spoon).
- Sugar: 0 to 1 1/2 tablespoons less. Start with none or a little.
- Milk: 1 to 2 tablespoons more.
- Oven: 365 to 375 °F (185 to 191 °C), checked early.
Wyoming's advice is to make the smallest change first and add more only if the cake still fails. A first test might change only the baking powder and the oven, and leave sugar and liquid for the second bake.
The altitude tables are starting points, not answers. NMSU says there is no fixed rule and that the changes depend on the balance of each recipe. Wyoming says to make one change at a time, starting small. Expect a recipe to take a test bake or two at your elevation, and log each one.
Hot sugar syrup and caramel cause severe burns. Use a deep pan, keep children away from the stove while sugar cooks, and do not test syrup with a finger. The syrup temperatures below matter only for frostings and fillings that need a cooked syrup.
The altitude tables compared
Three extension tables carry nearly the same numbers under different altitude labels. Wyoming (B-1310, 2018) and the archived Utah State page (2005) put CSU's three columns at 3,000, 5,000 and 7,000 feet. So in Wyoming's version, the largest adjustment starts at 7,000 feet; in CSU's, at 8,500. At 5,000 to 6,500 feet, CSU's figures give the smaller change.
| Adjustment | CSU (3,500 to 6,500 ft) | Wyoming (5,000 ft) | King Arthur (5,000 to 6,500 ft) |
|---|---|---|---|
| Baking powder, per teaspoon | 1/8 tsp less | 1/8 to 1/4 tsp less | 1 tsp becomes 1/2 tsp |
| Sugar, per cup | 0 to 1 Tbsp less | 0 to 2 Tbsp less | 1 Tbsp less, at any altitude |
| Liquid, per cup | 1 to 2 Tbsp more | 2 to 4 Tbsp more | 1 to 2 Tbsp at 3,000 ft, plus 1 1/2 tsp per 1,000 ft more |
| Flour, per cup | Not in the table | 0 to 2 Tbsp more | 1 Tbsp at 3,500 ft, plus 1 Tbsp per 1,500 ft more |
| Oven | +15 to 25 °F | +15 to 25 °F (cookies may not need it) | +15 to 25 °F; time 5 to 8 minutes less per 30 |
Sources: CSU, as linked; UW Extension B-1310; King Arthur Baking, High-Altitude Baking.
King Arthur cuts leavener much harder at height: at 6,500 to 8,000 feet its chart turns 1 teaspoon into 1/4, a 75 percent cut, where CSU's is 12 to 25 percent. NMSU's circular gives a third form: about 1/4 to 1/2 teaspoon less baking powder per 2 cups of flour for each 2,500 feet. The University of Arizona's AZ1939 (2021) draws on CSU and King Arthur and says to use the lower oven increase for chocolate or delicate cakes. We default to CSU because it was reviewed most recently; if a CSU-adjusted cake still rises and falls, King Arthur's larger leavener cut is the next test.
Sugar syrup at altitude
A cooked syrup reaches a stage (soft ball, hard ball and so on) when enough water has boiled off, and at altitude water boils off at a lower temperature, so each stage comes at a lower reading. CSU's rule is to lower the recipe's temperature by 2 °F for each 1,000 feet (CSU Extension, Candy Making at High Elevation).
| Stage | Used for | Sea level | 5,000 ft | 7,500 ft |
|---|---|---|---|---|
| Soft ball | Cream candies, fudge frosting | 234 to 240 °F | 224 to 230 °F | 219 to 225 °F |
| Firm ball | Chewy fillings | 244 to 248 °F | 234 to 238 °F | 229 to 233 °F |
| Hard ball | Egg-white frostings | 250 to 260 °F | 240 to 250 °F | 235 to 245 °F |
| Soft crack | Toffee | 270 to 284 °F | 260 to 274 °F | 255 to 269 °F |
Every figure is the sea-level range lowered by 2 °F per 1,000 feet, CSU's rule, computed by us. CSU's own table prints slightly different ranges for some rows, and its hard-ball row at 5,000 feet (241 to 258 °F) does not match its own rule or its other rows; it looks like a typo, so we compute from the rule. The syrup calculator does the same.
The more direct method, which Wyoming and CSU both describe: boil water, read your candy thermometer, and subtract the difference from 212 °F from the recipe's temperature. That also checks the thermometer. Wyoming notes that the cold-water test (dropping syrup into cold water and feeling the ball it forms) works at any altitude.
A recipe from altitude, baked at sea level
None of the sources we read covers the reverse case. Our reasoning, labeled as ours: a recipe tested at altitude usually has less leavener and sugar and more liquid than a sea-level version, so at sea level it may rise less, taste less sweet and bake up wetter. Undoing the table, one change at a time, is a reasonable first test. Test it
See it: flat cookies and a gummy loaf See it
Dana Reyes is fictional, and every fact about her is invented for this manual. She lives in an apartment at sea level, with a full-size electric oven she had not checked. She measures with cups and spoons, and has one light sheet pan and a 9 × 5 loaf pan. Her chocolate chip cookies spread flat, and her banana bread is gummy in the center.
Known: she checked the oven with a borrowed oven thermometer (The oven and the pan), and it runs 20 °F hot: set to 350 °F, it holds about 370 °F. Both recipes bake at 350. Her sheet pan is light metal, on the middle rack. Nebraska's tables name the wrong oven temperature among the causes of flat cookies, and name underbaking among the causes of a soggy quick bread.
Assumed (Dana's assumption): the banana bread browned early in the hot oven, so she took it out when it looked done, before the center had set. Under that assumption, a hot oven explains both bakes, and correcting it is the first change. The bake log row reads: banana bread, gummy center, top dark at 50 minutes; suspected cause, oven 20 °F hot; next change, set the dial to 330 °F for a true 350 and bake to the recipe's test, not its color.
Open, and who settles each:
- How she filled the flour cup. Spooned lightly, a cup holds less flour than the recipe writer's may have, and Nebraska lists mismeasured flour as a cause of spreading. Dana settles it by weighing her cupful once on a borrowed scale and comparing it with the ingredient weights page.
- How warm her butter and dough were. Utah and Nebraska list warm dough and a hot sheet. Dana settles it on the second test by chilling the dough, but only if the oven change does not fix the cookies.
- Whether she wrapped the banana bread warm. Nebraska lists that too. She writes "cooled on a rack, wrapped next day" in the log next time.
One change, then one more. If the corrected oven fixes the banana bread but not the cookies, the cookies go to the second check, measuring.
The Hale household (fictional) lives in Denver, at 5,280 feet. Last year's birthday cake sank. Known: Denver is in CSU's first band, 3,500 to 6,500 feet; Nebraska and Utah both list too much baking powder among the causes of a fallen cake, and Nebraska adds too much sugar. Assumed (Priya's): the recipe was written for sea level and was not adjusted. Open: whether the oven runs true, which Tom settles with an oven thermometer before any test; and how much adjustment the cake needs, which a test layer settles. Their first test changes only the baking powder (1/8 teaspoon less per teaspoon, CSU) and raises the oven 15 °F. If the layer still dips, the second test adds 1 tablespoon of milk per cup. Baking ahead has the rest of their plan.
- Nebraska Extension, 4-H Foods Judging Guide (PDF): "what happened, because of" tables for cookies, cakes, quick breads, pies, muffins and bread.
- Utah 4-H, Fair Judges' Manual (PDF): defects and probable causes, including foam cakes and pastry.
- CSU Extension, High Elevation Food Preparation (PDF): the altitude table and the reasons, on two pages.
- Red Star Yeast, Tips and Troubleshooting Guide: yeast dough problems, row by row.
Practice: one failed bake, one change Practice
Minimum: one line in the bake log for a bake that went wrong, with what you saw, a suspected cause and one planned change. The test bake can come later. Time: 15 minutes to diagnose; one small batch for the test. Materials: the symptoms page, the bake log, and if you have them, an oven thermometer and a kitchen scale.
- Write what you saw, before you look anything up: top, bottom, height, inside, time baked.
- Find the symptom on the symptoms page and copy its causes.
- Cross out what your notes rule out.
- Check measuring and the oven, whatever the row says. Weigh one cupful of flour your usual way; read the oven with a thermometer if you have one.
- Write one suspected cause and one change.
- Bake a small test with that one change, and write the result in the same words.
Run a second test. If the first change did not settle it, take the next suspect in the order of checks and test that, with the first change kept or reversed as the result says.
Test an altitude adjustment. If you live above 3,000 feet, bake a single layer with CSU's smallest adjustments and one without, on the same day, and compare.
Check your boiling point. Boil water and read your thermometer. Write the reading and your elevation in the log; it calibrates your thermometer and gives your syrup correction.
Your kitchen Your kitchen
Check your work Check your work
Criteria
- Did you write what you saw separately from what you suspect?
- Did you read the whole row of causes, not just the first?
- Did you check measuring and the oven before changing the recipe?
- Is your next bake different in one way only?
- Above 3,000 feet: did you start from CSU's smallest adjustment, and log it as a test?
- Does the bake log hold the failed bake, the suspect and the change?
Worked example
Dana's log meets the criteria. The observation (gummy center, dark top at 50 minutes) is separate from the suspect (oven 20 °F hot). She checked the oven before touching the recipe, and her next bake changes only the dial. Her conclusion rests on an assumption, that she took the bread out by its color; under that assumption the oven explains both bakes, and the test bake settles it. Measuring is still open, and it is the next test if the cookies still spread.
Common mistakes
- Changing three things at once. The next bake works and you do not know why.
- Fixing the recipe for a hot oven. Less sugar or a shorter time hides an oven error that returns in every recipe.
- Reading only the first cause in a row. The tables do not rank their causes.
- Applying the largest altitude adjustment first. Wyoming says start small.
- Testing on the day it matters. Test on a small batch when nothing depends on it.
- Treating a center crack in a quick bread as a fault. Nebraska says it is normal.
What is still unresolved
This chapter cannot say which cause happened in your kitchen; your log does, a change at a time. It cannot give exact altitude changes for your recipe; the extension services say a recipe may take trial and error. Oven faults beyond an offset, such as a heating element that does not come on, are for the owner's manual and the maker, not this manual. The methods behind each bake are in Cookies, muffins and biscuits, Cakes and frosting, Pie and pastry and Yeast bread.