How to See Who Changed a Schedule in EDGEBIC

To see who changed a schedule in EDGEBIC by User Solutions, open the job audit trail from the Job Audit button on the Job View tab, or by right-clicking an operation's bar and choosing View Audit Trail. It lists every scheduling event for the job, newest first, each carrying a type, a timestamp, an actor, and, where they apply, the dates before and after the change. It is the thirty-second answer to "what moved and why" before a customer asks.

Every reschedule leaves one of these events behind, which is one of the golden rules covered in rescheduling explained. This post is how to read the record.

Before You Start

Step 1: Open the Audit Trail

Two routes reach it.

The report opens with the newest event at the top and the original scheduling run at the bottom.

Step 2: Read the Event Types

Each row is a state transition. The types you will see:

The trail captures when a job moved or changed state. It does not log every keystroke. For the value-level history of a particular day's hours, use View History inside the Log Actuals dialog, which carries old value, new value, author, and reason for each edit.

Step 3: Read the Before-and-After Dates

The most useful rows carry both the old and new dates. A date-override event from a manual drag records the old start, new start, old end, and new end, so you can measure the slip exactly rather than estimating it. A reschedule event shows the job's dates before and after the run. Pair a reschedule event with the actual that triggered it and you have the reason a promise date moved.

Step 4: Read the Actor With the Right Expectation

Every event names an actor. On a shared server that actor is the Windows account the application runs under, which is often a service account rather than the individual planner. For genuine per-person attribution, the operator name on shop floor punches is the dependable identity, because operators type their own name when they start a terminal session. So: the audit trail tells you which process made a scheduling change; the punch history tells you which operator recorded a given actual.

Distinguishing an Order Event From a Step Event

Some events belong to the whole order (marking the job complete, reopening the order) and some belong to a single operation (a drag, an operation completion). The trail distinguishes them, so filtering to step-level events answers "which operations moved" while the order-level events answer "when was the job closed or reopened." Closing the order is covered in how to mark a whole job complete.

How to Check It Worked

The audit report opens with the job's events in reverse chronological order. Confirm the newest event matches the change you just made: a drag you saved appears as a date override with the dropped position, a reschedule you ran appears as a reschedule event with old and new dates, a completion appears as a closed event. For a per-day edit, cross-check the Log Actuals View History for the same operation and confirm the old value, new value, and your reason are all present.

Common Mistakes

• Expecting the trail to log every actuals edit. It records state transitions. Per-day value edits live in the Log Actuals history instead.
• Reading a work-center swap's timestamp as the drag time. The swap is applied on the next reschedule, so its timestamp is when that run happened, not when you dragged the bar.
• Trusting the actor as an individual on a shared server. It may be a service account. Use the operator punch name for person-level attribution.
• Concluding a completed step moved without checking the dates. Usually the actual start and end are identical before and after, and what changed was a paired row or the display window.
• Looking only at the newest event. The story is in the sequence. Read from the original scheduling run upward.

Next Steps

When the trail shows a job jumped further than expected, why did my job jump after a reschedule explains the resume point. When dates in the trail look wrong at the source, how to correct a wrong actual date is the fix. For regulated shops that need the trail as evidence, audit-ready scheduling covers the broader picture.

Every task in this library is indexed on the EDGEBIC how-to hub. Bring a job with a disputed ship date to a demo of EDGEBIC and we will read its history together.