User:The Wordsmith/Requests for comment/Administrator conduct/Closing

Closing uncertified disputes
RfC Candidates which do not meet the requirements should be marked for speedy deletion with  after 48 hours.

Closing certified disputes
Certified disputes may be closed under any of the following circumstances:


 * 1) If no additional comments are given for an extended period of time, and the dispute appears to have stopped, or after about 14 days from opening, if no progress is being made and consensus is unlikely to be achieved. From the main page, such RfC/Us are typically "delisted due to inactivity" but may be "delisted due to lack of progress".
 * 2) The Arbitration Committee accepts a case on the matter or desysops the user by another procedure.
 * 3) The parties and/or participants to the dispute achieve consensus on one or more proposals, as determined by an uninvolved administrator.

Closing due to inactivity
RfC/ADMINs are closed when no additional comments are registered for an extended period of time, and/or the dispute appears to have stalled after 14 days with no consensus forming. Typically, the major activity in an RfC/ADMIN is usually within the first couple of days, and few discussions are productive after a very long time. Discussions may be closed early if the dispute has been resolved (see below), or, occasionally, discussions may continue longer if they appear to be making progress towards resolving the dispute. To close the RfC due to inactivity:
 * 1) Delist the RfC so that it no longer appears at Requests for comment/Administrator conduct/UsersList in line with the instructions on that page.
 * 2) Add the following text to the top of the RfC: rfcuarchivetop.
 * 3) Add the following text below that so that it appears at the bottom of the RfC: rfcuarchivebottom.
 * 4) Add it to the archives at Requests for comment/User conduct/Archive.

Closing due to other dispute resolution
RfC/ADMINs are also closed when the dispute has proceeded to another venue in dispute resolution. Bear in mind that if it has proceeded to arbitration, a case needs to have been accepted and opened (or resolved by motion) before the RfC/ADMIN should be closed. To close the RfC accordingly:


 * 1) Delist the RfC so that it no longer appears at Requests for comment/Administrator conduct/UsersList in line with the instructions on that page.
 * 2) Add the following text to the top of the RfC: rfcuarchivesummarytop.
 * 3) Add the following text to the bottom of the RfC (below where it says "--->"): ==Summary==
 * 4) Write the summary with a link to the exact venue/case where dispute resolution is continuing (e.g. "proceeded to [ arbitration]").
 * 5) Add the following text below that so that it appears at the bottom of the RfC: rfcuarchivebottom.
 * 6) Add it to the archives at Requests for comment/Administrator conduct/Archive.  Please make a note of where the dispute resolution process continued.

Closing by consensus
RfC/ADMINs which are closed by consensus require a motion to close; this motion should be visible on the talk page of the RfC/U and may not be made until a minimum if 7 days after RfC certification. Here, other participants can either express their support or opposition to closing at this time. Closure by consensus may or may not include a summary of the dispute or agreement. This is usually done when there is a clear consensus to desysop the user, or an alternative proposal (such as a topic ban or other restriction in lieu of desysopping) has achieved a strong consensus.

It is also possible to request that an uninvolved administrator close the RfC/ADMIN by leaving a note at Administrators' noticeboard.

If the consensus supports resolving in this manner, the RfC/ADMIN can be closed in the following way:


 * 1) Delist the RfC so that it no longer appears at Requests for comment/Administrator conduct in line with the instructions on that page.
 * 2) Add the following text to the top of the RfC: rfcuarchivesummarytop.
 * 3) Add the following text to the bottom of the RfC (below where it says "--->"): ==Summary==
 * 4) An uninvolved administrator should then write the summary that is agreed upon at the talk page by participants.
 * 5) Add the following text below that so that it appears at the bottom of the RfC: rfcuarchivebottom.
 * 6) Add it to the archives at Requests for comment/Administrator conduct/Archive with a very brief summary of the outcome.

Suspending RfCs
Occasionally, an RfC/U will be suspended because a significant participant is not currently available. The participant may be unavailable for any reason, including a voluntary withdrawal from editing, being blocked or banned, or the demands of travel, work, school or illness. If the person's absence makes effective dispute resolution unlikely, then the RfC/U may be suspended and then re-opened upon the return of the participant.