Use case feedback - status or tasks?

[Byron Nash]

We're still refining our ftrack implementation and constantly trying to improve the pipeline. I'm curious how some of you are handling various steps in the process. Now, I generally have one, maybe two tasks per shot. Our VFX is usually pretty simple so Compositing and occasionally Rotoscoping is what we have been using. I track some of the steps of our process for tasks and shots with statuses. I'm curious to know when you decide to make a task for some to-do item on a shot versus keep it in the status? 

My shot statuses are:

1. Not Started
2. In Progress  (when the artist begins work)
3. Pending Review (when the artist submits a shot for review)
4. Client Approved (when the shot gets approved by the director)
5. Completed (when the shot is rendered)
6. Delivered (when shot is uploaded to the server for the colorist)

But, I wonder if we'd be better served by making tasks for things like generating the shot file for the artist, QC, final delivery, etc...?