Bakery Production Scheduling for Consistent Output

A bakery schedule is a chain, and the chain runs at the speed of its slowest link. Mixing, proofing, baking, cooling and packing each have a capacity, and consistent output comes from finding the one that limits the rest, keeping it busy, and timing everything else to feed it. Build the schedule backward from the time product must leave, and check every link, including the cooling racks and trays after the oven, before you commit to it.

What you are scheduling

Treat the stage times, rules and examples below as starting points for a planning method you run on your own figures, not as industry rules.

Every product passes through stages, some needing hands and some only time:

1. Mixing (labor and mixer time)
2. Bulk fermentation, where used (time)
3. Dividing and shaping (labor)
4. Proofing (time and proofer space)
5. Baking (oven time)
6. Cooling (time and rack space)
7. Finishing and packing (labor)

As an illustration, a baguette might take 15 minutes to mix, 2 hours of bulk fermentation, 20 minutes to shape, 45 minutes to proof, 25 minutes to bake and 30 minutes to cool: 4 hours 15 minutes from scaling to packing, most of it waiting time. Time your own products at each stage; those numbers are the raw material of the schedule.

Find the constraint

Capacity is set by the tightest stage. Calculate each stage’s output per hour and compare.

With assumed figures: two deck ovens that each bake 6 loaves in a 25-minute cycle produce 12 loaves every 25 minutes, about 29 an hour at full use. If proofing space can only release 20 loaves an hour, the ovens are not the constraint; the proofer is, and adding oven capacity would change nothing.

Once you know the constraint:

• Keep it running at full capacity during production.
• Time every other stage to feed it, without building up dough that waits and overproofs.
• Spend on capacity at the constraint first; extra capacity anywhere else adds cost without output.

The links after the oven

A schedule that stops at the oven stalls behind it. Three more links have capacities of their own:

• Cooling racks. Every pan out of the oven occupies a rack level for its whole cooling time. If the racks fill before the first pans are cool, the next bake has nowhere to go.
• Packing. Finished product needs people and stations to pack it at the rate the racks release it.
• Trays and dollies for dispatch. For wholesale routes, the number of clean plastic trays on hand at packing time limits how much product can leave. Trays out on yesterday’s routes may not be back in time for today’s packing, so check the tray count against tomorrow’s dispatch, not against the pool you own.

Schedule backward from the deadline

Start from the time product must leave and work back through each stage. With assumed figures: trucks load at 5:00 and loading takes 30 minutes, so packing must finish by 4:30; packing takes 45 minutes, so product must be cooled and ready at 3:45; then subtract cooling, baking, proofing, shaping, fermentation and mixing in turn. The result is the latest start time for each stage. If the calculation puts mixing at a time you cannot staff, the deadline, the product or the process has to change.

Run batches in parallel

Stages must happen in order for one batch, but different batches can overlap: while batch A proofs, batch B mixes; while A bakes, B proofs and C mixes. Draw a simple timeline with one row per station (mixer, bench, proofer, oven, racks, packing) and one bar per batch. Gaps show idle equipment; overlaps show conflicts.

The daily production sheet

Give staff a sheet that leaves nothing to memory:

• Product and quantity: “60 sourdough loaves,” not “sourdough.”
• Batches: batch size and number of batches. Take batch size from the mixer maker’s capacity figure for that dough, not from the bowl’s volume, and ask the maker how flour type changes it.
• Start time for each stage of each batch.
• Equipment: which mixer, proofer shelf, oven and rack.
• Variations: seeded, special orders, labels.

Sequencing rules

• Start the longest processes first.
• Group products by oven temperature, so the oven is not repeatedly heated and cooled between them.
• Bake the products that stale fastest closest to dispatch or opening.
• Give complex shaping to the shift with the skills for it.

When the day does not go to plan

Dough proofs slowly in a cold room, a mixer stops, an order changes. Two things help:

• Slack you set from experience. Compare planned and actual times for a few weeks and build in the slack your own records show you need, at the stages where delays occur.
• Known flex points. Some products tolerate timing changes, such as cookies; others, such as breads with narrow proofing windows, do not. Put the flexible products where they can absorb delays.

The weekly cycle

• Day-of-week demand. Record sales by product and weekday for several months; the weekly pattern is the baseline for production quantities.
• Batching longer-life products. Items that stay fresh for several days can be made in fewer, larger batches. With assumed figures, cookies that keep for 3 days and sell 100 a day could be baked as 300 on Monday and 200 on Thursday in a five-day week, instead of 100 every day. Products sold as “baked fresh daily” have to be.
• Labor from production. Once the production schedule is fixed, calculate labor hours by stage and shift, and plan overlaps for handoffs between shifts.

Forecasting demand

Production quantities come from a forecast, and the forecast comes from sales history: daily sales by product, weekly patterns, month-to-month trends and the effect of holidays and events. Adjust for what you know is coming: local events, promotions, new products. Check how well last week’s forecast matched sales, product by product, and correct the products that miss in the same direction every week.

For products that sell out early, the cost of making too few is lost sales; for products thrown away every night, the cost of making too many is waste. Set each product’s target from those two costs, not from a single rule for the whole range.

Tools

Choose the simplest tool that holds your product list, batch sizes, stage times and forecast. Ask any software vendor to run a week of your real production in a demonstration before you buy.

Do not schedule the oven before the racks

A well-planned bake can fall apart after the oven: racks full, nowhere to cool the next load, no clean trays for dispatch. Before you add a product or a batch to the schedule, check that every link after the oven can take it: rack space, packing capacity and tray count. A schedule that only fits the oven is half a schedule.