With the delay tolerance you can determine in which period after the due date an activity can still be checked off as on time.
An example: An activity should be completed by January 1. However, the user has not yet set a check mark. Today is January 6, so there are 5 days late. If you have set the delay tolerance greater than 5 days, the user will still be able to check off the activity on January 6 but the date January 1 remains. If the tolerance expires, the date of the day when the activity is actually checked off is used. The traffic light will switch automatically even if the activity has not been checked off yet.
Falcon follows a simple algorithm, which is shown in the diagram.
Case 1: If a check is made before the end of the plan, the field takes the current day of the check as the date. The traffic light remains green.
Case 2: If the checkbox is checked after the end of the plan and within the tolerance, the field takes the date as the end of the plan. The traffic light color changes to green. The tolerance therefore allows a late check mark for the plan end date. The tolerance therefore specifies how long you can check an activity retroactively to the end of the plan.
Note: If the activity tolerance is exceeded, the traffic light switches automatically, even if the activity has not yet been checked off.
Case 3: If the check is made after the end of the plan and outside the tolerance, the field also assumes the current date. The traffic light color is retained.
You can access the Finished Tolerance via the schedule settings.