How a Reschedule Protects Completed Work in EDGEBIC

A reschedule in EDGEBIC never moves work that is already done: completed operations keep their actual dates, wear the completed shade, and the engine re-plans only the steps that have not started, fitting them around the history the floor recorded. EDGEBIC by User Solutions builds this guarantee into the core of rescheduling, because the fastest way to lose a shop's trust is to rewrite what already happened. This post explains how completed work is protected, how you read it on the Gantt, and how to unwind a completion recorded in error.

The visual scheduling pillar guide covers reading the chart; here we focus on the one promise that makes rescheduling safe.

History Is Fixed, the Future Is Flexible

Every operation on the Gantt is either something that happened, something happening, or something still ahead. A reschedule respects that difference absolutely. When you press Re-Schedule, the engine:

• Leaves completed steps alone. Operations with actual dates are history, and history does not move.
• Resumes from where the job actually is. The remaining steps are planned to start after the last completed step, not from an idealized start that ignores reality.
• Re-plans only the future. Unstarted operations get a fresh, feasible placement around the actuals and around current capacity.

The result is a schedule that is honest at both ends: the past matches what the floor did, and the future is a clean plan built on that foundation. This is the difference between a schedule you can trust and a drawing that resets itself every time you touch it, and it is a core reason finite capacity scheduling earns a shop's confidence.

Reading "Done" on the Gantt: the Completed Shade

Completion has its own visual, and it is deliberately unmistakable. When the whole job or an individual operation is complete, EDGEBIC paints an opaque completed shade over the bar. That shade sits on top of whatever state color the bar carried, so a finished operation reads as done at a glance whether it was Applied, Rescheduled, or anything else.

The shade is a background fill, not one of the ordinary color states. The caption and borders still render, so you can still identify the operation and read its label; the shade simply overrides the state color to say "this is history." Because it is evaluated from the job's and the operation's completion facts rather than stored as a color, completing or reopening a job repaints the shade live on an open Gantt. For the full state vocabulary that the shade sits above, see colors and labels on the EDGEBIC Gantt.

What "Protected" Means in Practice

Put the two ideas together and the protection is concrete. A job three steps into a five-step routing has three shaded, completed bars and two ordinary ones ahead. A machine the job needs goes down. You reschedule.

1. The three completed bars do not move. Their actual dates and completed shade are exactly as before.
2. The two remaining steps re-plan to start after the last completed step and around the machine outage.
3. The job now has a fresh, feasible finish date built on real history, with not one recorded hour rewritten.

You got a new plan for the future without disturbing the past. That is what planners mean when they say a reschedule is safe to run on a live job.

Holding a Step by Hand

The engine protects completed work automatically, but sometimes you want to guarantee that a specific operation stays put during your own editing, even one that is not yet complete. The right-click menu's Lock Single Operation Segment in Current Position does exactly that: it protects the segment so your other drags and any automatic re-sequencing leave it alone. Lock the operation you need fixed, rearrange everything around it, and release the lock later if it ever needs to move. It is the manual counterpart to the automatic protection completed steps already enjoy.

One more bar is always immovable: the display-only lead-time tail at the end of a job. It represents information rather than work, so it cannot be dragged, resized, or edited at all.

Unwinding a Completion Recorded in Error

Because completion is powerful, EDGEBIC makes it reversible. If a step was marked done too early, you have two clean paths back to an editable state:

• Reopen the job from the Job View tab, which lifts the completed shade and returns the job to an in-progress state.
• Clear the actual dates from the right-click menu. Clear Operation Actual Start and End Date/Times removes the actuals that made the operation read as complete and returns the bar to its engine-planned position.

Either way, the operation stops being treated as history. Once it is no longer flagged as done, the next reschedule plans it as future work, in proper sequence with the rest of the job. The protection is strong, but it is never a trap: a mistaken completion is a few clicks from corrected.

Why This Guarantee Matters

Schedules that quietly rewrite completed work are the reason many shops stop trusting their planning system and go back to a printed sheet. If pressing a button might move the step your operator finished this morning to some other slot, you learn not to press the button. EDGEBIC removes that fear by making the rule absolute: a reschedule re-plans the future and never the past. The completed shade shows you which bars are locked in by history, the lock item lets you fix others by hand, and the reopen and clear-actuals paths keep the whole thing reversible when a completion was wrong.

That combination, automatic protection for finished work plus manual control for everything else, is what lets a planner reschedule a live plant as often as reality demands. For the deeper mechanics of what a reschedule preserves and what it moves, the drag-and-drop rescheduling walkthrough carries the story forward.

See the full EDGEBIC platform, or bring a half-finished job to a demo, reschedule it around a fresh disruption, and watch every completed step stay exactly where the floor left it, with US.