Critical Path Duration Calculator
Sum the durations of three sequential tasks to estimate critical-path duration. Use it for very simple linear project sizing or as an introduction to the critical-path concept — for real projects with branching dependencies, use proper CPM software.
Last updated: May 2026
Compare with similar
About this calculator
The calculator returns the total duration of three sequential tasks: Critical Path Duration = Task 1 Duration + Task 2 Duration + Task 3 Duration. This represents a simplified critical path for a project where three tasks must execute strictly in sequence (Task 1 finishes before Task 2 starts, Task 2 finishes before Task 3 starts). Variables: each task's duration is its individual estimated time in days. Edge cases: this simplified model assumes pure serialization with no parallel work and no float — far from reality for most projects. The true Critical Path Method (CPM) for a project of N tasks: (1) Build a network diagram showing each task as a node with arrows indicating dependencies; (2) Compute earliest-start and earliest-finish times (forward pass) — earliest a task can start = max(predecessor earliest-finishes); (3) Compute latest-start and latest-finish times (backward pass) — latest a task can finish = min(successor latest-starts); (4) Identify the critical path as the longest sequence of tasks where earliest = latest (zero float). Tasks not on the critical path have float (slack) — they can be delayed without affecting project duration. The critical path determines the minimum project duration; shortening any non-critical task does not help — only shortening critical-path tasks compresses the schedule. CPM was developed jointly by DuPont and Remington Rand in 1957 and is the foundation of all modern project scheduling. Real projects have hundreds or thousands of tasks; CPM is computed automatically by tools like Microsoft Project, Primavera P6, Smartsheet, and Asana.
How to use
Example 1 — Simple three-phase project. Task 1 = Requirements (5 days), Task 2 = Build (15 days), Task 3 = Test (4 days). Step 1: critical path = 5 + 15 + 4 = 24 days. Verify ✓. If all three tasks are strictly sequential with no parallel work possible, project completes in 24 days minimum. Note that real projects rarely have only three tasks; this is a teaching example for the critical-path concept. Example 2 — Construction phases. Task 1 = Site prep (10 days), Task 2 = Foundation (12 days), Task 3 = Framing (20 days). Step 1: critical path = 10 + 12 + 20 = 42 days. Verify ✓. This represents the most common pattern in construction — phased work where each phase depends on the prior. To shorten the project, you must shorten one of these three tasks; adding workers to Task 2 (Foundation) while Task 1 is in progress does not help, because Task 2 cannot start until Task 1 finishes.
Frequently asked questions
What is the critical path and why does it matter?
The critical path is the longest sequence of dependent tasks through a project network — it determines the minimum possible project duration. Tasks on the critical path have zero float (slack); any delay to any critical-path task delays the entire project. Tasks NOT on the critical path have float — they can be delayed within their float without affecting project duration. Identifying the critical path tells you exactly which tasks deserve management attention (the critical ones — delays here hurt) and which can be deferred or rescheduled without consequence (non-critical tasks with float). For schedule compression, you must shorten critical-path tasks; speeding up non-critical tasks does nothing for project duration. The critical path can change during execution — if a non-critical task is delayed beyond its float, it may become critical, and a former critical path may become non-critical. Smart PMs track the critical path actively and consider 'near-critical' tasks (those with small float, say 2 days) as risk areas needing monitoring.
What is the difference between critical path and critical chain?
Critical Path Method (CPM) considers only task DEPENDENCIES — Task B requires Task A's output. Critical Chain Method (CCM, popularized by Eliyahu Goldratt in 'Critical Chain', 1997) extends CPM by also considering RESOURCE constraints — Task B may require the same engineer as Task C, so they cannot run in parallel even if logically independent. In practice, resource conflicts often add significant time beyond what CPM alone predicts. CCM also handles task uncertainty differently: instead of putting buffer in every task estimate (which gets consumed by Parkinson's law), CCM uses aggressive task estimates and pools the saved time as explicit project buffer at the end of the critical chain. Studies show CCM can reduce project durations by 20–40% compared to traditional CPM, primarily by removing hidden buffers and aggregating risk at project level. CCM is widely adopted in research, product development, and IT projects; less common in construction where CPM remains dominant. Many modern PM tools (Primavera, MS Project Pro) support both methods.
What are the most common mistakes in critical-path analysis?
The biggest is failing to update the critical path as the project progresses — as tasks complete (or get delayed), the critical path changes; managing the original path is useless if it's no longer critical. The second is not capturing all dependencies; missing dependencies hide future bottlenecks and produce wildly optimistic schedules. The third is using only finish-to-start dependencies (Task B starts when Task A finishes) when real projects have other types: start-to-start (Task B starts when Task A starts), finish-to-finish (Task B finishes when Task A finishes), start-to-finish (Task B finishes when Task A starts). Proper CPM tools support all four. The fourth is ignoring resource constraints — pure CPM assumes infinite resources; resource-leveled CPM accounts for limited availability and often shows much longer durations. The fifth is using deterministic single-point estimates without uncertainty; PERT (Program Evaluation and Review Technique) extends CPM with three-point estimates (optimistic, most likely, pessimistic) and probability distributions. The sixth is treating CPM as a one-time analysis; it should be updated weekly during active project execution as conditions change.
When should I NOT use this simple three-task model?
Skip this simple model for any project with more than 5–10 tasks; even a simple home renovation has 20+ tasks with complex dependencies. Use Microsoft Project, Smartsheet, Asana, or Primavera P6 for any real project. Avoid it for projects with parallel work streams; the simple summation model cannot represent parallelization, which is the entire point of CPM. Do not use it for projects with resource constraints; resource-leveled CPM is required. Skip it for projects with uncertain task durations; PERT or Monte Carlo simulation gives much better risk-aware schedules. Do not use it for agile/iterative projects where the work decomposition itself evolves during execution; agile estimation (velocity, story points) replaces CPM in those contexts. And do not use this calculator for stakeholder commitment; serious project planning requires the discipline of proper CPM with full dependency mapping, not a three-task simplification.
How does critical path interact with project risk and uncertainty?
Critical-path management without risk awareness produces brittle schedules. The classic improvement is PERT (Program Evaluation and Review Technique), which uses three-point estimates for each task (optimistic O, most likely M, pessimistic P) and computes expected duration as (O + 4M + P) / 6 and standard deviation as (P − O) / 6. Project-level uncertainty can then be estimated by combining task variances along the critical path. Monte Carlo simulation goes further — run thousands of trial schedules with task durations sampled from probability distributions, and produce a probability distribution of project completion dates. Modern PM tools (Primavera Risk Analysis, @Risk, Crystal Ball) automate this. Risk-aware planning typically reveals that the deterministic 'most likely' completion has only 30–50% probability of being met; high-confidence dates (80–90%) require 20–50% additional buffer. Mature project management commits to high-confidence dates externally while internally targeting more aggressive dates — the gap is explicit project buffer that absorbs risk without surprising stakeholders. Critical Chain Method (CCM) is the most formal version of this risk-aware approach.