Overhauling ShotGrid Statuses With Webhooks
This blog post outlines a way to revamp ShotGrid statuses for production with a webhooks server and careful planning.
Statuses 2.0
"Versions affecting Tasks affecting Shots."
In order to redesign your status workflow in ShotGrid, the first thing to understand is that any entity in ShotGrid can have a status. Shots, Versions, Tasks, in ShotGrid these are considered "entities" meaning they can hold a number of attributes or "fields", one of which is a status.
When working in live action VFX, statuses are typically used for your Shots. You can get more granular if you've incorporated a task workflow, i.e for what specifically needs to be done on a shot, and more granular further, for versions, which can be iterations of work done for a task on that shot.

