Project Insight calculates a summary task’s Percent Complete by weighting each child task according to its work hours. A task with zero work hours has no weight in that calculation, so completing it does not change the summary task’s Percent Complete.
If you need zero-work tasks to contribute to progress, use Percent Complete Duration. That calculation weights tasks by duration instead of work hours, allowing a zero-work task with scheduled days to affect the summary percentage.
Best for: Project managers, schedulers, and administrators who use milestones, approvals, waiting periods, automated steps, or other tasks that have duration but no assigned work hours.
Why might a task have zero work hours?
A task may have zero work hours when it represents an important step in the schedule but does not require measurable labor from an assigned resource.
Common examples include:
- A milestone that marks the completion of a project phase
- A customer approval or sign-off
- A waiting period for a vendor, shipment, or external decision
- An automated system process
- A review date or deadline that needs to appear on the schedule
- A task used to control dependencies without allocating resource effort
This can also happen when a task was created with a duration but work hours were never entered.
Zero work hours do not necessarily mean the task is unimportant. They mean the task has no level of effort for the work-based Percent Complete calculation.
How is Percent Complete calculated in Project Insight?
Project Insight weights Percent Complete by work hours. Tasks with more work contribute more heavily to the rolled-up completion percentage of a summary task.
Project Insight does this by comparing the completed work represented by each child task with the total work hours beneath the summary task.
For example, suppose a summary task contains:
- One task with 2 work hours
- One task with 80 work hours
The total work is 82 hours. If the 2-hour task is marked 100% complete, the summary task becomes approximately 2.44% complete because:
2 ÷ 82 = 0.0244, or 2.44%
The 80-hour task carries much more weight because it represents most of the effort within the summary.
Why does a completed zero work hour task not change Percent Complete?
A zero-work task contributes zero hours to the total level of effort. Because Percent Complete is weighted by work hours, the task receives no mathematical weight in the summary calculation.
Marking that task complete changes its individual status, but it does not change the summary task’s work-weighted Percent Complete.
In short, a task with no work hours represents 0% of the total work, regardless of whether the task itself is incomplete or complete.
Why can the summary Percent Complete seem lower than expected?
The summary percentage may seem low when several small tasks are complete but a larger task with many work hours is still incomplete.
For example, completing five short tasks may have less effect than completing one task that contains most of the project’s work hours.
The calculation reflects completed effort, not the number of tasks completed. Ten completed tasks do not automatically equal more progress than one incomplete task if that one task contains most of the work.
What is Percent Complete Duration?
Percent Complete Duration is a separate calculation that weights task progress by duration instead of work hours.
This makes it useful when tasks have scheduled time but little or no assigned work, including zero-work tasks.
Project Insight calculates the completed duration represented by each task and divides that amount by the total duration of all child tasks.
How is Percent Complete Duration calculated?
For each child task, Project Insight multiplies the task duration by its completion percentage. It then adds those completed-duration values and divides the result by the sum of all child-task durations.
The calculation can be represented as:
Sum of each task’s duration × Percent Complete ÷ Sum of all task durations
What is an example of the Percent Complete Duration calculation?
Suppose a summary task contains three child tasks:
- A 5-day task that is 20% complete
- A 5-day task that is 80% complete
- A 10-day task that is 20% complete
Project Insight calculates the completed duration for each task:
5 × 20% = 1 completed day5 × 80% = 4 completed days10 × 20% = 2 completed days
The tasks represent 7 completed days in total:
1 + 4 + 2 = 7
The total duration used in the calculation is 20 days:
5 + 5 + 10 = 20
The Percent Complete Duration is therefore:
7 ÷ 20 = 35%
Why does the duration total not match the summary task duration?
The summary task may display a shorter calendar span than the total duration used in the Percent Complete Duration calculation because some child tasks overlap.
For example, three child tasks may span only 10 calendar days from the earliest start to the latest finish, while their individual durations add up to 20 days.
Percent Complete Duration uses the sum of the individual task durations, even when some of those task days occur at the same time.
How does Percent Complete Duration handle zero work hour tasks?
Percent Complete Duration does not use work hours as its weighting method. A task with zero work hours can still contribute to the calculation if it has a duration.
For example, a five-day waiting period with zero work hours contributes five days to the total duration. If it is 100% complete, those five completed days contribute to the rolled-up Percent Complete Duration.
Project Insight does this by measuring progress against scheduled time rather than assigned effort.
When should I use Percent Complete?
Use Percent Complete when work hours accurately represent the effort required for each task.
It is useful when:
- Tasks have reliable work-hour estimates
- Resource effort is the primary measure of project progress
- Larger work packages should carry more weight than smaller tasks
- Zero-work milestones should not affect the effort-based completion percentage
When should I use Percent Complete Duration?
Use Percent Complete Duration when scheduled time provides a more useful view of progress than work hours.
It may be helpful when:
- The project includes zero-work tasks with meaningful durations
- Waiting periods or external activities should contribute to progress
- Work-hour estimates are incomplete or inconsistent
- The team wants each task weighted according to its scheduled duration
Which percentage should I use for milestones?
A zero-duration milestone may not add meaningful weight to either a work-based or duration-based rolled-up percentage because it has neither work hours nor duration.
Milestones remain useful for marking important events, approvals, phase changes, or deadlines, even when they do not affect the summary completion percentage.
If an activity should influence Percent Complete Duration, it must have a duration rather than functioning only as a zero-day milestone.
Should I add work hours to every zero-work task?
No. Add work hours only when the task represents actual resource effort that should be planned and measured.
Do not add artificial work hours simply to make a task affect the Percent Complete calculation. Doing so can distort resource assignments, workload planning, and total project effort.
Instead, choose the progress calculation that matches what the task represents.
What do these calculations help a team accomplish?
Percent Complete and Percent Complete Duration provide two different ways to measure rolled-up project progress.
- Percent Complete shows progress weighted by estimated effort.
- Percent Complete Duration shows progress weighted by scheduled duration.
Understanding the difference helps teams choose a progress measure that reflects how their projects are planned. It also explains why a completed zero-work task may appear to have no effect on one percentage but affect the other.
What should I check when a summary percentage does not look right?
- Confirm whether you are viewing Percent Complete or Percent Complete Duration.
- Review the work hours assigned to each child task.
- Check whether completed tasks have zero work hours.
- Review the duration of each child task.
- Remember that overlapping task durations are still added together in the duration calculation.
- Confirm that each task’s individual completion percentage is accurate.
What are common mistakes when reviewing Percent Complete?
- Assuming every completed task contributes equally to the summary percentage
- Expecting a zero-work task to affect a work-weighted calculation
- Confusing Percent Complete with Percent Complete Duration
- Using the summary task’s calendar span as the total duration divisor
- Forgetting that overlapping child-task durations are added together
- Adding artificial work hours to milestones or waiting periods
Related questions
Does a zero work hour task affect Percent Complete?
No. Percent Complete is weighted by work hours, so a task with zero work hours has no weight in the rolled-up calculation.
Can a zero work hour task affect Percent Complete Duration?
Yes. If the task has a duration, it can affect Percent Complete Duration because that calculation is weighted by scheduled days instead of work hours.
Are all tasks weighted equally?
No. Percent Complete weights tasks by work hours, while Percent Complete Duration weights tasks by duration.
Why did completing a small task barely change the summary percentage?
The task may represent only a small portion of the total work hours beneath the summary task.
Why is Percent Complete Duration different from Percent Complete?
They use different weighting methods. Percent Complete uses work hours, while Percent Complete Duration uses the sum of task durations.
Where can I get help with Percent Complete calculations?
Visit Project Insight Support for help reviewing work hours, task durations, summary calculations, or percent-complete fields.
[Related article placeholder: Add a link to the Project Insight documentation about Percent Complete.]
[Related article placeholder: Add a link to the Project Insight documentation about Percent Complete Duration.]
[Related article placeholder: Add a link to the Project Insight article about milestones and zero-work tasks.]
Comments
0 comments
Please sign in to leave a comment.