Jump to content

User:Toadspike/How to RMTR

From Wikipedia, the free encyclopedia

How to handle requests at WP:RM/TR in a few simple steps:

  1. Read the request. Does it make sense? If not, contest.
  2. Check the article's move history. Has the requested move been performed before? Has the article been through an RM or several BOLD moves? If so, contest.
  3. Check the article's Talk page. Are any past RMs listed? If so, contest.
  4. Are there any open AfD discussions, RMs, histmerge requests, noticeboard discussions, or any other process that would be disrupted by a move while ongoing? If so, contest.
  5. Do you see any other good reason not to perform the move? If so, contest.

At this point, if there was no reason to contest the request, you may perform the move. You are not required to perform the move exactly as requested – you may correct typos, unambiguous violations of WP:NCCAPS, or other issues you notice.

If you contest a technical request, be sure to ping the requester to let them know why. This is usually to the effect of "this request is not uncontroversial because...". You may also explain how to open an RM (by clicking the blue "discuss" link in their request).

If one of the above steps tells you to contest, but you believe that the move should still be performed, you may do so, but you must take responsibility for performing the BOLD move. Potential exceptions to the checklist include:

  • Reverting an undiscussed move, especially one during an RM or other process listed in step 4 above.
  • The title has been changed several times uncontroversially (e.g. sports teams that regularly change their names for sponsorship reasons).
  • The current title is obviously incorrect or violates a core policy (e.g. BLP violations, obvious vandalism).
  • The last RM was an extremely long time ago.
  • The last RM had minimal participation or closed as no consensus and is not recent.

If you are not sure what to do with a request, it is best to leave it for someone else to handle.

These three scripts are crucial for RM/TR: