Estimated completion time is your best estimate of when a task will be finished. To calculate it, estimate the work remaining, fit it into your available work periods, and account for interruptions and waiting.
A task that needs two hours of active work can still take several days if you have only short openings in your schedule. The useful answer is a likely finish date with a realistic range, not a precise-looking promise. Start by defining what “done” means, estimate the effort, check how much time you can actually use, then place the work on your calendar. That gives you a forecast you can update when the task or your week changes.
What Does Estimated Completion Time Mean?
Estimated completion time describes when you expect a task to reach its finished state. To make a useful estimate, separate three things: active task duration, elapsed time from start to finish, and the completion date or clock time. Time spent working and time until completion are different estimates. Two hours of work might fit into one afternoon, or stretch across several days if you have limited work periods or must wait for something.
In this guide, estimated time of completion, or ETC, means the forecast finish point. Some project documents use ETC to mean “estimate to complete,” referring to remaining effort or cost. Check how a document defines the field before using it.
Estimated time of arrival, or ETA, usually means when someone or something will reach a destination. At work, people sometimes use ETA as shorthand for when a deliverable will be ready. Make clear which meaning you intend.
For a one-off task, define the finished result, such as a form submitted or twelve folders scanned and checked. For a recurring habit, estimate the length of one session, or the date you expect to reach a measurable milestone, such as completing a set of lessons. A session has a finish point; a habit becoming automatic does not have a reliable date to forecast.
Break the Task Down and Estimate the Work
Start with a visible finish condition. For example: twelve folders scanned, the files checked, and the originals put away. Then split the work into setup, repeatable work, checking, and cleanup. For a larger project, this breakdown of the work is called a work breakdown structure.
Where the task allows it, make each unit specific and measurable, and small enough to complete in about 20 to 90 minutes. Specific, measurable work units in that range can be easier to start and track. Some tasks, such as waiting for a reply or making a brief call, do not fit that size. Keep the units useful for the work rather than forcing every task into the same shape.
Estimate the smaller parts and add them together. That is bottom-up estimating. Or start with a whole-task allowance, then check whether the parts fit inside it. That is top-down estimating. If you have done similar work, use analogous estimating: compare with a completed task that resembles this one. For repeatable work, parametric estimating uses an observed rate, such as units remaining multiplied by minutes per unit, then adds setup and checking time.
Compare like with like. A folder that needed careful sorting is not a good match for one that was already organized, and “done” should mean the same thing in both estimates. If you have no useful past duration, record a representative work session with the time audit tool. Use what you observe to revise the estimate for the work still remaining.
Turn Available Time Into a Finish Date
Usable daily capacity equals the work time you reserve minus the time you expect to lose to interruptions during that window. If you reserve 45 minutes on a weekday and allow 15 minutes for interruptions, you have 30 minutes for active work.
Divide the remaining active work by the usable minutes in a session to estimate how many sessions you need. Round up to a whole session when you plan to work in fixed-length blocks. Count interruption time once: if your past session estimates already include interruptions, do not subtract them again.
Next, place those sessions on dates when you can actually work. Skip weekends, appointments, and days already committed elsewhere. With uneven availability, subtract each day’s usable minutes from the remaining effort until it reaches zero. A useful estimate fits your ordinary week, not the week you hope will suddenly open up. For example, 210 minutes of work at 30 usable minutes per weekday takes seven sessions, not seven calendar days. Use the time blocking planner to check whether those sessions fit beside your existing commitments.
For a habit, reserve the recurring session first. Then count the sessions needed to reach a measurable milestone and place them on your available dates.
Add Waiting Time and Task Dependencies
Active work is only part of a schedule. You may also need to wait for a delivery, approval, reply, or another task to finish. Put each wait where it belongs in the sequence instead of adding all waiting time at the end.
For example, you might scan documents, check the files, then complete a backup. The check depends on the scanning, and the backup depends on the check. In a project, the longest chain of dependent tasks and waits is the critical path, once limits on people and resources are accounted for.
Independent tasks can overlap only when your calendar and resources allow it. If you have to do both yourself, they still compete for your available work periods. When a dependency moves, revisit the dates for the tasks that follow it.
If you have a fixed deadline, use the goal countdown timer to see how many calendar days remain, then compare that with your forecast finish date. The countdown shows the time left, not the effort or dependencies in your task. If the forecast falls after the deadline, make a specific change: reduce the scope, reserve another work period, delegate a separable task, or renegotiate the date.
Calculate Three Possible Completion Dates
Say your records show that three similar folders took 45 minutes to scan, or 15 minutes per folder. Twelve folders would take 180 minutes at that rate. Add 30 minutes for setup and checking, and your most likely estimate is 210 active minutes.
Now make the assumptions visible with three-point estimates. The optimistic case is 150 minutes if sorting is straightforward. The most likely case is 210 minutes. The pessimistic case is 300 minutes if more rescanning is needed. Assume you start Monday, March 2, 2026, have 30 usable minutes each weekday, and do not schedule work on weekends.
| Scenario | Active work | Sessions needed | Completion date |
|---|---|---|---|
| Optimistic | 150 minutes | 5 | March 6 |
| Most likely | 210 minutes | 7 | March 10 |
| Pessimistic | 300 minutes | 10 | March 13 |
The three scenarios make clear what changes the estimate: the amount of sorting and rescanning. The PERT formula gives extra weight to the most likely case:
Weighted effort = (optimistic + 4 × most likely + pessimistic) ÷ 6
For these estimates, (150 + 4 × 210 + 300) ÷ 6 = 215 minutes. At 30 minutes per weekday, that takes eight sessions and ends Wednesday, March 11. The last session needs only five minutes of active work. If you can extend an earlier session by five minutes, the calendar may change accordingly.
March 6 through March 13 is a planning range tied to these three scenarios. It is not a promise of a particular finish date. Use the most likely date for ordinary planning, and pay attention to the later date if there is little room to recover from extra work.
Choose a Buffer for a Specific Risk
Choose a buffer for a risk you can name. Extra revisions may add active work. Unavailable materials may create waiting time. A missed work session changes the calendar, even if the amount of work stays the same. These risks need different reserves.
In the folder example, protect one extra 30-minute work period after the most likely finish. Your forecast is Tuesday, March 10, so the internal target becomes Wednesday, March 11. That spare period covers 30 minutes of extra work or one lost session. If extra rescanning takes 30 minutes and you also miss a session, the reserve is no longer enough. Recalculate the dates.
Match the buffer to the uncertainty and the cost of missing the date. If there is little room to recover, plan around the pessimistic scenario. Keep an external deadline separate from your current forecast and internal target. A deadline is a constraint, not a new estimate of how long the work will take.
At the end of each session, update the remaining work and the work periods you still have available. Keep the original estimate too, so you can compare it with what happened. When you record the work in Loggd, connect the task and focus session with its goal to keep them together.
Use Actual Times to Improve the Next Estimate
Keep a small record for each type of work: the original effort estimate, actual active time, forecast finish date, actual finish date, and the reason for any difference. Recording how long tasks actually take can improve estimates for similar future work.
At your weekly review, compare the folder estimate of 210 minutes with the 240 minutes the work actually took. Find the extra 30 minutes. If it went to rescanning, adjust the unit rate for similar folders. If it went to checking, revise the checking allowance instead.
Separate an effort miss from a capacity miss. If active work took the estimated time but the finish date slipped because you missed a work period, adjust the available capacity in future plans. Do not inflate the task duration to account for a calendar problem.
For a year review, compare your estimated minutes with your actual minutes. Compare the estimated minutes with the actual minutes to calculate a ratio. Use that as a starting adjustment for the same kind of archive work, then check whether the scope or conditions have changed. Keep unlike tasks separate. That archive adjustment may not apply to writing, exercise, or studying.
For a fresh timed sample, use the Pomodoro timer during a work session and record active minutes alongside interruptions. If you need to find where your available hours went before changing an estimate, use the time audit guide to gather that detail.
