How to Fix Microsoft Project Incorrect Slack for Finish-to-Finish Tasks
Question details
Users experience unexpected or incorrect total slack values when managing in-progress tasks that have deadlines and finish-to-finish predecessors in Microsoft Project.

- Product
- Microsoft Project
- Device & OS
- not provided
- Scenario
- Tracking task schedules and analyzing total slack with deadlines and finish-to-finish (FF) dependencies.
- Observed behavior
- A successor task shows positive slack even when the overall schedule is late, while its linked predecessor task displays substantial negative slack.
Verify that your project tasks do not have conflicting strict constraints and ensure that all task progress updates have been entered in chronological sequence.
Remove or Adjust Task Deadlines
Clearing or modifying the deadline on the driving task can resolve conflicting slack calculations caused by overlapping scheduling logic.
Microsoft Project calculates task slack based on hard constraints and deadlines before considering the logical network. When a task has a deadline combined with a finish-to-finish predecessor, the engine may miscalculate the true float of subsequent tasks.
Double-click the task showing negative slack on your Gantt chart to open the 'Task Information' dialog box.
Click on the 'Advanced' tab within the dialog box to view constraints and deadlines.
Locate the 'Deadline' drop-down field and change the date to 'NA' (Not Applicable) or clear it entirely.
Click 'OK' to apply the changes. Review the total slack column to ensure the values have recalculated correctly based on the standard network logic.

Update Schedule Progress Sequentially
Entering actual progress out of sequence can skew late-date calculations. Realigning progress entries ensures accurate slack reporting.
Submit Reproducible Feedback to Microsoft
Since this slack calculation behavior can be an inherent logic flaw in the software, submitting reproducible feedback helps Microsoft address the issue in future updates.
Simplify Project Tracking with WPS Office
Complex dependency calculations in Microsoft Project can sometimes lead to confusing schedule outputs. If you need a more straightforward way to track timelines and manage tasks, WPS Office offers a free, highly compatible alternative. You can easily create dynamic Gantt charts and project trackers using familiar spreadsheet tools without fighting strict software logic.
- 1. Download and Install: Visit the official WPS Office website to download the free suite and follow the simple installation prompts.
- 2. Open WPS Spreadsheet: Launch WPS Office and open a new Spreadsheet document to begin building your project timeline.
- 3. Use Project Templates: Access the built-in template library and search for 'Gantt Chart' to instantly set up a beautiful, logic-free project tracker.

Frequently Asked Questions
Why does my successor task have positive slack while the overall project is late?
This happens when a predecessor has a hard deadline but the successor does not. Microsoft Project calculates the predecessor's negative slack based on its missed deadline. However, it calculates the successor's positive float based on the overall project finish date, creating a disconnect between the two linked tasks.
Can I rely entirely on total slack to determine my project's health?
No, relying solely on total slack can be misleading. When complex dependencies, such as finish-to-finish links combined with out-of-sequence progress updates and strict deadlines are involved, slack numbers can skew. It is better to review the critical path and individual task finish variances.
How do I change a finish-to-finish link to a standard dependency in Microsoft Project?
Double-click the dependency line connecting the two tasks on the Gantt chart, or open the 'Task Information' dialog, navigate to the 'Predecessors' tab, and change the 'Type' from 'FF' (Finish-to-Finish) to 'FS' (Finish-to-Start).
How do deadlines affect total slack calculations?
Setting a deadline overrides the standard network float calculation. If a task is scheduled to finish past its deadline, its total slack becomes negative, representing the amount of time it is overdue, regardless of how much float it technically has in the overall project network.




