Match the Scheduling Mode to the Disruption State

A line goes down mid-morning. In one plant the planner regenerates the whole schedule; the algorithm rebuilds everything from scratch, including work the floor had already committed to, and the schedule stops being a commitment. In the next plant the planner hand-edits row by row, because the tool "cannot be trusted" to change anything, and spends the rest of the shift re-entering a schedule that a single rebuild could have produced in one pass. Neither planner is careless; each reached for the only response the tool offered.

The right planning response depends on the disruption state: what kind of change hit, and how much of the schedule it leaves binding. The method should follow that state, not habit.

The one-method trap

Spreadsheet planning has no capacity-aware rebuild; every change is a hand-shifted row, fine for a small adjustment and exhausting for a broad one. The opposite habit does as much damage: rebuilding the weekly schedule from scratch whenever a breakdown or a new priority job arrives, which moves work the plant wanted to leave alone. One approach cannot rebuild at all; the other cannot leave anything in place.

At the moment the schedule needs to change, the planner either works around the tool or accepts a schedule the floor does not recognize. The planner is not being stubborn: a tool with a single planning response applies it to every situation, even when it does not fit.

When a plant's disruptions differ in kind, a one-method tool leaves the planner fighting it exactly when the schedule needs to change.

Match the scheduling mode to the disruption state

A change can be met three ways: rebuild the schedule; hold the production sequence and re-time around the change; or hand-author a committed adjustment. Which one fits depends on the nature of the change, and there is no universal best response.

Known in advance or sudden, committed or free: those distinctions decide the response.

That matching is a heuristic the planner exercises, not a rule the tool enforces.

The axis: how much of the schedule is still binding?

Entered before the schedule is built: nothing is binding yet

A planned maintenance shutdown and a seasonal capacity shift are both known ahead of time. That alone does not free the schedule. A shutdown noticed only while the affected week is being built forces last-minute re-planning around work that is already committed. It is foreseeable and disruptive at the same time. What frees it is entering the change before the schedule is generated: add the calendar exception or the downtime window first, and nothing has been committed against the new conditions. For a broad change entered in time, a factory-wide shutdown or a switch of working regime, a full rebuild is simply the right response.

Sudden: the sequence stays put

A breakdown or a supply gap lands on work that is already set. The sequence is committed: downstream machines are loaded, the floor knows what comes next. Rebuilding from scratch discards that commitment. Holding the production sequence and re-timing around the newly entered outage keeps the schedule recognizable: the arrangement of the work survives, though machine assignments and timings are recomputed across it. Where the planner wants one specific adjustment rather than an optimized one, hand-authoring gives exact control: no optimization runs, the planner supplies the timing, and a Manual update applies only the rows the planner changes.

Holding the sequence trades some optimality for stability. Full regeneration remains the right response for broad changes.

Entering the change

The planner enters the change as a modeled capacity change. For the planned shutdown, that is a calendar exception or a downtime window, subtracted from working capacity before scheduling. A seasonal regime takes a different calendar per date range, with the working hours the planner's own input, and a re-run when the regime changes. A supply gap takes a downtime window, a calendar exception, or per-job quantity edits, and in Semi-Auto earliest-start edits; the gap is a capacity change the planner enters, not something the system rebalances. Then the planner re-runs the schedule and picks the mode. Nothing detects anything; the planner is always the trigger.

Three responses, three modes

Auto mode: rebuild freely

The planner supplies the jobs without a production sequence, and the algorithm decides the sequence, the machine assignments, and the timing. This is the build-from-scratch response, for the moments when nothing is binding.

Semi-Auto mode: hold the sequence, re-optimize within it

The planner fixes the production sequence. The algorithm preserves it exactly and optimizes machine assignment within it, re-timing around the newly entered outage; a per-job earliest start, when used, applies at the job's first required stage. Semi-Auto mode never reorders the sequence, which is what makes it the sequence-hold response.

Manual mode: hand-author a committed adjustment

The planner enters the full schedule row by row, and no optimization runs. Schantt validates routing, machine compatibility, position rules, and calendar constraints, then stores the authored schedule. This is the committed-adjustment response, and it means editing the rows that moved: a Manual update applies only the rows the planner changes or deletes, and the rest of the schedule keeps its existing values.

Schantt enforces no state-to-mode rule; the matching is the planner's call. Downtime and exception bands carry their reason and category on hover, so the planner can see why timing moved before choosing a mode.

Make the mode a decision, not a default

For buyers: evaluate a scheduling tool by which planning responses it offers and whether the planner can choose among them per state, not by whether it produces a schedule at all.

For planners: before the next re-run, name the disruption state. How much of the schedule is still binding? Then pick the mode deliberately.

Take three questions to the next planning meeting. Which disruption states does this plant actually hit? For each, what has the response been, and was it chosen or habitual? What would it take to make the mode a conscious step in the change workflow?

The schedule will change anyway. The question is whether the tool changes with the state, or the planner fights it.