Seven states. No ambiguity.
Project management that refuses to drift
Most trackers let anyone drag anything anywhere. Taskzen models delivery as a state machine, so a task can only move the way your process actually works — and every move is recorded.
The lifecycle, in full
- Backlog
- To do
- In progress
- In review
- Changes requested
- Blocked
- Done
That is the workflow projects start with. A manager assigns from the backlog, the assignee starts and submits, a manager or client approves or sends it back — and any project can rewrite the whole thing: rename the stages, add or drop them, and decide who may move work into each one.
A workflow per project
Every project defines its own stages and the rules for moving between them. Pick a template, then rewrite it — the engine enforces whatever you describe.
Roles that actually mean something
Managers plan and approve. Members do the work and can only move their own tasks. Clients review outcomes without touching the plan.
Review built in, not bolted on
Submitting work opens a review. Approving finishes it; requesting changes sends it back with the reason attached.
Blocking that remembers
Blocking a task records where it came from, so unblocking puts it back exactly where it was instead of guessing.
Every handoff on the record
Each transition writes an immutable activity entry: who moved it, from what, to what, and why.
A board you can actually read
Seven columns, filters for person and priority, and overdue work called out before it becomes a surprise.