How to Keep Today's Schedule From Changing in EDGEBIC

To keep today's schedule from changing in EDGEBIC, leave today's jobs out of your selection when you reschedule, log actuals so started and completed work is locked, and use planned-start pins to hold future positions. EDGEBIC by User Solutions scopes every run to the rows you tick, so an unselected job keeps its plan and its reserved capacity. There is no global freeze switch. Stability is a matter of selection discipline plus prompt actuals.

This is the near-term stability procedure. For the wider habit, read keeping schedules stable week to week; for the mechanics, how EDGEBIC reduces schedule churn goes deeper. It is one of the task guides in the EDGEBIC how-to hub.

Before You Start

The Three Guards

Near-term stability rests on three independent protections. Use all three together.

1. Do Not Select Today's Jobs

Scope comes from the rows you tick. When you replan future work, tick only the future jobs and leave today's rows unticked. Unselected jobs keep their exact dates and their reserved hours, and the jobs you do replan are placed around them. Do not answer yes to the Schedule All Orders prompt, which pulls everything in.

2. Log Actuals to Lock Started Work

An operation with a recorded actual start and end is historical fact and never moves. A started operation keeps its machine, and only its remaining hours can be replanned. Logging actuals promptly is the strongest single guard on the near-term plan, because it converts "please do not touch this" from a hope into a locked record.

3. Pin Future Positions You Want Held

For a future operation you need to stay put, drop a planned-start pin using the Planned Start drag mode on the Gantt. The pinned operation is placed on its pinned date and work center like an actual would be, and it dissolves honestly once a real start is logged. That holds a position across reschedules without faking shop-floor history.

What Changes When You Run

How to Check It Worked

1. Pick a job scheduled for today that you did not select. Compare its Start Date and Item Start before and after the run. They must be identical.
2. Open a running job in Job View and read the hours header. Actual Hours must be unchanged; the reschedule may only move planned timing on unstarted steps.
3. On the Gantt, confirm your pinned operations still sit on their pinned dates in their pinned work centers.
4. Press Job Audit on a today job. If you protected it correctly, it carries no new reschedule event.

A Typical Near-Term Protection

Say it is Wednesday mid-shift and you need to slot three new rush orders into next week without disturbing anything running today. The floor is halfway through two jobs, and four more are queued to start Thursday and Friday.

First, get actuals current on the two running jobs. That single act locks their started operations to their machines and freezes anything already completed, so no reschedule can touch them regardless of what you do next.

Then tick only the three rush orders and press Schedule + Re-Schedule. The four Thursday and Friday jobs are unticked, so they keep their exact start dates and their reserved hours, and the rush orders are placed into whatever capacity is left around them. If one of those Thursday jobs has a future operation you specifically need held on its machine, drop a planned-start pin on it first, and the pin survives the run.

The result is three new jobs planned, six existing jobs untouched, and a shop floor whose near-term plan reads exactly as it did before you started. That is stability by discipline rather than by a global switch.

Common Mistakes and Gotchas

• Answering yes to Schedule All Orders. That prompt appears only when nothing is ticked, and yes pulls today's jobs into the run. Answer no and tick only the future rows.
• Rescheduling before logging. If the floor has moved on and nobody logged it, the remaining steps resume from stale reality and today's work can shift. Log first, replan second.
• Faking an actual to hold a future position. A fake actual start invents shop-floor history that will not reconcile later. Use a planned-start pin, which is designed to hold and then dissolve.
• Expecting a freeze setting. There is no user-facing freeze window in the current release. The three guards above are how you protect the near term today.

To hold a future position properly, see how to change the drag mode on the Gantt, and to replan only what genuinely changed, how to reschedule only the jobs that changed.

Bring your current plan and we will show you how to replan next week without disturbing today, against your data. Contact US to book it, or read the EDGEBIC product overview first.