Skip to main content

Realism Bias

This article will explain how Realism Bias calculates progress statuses for Tasks and Packages in Playbook.


What Is Realism Bias?

  • Realism Bias calculates progress using planned Deliverable dates against actual progress.

  • This Bias provides the strictest status calculation. If required work is not completed by the expected date, the related Task or Package is flagged quickly as Late or Overdue.

  • Realism Bias is useful when Deliverable dates are strictly managed and delays need to be identified as soon as they occur.


When to Use Realism Bias

Use Realism Bias when:

  • Deliverable dates are strictly managed

  • Accurate schedule tracking is required

  • Delays need to be identified quickly

  • Progress should reflect missed Deliverables as soon as possible

  • Teams need detailed visibility of schedule performance


How Realism Bias Works

  • Realism Bias checks whether the required work due by the current date has been completed.

  • The date used for the calculation depends on the Task type. Some Task types are checked against scheduled Deliverables due up to the current date, while others are checked against the Task due date.

  • This means Realism Bias gives a more precise view of progress because it considers whether the expected work has actually been completed at the right time.


Status Logic

Status

Logic

Not Started

Task status is Not Started.

Completed

Task status is Completed.

Verified

Task status is Verified.

On Track

Required work due at this point is complete, or the applicable due date has not been missed.

Late

One required Deliverable is incomplete, or the Task is 1 day past the due date.

Overdue

More than one required Deliverable is incomplete, or the Task is 2 or more days past the due date.


Task Type Behaviour

Realism Bias is calculated differently depending on the Task type.

Task Type

How Realism Bias Is Calculated

Form - Recurring

Uses scheduled forms due up to the current date.

Checklist

Uses checklist items due up to the current date.

Form - Singular

Uses the Task due date.

Connect Folder & Criteria

Uses the Task due date.

Assign Doc Templates

Uses the Task due date and Deliverable completion.

Connect Files & Criteria

Uses the Task due date and Deliverable completion.


Form - Recurring and Checklist Tasks

For Form - Recurring and Checklist Tasks, Realism Bias checks the scheduled Deliverables due up to the current date.

Status

Criteria

On Track

Task status is In Progress and all scheduled Deliverables due up to the current date are complete.

Late

Task status is In Progress and one scheduled Deliverable due up to the current date is incomplete.

Overdue

Task status is In Progress and more than one scheduled Deliverable due up to the current date is incomplete.

EXAMPLE: If three scheduled Forms are due by today and all three are complete, the Task is On Track.

If one scheduled form is incomplete, the Task is Late.

If two or more scheduled forms are incomplete, the Task is Overdue.


Form - Singular and Connect Folder & Criteria Tasks

For Form - Singular and Connect Folder & Criteria Tasks, Realism Bias uses the Task due date.

Status

Criteria

On Track

Task status is In Progress and the Task due date is today or in the future.

Late

Task status is In Progress and the Task is 1 day past the due date.

Overdue

Task status is In Progress and the Task is 2 or more days past the due date.

EXAMPLE:

If a Task is due on 10 May, the Task is On Track on or before 10 May.

If the current date is 11 May, the Task is Late.

If the current date is 12 May or later, the Task is Overdue.


Assign Doc Templates and Connect Files & Criteria Tasks

  • For Assign Doc Templates and Connect Files & Criteria Tasks, Realism Bias uses the Task due date and Deliverable completion.

  • Before the Task due date, the Task remains On Track while it is In Progress.

  • On the Task due date, the system checks whether the required Deliverables are complete.

  • After the Task due date, the Task is marked as Overdue if it is still In Progress.

Date Rule

Criteria

Status

Before the Task due date

Task status is In Progress.

On Track

On the Task due date

All required Deliverables are complete.

On Track

On the Task due date

One required Deliverable is incomplete.

Late

On the Task due date

More than one required Deliverable is incomplete.

Overdue

After the Task due date

Task status is still In Progress.

Overdue

EXAMPLE:

If a Task is due on 10 May, it remains On Track before 10 May.

On 10 May, the system checks the required Deliverables.

If all Deliverables are complete, the Task is On Track.

If one Deliverable is incomplete, the Task is Late.

If more than one Deliverable is incomplete, the Task is Overdue.

From 11 May onwards, the Task is Overdue if it is still In Progress.


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

Applicable due date has not been missed.

Required work due at this point is complete.

Late

Applicable due date has been reached or missed by 1 day.

One required Deliverable is incomplete, or the Task is 1 day past the due date.

Overdue

Applicable due date has been reached or missed by more than 1 day.

More than one required Deliverable is incomplete, or the Task is 2 or more days past the due date.


Behaviour After the Due Date

  • Realism Bias flags overdue work quickly.

  • If the applicable due date has passed and the required work is still incomplete, the Task or Package will be marked as Overdue.

  • This helps teams identify missed work as soon as it affects the planned schedule.


Did this answer your question?