Production Scheduling for Industrial Bakery (Bread & Rolls)

This guide shows production planners and operations managers at industrial bakeries how to model bread, roll, and bun production in Schantt and schedule it across parallel mixers, ovens, and packaging lines with sequence-dependent changeovers and split-shift calendars.

This guide follows a fictional composite company built from industry research on industrial bakeries; all names, parameters, and figures are illustrative.

Industry context

Industrial bread and roll production is a classic hybrid flowshop. Dough moves through sequential stages — mixing, dividing and moulding, proving, baking, cooling, then slicing and packaging — with several parallel machines at most stages and products that diverge in routing depending on whether they are sliced or not. Each stage has distinct processing characteristics: mixing is batch work with fixed cycle times and batch sizes, dividing and moulding is continuous flow, proving is a temperature- and humidity-controlled rest period, baking is batch or continuous depending on oven type, cooling is a timed conveyor dwell, and packaging runs as a continuous high-speed flow operation.

A mid-market bakery producing bread, rolls, and buns typically runs on a split-shift model: mixing and baking happen overnight for same-day fresh delivery, while packaging runs during the day after the baked goods have cooled. The oven stage is nearly always the capacity constraint — oven throughput determines how much the plant can produce in a shift, and idle oven time is permanent lost capacity that cannot be recovered later in the week.

The scheduling environment is defined by several tightly coupled constraints. Changeovers on mixers are sequence-dependent, with cleaning times ranging from a quick 10-minute rinse between runs of the same dough family to a full 90-minute deep clean when switching between incompatible allergen groups. Proving times vary by product — white bread needs about 55 minutes, rolls about 30 — and are sensitive to ambient temperature and humidity. The packaging stage presents its own challenges: different product formats use different packaging lines, and changing between formats on the same line takes 15 to 20 minutes for tray and film adjustments. Bakeries operating on a split-shift model must also manage the handoff between the night baking shift and the day packaging shift, with baked goods cooling on conveyors during the gap.

Great River Bakery runs about 60 people at a 3,200 m² facility, making three product classes — white bread, crusty rolls, and soft burger buns — across four production stages, scheduled by a planner and a production manager.

Process overview

flowchart LR
  Mixing["Mixing<br/>(BATCH)"] --> Dividing["Dividing / Moulding<br/>(FLOW)"]
  Dividing --> Baking["Baking<br/>(BATCH)"]
  Baking --> Packaging["Slicing & Packaging<br/>(FLOW)"]

The production flow through a mid-market bakery. Mixing and baking are batch operations; dividing and packaging are continuous flow. The proving dwell and cooling dwell are configured as transfer times between the stages shown above.

Rolls and buns skip the slicing step and go directly to the flow-wrapper within the packaging stage — their route is shorter than the bread route.

Scheduling challenges and how Schantt handles them

The schedule at Great River Bakery is driven by the night-bake, morning-dispatch rhythm — orders arrive during the day, the production plan is built for the upcoming night shift, and finished products leave on trucks by mid-morning. Schantt optimises for minimum total production time, scheduling forward from a start date across a practical horizon of one to two shifts. In Auto mode the algorithm builds the sequence automatically; Semi-Auto mode lets the planner arrange jobs while the algorithm places them on machines and resolves timing.

What Schantt handles well

• Sequential multi-stage scheduling — model the bakery's production flow from mixing through packaging as a connected stage sequence with handoff delays.
• Parallel machines per stage — multiple mixers, ovens, and packaging lines, with automatic job-to-machine assignment.
• Per-class routing with stage-skipping — rolls and buns skip the slicing operation and go straight to packaging; bread follows the full route.
• Sequence-dependent changeovers — directional changeover matrices capture mixer cleaning times between dough and allergen groups, and oven temperature-recovery waits.
• Batch and flow processing in one schedule — mixing and baking are batch operations; dividing and packaging are continuous flow — Schantt handles both simultaneously.
• Calendar-aware scheduling with split shifts — night baking shift and day packaging shift, each on its own calendar, with planned downtime windows.

How Schantt handles each challenge

1. Oven bottleneck.

• The oven stage determines how much the bakery can produce. Three rack ovens with different capacities (18 or 36 trays each) must be fed continuously throughout the night shift, and each product class has a different bake time and temperature.
• Schantt models each oven as a machine on the Baking stage with per-product-class batch sizes and cycle durations — 30 minutes for 36 loaves of white bread, 18 minutes for 216 rolls. The scheduler assigns jobs to the available ovens and sequences them to keep the ovens running while respecting transfer timing from the preceding stages.

2. Mixer changeovers between dough types.

• Switching from white bread dough to rolls, or from plain dough to enriched dough, requires cleaning the mixer bowl, arms, and seals. The cleaning time varies by the dough types involved — a light rinse within the same family takes about 10 minutes, while a deep clean between incompatible allergen groups can take 60 to 90 minutes.
• Schantt models directional changeover times on each mixer. The changeover matrix captures the time penalty for every from-to pair of product classes, so the schedule groups same-family runs together and avoids time-consuming transitions. The planner still sequences the allergen groups correctly — the changeover duration models the cleaning time, while the run order is the planner's decision in Semi-Auto mode or verified in Auto mode.

3. Proving time variability.

• After moulding, dough pieces rest in a humidity-controlled prover for a product-dependent period — 55 minutes for white bread, 30 minutes for rolls and buns. The proving time is sensitive to ambient conditions, but the scheduling system treats it as a fixed minimum dwell.
• Schantt models the proving dwell as a transfer time from the Dividing/Moulding stage to the Baking stage. A conservative 60-minute transfer ensures the dough has adequate time regardless of minor recipe variation, and the schedule chains the oven start to the proving completion.

4. Packaging line contention.

• Great River Bakery has two packaging lines: a bagging line for sliced bread and a flow-wrapper for rolls and buns. Each line runs at a different speed, neither line can run the other's products, and changing between product formats on the flow-wrapper takes about 18 minutes.
• Schantt models both lines as machines on the Slicing & Packaging stage, each with its own throughput rate and its own changeover times. The scheduler assigns bread jobs to the bagging line and roll and bun jobs to the flow-wrapper automatically, respecting the routing constraints defined per product class.

5. Split-shift handoff.

• Baking runs on a night shift (22:00 to 06:00) while packaging runs on a day shift (06:00 to 14:00). Baked goods must cool for about 45 minutes before they can be sliced and packed, and the cooling period bridges the shift boundary.
• Schantt models this with two separate calendars — one for the mixing, dividing, and baking stages, and another for the packaging stage. The cooling transfer time (50 minutes) is long enough that packaging starts shortly after the day shift begins, creating a natural handoff that the schedule resolves automatically.

What to model in Schantt

The table below shows the entities a planner creates for this scenario.

The proving dwell and the cooling dwell are configured as transfer times on the stage detail pages rather than as separate stages — they do not need their own machines or capacity parameters. The two calendars reflect the split-shift operation: the mixing, dividing, and baking stages run on a night calendar (22:00 to 06:00), while the packaging stage runs on a day calendar (06:00 to 14:00). Five calendar exceptions cover non-working days — New Year's Day, International Workers' Day, and a three-day year-end shutdown — and two downtime entries capture planned maintenance on Mixer-1 and Oven-1.

The changeover configuration is the most detailed part of the setup — each mixer has a directional changeover matrix with distinct durations for every from-to pair of product classes. The oven machines also have directional changeovers to account for the temperature-recovery wait when switching between products that bake at different temperatures. The packaging changeovers are simpler: the bagging line only handles a single class, and the flow-wrapper has a single cross-class transition between rolls and buns.

Step-by-step setup

1. Create the stages in order. Set up Mixing (BATCH), Dividing / Moulding (FLOW), Baking (BATCH), and Slicing & Packaging (FLOW) in that order. On each stage's detail page, configure the transfer time to the next stage:

• Mixing → Dividing / Moulding: 10 minutes (dough trough movement)
• Dividing / Moulding → Baking: 60 minutes (proving dwell)
• Baking → Slicing & Packaging: 50 minutes (cooling and depanning)

2. Add the machines to each stage. Ten machines across four stages. Each machine belongs to exactly one stage and has its own capacity parameters and changeover settings.

Mixing (3 machines): Mixer-1 (spiral, 300 kg flour capacity), Mixer-2 (spiral, 200 kg), Mixer-3 (spiral, 100 kg). All three mixers are batch machines — each batch produces a fixed quantity of dough after a set mixing time, and the mixer is unavailable during loading, mixing, and discharge.

Dividing / Moulding (2 machines): Divide-Mould-1 (1,200 pieces/h, for bread loaves), Divide-Mould-2 (3,000 pieces/h, for rolls and buns). These are flow machines — they process dough continuously at a defined throughput rate.

Baking (3 machines): Oven-1 (single rack, 18 trays), Oven-2 (single rack, 18 trays), Oven-3 (double rack, 36 trays). All three are batch machines. Each load of proved dough bakes for a product-specific time before the oven is unloaded and reloaded.

Slicing & Packaging (2 machines): Pack-1 (bagging line for sliced bread), Pack-2 (flow-wrapper for rolls and buns). Both are flow machines with throughput measured in units per hour.

3. Create the product classes and define routings. Create three product classes:

• White Bread — routed through all four stages with no partial transfer
• Rolls — routed through mixing, dividing/moulding, baking, and packaging; the flow-wrapper on the packaging stage handles the downstream packaging
• Buns — same routing as rolls

On each class's detail page, confirm the routing visits the correct stages in order. Disable partial transfer for all product classes — dough is always transferred as a full batch between stages.

4. Add one representative product per class. Create one product for each class:

• Great River White Sliced 800 g → White Bread
• Great River Crusty Dinner Rolls → Rolls
• Great River Soft Burger Buns → Buns

Assign a distinct colour to each product for the Gantt view.

5. Set machine capacity parameters and changeovers. On each machine's detail page, configure the parameters that depend on the product classes created in step 3.

Mixer batch parameters (all three mixers):

• White Bread: cycle 15–18 min, batch size 280–420 kg (varies by mixer)
• Rolls: cycle 14–16 min, batch size 280–420 kg
• Buns: cycle 14–17 min, batch size 280–420 kg

Mixer changeovers (directional on each mixer):
- Same-family change (e.g. white bread to white bread): 8–12 min
- Cross-family change (white bread to rolls or buns): 20–25 min
- Cross-family reverse (rolls or buns to white bread): 22–25 min

Oven batch parameters (all three ovens):
- White Bread: cycle 30–32 min, batch size 36–72 loaves (oven-dependent)
- Rolls: cycle 18–20 min, batch size 216–432 pieces
- Buns: cycle 14–16 min, batch size 216–432 pieces

Oven temperature-recovery changeovers (directional):
- Switching between product classes with different bake temperatures: 8–14 min (modelled as a changeover)

Packaging line changeovers:
- Pack-1 (bagging): white bread to white bread — 8 min (film and date-code change)
- Pack-2 (flow-wrapper): rolls to buns or buns to rolls — 18 min (tray format and film adjustment)

6. Configure calendars, exceptions, and downtimes. Set up the split-shift model.

Night shift calendar (mixing, dividing/moulding, baking): Monday to Friday 22:00–06:00, Saturday 22:00–04:00, Sunday off. Set this as the default calendar.

Day shift calendar (slicing and packaging): Monday to Friday 06:00–14:00, Saturday 06:00–12:00, Sunday off.

Calendar exceptions (team-wide): New Year's Day (Jan 1), International Workers' Day (May 1), December 24–26 year-end shutdown — all non-working.

Machine downtimes: Mixer-1 deep clean and calibration, and Oven-1 seal inspection and thermocouple calibration, each set as an 8-hour window aligned with a full night shift. In practice these downtimes recur on a regular cycle — the example dataset shows one instance of each to illustrate the pattern.

For step-by-step instructions on configuring each of these in Schantt, see the Schantt documentation.

Common mistakes

1. A single blanket changeover for all mixer transitions. A single cleaning time for every mixer changeover ignores the large difference between a same-family rinse (10 minutes) and a cross-family deep clean (60 minutes or more). The schedule may propose an efficient but unworkable sequence if the changeover time does not reflect the actual cleaning effort.
Fix: Enter a directional changeover matrix on each mixer with distinct durations for every from-to product-class pair, especially between dough families that require full wash-down.

2. One product class covering both bread and rolls. Combining all baked goods into a single product class with a single routing masks the fact that rolls and buns skip the slicing step and use a different packaging line.
Fix: Create separate product classes for bread, rolls, and buns, each with its own routing. Bread visits all stages; rolls and buns visit the packaging stage through the flow-wrapper machine.

3. A single calendar for all stages. If baking and packaging use the same calendar, the schedule may show packaging activity during the night shift (when no packaging staff are present) or baking during the day shift (when ovens are idle).
Fix: Assign the night shift calendar to the mixing, dividing, and baking stages, and the day shift calendar to the packaging stage. The cooling transfer time bridges the gap between the two shifts naturally.

4. Overlooking oven temperature-recovery times. When the schedule jumps from white bread at 210 °C to rolls at 230 °C, the oven needs time to reach the new temperature. Without a changeover entry for this penalty, the schedule may pack oven cycles back-to-back with no recovery gap.
Fix: Add directional changeover entries between product classes on each oven to capture the temperature-recovery wait — 8 to 14 minutes depending on the temperature delta.

5. Entering a full cross-product throughput matrix. Assigning a throughput value for every product class on every packaging machine creates unnecessary setup work and may suggest routing paths that do not exist.
Fix: Enter throughputs only for the (product class, machine) pairs the routing actually uses — white bread through Pack-1, rolls and buns through Pack-2. Leave unused machine-class combinations empty. The same principle applies to the mixer batch parameters: not every mixer handles every product class at the same batch size, so enter only the combinations your routings require.

6. Setting proving and cooling as batch stages with machines. If proving or cooling are modelled as their own stages with machines and capacity constraints, the schedule gains unnecessary complexity — proving trays and cooling conveyors typically have adequate capacity at mid-market scale and do not constrain the schedule.
Fix: Model proving and cooling as transfer times on the stage detail pages instead. The transfer time captures the needed dwell without adding a constrained stage, machines, or capacity parameters. Reserve a separate stage only for proving or cooling when the physical tray or conveyor positions are genuinely finite and regularly saturated.

What a good schedule looks like

A well-built schedule for an overnight bakery run shows the ovens running continuously from shift start to shift end, with mixer cleaning breaks grouped between dough-family transitions and packaging starting about an hour into the day shift after the baked goods have cooled. The schedule respects the directional changeover matrix so that long-duration transitions (deep cleaning) happen only when necessary, and oven temperature-recovery waits are accounted for between product groups that require different bake temperatures.

Before (spreadsheet): The planner manually assigns products to mixers and ovens, tries to group same-dough-type runs together to minimise cleaning, and then adjusts when an oven finishes earlier or later than expected. If a roll run finishes 10 minutes early and the next bread run needs a different oven temperature, the oven sits idle for the recovery period. The schedule is rarely stable enough to share with the dispatch team before mid-morning, and the packaging team often arrives to find no clear plan for which products to run first.

After (Schantt Semi-Auto mode): The planner arranges the job sequence in a logical dough-family order — all white bread runs first, then rolls, then buns — to minimise temperature transitions on the ovens. Schantt assigns each job to the best available mixer and oven, respects the changeover matrix to insert the correct cleaning durations, and chains the timing through proving and cooling so packaging starts promptly on the day shift. The schedule is available by the time the day shift starts, and the packaging team sees their jobs lined up and sequenced as soon as they arrive. The planner can also run the schedule in Auto mode to see what the algorithm proposes without any manual arrangement, then switch to Semi-Auto to adjust the sequence if a specific customer order needs to leave earlier than others.