Save vs Re-Schedule: Two Different Buttons on the EDGEBIC Gantt

Save and Re-Schedule are two different buttons on the EDGEBIC Gantt that answer two different questions: Save records the dates you dragged without re-checking capacity, while Re-Schedule re-plans only the jobs you touched around those changes. EDGEBIC by User Solutions keeps them separate on purpose, and understanding the split is the single most useful thing a new planner can learn about the interactive schedule. This post draws the line clearly and shows the two-step that handles a real disruption.

The visual scheduling pillar guide covers the Gantt broadly; here we settle the one distinction that trips people up.

Save Records. It Does Not Re-Plan.

When you drag a bar and press Save Changes, EDGEBIC writes the dates you chose to the database. That is the entire action. It does not re-run the scheduling engine, and it does not re-check whether the machine has room. The bar moves from its pending Overridden state to a committed state that records what you did, and the job's later steps do not move on their own.

This is deliberate, and it is the platform's override-and-warn contract. You can drop a bar onto an already-busy afternoon; EDGEBIC warns you about a questionable move but does not block it, and the save records your decision as fact. You are the planner, and sometimes you know something the calendar does not. Save is where your judgment becomes the recorded plan.

What Save gives you:

• The operation's new dates, committed and auditable.
• A state color recording the kind of change (a time move, a machine swap, an actual start, or a planned pin).
• Nothing else moved, and no capacity recomputed.

Re-Schedule Re-Plans, and Only the Jobs You Touched

When you want the engine to actually re-plan around your change, that is Re-Schedule, a separate button with a very different job. It runs the scheduling engine to re-plan the jobs you manually changed, fitting their remaining steps around your edits and around current capacity.

Two properties make it safe to press:

• It is targeted. EDGEBIC remembers which jobs you edited since the last reschedule and re-plans only those. Every other job in the plant stays exactly where it was, so one machine swap does not scramble forty unrelated jobs.
• It preserves history. Inside the jobs it re-plans, completed steps do not move; only the unstarted steps are re-planned around the actuals you recorded. The past stays fixed while the future re-fits.

Re-Schedule is where the engine takes your committed decision and turns it into a feasible forward plan. It is the "now clean up around what I did" step.

The Two-Step for a Real Disruption

Put them together and a disruption has a clean, two-move recovery:

1. A machine goes down. You drag the affected operation to its new slot, or onto an alternate machine, and press Save Changes. Your decision is recorded. The job's later steps flag as Downstream Changed, a review signal that they may now be out of sequence.
2. You press Re-Schedule. The engine re-plans the job's remaining steps around your move, honoring completed work and current capacity. The downstream flags clear on reload, and the plant beyond that job is untouched.

Save then Re-Schedule. The first records what you decided; the second makes the rest of the job consistent with it. Skip the second step and the later operations sit where they were, which is exactly why a downstream flag appears: it is EDGEBIC telling you the re-plan is still pending. This is the standard advanced-planning rhythm, a manual override followed by a targeted re-plan, and it is at the heart of practical job shop scheduling.

Why Not Just Re-Plan on Every Save?

It is a fair question: why not have Save re-run the engine automatically? Because that would take a decision away from the planner at the exact moment they are making one. Sometimes you save a move precisely because you do not want the engine to touch it yet; you are staging a set of deliberate changes and will re-plan once, at the end. Auto-rescheduling every save would fight that, snapping your careful placements around before you finished. Keeping the two separate means you decide when the engine gets a turn.

It also keeps the override-and-warn promise honest. If Save always re-planned, it could quietly undo a knowing overload you meant to keep, because the engine would try to make everything fit. By recording your dates as-is and leaving the re-plan to an explicit button, EDGEBIC lets you hold a deliberate override and only invites the engine in when you say so.

Confirming a Manual Move Was Feasible

Because Save does not check capacity, planners reasonably ask how to know a manual move actually works. Two checks close the loop:

• The warning at save time. A genuinely awkward drop triggers an override-and-warn message, so an obviously infeasible move does not pass in silence.
• The resource load view after Re-Schedule. Once you re-plan, open the resource load view. If the machine you loaded now shows a bar over 100 percent, the engine could not make the remaining work fit, and you have an overload to resolve. If every bar is under the line, your move fit.

Save records your intent, Re-Schedule tests it against finite capacity, and the load bar reports the verdict. That sequence turns a hopeful drag into a confirmed plan.

The One-Sentence Rule

If you remember nothing else: Save records dates, Re-Schedule re-plans jobs, and capacity is only ever re-checked by the engine. A planner who internalizes that never again wonders why saving a move did not fix the downstream steps, or why the machine still looks overloaded until the reschedule runs. The two buttons are not redundant; they are two halves of how an interactive, finite-capacity schedule stays both flexible and honest. For the staging that happens before either button, see Save and Discard, and for the drag modes that decide what a save records, see drag-and-drop rescheduling. For what the board does after either button, patching only the changed bars or refetching the whole chart, see how the EDGEBIC Gantt refreshes after a change.

See the full EDGEBIC platform, or bring a disrupted schedule to a demo and run the Save-then-Re-Schedule two-step on a live job with US.