For context on how this process came to be, please see our initial commitment to responding to Meta and Mods, our guidelines for the testing period, and the results of the initial test and next steps.
For context on the current status tag definitions and usage see this post, and for our current reporting metrics framework see this post.
The question contains guidance that is applicable for as long as this process is in effect. Answers containing the response targets and guidance specific to a given period will be posted every quarter. The answer that relates to the period currently in effect will be accepted so it's pinned to the top. Once that period has elapsed, that answer will be updated to include stats for how we did with regards to our response targets as well as some noteworthy posts, as defined in this Meta post.
We realize that there are a lot of outstanding posts all over the various Meta sites on the network that have not been addressed by staff — some of them posted a long time ago too. To ensure that the most relevant of those get surfaced and responded to, we ask that you focus mostly on resurfacing old questions that relate to either something only a Community Manager would be able to respond to, or to things currently being worked on by the various product teams as part of their quarterly roadmapsquarterly roadmaps (which allows us to easily find these older discussions so that we can use them as part of our research).
If you’re unsure, talk to your fellow mods about what they think, or feel free to ping a CM in The Teachers’ LoungeThe Teachers’ Lounge for guidance. It’s OK if moderators err on the side of over-escalating issues, rather than under-escalating them: if the CM Team determines something could have been answered without having to elevate to staff, it presents a good opportunity to point moderators to where that information could have been found, as well as to tweak this guidance.
If the post already has the status-review tag, ping a CM in The Teachers’ Lounge, and we’ll add it to our internal system manually.
The CM Team will categorize and prioritize the post, and will then respond when they have the necessary context to do so. If they don't, they'll pass it along to the relevant team, which can be the CMs or any relevant product team. It will then be worked into that team’s existing weekly workflowworkflows, with the intent of being replied to as soon as the team can manage to.
Note that the commitment being made is to respond to as many posts as possible —ensure that could mean answering or leavingposts escalated do not sit on a commentgiven process tag for too long, or addingand will eventually reach a differentconclusive state, as per the definitions for status tagtags presented in this post, and the target framework defined in this post. This doesn’t necessarily mean implementing feature requests or fixing bugs — hopefully that will sometimes happen as appropriate, though.
2020:
2021:
2022:
2023:
2024:
- N/A, as process was undergoing internal changes; no escalation guidance or reporting was shared publicly
2025:
