Map project dependencies from a planning recording
For each task, note what it needs, who provides it, how to tell when it is ready, when it is needed and what to do if it is late. Link the dependencies to see where the schedule relies on an unconfirmed promise.
How to build a project dependency map
For each task, note what it needs, who provides it, how to tell when it is ready, when it is needed and what to do if it is late. Link the dependencies to see where the schedule relies on an unconfirmed promise.
A transcript lets you verify what was said. It preserves context, qualifications and the order of the reasoning. The author still needs to decide what the final document says and ask participants to check it.
Build the map step by step
Look for conditional phrases
Mark “after,” “if,” “waiting for,” “we need to get” and “we won’t start until” in the transcript.
Describe the input
Identify a specific deliverable such as a file, decision, access, approval or environment. Name the team responsible separately.
Assign owners
Identify both the provider of the input and the owner of the task that depends on it.
Check the sequence
Add acceptance criteria, the required date, a buffer and an escalation plan if the deadline slips.
Example: launching a training webinar
This is a fictional training example. The names, circumstances and outcomes are included solely to explain the method.
“We’ll start editing after the terms have been approved. The product team promised the glossary by Thursday.”
Editing is the dependent task. The approved glossary is the input, the product team supplies it and it is needed on Thursday. The team name alone gives you too little information to manage the schedule.
Define what counts as ready: the file covers the disputed terms and the content owner has approved it. Plan how to handle a late input: reschedule, use a provisional glossary or cut scope.
| Input | Needed by | Dependent task |
|---|---|---|
| Approved glossary | Thursday 12:00 | Subtitle editing |
| Platform access | Friday | Rehearsal |
| Participant list | Monday | Send the email |
| Decision on format | Tuesday | Set up the venue |
Dependency register template
Copy the template and fill it in using a specific recording. Label unconfirmed assumptions as hypotheses.
Dependent task: Required input: Provider / recipient: Acceptance criteria: Required date and buffer: Action and owner if delayed:
Four checks before sending
- Each dependency refers to a specific deliverable.
- The provider and recipient are identified separately.
- The acceptance criteria can be checked.
- There is an action for a critical delay.
A closer look
How is this different from a risk list?
A dependency is a specific input you need. A risk is an uncertain event. A delay to a required input can become a risk.
Do I need to draw a network?
A table is enough for a few dependencies. A network helps when one delay affects three or more deliverables.