Calculate completion percentage, completed amount, total target, remaining progress, or weighted progress from a defined scope of work.

Completion Percentage Formulas

The basic task-based completion percentage formula divides completed units by total units:

C% = (Tasks Completed / Total Tasks) x 100

Use completed and total amounts in the same units and scope. Choose the desired calculation mode; zero completion does not identify a unique total target.

For projects where tasks vary in size or effort, a weighted formula gives a more accurate picture:

Weighted C% = (W1 x P1 + W2 x P2 + … + Wn x Pn) / (W1 + W2 + … + Wn)

W is the planned weight of each group and P is its completion percentage. Choose Weighted completion percentage and enter one weight, percentage pair per line. Use comparable weights, such as hours or points.

Five Methods for Measuring Completion Percentage

Choose a measurement approach that matches the work and agreed reporting method. Task count, duration, cost and weighted progress measure different things.

1. Task Count (Units Completed)

Divide finished tasks by total tasks. Best for projects with roughly equal-size tasks, such as processing applications, grading assignments, or running QA test cases. Accuracy drops when task sizes vary widely.

2. Cost-to-Cost (Percentage of Completion Method)

A cost-to-cost ratio divides eligible costs incurred by the current estimate of total eligible costs. Spending $320,000 against an $800,000 estimate gives a 40% ratio. That arithmetic alone does not establish accounting progress or revenue recognition; see the accounting section below.

3. Duration-Based

A duration ratio is Actual Duration / Current Planned Duration × 100. Seven actual days in a 10-day duration give 70%. Microsoft Project documentation distinguishes this field from work completion. Elapsed calendar time alone does not establish completed work.

4. Weighted or Effort-Based

Weight each group by a comparable planned measure, then average its completion percentages using those weights. This can make mixed-size groups easier to compare, but the weights and progress estimates must still be appropriate.

5. Milestone (0/100 or 0/50/100)

A task may receive 0% or 100% credit, with no partial credit. An illustrative 50/50 rule credits 50% at start and 50% at finish. Use the measurement rules agreed for the project; an EVMS requirement does not universally mandate one milestone technique.

Completion Measures by Industry

The examples below illustrate measurement choices. They are not measured industry benchmarks. Compare progress with the project’s own baseline; neither a calendar midpoint nor a 90%-complete report establishes a universal expected value or overrun.

Context	Illustrative measure	Check before reporting
Construction	Eligible cost ratio	Accounting method and cost estimates
Software	Comparable effort weights	Accepted work and scope changes
Manufacturing	Completed units	Quality acceptance and total target
Coursework	Completed credits or assignments	Course requirements and weights
Government contracts	Approved earned value measures	Applicable contract and reporting rules
Film or media	Agreed milestones	Milestone acceptance and planned weights

A project need not be 50% complete at its calendar midpoint. The relationship depends on the planned sequence, progress measure, scope and baseline.

The 90% Syndrome

The “90% syndrome” describes a project that appears nearly finished while substantial work remains. It is a useful caution about measurement, not a measured overrun percentage or a forecast.

A task count gives equal credit to every task. If the remaining tasks are larger or less predictable, the percentage may conceal remaining effort. There is no universal conversion from 90% of tasks to a particular effort percentage.

Weighted completion can help when groups differ in size. Choose comparable planned weights and enter their progress in Weighted completion percentage; the result still depends on the quality of those estimates.

Earned Value and Completion Percentage

Earned Value Management (EVM) extends completion percentage into a full performance measurement system. Three core values drive it:

Planned Value (PV) = % of work scheduled x Total Budget

Earned Value (EV) = % of work actually completed x Total Budget

Actual Cost (AC) = money spent to date

From these, two ratios reveal project health. Schedule Performance Index (SPI) = EV / PV, where SPI below 1.0 means behind schedule. Cost Performance Index (CPI) = EV / AC, where CPI below 1.0 means over budget. A project at 50% complete with a budget of $200,000 that has spent $120,000 has: EV = $100,000, CPI = 0.83, meaning each dollar is producing only 83 cents of value.

EVMS requirements depend on the agency, contract type, value, clauses and applicable deviations. They do not apply to every federal contract above one universal threshold. Check the contract and current DoD EVMS rules.

Completion Percentage in Construction Accounting

Revenue recognition depends on the applicable accounting standard and performance obligation. Under IFRS 15, an appropriate progress measure is used when a performance obligation is satisfied over time. A cost ratio does not decide whether those conditions are met, and this calculator does not apply IFRS 15 or ASC 606 accounting judgments.

The cost-to-cost formula: % Complete = Costs Incurred to Date / Total Estimated Costs

Revenue Recognized = % Complete x Total Contract Price – Revenue Previously Recognized

Illustrative arithmetic only: $600,000 / $1,500,000 = 40%. If that ratio is an appropriate accounting progress measure and $2,000,000 is the relevant allocated transaction price, cumulative revenue would be $800,000. Subtracting $500,000 previously recognized gives $300,000 for the period. Those assumptions require accounting review.

Changing an estimate changes the ratio: $600,000 / $1,800,000 = 33.3%, rather than 40%. Accounting treatment, eligible costs and estimate revisions require the applicable standard and contract facts.

Example Problem

How to calculate a completion percentage?

First, determine the total number of tasks.
A website redesign project has 40 total deliverables across design, development, content, and QA phases.
Next, count the tasks completed so far.
The team has finished 14 deliverables: all 8 design tasks, 4 of 16 development tasks, 2 of 10 content tasks, and 0 of 6 QA tasks.
Finally, calculate the completion percentage.
C% = 14 / 40 x 100 = 35%. By task count the project is 35% complete. However, if you weight by estimated hours (design: 80h, development: 320h, content: 120h, QA: 80h) the weighted completion is (80×100% + 320×25% + 120×16.7% + 80×0%) / 600 = 30.0%, reflecting that the heaviest work phase is still mostly ahead.

FAQ

What is a completion percentage?

Completion percentage compares finished work with a defined total scope. It is usually between 0% and 100%, but this calculator also reports over-target values above 100%. Different measurement methods can give different results.

What is a good completion percentage for a project?

There is no universal “good” number because it depends on where the project is in its timeline. A project scheduled for 50% completion by June that shows 50% is on track. The more useful metric is comparing actual completion to planned completion. In EVM terms, a Schedule Performance Index (SPI) of 1.0 or above means the project is on or ahead of schedule.

Why does my project seem stuck at 90%?

This is the 90% syndrome. Early tasks tend to be well-defined and easy to count, while the final 10% of tasks (testing, integration, review, bug fixes) are open-ended and unpredictable. Switching from task-count to weighted or effort-based measurement gives a more honest picture. If 90% of tasks are done but those tasks represent only 60% of total effort, the real completion is closer to 60%.

When should I use weighted vs. simple completion percentage?

Use simple task count when tasks are roughly the same size, such as processing forms, completing survey responses, or running standardized tests. Use weighted completion when tasks vary significantly in effort, cost, or duration. Software sprints with story points, construction schedules of values, and academic programs with variable-credit courses all benefit from weighted measurement.

How is completion percentage used in revenue recognition?

A cost ratio may be an input to a suitable progress measure for a performance obligation satisfied over time. It is not a universal requirement or a standalone revenue-recognition rule; consult the applicable standard and contract facts.