What Is Optimism Bias?
Optimism Bias calculates progress using the Task or Package due date, with an additional allowed delay before work is marked as Late or Overdue.
This Bias gives teams more flexibility when tracking work that is already In Progress. It allows a defined number of extra days after the due date before the status changes.
Optimism Bias is useful when short delays are expected and should not immediately cause a Task or Package to be flagged as late or overdue.
When to Use Optimism Bias
Use Optimism Bias when:
Flexible progress tracking is required
Short delays are likely to resolve naturally
Minor slippages should not be flagged immediately
A grace period is needed after the Task or Package due date
Teams want to reduce unnecessary late or overdue statuses
How Optimism Bias Works
Optimism Bias uses the Task or Package Due Date and the configured Allowed Delay to calculate progress.
The Allowed Delay defines how many days after the due date are treated as acceptable before the Task or Package is considered late or overdue.
For Tasks or Packages that are In Progress, the system checks the current date against the due date and allowed delay.
This determines whether the Task or Package is On Track, Late, or Overdue.
Allowed Delay
The Allowed Delay is the number of additional days added after the due date.
EXAMPLE:
If a Task due date is 10 May and the allowed delay is 2 days, the Task can remain On Track until 12 May, provided the Task is still In Progress.
After the allowed delay has passed, the Task can move to Late or Overdue depending on the current date.
Status Logic
Status | Logic |
Not Started | Task status is Not Started. |
Completed | Task status is Completed. |
Verified | Task status is Verified. |
On Track | Task status is In Progress and the current date is on or before the due date plus the allowed delay. |
Late | Task status is In Progress and the current date is exactly 1 day after the due date plus the allowed delay. |
Overdue | Task status is In Progress and the current date is more than 1 day after the due date plus the allowed delay. |
EXAMPLE:
A Task has a due date of 10 May.
The allowed delay is set to 2 days.
This means the Task can remain On Track until 12 May, as long as the Task status is In Progress.
The system then checks the current date:
On Track: The current date is 12 May or earlier.
Late: The current date is 13 May.
Overdue: The current date is 14 May or later.
Status Criteria
Status | Date Rule | Progress Logic |
Not Started | Any date | Task status = Not Started |
Completed | Any date | Task status = Completed |
Verified | Any date | Task status = Verified |
On Track | Current date is on or before the Task due date + Allowed Delay | Task status = In Progress |
Late | Current date is 1 day after the Task due date + Allowed Delay | Task status = In Progress |
Overdue | Current date is more than 1 day after the Task due date + Allowed Delay | Task status = In Progress |
Behaviour After the Allowed Delay
If the Task or Package is still In Progress after the due date and allowed delay have passed, the status will move to Late first.
If the Task or Package remains In Progress for more than 1 day after the due date and allowed delay, it will move to Overdue.
This gives teams a short grace period before delays are escalated.