Why “In Progress” Is the Most Dangerous Status on Your Board


I audited a 25-person agency’s ClickUp workspace last quarter. They had 847 tasks marked “In Progress.”

Eight hundred and forty-seven.

When I asked the team what “In Progress” actually meant, I got twelve different answers. I’ve started it. It’s on my radar. I’m waiting for the client. It’s in review. I touched it once three weeks ago.

“In Progress” had become the status equivalent of a junk drawer — everything goes in, nothing useful comes out.

This is the most common visibility killer I see in service businesses. Not missing tasks. Not wrong assignments. Meaningless statuses that tell you nothing about where work actually stands.

Here’s how to fix it permanently.


The Status Update Tax

Let me quantify the damage.

If you manage ten active projects and spend just fifteen minutes per project per week asking “where are we on this?” — that’s 2.5 hours a week. Over 100 hours a year. Just asking a question your PM tool should answer for you.

That’s the Status Update Tax. Every team with meaningless statuses pays it.

[VISUAL: blog1-status-update-tax.html]
Replace this block with the screenshot

The fix isn’t more meetings or better communication. The fix is a status system where every status tells you exactly what’s happening without anyone having to ask.


The 9-Status Strategic Workflow

Here’s the system I implement with every client. Delete your defaults — yes, all of them — and replace them with nine statuses organized into four phases.

[VISUAL: blog1-9-status-system.html]
Replace this block with the screenshot

Phase 1 · Not Started

OPEN — This task is defined, assigned, and ready to begin when the assignee has capacity. It’s not urgent, it’s not forgotten — it’s queued. Think of it as the waiting room.

REFERENCE — This isn’t a task to be completed. It’s information, future planning, or a placeholder for something that doesn’t have a timeline yet. It exists so it doesn’t get lost, but it’s not cluttering anyone’s active work.

Phase 2 · Active

IN PROGRESS — And now it actually means something: I am actively working on this today or this week, and I will have an update by [specific date]. Not “I’ve seen it.” Not “it’s on my list.” Actively. Working. On. It.

INTERNAL REVIEW — Work is complete from the assignee’s perspective and needs internal feedback before moving forward. When a task hits this status, automation should reassign it to the designated reviewer and add a comment: “Please review and provide feedback by [date].”

IN REVISION — Feedback has been received and changes are being made. This status exists because “In Progress” shouldn’t mean both I’m creating and I’m revising. Those are different mental modes and different priorities.

EXTERNAL WAIT/REVIEW — The ball is no longer in your court. It’s with the client, a vendor, legal, or any external party. This status is critical because it tells you: we can’t move this forward, and the reason is outside our control. Include a comment noting what you’re waiting for and the expected timeline.

READY FOR LAUNCH — Everything is approved. Everything is final. This task is scheduled for deployment, publication, or delivery on a specific date. The green light status.

BLOCKED — Something is preventing progress that requires escalation or resolution. Unlike EXTERNAL WAIT (which is normal workflow), BLOCKED means something unexpected is in the way. A blocker comment is required: what’s blocking, who can unblock it, and what happens if it stays blocked.

Phase 3 · Done

DONE — Work is completed and delivered. The deliverable has reached its destination.

Phase 4 · Closed

COMPLETE — Fully closed and archived. The “we’re never touching this again” status. In ClickUp, tasks in this status can be hidden from default views to keep your workspace clean. This is where the archive, don’t delete principle lives — the data is preserved for learning and compliance, but it’s out of your daily view.


The One Priority System

A status system is only half the equation. The other half: make sure priorities mean something too.

Most teams mark everything as urgent, which means nothing is urgent. Instead, implement the One Priority System: each person can only have one Urgent task at a time.

When they complete it, they can designate the next most important thing as Urgent. If someone wants to flag a new task as Urgent, they have to explain why it’s more important than what’s currently flagged — which forces real prioritization conversations instead of everything-is-on-fire chaos.


Automation Recipes That Make It Work

The status system becomes truly powerful when you add automations. Four recipes turn the system from a naming convention into an accountability engine:

[VISUAL: blog1-automation-recipes.html]
Replace this block with the screenshot

Recipe 1 — When status changes to INTERNAL REVIEW: reassign to the Role Responsible (using your custom people field), add a review-request comment with a 2-business-day deadline, and set a reminder.

Recipe 2 — When status changes to EXTERNAL WAIT: log the date the task entered this status (for tracking client response times), notify the account manager, and set a 3-business-day follow-up.

Recipe 3 — When status changes to BLOCKED: require a blocker comment before the status change saves, notify the project lead, and add the task to a “Blocked Items” dashboard widget.

Recipe 4 — When status changes to DONE: prompt for Lessons Learned field completion, and notify the Role Responsible that work is complete.

Four automations. Zero status meetings. The tool enforces the system while you’re asleep.


The Monday Morning Status Board

Once the 9-status system is in place, create a Board view grouped by status. Your Monday morning now looks like this:

Open the Board. Scan left to right.

  • OPEN has 12 tasks? Good — your queue is healthy.
  • IN PROGRESS has 8? Check that nobody has more than three or four active tasks at once.
  • INTERNAL REVIEW has 5? Those need reviewer attention today.
  • EXTERNAL WAIT has 7? Check the dates — any been waiting more than three business days?
  • BLOCKED has 2? Those are your priority escalations.
  • READY FOR LAUNCH has 3? Confirm deployment dates.

Total time: under sixty seconds. Zero questions asked. Complete visibility.


Implementation: The 48-Hour Switchover

Don’t phase this in gradually. Status systems work best when everyone switches at once.

Day 1 (30 minutes) — Delete old statuses, create the nine new ones, set up automations for INTERNAL REVIEW and BLOCKED at minimum.

Day 1 (15 minutes) — Quick team walkthrough. Share the status definitions. Biggest message: “In Progress now means you’re actively working on it today.”

Day 2 — Review the Board view as a team. Address any tasks that are miscategorized. Expect some adjustment — that’s normal.

Week 2 — Your first status update meeting that you cancel, because you don’t need it anymore.


Your Move

Default statuses describe intent. The 9-status system describes reality — and reality is what needs managing.

Download the 9-Status System Template + Automation Guide — it includes the exact status definitions, all four automation recipes ready to copy, and a migration checklist for switching from your current system.

Want to see this built in real time? Watch Stop Asking for Status Updates on YouTube where I walk through the complete setup end to end.


Lee Cooley is the founder of Process Quotient. He helps service businesses build the operational systems that make accountability automatic — across ClickUp, Monday.com, Asana, and SmartSuite.