Most teams inherit their status system by accident. Whatever the tool shipped with — To Do, In Progress, Done — becomes the workflow, not because it fits how work moves, but because nobody stopped to change it. Then they wonder why accountability keeps slipping.
Here’s the hard truth: a bad status system doesn’t just fail to help. It actively hides where work is stuck, which makes it worse than no system at all. Let me show you why the defaults fail, and what to replace them with.
Why “To Do → In Progress → Done” Falls Apart
Three statuses can’t describe real work. Consider everything that happens to a single deliverable: it gets started, sent for internal review, revised, sent to the client, revised again, approved, scheduled, and finally shipped. Try to cram all of that into “In Progress” and the status stops telling you anything.
That’s the core failure. When a status covers too many real situations, it loses its information value. “In Progress” ends up meaning “somewhere between not-started and done” — which is to say, it means nothing. And a status that means nothing is where accountability goes to die, because no one can tell whether a task is moving or rotting.
The second failure is the mirror image: missing states. If half your work goes through a client-review phase but there’s no status for it, those tasks sit in “In Progress” the entire time they’re actually out of your hands. Your board is lying to you about where the work is.
The 9-Status Strategic Workflow
The fix is a status system that reflects how work actually moves through a service business. Here’s the one I build with clients, grouped into four phases:
Not Started
- OPEN — ready to begin when capacity allows
- REFERENCE — information or future-planning items, deliberately parked
Active
- IN PROGRESS — actively being worked on right now
- INTERNAL REVIEW — complete, waiting on internal feedback
- IN REVISION — changes being made based on feedback
- EXTERNAL WAIT/REVIEW — with the client or an outside party
- READY FOR LAUNCH — approved and scheduled for deployment
- BLOCKED — waiting on an external dependency
Done
- DONE — work completed and delivered
Closed
- COMPLETE — fully closed and archived
Nine statuses sounds like a lot until you realize each one answers a question the old three couldn’t: Is this waiting on us or on them? Is it blocked, or just not started? Is it truly finished, or finished-pending-approval?
The Rule That Makes It Work: Clear Exit Criteria
Statuses only help if everyone agrees what they mean. So each one needs a written exit criterion — the specific condition that moves a task out of it:
- IN PROGRESS means “someone is actively working this and will have an update by a specific date.” If that’s not true, it doesn’t belong here.
- EXTERNAL WAIT/REVIEW requires a note on what you’re waiting for and when you expect it back.
- BLOCKED requires a comment naming the specific blocker and what’s needed to clear it.
- DONE means the deliverable met its definition of done — proofed, approved, delivered — not “I think I’m finished.”
Without exit criteria, you’ve just renamed the parking lot. With them, the board becomes a live map of reality.
One More Thing: Kill the Fake Urgency
While you’re rebuilding statuses, fix priorities too. Most teams flag everything urgent, which makes nothing urgent. Try the One Priority rule: each person can have exactly one urgent task at a time. When they finish it, they promote the next. It forces real prioritization conversations instead of a wall of red flags nobody believes.
Where This Fits
A status system is the Smart Status Systems component of the Clear Task Ownership Formula — the “Flow” that keeps work moving between clear task creation and role-responsible ownership. Get it right and tasks stop disappearing into ambiguity; you can see, at a glance, exactly what’s moving and what’s stuck.
Rebuilding your statuses is a half-day project with outsized payoff. Start by listing every real stage a piece of work passes through in your business, then build a status for each — and write the exit criteria before you roll it out.
If you want the strategic 9-status system mapped to your specific workflow, with the automations that make it self-maintaining, that’s exactly the kind of build we do with service teams. \[Book a call\] and we’ll design yours.