Dependency Log

Published by Dan on

Blank Dependency Log template


A dependency log is an important element of good project governance. Almost all projects and programmes are dependent on at least one internal or external factor. This could be a dependency on another project finishing first. Or that planning permission is given by the local authority. Or even that your organisation hires certain skills before beginning.

Although it may be impossible to understand all dependencies, it’s important to try your best. Failure to understand your dependencies could mean that you find yourself at a dead end. Something that could cause serious delays or cost a lot of money to resolve.

Thus, whatever your dependencies may be, it’s important to record and track them. And our free dependency log can help you do this.

Difference between dependencies and assumptions

Dependencies and assumptions can seem very similar, but there is a crucial difference.

An assumption is something that you believe to be correct without any real proof of it being so. This is often derived through experience.

Dependencies refer to task scheduling/planning and don’t contain the ambiguity of an assumption.

For example, my project might be dependent on project X finishing first. But my forecasted timeline is based on an assumption that project X will finish on time.

Check out our free assumptions log here!

Points of Interest

These relate to the blue boxes in the template – please delete them

1) ‘Project’ Column – If you’re working on one specific project then remove this column. Or you can change it to read ‘area’ or ‘project stage’ etc.

2) Formatting – Be sure to format the document to your brand colours and replace the logo with your own.

3) ‘Expect dependency date’ Column – This is the date you expect the dependency to be fulfilled or realised.

4) ‘Impact if dependency isn’t realised in time’ Column – Try to include as much information as possible here, but giving a vague answer (such as ‘expensive’) is better than nothing

5) ‘Criticality of dependency’ Column – This will be derived from point 4 above and is a simple high, medium, or low selection. This allows you to filter the document by criticality

Process Recommendations

Contrary to popular belief, dependencies change over the course of a project. Old ones may no longer be valid and new ones may arise. Thus, we recommend that you regularly review the dependency log to ensure it’s kept up to date.

Got a recommendation? Then please get in touch with me here to let us know! We’re always looking to improve our documentation.