Frame Challenge: We don't need separate mod/CM status tags - instead, we should be more discerning in how we apply certain status tags.

Status tags can be loosely grouped into two categories: "final" and "transitional". 

  - *Final* tags are added when a task or request is considered 'done'. No further update or consideration of the topic is required: [meta-tag:status-completed], [meta-tag:status-declined], [meta-tag:status-norepro], [meta-tag:status-bydesign]
  - *Transitional* tags are applied to tasks or requests that are in progress in some form, but pending some action *from the company*: [meta-tag:status-review], [meta-tag:status-reproduced], [meta-tag:status-deferred], [meta-tag:status-planned]

The recent CM [Community Asks][1] push, which saw massive CM activity on cross-site metas, only updated uses of *transitional* tags. Most notably on MSU, was the removal of [meta-tag:status-planned] from tag cleanups. Note that [questions with \[status-completed\] and \[tag-cleanup-request\]][2] were not touched, for example.

Thus, in my opinion:

### 1. Continue to use 'Final' tags freely

They aren't interfering with ongoing CM work, they  allow us to mark stuff as 'done', and they [help to filter out completed or declined requests][tag-cleanup-filter] with ease.

### 2. Use 'Transitional' tags only in specific circumstances

There are occasions where mods adding [meta-tag:status-planned] etc are useful, but probably the most likely use case is when you are simply keeping local bug/feature request posts up to date, when the topic of that post has received a staff response elsewhere e.g. on MSE or MSO, or in a Mod Chat room (and the staff have explicitly stated they're ok with an update being made public!).

For example, I added [meta-tag:status-planned] to [Can the review queues respect ignored tags?][arqade-review-ignore] <sup>Arqade</sup>, after seeing it applied to [Review Queues and Ignored Tags][mse-review-ignore] <sup>Meta SE</sup>.

Note: [meta-tag:status-review] is a special egg that allows us to raise a post for CM review. So continuing to use that one for that purpose is obvious.

### 3. We don't need to group by "planned" anyway.

If we are vigilant in applying *Final* tags, then anything without those tags can be considered as fair game to be considered, worked on, updated, and so on. Filters, like the [one I linked earlier][tag-cleanup-filter], can be used to the same effect as a dedicated 'planned' tag, but with the added benefit of not accidentally excluding ones where [meta-tag:status-planned] was never added. This might require a bit of cleanup on the mod's behalf.

If something requires action but the question and discussion doesn't make it clear: put what needs to happen in an answer, and update that answer with any stats or other updates as you go.



  [1]: //meta.stackexchange.com/q/401060/179041
  [2]: //meta.superuser.com/questions/tagged/status-completed+tag-cleanup-request
  [tag-cleanup-filter]: //meta.superuser.com/questions/tagged/tag-cleanup-request+-status-completed+-status-bydesign+-status-declined+-status-norepro?sort=Newest&uqlId=12 
  [arqade-review-ignore]: //meta.arqade.com/q/7079/28182 "Feature request on Arqade Meta"
  [mse-review-ignore]: //meta.stackexchange.com/q/178378/179041 "Feature Request on Meta Stack Exchange"