About Project Time Estimator -- Free Task Planner
Free project time estimator that calculates realistic timelines. Break work into tasks, set best/worst/likely durations, and get a total estimate that accounts for uncertainty.
How to use
- List all the tasks or phases in your project. Break work down into the smallest meaningful units -- tasks should ideally represent 2-8 hours of work. Larger tasks are harder to estimate accurately because they contain hidden sub-tasks and dependencies. If a task feels like it would take 'about a week,' that's a sign it needs to be decomposed into 3-5 smaller pieces.
- For each task, enter a best-case, worst-case, and most likely time estimate. The best case is the optimistic scenario where everything goes smoothly. The worst case is the pessimistic scenario including probable setbacks (not catastrophic ones). The most likely estimate is what you'd expect under normal conditions. Being honest about the worst case is critical -- research shows that people consistently underestimate by 25-50% when only giving a single estimate.
- The tool calculates a weighted average duration for each task using the PERT formula: (Optimistic + 4 x Most Likely + Pessimistic) / 6. This formula weights the most likely estimate most heavily while accounting for the asymmetric risk that tasks usually take longer than expected rather than shorter. The result is a statistically informed estimate that's more reliable than any single guess.
- Review the total estimated project duration and uncertainty range. The range shows you the best-case total and worst-case total alongside the weighted estimate. If the spread between best and worst case is very large, that indicates high uncertainty in your plan -- consider doing more research or prototyping before committing to deadlines. Use the Goal Tracker to convert your timeline into actionable milestones.
- Adjust task estimates as you learn more and refine your plan. Estimation is iterative -- the first pass is a rough sketch, and each revision improves accuracy. After completing a few tasks, compare actual durations to your estimates. If you're consistently running 30% over, apply that correction factor to remaining estimates. This calibration process makes each subsequent project more predictable.
Frequently asked questions
What is three-point estimation?
Three-point estimation (also called PERT estimation) is a project management technique that uses three values for each task: optimistic (best case), pessimistic (worst case), and most likely duration. These are combined using the PERT weighted formula -- (O + 4M + P) / 6 -- to produce a single estimate that accounts for uncertainty. Developed by the US Navy in the 1950s for the Polaris missile program, it remains one of the most widely used estimation methods in both traditional and agile project management because it explicitly acknowledges that single-point estimates ignore risk.
How accurate is this?
Three-point estimation is significantly more accurate than single-point guesses because it forces you to think about best and worst cases rather than anchoring on an optimistic number. Studies on the planning fallacy (first described by Kahneman and Tversky) show that people consistently underestimate task duration by 25-50% when giving a single estimate. By requiring a pessimistic bound, three-point estimation counteracts this bias. Accuracy improves further with granular task breakdowns -- estimating 10 small tasks is more accurate than estimating 2 large ones because errors tend to average out.
Should I add buffer time?
The three-point formula already builds in some buffer through the pessimistic estimate, but it accounts for known risks within individual tasks -- not for unknown unknowns at the project level. For important projects, add a 10-20% contingency buffer on top of the total PERT estimate. This covers integration issues, scope changes, dependencies on external teams, and the inevitable tasks that nobody thought of during planning. The more novel and uncertain the project, the larger the buffer should be. A routine project you've done before might need 10%; a first-of-its-kind project might need 25%.
Can I use this for sprint planning?
Yes. Three-point estimation works well for agile sprint planning. Break your sprint backlog into user stories or tasks, estimate each with optimistic/likely/pessimistic ranges, and compare the total PERT estimate against your team's velocity (available capacity). If the PERT total exceeds your capacity, you know the sprint is overloaded before it starts -- move lower-priority items to the next sprint. This approach is more reliable than single-point story points because it makes uncertainty visible rather than hiding it in a single number.
Why do projects always take longer than estimated?
The planning fallacy, identified by psychologists Daniel Kahneman and Amos Tversky, explains this pattern. When estimating, people focus on the specific task at hand and imagine the ideal path to completion, systematically ignoring base rates (how long similar tasks took in the past), integration overhead, context switching, meetings, and unexpected blockers. Three-point estimation mitigates this by forcing you to explicitly consider the pessimistic scenario. Another effective technique is reference class forecasting -- looking at how long similar past projects actually took and using that as your baseline instead of estimating from scratch.
How should I handle tasks I've never done before?
For unfamiliar tasks, widen the gap between your optimistic and pessimistic estimates. If you've done something similar, your range might be 2-4 hours. For something completely new, the range might be 4-20 hours. This wide range honestly represents your uncertainty. If the range makes the total estimate unacceptably uncertain, that's a signal to do a time-boxed spike or prototype first -- spend 2 hours exploring the unknown task, then re-estimate with better information. Pair this approach with the
Decision Matrix to evaluate which approach to an unfamiliar task is most likely to succeed.
What is the difference between PERT and critical path method?
PERT (Program Evaluation and Review Technique) focuses on estimating task durations using probabilistic three-point estimates. The Critical Path Method (CPM) focuses on identifying which sequence of dependent tasks determines the shortest possible project duration. They complement each other: use PERT to estimate individual task durations, then use CPM to identify which tasks are on the critical path (meaning any delay to them delays the entire project). Tasks not on the critical path have float -- they can slip without affecting the deadline. This tool handles the PERT estimation side of the equation.
Part of ToolFluency’s library of free online tools for Productivity. No account needed, no data leaves your device.