Why periodic tasks quietly disappear
The pattern is consistent. A quarterly task falls due, the booking needs a week's notice, nobody requested it, and the task moves to next month. The following quarter the same thing happens. Within a year the task has effectively left the schedule, and neither party made a decision to remove it. It simply became impossible to arrange within the notice period each time.
The fix is administrative rather than operational. Recording the lead time alongside the task means the request is triggered before the due date rather than at it. That single field, in the periodic schedule, prevents the most common cause of a periodic cycle collapsing in a managed building, and it costs nothing beyond noticing the requirement once. Recording the request date alongside the due date also shows, over a year, whether the building's notice periods are being met or whether the schedule itself needs moving earlier.
