What do the different task statuses mean and how do transitions work?

Every task in ComplyBar follows a four-step workflow:

1. Not Started — The task has been created but no one has begun work on it.

2. In Progress — A team member is actively working on the task.

3. Ready for Review — The preparer has finished their work and the task is waiting for a reviewer to inspect it.

4. Approved — A reviewer has signed off on the task. It's done.

Transitions move forward through this sequence. A task can also be sent back — for example, a reviewer can move a task from Ready for Review back to In Progress if corrections are needed.

In addition to these statuses, tasks can have a Blocked overlay. A task becomes blocked when it has unresolved dependencies (other tasks that must be Approved first). The blocked overlay is independent of the task's status — a task can be "In Progress + Blocked," meaning work has started but it can't move to Ready for Review until dependencies clear. The database trigger enforces these transitions, so invalid status changes are rejected at the data layer, not just in the UI.