PM Planning

Project Timeline Calculator: Dependencies, Capacity and Contingency

By Vact Published · Updated

A useful timeline starts with the work and its dependencies, then adds the people and calendars that make the plan possible. Total effort alone cannot tell you a finish date. Two activities may run together, or they may have to wait for the same specialist even when the task list shows no technical dependency.

Use the calculator below to explore a simple project network. Then follow the planning steps to replace its example durations with a schedule that reflects your own work.

1. Try the four-activity timeline calculator

The network is A, followed by parallel activities B and C, followed by D. D can begin only when both B and C finish. Enter durations in the same working-day unit. The calculation assumes B and C have the resources to run in parallel and uses no holidays or imposed dates. Add contingency as a separate number of working days.

With the example values, A-B-D takes 9 working days and A-C-D takes 7. B controls the finish.

The calculator runs in your browser and does not save or submit the entries. The critical-path guide shows the full forward and backward calculation for this network.

2. Define the result before estimating

Write the deliverable and its acceptance criteria. For a help-center launch, specify the article list, review requirements, navigation, and launch checks. Record exclusions such as translation or a new chat service. A vague instruction to “finish the help center” can hide substantially different amounts of work.

Break the deliverable into work packages and then activities. A package may be “12 approved help articles”; activities include drafting, screenshots, technical review, corrections, and publishing. Keep the distinction visible so that the estimate includes all the work needed to reach the accepted result.

NASA’s WBS Handbook provides a formal approach to decomposing project scope. For a small project, a clear list with owners and completion criteria may be enough to begin.

3. Separate effort from duration

Effort measures work, such as person-hours. Duration measures elapsed working time on the schedule. A review requiring four hours of effort may take several days to finish if the reviewer is available only in short windows. Waiting for an external response also affects duration without necessarily consuming continuous team effort.

For an illustrative task with 12 hours of effort and three available hours per working day, the work needs four working days if it can be divided that way. If a required approval arrives only on Friday, that calendar constraint must also appear in the plan. Adding more people will not automatically shorten a task that requires sequential work or one person’s decision.

Use the capacity-planning guide to calculate actual availability by role. Avoid replacing the team calendar with a single assumed productivity percentage.

4. Map dependencies and resource conflicts

Ask what must be true before each activity can start or finish. Record technical dependencies, access requirements, review handoffs, and external deliveries. Distinguish a genuine dependency from a preferred sequence that could change.

In the calculator’s example, A takes 2 days, B takes 5, C takes 3, and D takes 2. With separate resources for B and C, the project takes 9 working days. If one person must perform B and C sequentially, the same work takes 12 working days before any contingency. That difference comes from resource availability, not a change in the task estimates.

The GAO Schedule Assessment Guide covers the relationships among activities, resources, critical paths, and schedule risk. Its central practical lesson for this exercise is to model the work as a connected schedule instead of a disconnected list of dates.

5. Record the basis of each estimate

For repeatable work, use actual durations from comparable completed tasks and describe what is different this time. For unfamiliar work, ask the person who will perform it to identify the uncertainty and the information that would narrow it. A short investigation may be more useful than debating a precise number with no evidence.

Keep an estimate note beside the task: scope, assumptions, person or team, source of the estimate, and review date. If an assumption changes, you can identify which estimate needs updating. Do not turn a desired deadline into an estimate without checking whether the work fits.

Where a range is useful, explain the conditions behind its endpoints. “Three days if access is ready; five if setup is needed” gives the team an actionable dependency. A range with no explanation is harder to improve.

6. Make contingency visible

Choose contingency based on the risks the project actually faces and explain how it will be used. Keep it separate from the activity durations when communicating the plan. If the calculated work takes 9 days and you add 2 days of contingency, the planning allowance is 11 working days.

That arithmetic does not establish an 85% or 95% chance of success. A quantified confidence level needs an appropriate risk analysis and evidence about uncertainty. For a small project, explicit scenarios and named risks can be more useful than an unsupported probability.

Assign an owner to each material risk and a trigger for action. The risk-register guide shows how to connect those triggers to decisions and affected milestones.

7. Update the forecast as work finishes

Record actual completion dates and re-estimate remaining work. Preserve the approved baseline so that changes remain visible. A new forecast should explain the cause of movement, such as a late dependency, added scope, or a task finishing earlier than expected.

Review the controlling path after every meaningful change. In the calculator, raising C from 3 to 6 days makes A-C-D the longer path at 10 days. Continuing to focus only on B would miss the new constraint.

Share the next milestone, its current forecast, and the decision most likely to affect it. Keep the detailed schedule available for the people doing the work, and use a concise status report to explain what stakeholders need to know.

Sources