Delayed vs. Not Completed
I have an idea that there is an 'operational gap' in the use of
delayed when tasks or milestones pass their assigned completion date.
Delayed is used as a catch all term, & it implies that an action is this way because of circumstances beyond the operator's control. This is not always so--a task may simply be not completed or incomplete, rather than delayed.
For example, I might have a task that is continuous over a 1 or 2 week period, and therefore, have the task repeat for a total of 5-10 days, 1x / day.
For various reasons, I might be able to complete the chosen task 3 of 5 days in the 1st week, and 4 days of 5 in the 2nd week.
In the homepage, I might have each of the 2 days of the first week and 1 day of the 2nd week show as delayed, while all the other days are hidden in the relevant completed section.
Thus, by the end of the 2nd week, the task might be finished, but will remain forever showing as 'delayed' only until I go to the task list or milestone and delete the entire event there.
I think then that a clearer meaning here is for those events in this case is incomplete.
Where an event is delayed, then the logical choice is to alter the completion date, which would then not show as 'delayed'.