Fix Microsoft Project Successor Dates That Do Not Update
Question details
The user wants successor task dates to reflect a predecessor that was completed ahead of schedule.

- Product
- Microsoft Project
- Device & OS
- not provided
- Scenario
- A predecessor is marked 100% complete, and the user expects dependent tasks to move earlier while retaining the predecessor's planned duration.
- Observed behavior
- Successor dates do not move as expected after the predecessor is marked complete.
Identify the completed predecessor and its successor in the Gantt Chart. Check when the predecessor actually started and finished, and decide which date you want to use as the project's reporting status date.
Enter actual dates in the Tracking table
Use actual start and finish information to record early completion instead of relying only on percent complete.
On the Project tab, select Status Date and enter the date through which you are reporting progress.
Open View > Gantt Chart, then choose View > Tables > Tracking to display tracking fields.
For the predecessor, enter the actual start and actual finish, or use actual duration and remaining duration as appropriate. When a task is complete, its remaining duration should be zero; Project can calculate percent complete from the tracking information.
Return to the Gantt Chart and check the successor's start date. If it has not moved, inspect its task link, scheduling mode, constraints, and resource assignments.

Check task links, scheduling mode, and constraints
Use this check when actual completion dates are correct but the successor still starts later than expected.
Review resource leveling delays
Use this approach if resource availability or an existing leveling delay is holding the successor back.
Track Project Dates in WPS Spreadsheets
WPS Office is a free, lightweight Office alternative with a familiar interface for maintaining task lists and sharing schedules in Microsoft Excel formats. It does not recalculate Microsoft Project dependencies or replace Microsoft Project for this scheduling fix.

Frequently Asked Questions
Why doesn't marking a predecessor 100% complete move its successor?
Percent complete alone may not reflect the actual finish date you intended. In View > Tables > Tracking, review the predecessor's actual dates, then check the successor's link, task mode, constraints, calendar, and resource delays.
Should I set a completed task's duration to zero?
No. A zero-duration task is a milestone. Enter the actual start, finish, or duration in the Tracking table and set remaining duration to zero for completed work.
Do actual dates have to be before the status date?
No. The status date is a reporting cutoff, not an absolute restriction on actual dates. For an as-of report, choose Project > Status Date and make sure the progress you report matches that cutoff.
Where can I check whether a successor has the right dependency?
Open the successor's Task Information and select Predecessors. Check the predecessor task, link type, and lag, and remove a link only if it does not represent a real dependency.
Can resource leveling make a successor start earlier?
Not necessarily. Leveling generally delays or splits work to address resource conflicts. Check the Leveling table and resource assignments before changing leveling settings on the Resource tab.




