Sourdough Baking Schedule & Reverse Timeline Guide: Weekend, Workday & Same-Day Clocks

Why a Reverse Timeline Beats a Recipe

A sourdough formula tells you what to mix. It never tells you when to start. That single omission explains why the same recipe produces a world-class loaf on Sunday and a flat frisbee on Wednesday: a full sourdough bake spans roughly 26 to 36 hours of wall-clock time, and every stage in that chain is governed by your kitchen's temperature rather than by the clock on your wall.

The correction is to stop reading forward and start reading backward. Anchor the schedule to the only timestamp that genuinely matters — the minute a cooled loaf hits the wire rack — and subtract the duration of every stage that precedes it. That is the entire logic behind the 9-Stage Sourdough Baking Schedule engine, which reverse-engineers all nine stages from a target bake hour and exports the result as an RFC 5545 .ics file so your phone can wake you for every single stage.

The Nine Physical Stages of a Sourdough Bake

The Reverse Timeline Arithmetic

The entire scheduling problem collapses into one subtraction. Every stage carries a duration $d_i$, so the moment you must feed your starter is simply:

In the canonical weekend configuration — a 500g flour country loaf, 20% levain at 1:2:2, a 45-minute autolyse, a 12-hour cold retard and dough held at 75°F — the nine stages total exactly 27 hours. Subtracting 27 hours from a Sunday 09:00 AM slice lands the starter feed on Saturday 06:00 AM, and every subsequent stage falls into place at a fixed clock time.

Temperature Rescales Every Duration

Stage durations are not constants; they are kinetic functions of temperature. The schedule engine applies a Q10-style exponential correction anchored at 75°F (24°C), where the 3.8% per-degree factor reflects how much faster a wild yeast and lactic acid bacteria culture metabolises as the dough warms:

Every degree below 75°F stretches the clock by about 3.8%; every degree above compresses it by the same proportion. At 82°F (28°C) the 90-minute fold window compresses to roughly 76 minutes, and at 68°F (20°C) the five-hour bulk target stretches toward seven hours. The starter peak scales identically, which is why a 1:2:2 build takes 6.0 hours at 75°F but only 4.2 hours at 82°F.

The Bulk Target Is a Volume, Not a Height

The most common scheduling error is not using a clock at all — it is waiting for the dough to "double" in a sloped mixing bowl. Because a flared bowl widens as it rises, a percentage increase in vertical height maps to a much larger percentage increase in true dough volume. The engine converts a target volume rise into a target height by solving the conical frustum volume equation numerically:

In a standard 24cm-rim, 14cm-base artisan bowl starting at 4.0cm depth, a +50% true volume target is only a 38.1% rise in vertical height. Wait for a 50% rise in height instead, and true volume balloons by roughly 67%. At 82°F the same trap is worse: a +25% volume target is a 19.7% height rise, but waiting for a 25% height increase inflates the dough by 32% in true volume. This single geometric illusion is the most common root cause of overproofed, collapsed loaves.

Three Realistic Clocks

Choosing the Clock That Matches Your Life

• **The Sunday morning bake** is the highest-quality option: a 1:2:2 levain, a full 45-minute autolyse and a 12-hour cold retard give the yeast time to exhaust the maltose pool and leave a complex, lactic crumb with a deep caramelised crust.
• **The workday bake** trades a shorter autolyse for a much longer 16-hour retard and a high-ratio 1:4:4 levain built in the early morning. Total elapsed time stretches to 35.75 hours, but every active step lands outside working hours.
• **The same-day bake** is a genuine 12.25-hour express route: a 1:1:1 levain peaks in 3.5 hours, the bulk target drops to +39.5% because no cold retard is available to finish the fermentation, and the final proof happens at ambient temperature for 90 minutes in the banneton.

The Levain Arithmetic Behind Each Clock

The starter build is not a fixed recipe; it is a ratio solved backwards from the levain weight your dough demands. For a 500g flour loaf at 20% inoculation you need roughly 100g of active levain, plus a small jar-residual buffer:

Five Sensory Gates That Override the Clock

A schedule is a prediction; the dough is the measurement. Even a perfectly computed timeline must defer to five physical gates, because dough temperature, starter vigour and ambient humidity all vary by several degrees between batches.

• **The levain dome.** Peak levain domes into a taut convex pillow and releases gas in visible streaks when you tilt the jar. A levain that merely doubled but stayed flat is under-fermented.
• **The clean bowl wall.** At the end of bulk the dough should release the sides of the container in one slow, slumping mass rather than tearing away in chunks.
• **The marshmallow jiggle.** Dough at target rise dents gently under a floured knuckle and springs back in roughly half a second.
• **Translucent sub-surface bubbles.** Hold the dough up to a window: you should see gas cells glowing through the skin rather than an opaque mass.
• **The surface bubble test.** A large surface bubble that refuses to pop when you flick it signals a well-fermented, fully inflated dough.

When the Schedule and the Dough Disagree

The schedule assumes a 75°F dough. If your actual dough temperature drifts more than 3°F from the target, abandon the computed clock and re-anchor on the bulk rise percentage instead. The Bulk Fermentation engine converts any dough temperature into a corrected target volume rise, so a single recalculation replaces nine guessing stages with one measurable number.

That final column is the most valuable number on the schedule: it tells you exactly how much extra fermentation you buy by misreading a flared bowl, and therefore exactly how much undischarged acid you are silently adding to your crumb.

Export It and Stop Guessing

Once the numbers are solved, the schedule is worthless if it lives only in a spreadsheet. The Baking Schedule engine emits a standards-compliant .ics calendar containing all nine stages, each with a five-minute advance alarm, full timezone definitions and local wall-clock timestamps — so Google Calendar, Apple Calendar and Outlook all fire the same alarm sequence.

Load the reverse clock, export the file, and the next loaf stops being a gamble on whether you remembered to feed the starter on Saturday morning.