Work Task Occurrence Statuses
How a Work Task occurrence moves from due to complete.
Each time a Work Task comes due, it creates an occurrence — a single instance with its own status. This is a separate, simpler lifecycle from Work Request statuses; occurrences don't have On Hold, Blocked, or Active overlay statuses, and the stages themselves are different.
Occurrence stages
| Stage | What it means |
|---|---|
| Pending Appointment Confirmation | Waiting for staff to confirm availability to do the work. |
| Pending Assignment | Confirmed and waiting for someone to be assigned to it. |
| Pending Execution | Assigned and waiting to be carried out. |
| Pending Finalization | The work has been done and is waiting on final review or sign-off. |
| Completed | The occurrence is finished. |
| Skipped | This occurrence was deliberately skipped rather than completed. |
Occurrences can also end up Retired or Deleted — these mean the occurrence no longer needs action, rather than describing a step in normal progress.
A worked example
Say a rooftop HVAC unit has a time-based Work Task set to recur quarterly. Each quarter, a new occurrence is generated in Pending Appointment Confirmation. Once staff confirm a time to do the inspection, it moves to Pending Assignment, then Pending Execution once someone is assigned. After the technician finishes the inspection, it moves to Pending Finalization while a supervisor reviews the results, and finally to Completed. The next occurrence for the following quarter is generated separately, on its own timeline — completing one occurrence doesn't affect any others already scheduled.