DailyWF / Projects
Dependency Tracker
Track decisions, inputs, vendors, systems, people, and approvals that can block delivery.
Project use
Use this when progress depends on people, vendors, systems, decisions, or dates outside direct control.
- Record the dependency, source, owner, needed-by date, and affected work.
- Classify each dependency as blocking, risky, informational, or resolved.
- Check whether the dependency has an alternate path or mitigation.
- Escalate before the needed-by date, not after the schedule is already damaged.
- Close dependencies only when the dependent work can actually proceed.
Expected output
A project record that states the decision, owner, boundary, dependency, next checkpoint, and evidence needed to continue.
Common failure mode
Listing dependencies without dates, owners, or escalation triggers.
Use notes
| Best trigger | Use before a project decision becomes expensive to reverse. |
|---|---|
| Evidence | Keep enough context to explain the decision later without reconstructing conversations. |
| Review point | Review when scope, stakeholder expectation, timing, risk, or ownership changes. |
Related pages
- Rollout ReadinessVerify people, systems, support, communication, and rollback before broad deployment.
- Assumption LogTrack project assumptions before they become invisible sources of risk.
- Project CharterDefine purpose, scope, owner, constraints, and success criteria.
- Project CloseoutClose work formally and preserve ownership of remaining obligations.
- Project PlanTurn a charter into phases, tasks, owners, dependencies, and checkpoints.
Use this with a tool
Find related documents, copy a checklist, or request a missing workflow.