What is the typical Task Lifecycle?

Recently I was asked what default task status we use at Pelago and what our Task Lifecycle looks like. With Intervals you can bend it to match your process, but here is how we work:

1. Task Creation
When a task is created it is set to Open. The assignee will receive an email with the task summary, due date, etc.

2. Task Completion or Clarification
When the assignee has completed the task they set it to Verify & Close (this emails the owner letting them know the task is ready to be closed). If they are unable to complete it, they set it to Needs Assistance (which also emails the owner letting them know the task needs some help to keep it moving)

3. Task Closed or Opened
The owner of the task then views it and can set the task to Closed if they feel it has successfully been completed or Open with comments and further instructions. It is not uncommon to have a task go back and forth like this for a while before it gets Closed.

If the task requires customer approval before closing it, we will use the "Send email message" option on the task and notify our customer that we need their review and approval. If a task needs customer approval we set it to Review with Client. This tells us that there is nothing further we can do until we receive feedback. Once we get the blessing from our client we go in and set it to Closed.

There are a variety of ways to tune the task flow to match your process, but that is how we do it. Some Intervals customers change the assignee of the task back and forth while keeping the status Open. We like to keep the owner to assignee relationship and manage tasks based on their status.

2. Task Completion or Clarification
When the assignee has completed the task they set it to Verify & Close (this emails the owner letting them know the task is ready to be closed). If they are unable to complete it, they set it to Needs Assistance (which also emails the owner letting them know the task needs some help to keep it moving)