TLDR: A review task becomes overdue if not resolved by its due date, set by default to two business days after creation. Tasks are created when a check finds an issue or a reviewer is assigned. The Due column shows relative timestamps, with overdue tasks highlighted in red and a badge. Hovering reveals the full date and time. This guide applies to Thirdfort clients on the new CDD platform.
A review task becomes overdue when it passes its due date
Every review task carries a due date. When that date passes without the task being resolved, the row is flagged as overdue: the Due column shows red text and a badge, and the check appears in the My Checks – Overdue tab.
How the due date is set
By default, a review task is due two business days after the task is created.
The events that trigger this are:
| Triggering event | What happens |
| The check completes with a finding requiring attention | The task is created and the clock starts |
| If a finding requiring attention wasn’t found, but a reviewer is assigned via the Request a review flow | The task is created and the clock starts |
What the Due column shows
The Due column displays a relative timestamp — for example, "due in 1 day", "due today", or "overdue 2 days". Overdue items are shown in red with a badge. Hovering over the timestamp shows the full date and time.
This guide is for Thirdfort Clients using the new CDD platform. This article may not apply if you have not yet been migrated to the new platform or access Thirdfort via a partner or reseller