Fix Deliverable Dependencies in Project 2016 and Project Online
Question details
The user needs destination tasks to respond to changes in deliverables from another project schedule.

- Product
- Microsoft Project 2016 and Project Online
- Device & OS
- not provided
- Scenario
- A destination project is linked to deliverables in a source project through Manage Dependencies.
- Observed behavior
- The synchronized deliverable dates appear correct, but changes to source dates or completion percentages do not update the destination tasks.
Confirm that you can open and edit both project schedules in Project 2016 and that you have permission to save and publish them if they are managed in Project Online. Identify the source and destination tasks you want to link.
Create a cross-project task dependency
Use a task link when a source task should influence the schedule of a task in another project.
Deliverable dependencies are soft references; they do not automatically move successor tasks. A cross-project task link creates a scheduling relationship, such as Finish-to-Start.
The link does not copy the predecessor's percentage complete to the successor. The successor's dates also depend on its scheduling mode, constraints, calendars, and other dependencies.
In Project 2016, create a blank project, then select Project > Subproject and insert the source and destination projects.
In the master project's task list, select the source task first, then hold Ctrl and select the destination task. On the Task tab, select Link Tasks to create a Finish-to-Start link.
If you need a different relationship, open the destination task's Task Information, select the Predecessors tab, and change the link type to Start-to-Start, Finish-to-Finish, or Start-to-Finish.
Save the affected projects and publish them if they are managed in Project Online. Change the source task's scheduled dates, save the source project, then open or refresh the destination project and accept any prompt to update external links.

Check scheduling and external link updates
Use these checks if an existing cross-project task link does not update the destination schedule.
Track project information in WPS Office
WPS Office is a free, lightweight Office alternative with a familiar interface and compatibility with common Microsoft Office formats, making it easy to move project notes and tracking spreadsheets. It does not fix Microsoft Project dependencies or replace Project Online scheduling.

Frequently Asked Questions
Why doesn't a deliverable dependency move my destination task?
A deliverable dependency is a soft reference, not a scheduling link. Create a cross-project task dependency if the source task should affect the destination task's schedule.
Will a cross-project task link copy percentage complete?
No. A task link controls the scheduling relationship; it does not copy the source task's percentage complete to the destination task.
Which task relationship should I use?
Use Finish-to-Start when the destination task should start after the source task finishes. In Task Information > Predecessors, you can choose Start-to-Start, Finish-to-Finish, or Start-to-Finish for other scheduling needs.
Why might a linked destination task still not move?
Check that the destination task is automatically scheduled and review its constraints, calendar, and other predecessors. Save the source project, reopen the destination project, and accept any prompt to update external links.




