Map Project Dependencies: A Practical Workbook

Choose a small delivery outcome

Use this workbook when a team cannot complete its work without an input, decision or output from elsewhere. APM defines an activity dependency as a relationship between activities in a network diagram. This exercise focuses on making those relationships discussable.

Begin with one deliverable. Avoid mapping the entire organisation before understanding the immediate handovers. Keep the scope small enough for the people responsible to review it.

Describe the input precisely

Record what is needed, why it is needed and the activity that depends on it. A vague statement such as waiting for IT may hide several separate inputs and owners. Describe the output or decision in observable terms.

In a fictional reporting project, the dashboard team needs an approved sample dataset before it can test the calculation. Record which dataset, who can approve access and what acceptance conditions apply. Do not put confidential data into a shared learning copy.

Identify the relationship and timing

Ask which work must happen first and whether any work can proceed in parallel. Distinguish a genuine sequencing relationship from a convenient habit. Confirm timing with the people who provide and receive the input.

Record the needed-by date, the provider forecast and the basis for both. If these do not align, explain the potential effect rather than assuming the provider can simply work faster. The workbook is not a scheduling engine and does not calculate a critical path.

Agree ownership and a response

Name the person or role responsible for providing the input and the person responsible for accepting it. Record the agreed check-in and the condition that triggers escalation. Use the established governance route for decisions outside the team.

Consider a proportionate alternative: a smaller authorised sample, a changed sequence or a revised scope may be possible. Record the decision and its limitations. Do not bypass access or approval controls to remove a dependency.

Review changes with both sides

A dependency record needs review when the expected input, delivery date or receiving activity changes. Update the relevant plan and risk or issue records through your organisation’s process. Notify affected people so the record supports coordination.

Download the workbook and map one fictional handover. Ask another person to play the provider and challenge the input, timing and acceptance conditions. Revise the record so both sides can explain the agreement.

Source and practice note

APM provides the dependency and network-logic terminology used as the starting point. This resource is an original RDE practice aid. The examples are fictional. Adapt it to your organisation and obtain the appropriate decision authority.

APM dependency and planning terminology

Cover image: AI-generated illustrative scene created specifically for this resource.

Download and complete the exercise

Read or print the PDF

Download the editable Word document

Printable PDF and editable Word document. Version 2.0, 7 October 2026. Personal and internal organisational adaptation permitted with Jefferson Otonbara Imgbi author credit retained.