Kodavara Guide
ClickUp Status Audit: Stop Every List Speaking a Different Language
Statuses can be set at Space, Folder or List level, and Lists inherit from their parent unless overridden. Over time that gives you dozens of near-duplicate statuses, reports that cannot compare teams, and automations that miss tasks. This guide shows how to audit statuses, standardise them and clean up without breaking work in flight.
Last reviewed October 2026. ClickUp changes often, so check ClickUp's help center for the latest. Written by Kodavara, an independent ClickUp Partner. Not published or endorsed by ClickUp.
What ClickUp Does Today
What You Can Do Natively
Start with the features available on your ClickUp plan.
Statuses at Every Level
Statuses are defined at Space, Folder or List level. Folders and Lists inherit from their parent unless you override them.
Status Types
Statuses sit in types: Active, Done and Closed. A Not started type is switched on through a ClickApp.
Moving Between Lists
Moving a task to a List with different statuses prompts you to map the old statuses to the new ones.
Time in Status
A ClickApp measures how long tasks sit in each status, on higher plans. Renaming a status resets its history, so rename with care.
Where It Falls Short
The Gaps People Run Into
If these are your problem, keep reading.
- A task has one status even when it lives in more than one List, so different Lists cannot show it differently.
- Renaming or merging statuses can reset Time in Status data and break automations that name the old status.
- Near-duplicates such as In Review, Review and Reviewing split reports into separate buckets.
- Nothing enforces a standard set, so new Lists drift back to custom statuses.
- Moving a task between Lists with different statuses forces a mapping decision each time.
Worked Example
Example: Consolidating Statuses
A typical cleanup map. Values are illustrative.
| Found In Use | Standard Status | Type |
|---|---|---|
| To do, Todo, Backlog | Backlog | Not started |
| In progress, Doing, WIP | In Progress | Active |
| Review, In review, Reviewing | In Review | Active |
| Blocked, On hold, Waiting | Blocked | Active |
| Done, Complete, Finished | Complete | Done |
| Cancelled, Dropped | Closed | Closed |
Sample data for illustration.
The Configuration
The Configuration: What We Build and Monitor
We audit what exists, design a standard, and migrate safely.
| Step | What We Do | What We Watch |
|---|---|---|
| Inventory | List every status in every Space, Folder and List with task counts | Unused and near-duplicate statuses |
| Standard Set | Design a small shared set plus approved exceptions per team | Teams needing a real exception |
| Dependency Check | Find automations, views, dashboards and integrations that name each status | Anything that breaks on rename |
| Migration Plan | Map old statuses to new, in batches, with a rollback note | Tasks in flight |
| Apply | Change statuses at the highest sensible level so Lists inherit | Lists overriding the standard |
| Guardrails | Templates and a rule for new Lists, and a periodic re-audit | Drift back to custom sets |
How Workbench Workspace Audit Does It
Set It Up Once
Workbench audits statuses and compares them across workspaces. We design the standard and run the migration.
Audit Statuses
We inventory every status and how often it is used.
Design the Standard
We agree the shared set and exceptions.
Check Dependencies
We find the automations and reports that name old statuses.
Migrate in Batches
We map and move tasks, starting with a pilot.
Lock It In
We set templates and a re-audit date.
FAQ
Common Questions
Not here? Ask us.
How do ClickUp statuses inherit?
Statuses can be set at Space, Folder or List level. Folders and Lists inherit from their parent unless overridden.
Will renaming a status break anything?
It can. Time in Status history resets, and automations or views that name the old status may stop matching, so check dependencies first.
Can one task show different statuses in different Lists?
No. A task has one status even when it is in several Lists.
What happens when I move a task to a List with different statuses?
ClickUp prompts you to map the statuses.
How many statuses should we have?
As few as the process needs. Most teams do well with a shared set of five to seven and a small number of approved exceptions.
Can you compare statuses between two workspaces?
Yes. Workbench compares custom fields, tags and statuses side by side.
Keep Reading
Related Guides
Workspace Cleanup
How to clean up a messy ClickUp workspace: merge duplicate custom fields, remove unused setup, and audit what you have before you delete.
Read the Guide →GuideCustom Field Audit
Audit ClickUp custom fields for duplicates, unused fields and inconsistent types.
Read the Guide →GuideGovernance
How to govern a growing ClickUp workspace: ownership, naming standards, templates, change control and a runbook, so it stays tidy as more people join.
Read the Guide →LiveWorkbench Workspace Audit
The Kodavara app behind this guide, with features, examples and FAQs.
Learn More →Want Help Setting This Up?
Tell us what you are trying to get done and we will point you at the fastest route.