Percent Delay Calculator
Percent delay turns a slipped schedule into one comparable number: how much longer a task actually took than planned, as a percentage of the plan. A 30-hour job against a 20-hour estimate is a 50% delay, whether you measure in hours, days or minutes. This calculator computes that figure from your original estimate and the actual time taken, and shows the absolute delay beside it so the percentage keeps its scale. It is the schedule-overrun member of the site’s percentage family; for comparing two measurements with no “right” answer, see the percent discrepancy calculator.
Percent Delay = (Actual time − Original time) ÷ Original time × 100. Positive means late, negative means early, zero means exactly on plan.
Quick Answer
A 20-hour estimate that took 30 hours is a 50.00% delay, computed as (30 − 20) ÷ 20 × 100, with an absolute delay of 10.00 hours. Type the two numbers into the calculator and press Calculate percent delay to get both figures. A negative result means the work finished early: 10 hours estimated against 8 hours actual is −20.00%.
Key takeaways
- Percent delay = (actual − planned) ÷ planned × 100. The sign carries the meaning: positive is late, negative is early.
- A percentage without the absolute delay can mislead: 50% of a 2-hour task is one hour; 50% of a 2-month project is a month. The calculator shows both.
- Repeated small overruns matter more than one big one. Five tasks each 4% late still burn a fifth of a task's worth of buffer across a sprint, and a bias that steady is systematic, not noise.
- The estimate must be greater than zero, and both inputs must use the same unit. Mix hours with days and the answer is nonsense.
How to use the percent delay calculator
Enter the plan, enter the reality, click Calculate percent delay. The results stay hidden until you calculate, so the page loads clean and the button earns its keep.
- Enter the original time estimate: the duration planned before the work began, in hours or any consistent unit. 20 is pre-filled as the worked example. Zero and negative plans are rejected, because dividing by zero has no meaning here.
- Enter the actual time taken: what the task really consumed, in the same unit. 30 is pre-filled. Enter 8 against a 10-hour plan and the tool reports −20.00%, finished early.
- Read the two results: the headline percent delay in large type, and the badge underneath with the absolute delay. Copy or share either from the buttons in the results box.
The badge is the difference between a number and an insight. Savvy Calculator's percent delay page earns its ranking partly by showing the absolute delay next to the percentage, and the check below shows why: the same 50% headline hides a 10-hour reality on the worked example.
The percent delay formula
Percent delay is a signed relative change: subtract the plan from the reality, divide by the plan, multiply by 100. It is the same ratio project schedulers call the schedule variance percentage, expressed against planned duration rather than earned value.
Absolute Delay = Actual Time − Original Time (in the same unit as the inputs)
The denominator is the original estimate, so the result scales with the size of the commitment. Guidance on keeping that denominator honest comes from the scheduling discipline itself: the PMI Practice Standard for Scheduling sets out how estimates should be built and baselined, and the GAO Schedule Assessment Guide describes how variances against a baseline should be measured and reported. A percent delay is only as trustworthy as the plan it divides by. For the planning discipline that sits behind the estimate itself, see PMI's What Is Project Management? overview and the PMBOK Guide.
Worked example: the 20-hour website task
A website design task was estimated at 20 hours but took 30 after revisions. The calculator is pre-filled with exactly these numbers, so click Calculate percent delay to reproduce the answer.
The early-finish case works the same arithmetic in reverse: a 10-hour estimate with 8 hours actual gives (8 − 10) ÷ 10 × 100 = −20.00%, two hours of the plan unused. The checks below are real runs of this calculator; type any row in to verify it.
| Original estimate | Actual time | Percent delay | Absolute delay |
|---|---|---|---|
| 20 hours | 30 hours | 50.00% | +10.00 hours |
| 10 hours | 8 hours | −20.00% | −2.00 hours |
| 4 hours | 5.5 hours | 37.50% | +1.50 hours |
| 100 days | 100 days | 0.00% | 0.00 (on plan) |
Reading your result: when to worry
Zero or negative is good news: the work landed on or ahead of plan. Above zero, judge the size in context rather than by a fixed rule, but a practical ladder works for most teams:
- Under 5% late: ordinary estimating noise on a single task. Note it, do not reorganize around it.
- 5% to 25% late: worth a retrospective line. Find the cause (scope creep, blocked dependencies, underestimated testing) and adjust the next estimate.
- Over 25% late: a planning failure, not a rounding error. On the worked example the task consumed half again as much time as budgeted, which usually points at a broken estimate rather than a slow team.
The pattern to watch is repetition, not size. A steady 4% overrun across every sprint task is a systematic estimating bias, and it compounds exactly like interest: sprint planning that assumes 100% of estimates will hold keeps starting each cycle one task short. Teams running Scrum capture this in velocity; if your sprints keep slipping, the sprint velocity calculator converts the same planned-vs-actual history into a capacity number you can plan against. Agile guidance on inspecting and adapting each cycle is set out in The Scrum Guide.
What competing calculators miss
Every rival page agrees on the formula; they differ on what surrounds it:
- Formula-only pages (CalculatorDoc, Calculator Ultra): correct arithmetic and a worked example, but the tool behind them is a single percent with no absolute figure and no reading guidance. You get 50% and are left to supply the "so what" yourself.
- Delay-as-input tools (one Savvy variant): ask for planned time and delay minutes rather than actual time. That is a different question, useful for pure downtime tracking but awkward when you only know the plan and the finish.
- Absolute-plus-percent tools (Savvy's main percent delay page): the strongest of the field. It reports the absolute delay in minutes alongside the percentage and walks a worked example with both numbers, which is exactly the pairing this page keeps as its headline and badge.
- Schedule variance explainers (TeamHub): solid method articles with no tool at all. Useful background on variance thinking, but you still do the division yourself.
- The gap this page fills: the absolute delay shown with the percentage on every run, a unit-free design so hours, days or minutes all work as long as they match, the negative case explained instead of hidden, and guidance on what different delay sizes mean for planning. Nothing to configure, nothing to convert.
Honest limits of this tool
Percent delay measures pure time against pure time. It knows nothing about weekends, holidays or working hours: a task estimated at 5 working days that spans 7 calendar days is not 40% late, so use working time on both sides or keep a calendar view alongside it. It prices nothing either; time overruns usually cost money, especially on billable-hour work, and that second step belongs to the cost of delay calculator, which turns late time into money. The calculator handles one task per run; for a project, log each task's percentage and watch the trend rather than averaging everything into one blended figure, since averages hide the one task that is really on fire.
It is also worth naming the sibling it is not. Percent delay is signed: it keeps the direction, late or early. When you compare two numbers where neither is the plan and the sign has no meaning, such as two lab readings, the symmetric comparison on the percent discrepancy calculator is the right tool. And when the question is a general increase or decrease rather than a schedule, the change percent calculator covers that broader case.
Frequently asked questions
Percent delay is the percentage by which actual time exceeded (or beat) the original estimate: (actual − original) ÷ original × 100. A 20-hour estimate that took 30 hours is a 50% delay; the same estimate finished in 16 hours would be a −20% delay. Project teams use it to compare overruns across tasks of very different sizes.
It means the task finished early. A −20% result says the work used 20% less time than planned. That is good news worth recording: the practices behind an early finish are the ones to repeat, and repeated early finishes suggest the estimates for that kind of work can be tightened.
Any unit works as long as both inputs use the same one. Hours against hours, days against days, minutes against minutes. Mixing units, such as a 2-day estimate against 30 actual hours, produces a meaningless answer.
The calculator shows "Please enter valid time values." Percent delay divides by the estimate, and division by zero has no answer, so the estimate must be greater than zero. If unplanned work arrives with no estimate, record the actual time and create an estimate for it rather than forcing a zero into the formula.
Closely related. In earned-value scheduling, the schedule variance percentage is the deviation from plan divided by the plan, times 100, which is the same ratio this calculator computes against planned duration. The difference is only in what the plan figure comes from: a task estimate here, earned-value figures in a formal EVMS setup.
No. The tool works with pure time values, so a task estimated at 5 working days that spans 7 calendar days is not 40% late. Enter working time on both sides, or keep a calendar-aware view alongside the percentage.
The calculator handles one task per run. For a project, log each task's percent delay in a spreadsheet and watch the trend. Look especially for systematic bias: every task 3 to 5% late is a broken estimating habit, not bad luck. For agile teams, rolling the same planned-vs-actual history into the sprint velocity calculator gives a capacity number to plan the next sprint against.
Because a percentage without its scale misleads. A 50% delay is 10 hours on the worked example but a full month on a 2-month project, and those demand very different responses. The badge under the headline keeps the raw figure beside the percentage on every run.
Add This Calculator to Your Website
Embed this calculator on your own site with the code below. Pick a size to preview it live, then copy the code.
Powered by Calculator Zilo
References
- Project Management Institute. Practice Standard for Scheduling, Third Edition. Accessed October 24, 2026.
- U.S. Government Accountability Office. GAO Schedule Assessment Guide: Best Practices for Project Schedules (GAO-16-89G). Accessed October 24, 2026.
- Schwaber, K. and Sutherland, J. The Scrum Guide. Accessed October 24, 2026.
- Project Management Institute. What Is Project Management? Accessed October 24, 2026.
- Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK Guide). Accessed October 24, 2026.
