How to Fix Unexpected Slack for SF Relationships with Negative Lag in Microsoft Project
Question details
The user is experiencing calculation issues in Microsoft Project where an SF (Start-to-Finish) task dependency with negative lag produces unexpected slack values.

- Product
- Microsoft Project
- Device & OS
- not provided
- Scenario
- Calculating project schedules and critical paths using advanced task dependencies like SF with negative lag.
- Observed behavior
- The scheduled dependency produces a slack calculation that does not match the expected zero-slack result, leading to confusing critical-path reporting.
Check your project schedule for unnecessary date constraints, such as 'Must Finish On', which can further complicate slack calculations and logic errors.
Restructure Dependencies to Use Finish-to-Start (FS) Relationships
Start-to-Finish (SF) relationships with negative lag are uncommon and often trigger calculation anomalies in Microsoft Project. Replacing them with standard FS dependencies resolves most slack calculation issues.
Unusual predecessor relationships, particularly SF with positive or negative lag, rarely reflect actual real-world scheduling and can severely confuse Microsoft Project's critical-path engine.
By reevaluating the task logic and utilizing Finish-to-Start (FS) dependencies instead, you can maintain accurate timelines and ensure zero-slack calculations are processed correctly.
In Microsoft Project, navigate to the Gantt Chart view and double-click the successor task that currently has the SF dependency.
Navigate to the 'Predecessors' tab within the Task Information dialog box.
In the 'Type' column, click the dropdown menu and change the relationship from 'Start-to-Finish (SF)' to 'Finish-to-Start (FS)'.
Adjust the 'Lag' column to a realistic positive value or zero, depending on the schedule requirements, and click 'OK' to recalculate the slack.

Submit a Support Ticket to Microsoft
If the SF relationship with negative lag is strictly required by your project guidelines and the calculation remains incorrect, escalate the issue to Microsoft Support.
Manage Project Schedules Easily with WPS Office
If complex dependency constraints in Microsoft Project are causing calculation errors, consider simplifying your workflow. WPS Office provides intuitive, lightweight spreadsheet tools perfect for project tracking, Gantt charts, and timeline management without the steep learning curve or expensive licensing.
- 1. Download WPS Office: Visit the official WPS Office website and install the free software on your device.
- 2. Open a Project Template: Launch WPS Spreadsheets, click on 'New', and search for 'Project Schedule' or 'Gantt Chart' in the template library.
- 3. Track Your Tasks: Input your project tasks, start dates, and durations to generate a visual, easy-to-understand project timeline.

Frequently Asked Questions
What is a Start-to-Finish (SF) relationship in project management?
An SF relationship means the successor task cannot finish until the predecessor task has started. It is the least common dependency type and is rarely used in standard scheduling because it can be counterintuitive.
Why should I avoid using negative lag in project dependencies?
Negative lag (or lead time) creates overlapping tasks that can distort the logical flow of a schedule. When combined with unusual relationships like SF, it often causes calculation errors and makes identifying the true critical path extremely difficult.
How is total slack calculated in a project schedule?
Total slack (or float) is calculated as the difference between a task's Late Finish and Early Finish dates (or Late Start and Early Start). It represents the amount of time a task can be delayed without delaying the final project completion date.




