A project can be on schedule and still be unable to move. Map the few dependencies that control progress so you can surface risk before the client feels the delay.
A client deliverable can be ready while the project remains stuck. The analysis needs a data export. The recommendation needs a sponsor decision. The next workshop needs people who are already at capacity.
These are dependencies: conditions outside one task that must be true before the next task can move.
List only dependencies that can change the path
Do not create a project encyclopedia. Start with the next milestone and ask what must happen before it can be completed.
Useful dependency categories include:
- Client input or access
- A decision from a named approver
- Availability of a person or system
- A prior deliverable being accepted
If the condition would not change the sequence, it does not belong on the first map.
Give every dependency an owner and a needed-by point
Write the condition as a testable statement. “Data available” is vague. “The client analyst sends the closed-project export before baseline analysis begins” is clear.
Add the owner, the date or milestone it affects, and the consequence if it slips.
| Dependency | Owner | Needed by | If it slips |
|---|---|---|---|
| Closed-project export | Client analyst | Baseline analysis | Rework the sample |
The owner is the person who can get the condition confirmed, not necessarily the person doing the next task.
Surface the highest-risk dependency early
Review the map with the client before the schedule is full. Ask which item is least certain and what evidence would make it more reliable.
This creates a practical conversation while there is still time to change the sequence, narrow the scope, or find another path.
Add a fallback, not just a warning
For important dependencies, decide what you will do if they fail. Can you use a smaller sample? Run a stakeholder interview first? Move a decision forward with an explicit assumption?
A fallback is not a promise to absorb unlimited delay. It is a deliberate alternative with its own boundary.
Review the map when the plan changes
Dependencies move as the project moves. Check them at kickoff, before major analysis, and whenever a client decision changes the plan. Close items that are no longer relevant so the map stays usable.
The value of a dependency map is not that it predicts every delay. It gives you a shared way to see what the next step depends on and act before the path closes.
[Keep consulting projects moving through every dependency](https://getconsultkit.com)
ConsultKit makes it systematic
Each app starts at $9/month. Monthly billing only. See the current pricing steps and caps.
The Solo Consultant Brief
Weekly tips on referrals, pricing, and client management — straight to your inbox.
Prefer shorter ideas? Follow @getConsultKit on X.