Active delivery, rework, dependency, review, and contingency contribution with finish range Updates with every input
Date & Time
Project Deadline Duration Calculator
Estimate project duration from adjusted scope, team throughput, focus, rework, dependencies, review cycles, contingency, and an uncertainty range.
Expected elapsed duration —
Active delivery days —
Rework-adjusted scope —
Effective daily throughput —
Dependency and review time —
Contingency reserve —
Planning duration range —
Largest duration driver —
Duration uncertainty anatomy
Active delivery, rework, dependency, review, and contingency contribution with finish range
The visual combines a duration waterfall with an optimistic-to-stressed planning interval, making reserve time and nonproductive waits explicit.
Duration sensitivity
Project duration driver and stress table
See how throughput, focus, rework, dependencies, reviews, and contingency change the expected completion duration.
| Scenario | Focus | Rework | Dependency wait | Review time | Contingency | Elapsed duration |
|---|
How to estimate duration
Start with measurable scope and throughput
- Use one consistent scope unit.
- Use observed throughput from comparable work.
- Reduce nominal capacity for realistic focus.
- Add rework before calculating active days.
- Keep dependency, review, and contingency time separate.
Duration logic
More team capacity only compresses active delivery work
Dependencies and review cycles can remain fixed even when the delivery team grows.
The duration range is designed for commitments: optimistic conditions reduce rework and waits, while stressed conditions lower focus and consume more reserve.
Calculation method
Convert adjusted scope to active delivery days, then add waits and contingency
Scope is inflated for expected rework. Team throughput is reduced by focus. Dependency and review waits are added after active work, then contingency protects the combined base duration.
Detailed calculation process and general formulas
S_adj=S*(1+q)Cap=t*v*fD_active=S_adj/CapD_base=D_active+D_dep+n_review*d_reviewD_expected=D_base*(1+c)Symbols, meanings, and units
- S_adj
- scope including expected reworkscope units
- t
- delivery team memberspeople
- v
- nominal throughput per memberunits/person-day
- f
- delivery focusdecimal
- c
- schedule contingencydecimal
Planning diagnostics
Why a single finish estimate is not enough
Separating active delivery from waits and reserve shows which interventions can actually move the date.
Adjusted scope
—Base units plus expected rework demand.
Effective throughput
—Team output after focus loss.
Non-delivery wait
—Dependencies and review cycles outside active production.
Planning interval
—Optimistic through stressed elapsed duration.
Decision takeaway: Add people only when active delivery dominates; manage approvals and dependencies when waiting dominates.
Estimate checks
Challenge the inputs before committing
- Scope units must be comparable.
- Throughput can fall as team size grows.
- Rework may cluster near final review.
- Contingency is not a substitute for known work.
Estimation evidence
Inputs that strengthen the forecast
- Comparable completed-project throughput
- Scope baseline and change log
- Dependency commitments
- Review-cycle history
- Risk register tied to contingency
Practical applications
Decisions this calculator is designed to support
Feature delivery estimate
A product team converts a unit backlog into an expected delivery interval with review and dependency time.
What the result clarifies: The waterfall identifies whether work or waiting controls the date.
Remediation program
A team must process hundreds of similar units with material rework risk.
What the result clarifies: Adjusted scope prevents rework from being hidden inside contingency.
Worked example
Current-input substitution and reconciliation
Model limitations
This deterministic planning model assumes scope units and throughput are comparable and that team output scales linearly. It does not model resource contention, learning curves, correlated risks, critical-path networks, calendar holidays, or stochastic simulation.
Project Deadline Duration Calculator FAQ
Why add rework to scope?
Expected corrections consume productive capacity just like original scope.
Does team size shorten dependencies?
No. Team size changes active delivery capacity only.
What is the planning range?
It is an optimistic-to-stressed duration interval derived from changed focus, rework, waits, and reserve.
Should known work be contingency?
No. Known work should be included in scope or explicit phases.