Progress Rate Calculator | Weighted Average of Multiple Tasks

Enter each task's completion rate and weight (effort share) from your WBS to instantly calculate overall project progress using a weighted average. A free tool to see your project's real progress at a glance.

Last updated: 2026-10-08

What weighted progress is

Five of ten tasks finished does not necessarily mean fifty per cent done. Count a week’s work and a three-month effort as one task apiece and the progress you report parts company with the reality. This tool gives every task a **weight** — its share of the effort — and takes a **weighted average**, letting each completion figure carry in proportion to that weight.

**The weight can be any number that expresses the size of the task: person-days, share of budget, whatever you have. It need not add to 100; the tool turns the figures into proportions on its own.** So “requirements 20, design 30, build 50” gives the same answer as “4 person-days, 6, 10”. Entering weights for tasks not yet started, while their completion sits at zero, shows in advance how much each will bear on the whole.

How to use the calculator

Add the tasks Use “add task” to create rows and name each one. Listing your WBS items straight down works well.
Enter the weights Give a number expressing size — person-days, budget, anything. The unit only has to be consistent, and there is no need to make the total 100.
Enter the completion figures Give each task’s progress as a percentage. Anything not yet started stays at zero.
Read the overall figure You get the weighted average. The individual completion figures appear on a chart too, so what is running late shows at a glance.
Work on the heavy tasks first Raising completion on the larger tasks moves the overall figure most efficiently.

Tips for getting more out of it

Weight can be any number representing task size, such as person-days or budget share. Even if the total isn't 100, it's automatically calculated as a correct ratio.
Entering the weight for a task at 0% completion lets you see in advance how much it will affect overall progress once work begins.
Enter your entire WBS as tasks to see each one's progress or delay at a glance, like a simplified Gantt chart.
Prioritizing completion on tasks with a larger weight (scope) improves overall progress more efficiently.

Where it helps

Reporting at the weekly progress meeting

One figure that accounts for weight conveys the state of things better than “five of ten tasks done”.

Giving a client a brief update

Where wheeling out a full Gantt chart would be too much, this gives you one progress figure with reasoning behind it.

Sizing up the effect of a delay

The same week of slippage lands differently depending on whether the task carries much weight.

Checking the plan before work begins

Entering weights while completion is still zero shows which tasks will govern the whole.

Tying progress to effort and margins

For hours worked beyond schedule, see the overtime hours calculator; for where a project turns profitable, the break-even point calculator.

Terms about progress measurement

Weighted average: An average in which each item carries a weight. It suits progress tracking because tasks of unequal size are not treated alike.
Weight: A number expressing the size of a task. Person-days or budget both serve, and the total need not come to 100 — the figures are read as proportions.
Completion figure: How far a task has progressed, as a percentage. Not started is zero; finished is one hundred.
WBS (work breakdown structure): A hierarchical decomposition of a project’s work. The tasks it yields become the rows entered here.
EVM (earned value management): A method that converts work performed into money so that progress and cost are managed together. Weighted progress tracking belongs to the same lineage.
Simple average: Averaging the completion figures with no weights at all. Unless the tasks are of equal size, it drifts from the reality.

FAQ

It sums each task's "weight × completion rate" and divides by the total weight — a weighted average. Unlike a simple average, tasks with a larger weight (scope) have a bigger impact on overall progress.

No. Weight can be entered in any unit, such as person-days or budget, and is automatically calculated as a ratio even if the total isn't 100.

A simple average treats every task as equally important, while a weighted average reflects the completion of larger, higher-effort tasks more strongly. In real project management, a weighted average tends to represent the actual state more accurately.

There's no system-imposed limit — add as many rows as your WBS requires. That said, too many tasks can hurt readability, so grouping into larger work units is recommended.

Side Note — Why a Simple Average Fails to Represent Project Progress

Showing an accurate "overall progress rate" for a project is trickier than it sounds. If 5 out of 10 tasks are complete, that doesn't necessarily mean the project is "50% done." Treating a one-week task the same as a three-month task produces a progress report that's far from reality.

A weighted average solves this problem. By assigning a "weight" — such as effort or budget — to each task and reflecting completion in proportion to that weight, you get an overall progress rate closer to reality. The PMBOK Guide's concept of Earned Value Management (EVM) explains the importance of this kind of weighted progress tracking as well.

Full-featured Gantt chart tools require setup and a learning curve, which can be overkill just to report progress. A simple calculator where you enter tasks, weights, and completion rates on the spot is handy for weekly status meetings or a quick client update.

Browse all trivia