A bakery production schedule: oven time, labor and peak demand

Start with the product release time

A bakery can have spare oven capacity and still miss its best selling window. A loaf that emerges after the commuter peak has a different chance of sale from one already cooled and displayed when the door opens. A daily revenue forecast hides that timing. For each product, write the latest display-ready time and work back through cooling, bake/reset, proof, shaping and mixing.

Use a first-wave quantity supported by actual time-slot sales or preorders, then reserve a later wave if needed. The reference case uses carryout pan bread, sweet buns and cookies; it has no café receipts or wholesale shipments. Its six-day retail pattern and menu are assumptions. The schedule is a production-planning example, not a measured customer arrival pattern.

A release target is also a quality gate. Do not put an uncooled loaf into a wrapper merely to meet an opening time, or hold a temperature-sensitive product outside the approved process. FDACS describes the applicable Florida food-permit/process boundary; an actual menu needs site-specific review.

Turn the menu into oven occupancy

Ten slots for three hundred minutes give three thousand theoretical tray-minutes. The model keeps 85.0% available, leaving 2,550. The reference uses 65.5% of that allowance. The maker and seller establish 25 kW connection and the rack configuration; they do not certify forty-five-minute pan-loaf cycles or a particular loaf arrangement. Manufacturer specifications; double-deck configuration.

Using two independently controlled sections can separate bread from a cooler cookie/bun sequence. Whether a real section produces five evenly baked trays at once is a recipe and spacing test. Aggregate minutes should be followed by an actual cavity-by-cavity plan, with temperature changes and maintenance room.

A worked oven-wave plan

The exhibit accounts for all forty bread/bun trays and ten cookie trays. It deliberately exposes a weakness: the final waves finish after a seven o'clock counter opening, and cooling adds more time. If local demand is concentrated at opening, move preparation earlier, change the wave quantities or restrict the morning promise. Do not “fix” the forecast by calling an oven exit time a sale time.

This is not a complete critical-path schedule. It illustrates cavity occupancy, while the next tests determine whether each load can be ready. An owner should trial the recipe and write the actual start/finish times before adopting the proposed windows.

Add paid people and dough-space gates

The paid owner supplies six production hours a day; the baker supplies another six and the assistant five under the stated weekly roster. Three shared hours are held out for setup, cleaning and nonrecipe work, leaving fourteen hands-on recipe hours. The planned 9.8 hours fit that envelope. It does not mean all workers can perform every task or that leave coverage is free.

At the assumed dough weights, bread needs four conservative forty-five-pound spiral loads and buns one more; each uses twenty minutes including resetting. The cookie mixer needs two fifteen-pound loads. These are integer cycle counts. The SM40 listing supports a fifty-six-pound nameplate dough capacity, while the smaller usable load is our assumption pending a hydration/duty test.

Proofing is another shared queue. The cabinet listing has closely spaced slides; the model uses eighteen tall-pan places, not thirty-six tall loaf-pan positions. Bread needs sixty assumed proofing minutes per tray and buns forty-five. Do not schedule every proof simultaneously or put tall tins into the clearance for flat sheets. Proofer scope.

Next, assign each person a timeline. Record who mixes while the other shapes, who checks an oven when both are handling dough, and who can cover a late customer. An activity that requires two people must occupy both calendars. BLS's description of early/weekend shifts is occupational context; it does not validate this roster or its wages. BLS.

Validate demand by release wave

During a trial week, log product availability and customer requests in consistent time slots. Record stockouts separately from sales so that missing stock does not masquerade as low demand. Record unsold late batches by batch ID, not just total till revenue. Compare the first wave, midday replenishment and closing stock at the same price and weekday.

Raise the next wave only when the extra units can be sold and the labor/proofing sequence fits. A frequent early stockout with little closing waste can support a larger first wave. A late cabinet full of bread suggests moving or reducing a batch, even when oven utilization looks efficient. The model's sale-through fractions are starting hypotheses that these observations should replace.

Review the plan weekly with three questions: which release missed its target, which constraint caused the delay, and which batch was still unsold at closing. Adjust one identifiable bottleneck or quantity at a time so the next measurement explains the effect.