Progress, and the pace the rest of the period needs.
Progress, and the pace it needs
A percentage alone cannot say if you are on track.
68000 of 100000
68%
Ahead of a steady run rate by 1333.333333….
Progress against the clock
The filled bar is progress; the vertical line is where a steady run rate would have you by now. The bar is past the line, so you are ahead.
Progress
68%
32000 still to go
On-pace figure
66666.666666…
where a steady rate would be
Pace so far
8500
per period achieved
Pace needed
8000
per remaining period
68000 of 100000 is 68%, with 32000 still to go.
66.666666…% of the time has gone, so a steady run rate would have you at 66666.666666… by now — you are ahead by 1333.333333….
Sustaining 8500 per period would not be enough or would be more than enough on its own; what the remaining 4 periods actually need is 8000 each.
The required pace is computed from what is left, not from the average so far — which is the number a progress bar never shows.
What this tool shows
68% of the target with 67% of the year gone sounds fine. What it does not say is that the remaining four months now need 8,000 each against the 8,500 a month achieved so far — and that is the number worth acting on.
The percentage of a goal reached
How much is left
Where a steady run rate would have you by now
Whether you are ahead or behind it
The pace achieved so far
The pace the remaining periods need
Progress and pace Against a steady rate What the rest needs Works at any scale
Updated 7 September 2026 · Works in any browser, no installation
Divide what you have by what you need. 68,000 of 100,000 is 68%. To know whether that is good, compare it with the time: at 8 months of 12, a steady rate would have you at 66,667 — so 68% is slightly ahead, and the remaining four months need 8,000 each.
At a glance
Formula shown
Progress = current \u00f7 goal \u00d7 100. The on-pace figure is goal \u00d7 (elapsed \u00f7 total). The required pace is (goal \u2212 current) \u00f7 (total \u2212 elapsed), which is what each remaining period must deliver.
Scenario support
A sales target part way through a quarter; a fundraising campaign; any plan with a deadline and a running total.
Educational estimate
Planning support from the values you enter — not professional advice.
Why a percentage is not enough
“68% of target” is a fact with no verdict attached. Whether it is good news depends entirely on how much of the period is left.
68% at the halfway point is comfortable. 68% with two weeks to go is a problem. The same number, opposite conclusions, and the percentage alone cannot tell you which.
So the page asks for the timeline and computes the on-pace figure: what a steady run rate would have delivered by now. The comparison is the answer; the percentage is just an input to it.
Reading the required pace
This is the number the page exists for, and almost nobody computes it.
At 45,000 of 100,000 with 9 months of 12 gone: the average so far is 5,000 a month. The remaining 55,000 over 3 months needs 18,333 a month — more than three and a half times the pace achieved.
“45% of target” does not convey that. “Needs 3.7× the run rate for the rest of the year” does, and it is the same data.
The page flags it when the required pace exceeds the achieved pace by half again, because that is roughly where a gap stops being recoverable by working harder and starts needing a different plan.
A steady rate is an assumption
The on-pace figure assumes progress arrives evenly. Plenty of things do not.
Seasonal businesses. A retailer at 60% of the annual target in November is probably fine; December is not an ordinary month. A linear run rate would call that behind.
Anything with a pipeline. Sales that close in batches arrive lumpy, and the average of a lumpy series says little about the next period.
Anything compounding. A user base growing by a percentage is exponential, not linear, and a run rate systematically understates where it will finish.
The page reports pace rather than predicting an outcome for exactly this reason. It tells you what the remainder requires; whether that is achievable is not arithmetic.
Overshooting the goal
Past 100% the required pace stops meaning anything, and the page says so rather than reporting a negative one.
A negative required pace would technically be the answer to “how much per period to reach the target” when you already have, and it is not a useful sentence. The page reports the overshoot instead.
Progress past 100% is still worth reporting as a percentage — 120% of target is a meaningful statement. What is not meaningful is a pace to get somewhere you already are.
Where it gets used
Sales quotas. Attainment against quota, part way through a period, is exactly this calculation, and the required-pace figure is what a pipeline review should open with.
Fundraising. The thermometer graphic is a progress percentage. The number that decides whether the campaign lands is the daily total the remaining days need.
Project delivery. Story points, tickets closed, milestones hit — the same arithmetic, and the same trap of reading progress without reading the clock.
Personal targets. Steps, savings, pages written. A goal with a deadline and a running total is this shape whatever the units.
The traps in progress reporting
Progress without a clock. A percentage on its own has no verdict. Always pair it with how much of the period has gone.
Averaging instead of projecting. The pace so far is history. The pace required is the decision. They are different numbers and only one is actionable.
Assuming linear. If the underlying process is seasonal or compounding, a run rate will mislead in a predictable direction. Know which direction before trusting it.
Moving the goal. A target changed mid-period makes every earlier percentage incomparable. Recompute from the new goal and say that you did.
Sources and methodology
Run-rate reporting is a management convention rather than a standard, so these are references for the arithmetic and its limits.
Method. Everything is carried as exact rationals, so a target of a third is a third. The required pace is computed from what REMAINS divided by the periods that remain — not from the average so far — because those are different numbers and only the first one is actionable. The page refuses to report pace when only one of elapsed and total is given, since one without the other says nothing. That engine is verified on every change against 81 hand-written assertions, including that the on-pace figure is always the same fraction of the goal as the elapsed time is of the total, and that passing the goal reports an overshoot rather than a negative required pace. The count and the per-case breakdown are published on the formula verification page.
Related calculators
Where this goes next:
PercentageSolve X% of Y, what percent X is of Y, reverse percentage, increase/decrease, discounts, and tax, tip, or commission.
Percentage ChangeWork out percentage increase or decrease, reverse change, loss recovery, percentage points, multi-period change, and CAGR.
ProportionSolve a : b = c : d for whichever term you leave blank, with cross multiplication derived rather than asserted — or fill all four and have it checked.
Percentage PointA move from 4% to 6% is two percentage points and a 50% increase. Both are computed and named, so the two can never be quietly swapped.
Average PercentageAveraging 50% and 100% gives 99.02%, not 75%, when the groups are 2 and 100 — the page weights by group size and shows the naive answer beside it.
Exponential GrowthGrowth, decay, doubling time and half-life from one rate — with the widening period-on-period change that is what exponential actually means.
If the quantity compounds rather than accumulating steadily — a balance, a user base — the Exponential Growth Calculator is the better model, since a run rate assumes a straight line.
Educational use disclaimer
This is an educational tool. A steady run rate is an assumption, not a forecast — seasonal targets are rarely linear, and the page reports pace rather than predicting an outcome.
Published the percent-to-goal page computing the pace the REMAINING periods need, which is the actionable number and the one a progress percentage hides completely.
Compares progress against a steady run rate rather than reporting a percentage alone, since 68% is comfortable at halfway and a problem with two weeks left.
States that a steady rate is an assumption: seasonal targets are not linear, and the page reports pace rather than predicting an outcome.
Add this calculator to your site
Responsive embed — and private: nothing your visitors type leaves their browser.