Free project scheduling tool
Project Deadline Estimator
Estimate a likely completion date from remaining work, available resources and actual delivery velocity, then test whether more capacity can move the deadline.
Simple estimator
Working-day forecastEnter remaining work and delivery velocity
Forecast starting point
Remaining work & resources
Schedule protection
Simple methodTeam velocity = resources × velocity per resource. Base weeks remaining = remaining work ÷ team velocity. The schedule buffer extends that duration, then the calculator converts the estimate into working days from the as-of date.
Advanced estimator
Historical velocity + scenariosModel scope, resources and deadline risk
Dates & scope
Resource plan
Remaining-work risk
Forecast range
Advanced velocity modelHistorical velocity is converted into a per-resource rate, then scaled to the planned team using the entered scaling efficiency, availability and blocker loss. Remaining scope is increased for expected scope growth and rework before the schedule buffer is added to duration.
Forecast range
Same scope, different future velocityOptimistic, likely and conservative completion dates
| Scenario | Velocity / week | Base weeks | Buffered weeks | Completion date | Position vs target |
|---|
Resource sensitivity
Scaling efficiency and risk assumptions preservedCompletion date at different team sizes
| Planned resources | Effective velocity / week | Buffered weeks | Completion date | Days early / late | Marginal change vs current plan |
|---|
Velocity sensitivity
Risk-adjusted scope held constantCompletion date as team velocity changes
| Velocity change | Velocity / week | Buffered weeks | Completion date | Days early / late |
|---|
Scope-growth sensitivity
Velocity and buffer held constantCompletion date if remaining scope expands
| Scope growth | Adjusted remaining scope | Buffered weeks | Completion date | Days early / late |
|---|
Scope
A completion date is only as good as the workload and velocity assumptions
This estimator treats work units as comparable and assumes a reasonably stable delivery system. Adding people does not always scale output linearly, which is why Advanced mode includes a resource-scaling efficiency input. It does not automatically model holidays, individual leave, milestone dependencies, critical-path sequencing, fixed-duration vendor lead times, approval gates or work that cannot be parallelized. For complex projects, use this as a directional forecast alongside a detailed schedule.