What Is Average Bias?
Average Bias calculates progress based on the number of Deliverables expected to be completed across the Task or Package duration.
This Bias uses the Task or Package Start Date and Due Date to calculate expected progress. It does not rely on the individual due dates of each Deliverable.
Average Bias is useful when Deliverable dates are not fully defined, or when progress needs to be tracked at a higher level across the overall duration of the work.
When to Use Average Bias
Use Average Bias when:
Deliverable dates are not yet defined
High-level progress tracking is required
Progress should be measured across the full Task or Package duration
A flexible status calculation is needed before detailed Deliverable scheduling is available
How Average Bias Works
Average Bias calculates how many Deliverables should be completed by the current date, based on the total number of planned Deliverables and the Task or Package duration.
The system compares the number of completed Deliverables against the expected number of Deliverables for that point in time.
This comparison determines whether the Task or Package is On Track, Late, or Overdue.
Average Bias Formula
Average Bias uses the following calculation:
Planned Daily Average = Total Planned Deliverables ÷ Total Number of Task Days
The total number of Task days includes both the Start Date and the Due Date.
The system then calculates the expected number of Deliverables for the current date:
Current Expected Deliverables = Planned Daily Average × Number of Days Passed
The number of days passed includes the current date.
The system then compares actual progress against expected progress:
Average Deliverables = Actual Completed Deliverables − Current Expected Deliverables
Status Logic
Status | Logic |
On Track | Average Deliverables is greater than or equal to 0. |
Late | Average Deliverables is less than 0, but greater than or equal to -1. |
Overdue | Average Deliverables is less than -1. |
EXAMPLE: A Task runs from 8 May to 12 May. This gives the Task a total duration of 5 days.
If the Task has 10 planned Deliverables, the planned daily average is: 10 ÷ 5 = 2 Deliverables per day
If today is 11 May, then 4 days have passed, including today.
The current expected number of completed Deliverables is:
2 × 4 = 8 Deliverables
The system then compares the actual number of completed Deliverables against the expected number.
On Track: 8 or more Deliverables have been completed.
Late: 7 Deliverables have been completed.
Overdue: 6 or fewer Deliverables have been completed.
Status Criteria
Status | Date Rule | Progress Logic |
Not Started | Any date | Deliverable completion = 0%. |
Completed | Any date | Task status = Completed. |
Verified | Any date | Task status = Verified. |
On Track | Current date is on or before the Task due date. | Completed Deliverables meet or exceed the planned average pace. |
Late | Applies to Tasks with Deliverables. | Completed Deliverables are exactly one below the number required by the planned average pace. |
Overdue | Current date is after the Task due date. | Deliverable completion is less than 100%. |
Behaviour After the Due Date
If the current date is after the Task due date and the Task is not complete, the Task or Package will be marked as Overdue.
This ensures that incomplete work is flagged once the planned duration has passed.