Focus & productivity
Task estimate calculator
Enter your rough estimate and your confidence to get a realistic, buffered time for the task.
Base your confidence on how often you have done this exact task before. Novel work deserves the lower confidence and the larger buffer.
Why your first estimate is usually too low
People are consistently optimistic about how long work will take. This is the planning fallacy: we picture the task going smoothly, forgetting the interruptions, revisions and small snags that always creep in. The fix is not to guess harder but to multiply your gut estimate by a buffer. This calculator does exactly that, scaling the buffer to your confidence: the less sure you are, the more padding it adds, because low confidence usually hides steps you have not yet imagined.
| Confidence | Buffer | Best for |
|---|---|---|
| Not very | ×2 | New or unclear work |
| Fairly | ×1.5 | Familiar work with some unknowns |
| Very | ×1.25 | Routine tasks you have done often |
Using the buffered estimate
Give the buffered figure to others when you commit to a deadline, rather than your raw guess; it protects both your reputation and your evenings. For your own planning, compare the estimate against how long similar tasks actually took, since recorded history beats intuition every time. If a task still overruns the buffered figure, that is a signal it was poorly understood, and worth breaking into smaller pieces you can estimate one by one.
Frequently asked questions
Why multiply my estimate at all?
Because the planning fallacy makes first estimates reliably optimistic. We imagine the smooth version and forget interruptions and rework. A buffer corrects for that bias rather than relying on willpower.
How do I pick my confidence level?
Base it on how often you have done this exact task. Routine work you know well earns high confidence and a small buffer; new or vague work earns low confidence and a larger one.
What if the task still takes longer?
Treat the overrun as useful data. It usually means the task was less understood than it looked, so break it into smaller pieces and estimate each one separately next time.