How to Set How Partial Completions Are Handled in EDGEBIC

To set how EDGEBIC handles partial completions, open Settings, go to the Schedule tab, and choose under Partial-Confirm Behavior: trust the operator's actual end, forward-shift the remaining hours, or trust unless the step is flagged short. The policy in EDGEBIC by User Solutions decides what the engine does with the gap when an operation is marked finished but logged fewer hours than planned, and it is read fresh on the next scheduler run.

This post covers the one policy. For the full scheduling rulebook it belongs to, read how to configure scheduling policy in EDGEBIC; the full task library is at the EDGEBIC how-to hub.

Before You Start

• You can reach the Settings tab, which is permission-controlled.
• You understand a short confirm: an operation marked finished with fewer logged hours than planned.
• You know that whichever policy you pick, completed operations never move; the policy only governs future work.

The Steps

1. Open the Settings tab and select the Schedule tab.
2. Find Partial-Confirm Behavior and choose one:
   • Trust the operator's Actual End: the finish stamp is final; the missing hours are written off.
   • Forward-shift the remaining hours (the default): the gap between planned and logged is re-planned on a future slot, and downstream steps queue behind it.
   • Trust Actual End unless the step is flagged short: trust the stamp everywhere except on routing steps individually flagged for strict tracking.
3. Click Save. The status line confirms it.
4. Run the scheduler (or reschedule) so the new policy takes effect.

What Changes When You Save

The choice changes where the next reschedule places downstream work after a short confirm. Trusting the stamp pulls downstream work earlier, because the shortfall is written off and the operation is treated as done. Forward-shifting keeps the unfinished hours visible in the plan, so downstream work queues behind the re-planned remainder. The hybrid lets you make that decision per routing step instead of once for the whole site.

The policy matters most in the end-of-day reschedule, when a shift's short confirms all land at once. If you run an evening reschedule to reflect the day's production, the choice here decides whether tomorrow's plan absorbs the shortfalls or writes them off. Forward-shift keeps the unfinished hours in view so tomorrow queues behind them, which is the honest picture in a shop where operations sometimes need more time than logged. Trust pulls tomorrow's work earlier, which suits a shop where the operator's close-out is the final word and there is no rework to worry about. Pick the one that matches how your floor actually reports, and keep it stable so the plan reads the same way night after night.

How to Check It Worked

Short-confirm one operation (log fewer hours than planned and stamp the end), then reschedule and read the plan. Under trust, the operation shows no remaining hours and downstream work moves up. Under forward-shift, a fresh future slot appears for the leftover hours and downstream work sits behind it. If the plan does not reflect your policy, confirm you saved the setting and ran the scheduler afterward; the policy is read at run time, not at save time.

Common Mistakes

Expecting the policy to move completed work. It never does. Only future work is re-planned. Completed operations are immutable.

Changing the policy but not rescheduling. The policy is read on the next run. Until you reschedule, the plan still reflects the old behavior.

Choosing trust in a shop with rework loops. Trusting the actual end writes off the shortfall. If operations routinely need more time than logged and that time matters, forward-shift keeps it honest.

Setting the hybrid without flagging anything. Trust Actual End unless the step is flagged short behaves exactly like plain trust until you flag the steps that should forward-shift. Flag the exceptions or the hybrid does nothing different.

What to Do Next

Partial-Confirm Behavior is about what the engine does with a short confirm; recording the short confirm itself is a separate task. How to record a partially finished operation in EDGEBIC covers the logging side. For how reschedules preserve finished work while re-planning the rest, EDGEBIC rescheduling explained is the overview, and the EDGEBIC product page shows the scheduler this policy feeds.