Project Completion Calculator
Calculates what percentage of a project's tasks have been finished at any given moment. Use it in status reports or dashboards to give stakeholders a clear, at-a-glance view of progress.
About this calculator
Project completion percentage is one of the most straightforward progress metrics in project management. The formula is: Completion % = (completedTasks / totalTasks) × 100. It expresses finished tasks as a proportion of all planned tasks, then scales that proportion to a percentage between 0 and 100. While simple, the metric is most meaningful when all tasks are defined upfront and have roughly comparable scope. If tasks vary widely in effort, consider weighting them by estimated hours before applying the formula. Tracking this figure over time — plotting it on an S-curve, for instance — lets you spot whether work is proceeding at the expected pace or whether the project is at risk of missing its deadline.
How to use
Your software project has 80 tasks in total. At the end of week 3, your team has marked 52 of them as complete. Step 1 — Divide completed by total: 52 ÷ 80 = 0.65. Step 2 — Multiply by 100: 0.65 × 100 = 65%. Your project is 65% complete. If your timeline is 10 weeks and you are at week 3 (30% of the time elapsed), 65% completion indicates you are tracking ahead of schedule — a strong position heading into the second half of the project.
Frequently asked questions
How is project completion percentage different from percentage of time elapsed?
Completion percentage measures work done relative to total work planned, while time elapsed measures calendar progress. Comparing the two reveals schedule health: if 50% of time has passed but only 30% of tasks are done, the project is behind schedule. This comparison is the foundation of Earned Value Management, where schedule performance is tracked as a ratio. Monitoring both figures together gives far more actionable insight than either metric alone.
What are the limitations of using task count for project completion percentage?
Task-count-based completion assumes all tasks are roughly equal in effort and complexity, which is rarely true in practice. A task labelled 'write unit tests' might take 2 hours, while 'design database schema' takes 20 hours, yet both count as one completed task. This can create the illusion of faster progress early in a project if smaller tasks are completed first. Weighting tasks by estimated hours or story points produces a more accurate measure of true project progress.
When should I update the project completion percentage during a project?
Completion percentage should be updated at every meaningful checkpoint — typically at the end of each sprint, work week, or project phase. More frequent updates improve visibility and allow faster course correction if progress stalls. In agile environments, updating the figure at the close of each daily stand-up or sprint review is common practice. Stakeholder-facing dashboards often refresh automatically, but the underlying task status data must be kept current for the metric to remain trustworthy.