Others

Schedule a Milestone 30 Days Before an Installation Task in Microsoft Project

Jason MillerJason Miller Nov 13, 2026 868 views

Question details

Schedule each buyout milestone 30 working days before its corresponding installation task.

Schedule a Milestone 30 Days Before an Installation Task in Microsoft Project
Product
Microsoft Project
Device & OS
not provided
Scenario
Installation dates are fixed by the contract schedule, and the project calendar includes holidays and other nonworking days.
Observed behavior
Each buyout milestone should be driven by its corresponding installation start date rather than by the project start date.
Before you start

Confirm that each installation task has the correct contract start date and that the project calendar contains the applicable holidays and nonworking days. Check File > Options > Schedule to ensure the hours-per-day setting matches the working time defined in the calendar.

Solution 1Recommended

Link each buyout milestone to its installation task with SF-30d

Use a start-to-finish relationship with negative lag to place the milestone before the installation start.

The installation task is the predecessor because its start date drives the buyout milestone. The buyout milestone is the successor, even though it occurs earlier in the schedule.

A lag of -30d represents 30 working days using the applicable scheduling calendar, not necessarily 30 calendar days.

1
Check the project calendar

Open Project > Change Working Time and verify the holidays and working hours. In Project > Project Information, confirm that the intended project calendar is selected.

2
Set up the milestone

In the Gantt Chart, select the buyout task and set its Duration to 0 days. Use Task > Auto Schedule if it is manually scheduled.

3
Add the predecessor

Open the buyout milestone's Task Information dialog and select the Predecessors tab. Add the corresponding installation task by its task ID.

4
Set the relationship and lag

For that predecessor, set Type to Start-to-Finish (SF) and Lag to -30d, then select OK. Repeat for each installation and buyout pair.

5
Verify the scheduled date

Check the milestone date in the Gantt Chart against the installation start and the applicable working calendar. In Task Information > Advanced, leave the milestone's Task Calendar set to None unless it needs a special calendar.

Link each buyout milestone to its installation task with SF-30d
Check constraints and other links: If the milestone does not move as expected, inspect its constraints and other predecessors in Task Information. Also verify that the installation task retains its contract start date.
Free Microsoft Office alternative

Track Project Dates in WPS Spreadsheets

WPS Office is a free, lightweight alternative for everyday document and spreadsheet work. Its familiar interface and Microsoft Office format support make it easy to move existing files into WPS, although it does not replace Microsoft Project's task-dependency scheduling.

Review installation and buyout dates in a spreadsheetOpen and edit Microsoft Excel XLSX filesUse a familiar interface for everyday office workWork with a free, lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Why is the installation task the predecessor if the buyout happens first?

The installation start is the date that drives the buyout milestone. Set the installation task as the predecessor on the milestone's Task Information > Predecessors tab, with Type set to SF and Lag set to -30d.

Does -30d mean 30 calendar days?

No. A -30d lag uses working time and the applicable scheduling calendar. Check Project > Change Working Time for holidays and working hours, and File > Options > Schedule for the hours-per-day setting.

Where do I enter holidays in Microsoft Project?

Open Project > Change Working Time, select the calendar used by the project, and enter holidays or other nonworking dates as exceptions. Check the selected calendar under Project > Project Information.

Why is the milestone not moving when I add the relationship?

Check that the milestone is auto scheduled, then review Task Information for constraints, other predecessors, and any special task calendar. These settings can affect the resulting date.