While time-based preventative maintenance tasks are automatically given a due date based on the schedule in the automation, reactive tasks and non-time-based automated tasks (such as those triggered by meter readings or conditions) do not have a due date set by default.
You can manually add a due date to these tasks to reflect when the work is expected to be completed. This is useful for prioritising and tracking completion timelines, especially for reactive work or tasks generated from condition-based automation.
For these types of tasks, a due date works alongside the planned start date to help distinguish:
When work should begin (planned start)
When work should be completed by (due date)
This helps maintenance teams schedule, prioritise, and follow up on tasks with clearer expectations, even when the task wasn't time-triggered.