Recognize overdue
without changing status.

Explain the rule

Open + nonempty due date + date before today → Overdue. Everything else → blank.

Build and compare

• FollowUps::cOverdue: Calculation, Text result, one repetition, unstored, not global.
• Keep Status, DueDate and their validation unchanged.
• Display cOverdue beneath Task on the overview; adjust height and padding so the bold label is fully visible and fits inside each Body row.
• Use a formula-based conditional style and the visible word Overdue.
• Preserve all five Header buttons and the report.

Test in a disposable copy

1. Make a disposable practice copy. On Follow-up Overview click All tasks. Choose an existing task and note its original Status and DueDate.
2. Set that task to Open and its due date to yesterday, using your computer’s current date. Commit by clicking outside the fields. Expect an Overdue label with the conditional color.
3. Keep Status Open and change the date to today, then tomorrow, committing each change. Neither should show Overdue.
4. Change the date back to yesterday and set Status Done. The label should disappear. Restore Open and commit; the label should return. These are manual practice changes, not new button behavior.
5. Clear DueDate and try to commit. The existing required-date validation should prevent the save. Restore a valid date. Do not disable validation to test the formula; its empty-date guard is explained in the rule table.
6. Click Open tasks and All tasks. Check that searches still select the correct tasks, dates remain sorted and the summary still counts tasks rather than overdue labels.
7. Check Contacts, Tasks, Report and Back to Tasks. The report keeps its previous design; this lesson adds the cue only to the overview.
8. Restore the task’s original values, save, close and reopen the practice file. Confirm the label agrees with the current date and saved status. At a later date, reopen or refresh before judging the result; do not assume an idle screen updates at midnight.

Explain what you learned

Why is a task due today not overdue?

Why does the calculation need unstored evaluation, and what triggers an update?

Why keep the word Overdue as well as a color cue?

Your notes and questions