ETA Calculator

About ETA Calculator

How the ETA Calculation Works

The formula is straightforward. The tool divides the number of items completed by the elapsed time to get your rate, then divides the remaining items by that rate to get the time left:

Value	Formula	Example (200 items, 80 done in 2 hours)
Rate	Completed / Elapsed time	80 / 2 = 40 items per hour
Remaining	Total - Completed	200 - 80 = 120 items
Time left	Remaining / Rate	120 / 40 = 3 hours
ETA	Current time + Time left	If it is 2:00 PM, ETA is 5:00 PM
Progress	(Completed / Total) x 100	80 / 200 = 40%

This assumes a roughly constant rate. If your speed fluctuates, the ETA updates in real time as you update the completed count.

Auto Rate vs Manual Rate Mode

Mode	How It Works	Best For
Auto rate	Calculates rate from elapsed time and completed count	Tasks where you update progress as you go
Manual rate	You enter a fixed rate in items per hour	Planning ahead when you know your typical speed

Auto mode recalculates every second, so the ETA adjusts as your pace changes. Manual mode gives a fixed estimate that does not shift - useful when you want a prediction before starting.

Dashboard Readings

Metric	What It Shows
Elapsed time	How long since you started the timer
Remaining time	Estimated time until completion
Current rate	Items per hour (auto-calculated or manually set)
ETA	The clock time when you are expected to finish
Progress bar	Visual percentage with colour coding (green as you approach 100%)

The unit label is customisable. Change "items" to "pages", "km", "tickets", "emails", or anything that fits your task.

Common Use Cases

Task	Total	Example Rate	Estimated Time
Processing invoices	500 invoices	60 per hour	8 hours 20 minutes
Driving a distance	350 km	90 km per hour	3 hours 53 minutes
Reading a book	400 pages	30 pages per hour	13 hours 20 minutes
Closing support tickets	45 tickets	8 per hour	5 hours 37 minutes
Data entry rows	2,000 rows	150 per hour	13 hours 20 minutes
Moving boxes	80 boxes	12 per hour	6 hours 40 minutes

Why ETAs Shift During a Task

If your ETA keeps jumping around, it is because your actual rate is not constant. This is normal for most real-world tasks. Early in a task, a small change in completed count causes large swings in the calculated rate. As more data accumulates, the rate stabilises and the ETA becomes more reliable.

Situation	Effect on ETA	What to Do
You speed up mid-task	ETA moves earlier	Nothing - the tool adjusts automatically
You slow down (fatigue, complexity)	ETA moves later	Consider switching to manual rate for a conservative estimate
You take a break without pausing	Rate drops, ETA moves much later	Pause the timer during breaks for an accurate rate
Task has variable difficulty	ETA fluctuates	Use the average rate over 30+ minutes for the best prediction

Tips for More Accurate Estimates

Tip	Why It Helps
Update progress frequently	More data points give a smoother, more reliable rate
Pause during breaks	Prevents idle time from dragging down your calculated rate
Use manual mode for planning	Base it on a known rate from similar past tasks
Wait 15-20 minutes before trusting the ETA	Early readings are noisy because the sample size is small
Break large tasks into subtasks	Smaller totals reach a stable rate faster

For counting days until a deadline, use the day counter. For tracking work hours across a shift, the hours calculator handles clock-in and clock-out times. To plan focused work blocks around your ETA, the Pomodoro timer structures your sessions. Everything runs in your browser with no data sent anywhere.

Why Most ETAs Are Too Optimistic

Human time estimates are consistently shorter than actual completion times, a cognitive bias called the planning fallacy. Daniel Kahneman and Amos Tversky described the effect in 1979 and it has been replicated in dozens of studies since. In a 1994 Buehler, Griffin and Ross study of psychology honours students, the average predicted thesis completion time was 33.9 days. The average actual time was 55.5 days, a 64% overshoot. Only 30% of students finished within their own estimate.

The takeaway for anyone using an ETA calculator: the rate you start with almost always overstates your sustainable pace. A calculator that extrapolates from real elapsed time and real completed items corrects for this automatically, because it uses your actual rate rather than the rate you wish you had. That is why auto rate mode is more honest than manual mode for tasks in progress.

What Is a Realistic Sustained Work Rate?

Sustained output is lower than burst output, and the gap widens over long sessions. Published productivity research and call-centre benchmarks give rough sustainable rates that apply to knowledge and process work:

Work Type	Burst Rate (first hour)	Sustained Rate (full shift)	Drop
Data entry (single-field rows)	180-220 rows/hr	120-150 rows/hr	~30%
Support ticket triage	14-18 tickets/hr	8-12 tickets/hr	~35%
Manuscript reading	40-60 pages/hr	25-35 pages/hr	~40%
Code review (lines)	500 LOC/hr	200-300 LOC/hr	~50%
Invoice processing	80-100 invoices/hr	55-70 invoices/hr	~30%
Warehouse picking	100-140 items/hr	70-90 items/hr	~35%

When planning ahead with manual rate mode, use a figure closer to the sustained rate column. Using the burst rate produces an ETA that will slip the moment you hit your first break or complex edge case.

How Long Before Auto Rate Stabilises?

Early readings are noisy because a small absolute change in completed count produces a large proportional change in rate. The signal-to-noise ratio improves as the sample grows. A useful rule of thumb, borrowed from statistical process control, is that the estimate is usable once you have completed at least 10% of the total or run for at least 20 minutes, whichever comes later.

Worked example: a 500-item queue at 4 completed after 5 minutes gives an apparent rate of 48/hr and an ETA 10 hours away. Five minutes later, at 9 completed, the rate is already 54/hr and the ETA drops to just over 9 hours. By the 20-minute mark, with 18 completed, the rate has settled around 54/hr and the ETA becomes a dependable 8 hours 55 minutes. Before that point, the ETA moves by hours per minute of new data and should not be trusted.

When to Add Buffer to the ETA

Factor	Typical Buffer	Why
Client deadline (external commitment)	+20-30%	Covers the planning fallacy gap
Task involves unfamiliar work	+40-50%	Learning curve adds hidden time
Multiple dependencies on other people	+50-100%	Wait time compounds
Repetitive, well-understood task	+10%	Only covers normal variance
Task with known fatigue curve (long reads, manual entry)	+25%	Sustained rate drops after 2-3 hours

A common pattern is to use auto rate to produce a base ETA, then add the buffer manually before communicating the finish time to anyone else. The base ETA is for your own pacing. The buffered ETA is the one you promise.

Common Mistakes When Reading an ETA

Most misreadings come from treating a moving estimate as a fixed deadline. A few traps to avoid:

• Trusting the first-minute reading. With almost no data, the rate is dominated by start-up overhead. Wait at least 15-20 minutes.
• Forgetting to pause during breaks. If you stop working but leave the timer running, your rate drops and the ETA drifts later. Pause the start time or reset it after longer breaks.
• Assuming linear difficulty. The last 10% of a task is often slower than the first 90% - final QA, edge cases, documentation. Add a small finishing buffer when you are close to done.
• Treating the ETA as a commitment. It is a projection from the current rate, not a promise. If the rate changes, the ETA changes.
• Ignoring rate collapses. If your rate suddenly halves, something has changed - a harder batch, distraction, tiredness. Switch to manual rate with the new realistic figure rather than letting the average slowly catch up.

ETA Calculator vs Stopwatch vs Pomodoro

Tool	Best For	What It Shows
ETA calculator	Tasks with a countable total	Projected finish time
Online stopwatch	Untimed tasks where you just want to know elapsed	Time passed since start
Countdown timer	Fixed-duration tasks (cooking, tests)	Time remaining to a set endpoint
Pomodoro timer	Breaking work into focused intervals	Alternating 25/5-minute blocks
Pace calculator	Running and cycling distances	Pace per km or mile

For a task with a known endpoint in items, distance, or any countable unit, the ETA calculator is the right fit. Use it alongside a Pomodoro timer when you want the pacing discipline of fixed work blocks plus a running projection of the full finish time.

Sources

• Wikipedia - Planning Fallacy (Kahneman & Tversky, 1979)
• Buehler, Griffin & Ross (1994) - Exploring the Planning Fallacy, J. Personality and Social Psychology
• Project Management Institute - Planning Fallacy Causes and Solutions
• The Decision Lab - Planning Fallacy
• Ness Labs - Why We Underestimate How Long a Task Will Take