How to Run the Reschedule History Report in EDGEBIC

The Reschedule History report in EDGEBIC by User Solutions is the "who moved my job and why" report: it lives in the Reports hub under Supervisor / Planner, takes a date range, and lists every reschedule event with the old and new dates, the days moved, the actor, and the reason. After a Gantt drag or an automated scheduler run, the trail is here rather than in anyone's memory. Here is how to run it and read it.

For the wider report catalog, see EDGEBIC reports explained, and for the discipline of rescheduling safely, how to reschedule safely. Every task in this library is mapped on the EDGEBIC how-to hub.

Before You Start

• Reschedules have happened in the window you are asking about. An empty window returns an empty report.
• Audit logging was active when the events occurred. Events before logging shipped are not recorded.
• Planners are entering reasons at reschedule time if you want the reason column to carry weight.

Step 1: Open It and Set the Window

Open Reports and click Reschedule History in the Supervisor / Planner group. Set From and To in the range dialog, then OK.

Match the window to the question. A single suspected week to answer "why did this slip". The last 90 days to find your most-moved jobs. The full life of a job when you are reconstructing a story for a customer or an audit.

Step 2: Read One Event

Days Delta is where you start. Positive means later, negative means earlier, and its size is how much the customer-facing date moved. Sorting by it descending puts the biggest slips at the top.

Step 3: Understand the Actor Column

The actor tells you whether a person or the engine moved the job. A named actor points at a manual action, usually a drag on the Gantt. A scheduler-run actor points at an automated replan that recomputed the dates as part of a larger run.

That distinction changes the next question. A manual move has a person who can explain it. An automated move has a cause in the plan, usually a capacity constraint, which you chase in the work center utilization report rather than by asking around.

Step 4: Group by Job to Find Instability

For the "which jobs churn" question, group the grid by job number: right-click the job column header and choose the group option. Jobs with the most rows underneath them are the most frequently rescheduled.

One thing to know about the row count. A single reschedule can generate one row per operation it touched, not just one row per job, so the grouped view counts every step move. That is the correct view of instability, because a job whose every step gets shuffled each week is genuinely unstable even if it eventually ships.

Step 5: Cross-Reference and Export

Take the most-moved jobs into the late jobs report. A job that both churns and lands late is your priority; a job that churns but still ships on time is noise you can leave alone.

To answer a customer or feed an audit, filter to the one job number and click Export to PDF. The days delta and reason columns together are the narrative, and a dated export is what makes it evidence rather than recollection. Export mechanics are in how to export a report to Excel.

What Changes When You Run It

Nothing. The report is read-only and queries fresh each time. It records history; it never makes any.

How to Check It Worked

Two quick checks confirm the read. First, the event count should look plausible for the window; a busy replanning week that shows two events means logging was off or the window is wrong. Second, if a row shows blank old and new dates, that particular event has a malformed record behind it and its dates could not be recovered. A whole column of blanks points at a data problem worth raising rather than a report to keep reading.

Common Mistakes

• Expecting pre-logging history. Events before audit logging shipped are gone. The report builds forward, not backward.
• Reading a blank reason as no cause. The reason is entered by hand at reschedule time. A blank means nobody typed one, not that nothing happened.
• Miscounting instability by job. A grouped count includes per-step rows, which is the right measure of churn even though it is larger than the count of distinct reschedule actions.
• Treating an automated move as a mystery. A scheduler-run actor has a cause in the plan. Chase it in the capacity reports, not by asking colleagues.

See how the plan behind these moves stays stable, and why completed work is never touched by a reschedule, on the EDGEBIC product page.