A delayed project does not mean its completed work happened later. Before moving a plan forward, separate the historical record from the work that still needs a new place in the schedule.

Prepare a copy of a Project desktop for Windows file using automatically scheduled tasks. For a small trial, include one completed task, one partly completed task and one not yet started. Record each task's actual start, actual finish where applicable, and remaining work or duration. Use fictional progress for the trial rather than inventing history in a live plan.

Choose the operation for the unfinished portion

Microsoft documents Project, Update Project, Reschedule uncompleted work to start after. Set the intended future cutoff and inspect the operation's scope before applying it to the practice file. This rescheduling keeps actual dates in place. Move Project is a separate operation with its own choice about moving actual work dates; do not treat the two commands as interchangeable.

Choose a cutoff later than the unfinished work's existing placement. After rescheduling, compare the completed task's actual dates character for character with the record taken beforehand. Then inspect the partly completed task: its already performed history should remain anchored while the unfinished portion is replanned.

For the not-started task, inspect the new placement alongside its dependencies and calendar. The useful check is whether remaining work is represented after the selected cutoff under the plan's rules, not whether every task begins on the same displayed day.

Do not manufacture progress to improve the picture

Progress entry changes history-related fields. Microsoft's Update work guidance notes that entering an actual finish marks a task 100% complete, and entering actual work recalculates remaining work and percentage work complete. Do not use those entries merely to remove overdue bars from a chart.

Keep a small before-and-after record with separate columns for actual dates and planned remaining dates. If an actual date changes unexpectedly, stop and identify the operation or input that changed it before saving the result as the accepted schedule.

For an operational update, confirm reported progress with its source and review unresolved constraints instead of deleting them for convenience. The outcome should explain both what really happened and what is now planned. Replanning unfinished work is successful only when that distinction remains intact.

Sources: Microsoft: project scheduling dates; Microsoft: supporting procedure.