This is aninformation page. It is not anencyclopedic article, nor one ofWikipedia's policies or guidelines; rather, its purpose is to explain certain aspects of Wikipedia's norms, customs, technicalities, or practices. It may reflect differing levels ofconsensus andvetting.

Shortcuts WP:GRFAWP:GRFA WP:RFA GuideWP:RFA Guide

Please readReally simple guide to requests for adminship before you make a request for adminship, otherwise you might be wasting your own and everyone else's time. Self-evaluation is very important.

This is a guide to current practice at Wikipedia'srequests for adminship (RfA) process, a mechanism by which theWikipedia community decides who will becomeadministrators. In order to become an administrator, there needs to be a clearconsensus of support in the discussion regarding the candidate, which typically takes their contributions, past history with the project, commitment, qualifications, experience, level of trust, and overall fit for the role (among other things) into account when making a decision.

For an unprepared user, even if they're a very valuable contributor to the project, the process can be frustrating and even disheartening. Under no circumstances should any editor, otherwise considering acceptance of a nomination, interpret the contents of this guide as a barrier to nomination. Accordingly, no Wikipedian should refer to this guide for the purpose of deterring a candidate from accepting a nomination. This page is only a guide to current practice onWikipedia:Requests for adminship;it is not a policy.

For other pages with informal guides and advice for potential candidates, please see theminiguide to requests for adminship, and the more detailed page –advice for RfA candidates.

RfA is one of the two avenues by which the Wikipedia community developsconsensus on whether an editor should be granted theadministrator user rights, which gives them the technical ability todelete pages,protect pages, edit protected pages, andblock users (among other abilities).

Common areas where users may have expectations will usually be those that show:

1. breadth and duration of Wikipedia participation and experience;
2. participation in key areas, discussions, and processes on Wikipedia;
3. history of contributions, discussions, actions, behavior and conduct on Wikipedia;
4. appropriate approach and conduct as a community member (the quality of interactions, ability to work with others andresolve disputes, and the ability to remaincivil and diffuse heated discussions rather than escalate them);
5. understanding of the Wikipedia ethos and its most important norms and policies (including their "spirit" and intent); and
6. understanding of the norms that administrators must follow

Evidence of any concerns may also be raised and with questions asked. This is in order to help with reassurance with the community as to whether the candidate will present concerns in the future. Any other signs of helpfulness or work undertaken in the community will be seen positively.

The nomination process is not intended as a forum for voting on a nominee's popularity or strength as an editor. It is a forum by whichconsensus is generated on whether an editor should be granted the administrator user permissions. An editor should not construe the outcome of an RfA as a praise or a condemnation of their efforts as a member of the community. Instead, it is an evaluation of:

1. the candidate's abilities;
2. the likelihood that the candidate will use the administrator tools appropriately;
3. the level of trust with the community that the user will not become the cause or the center of community issues or concerns down the road regarding their use of administrator tools

An RfA is a very open voting process where your history of contributions, actions, discussions, conduct with other users, and use of judgment will be looked at by experienced (and sometimes opinionated) users – many of which after they have already made up their minds about what kinds of people they want as administrators. An RfA is open to everybody, including anyone you may have had disagreements with in the past, as well as new and inexperienced users you may be disagreeing with at the current time.

Some users will find the level of scrutiny and frankness by other users in their RfA discussion to be very difficult; some have evenleft Wikipedia as a consequence of an RfA that went poorly and against their favor. This should not happen, as this process does not judge an editor's overall value and impact to the Wikipedia project. There aremany good editors on Wikipedia who provide high-quality contributions to the project, and who wouldnot make good administrators.

Things that a potential administrator nominee should consider before accepting a nomination include:

• There are a lot of administrator-level things that you can do on Wikipedia without being an administrator! You might be here because you've made several hundred edits and contributions and are now looking for new avenues, challenges, or ways to help the project. Wikimedia projects are unique and different from most other websites in that they allow normal users to perform duties and tasks that normally only administrators could perform. There area lot of administrator-level areas that you can participate in, as well as administrator-level duties and tasks that youcan perform without being required to be one; for example:

• get involved with patrolling forvandalism and bad faithdisruption, reverting and removing bad edits and changes, and leaving appropriatewarnings or notices for the users responsible for it.
  • after you've been reverting vandalism for some time and have gained enough experience, you can be granted withrollback rights, which make reverting vandalism quicker and more convenient.
• help out with patrollingnew pages, reviewing legitimate page creations while tagging and reporting pages that have issues, contain violations ofpolicy, or were created in bad faith.
  • after you've assisted with patrolling new pages and with finding troublesome pages that contain policy violations, vandalism, or other issues for some time and gained enough experience, you can be granted with thenew page reviewer rights, which allow you to mark new pages aspatrolled orreviewed using the relevant tools.
• assist with variousWikipedia maintenance projects and tasks, such as reviewing requests made by other users, participating in page deletion discussions, fixing pages or content that are tagged as requiring cleanup.
• help others with clearing out theWikipedia backlog of requests, maintenance tasks, and issues that need to be resolved.
• get involved in differentWikiProjects that focus primarily on topics or subject areas that interest you.
• get involved in translation.
• help new users by responding to their questions at theteahouse or thehelp desk.

There are so many other admin tasks that you can already do on Wikipedia without requiring user permissions or user rights beforehand. You can always consider applying for the appropriate user rightsafter you begin finding certain duties or tasks that you're unable to perform unless you have them. Once you've participated in a number of different administrative areas, gained a number of user rights or permissions and demonstrated that you can use them appropriately, and gotten to the point where certain duties and tasks in the areas that you're involved with require an administrator in order to complete, you can always consider applying for the administrator user rights at that time. Otherwise,there isn't much of a point in trying to become an administrator. It's important to remember that only after you've gained a good amount of experience in various admin-related tasks are you likely to succeed in an application for adminship.

• RfA can be a harsh process. Your past record will come under scrutiny by many users, and anyquestionable actions that you've performed in the past can lead to intense open discussions about them. If you aren't experienced in handling conflicts, this can make your request for adminship become very distressing. On the other hand, you can take the experience as an opportunity to measure your skills in conflict resolution.

• Nominees with very low edit counts are less likely to succeed. Many administrator nominations for editors with low edit counts have been rejected for this alone, although some have succeeded. With fewer edits, you should be prepared to respond to this objection, or, better, explain in your nomination acceptance why you think you would nevertheless make a good administrator. Editors with a limited length of time of active experience on Wikipedia can expect similar concerns. If you are unsure if you have enough edits or experience, consider asking another Wikipedian or two that you trust before leaping into an RfA.RfA standards have historically risen over time.

• RfA contributors have differing standards for what they consider to be acceptable administrator candidates. A full list of links to individual voters' RfA criteria pages can be found atRfA essays and criteria. RfA voters may also use standards that may seem perverse or irrational. It is generally not well looked upon for the nominee to question the validity or good faith of those standards. But while each RfA contributor may use whatever criteria they wish, you can ask them why they think a criterion is important.

• Some people who oppose RfAs do not explain their opposition. This does not make their votes inherently worthless. While it is generally regarded as poor form not to explain the rationale behind a vote, it is not required. Some contributors may not wish to explain their rationale because they wish to avoid creating a sense of piling on. If the user opposes your nomination without an explanation, please do not feel offended; it is most likely not personal. By the same token, you should be honest if you are voting on a nomination. Do not be afraid to oppose for fear of hurting the nominee's feelings. It is better to stay out of a nomination instead of voting dishonestly.

• Ask yourself, "Am I ready to be an administrator?" Administrators can be and often are more involved in contentious disputes than regular editors. If you think you will likely not respond well in such situations, perhaps being an administrator is not for you. Adminship is not a statement of worth or acceptance in the Wikipedia community. Some of the most valued and active editors have said they do not want to be administrators, and many administrators find that they prefer to contribute largely or solely by editing articles.

• Declining is allowed. Declining a nomination will not be held against you and can show a desirable thoughtfulness; you can always accept a later nomination.

• Administrator status is not a trophy. Editors who regard being an administrator as an affirmation of their contributions as an editor or an award for good editing or other good service will generally be disappointed. Administrator status does not place you in an elevated status within Wikipedia. Since many editors believe administrators should follow a more strict code of conduct than the average user, the opposite may occur. Every good-faith editor, from the newest editor to the most experienced bureaucrat, has the same status within Wikipedia. You will not gain respect simply by being an administrator. Adminship is, in essence, janitorial duties for Wikipedia. (Hence the mop used to symbolise administratorship.)

• If you make adminship your primary goal you are less likely to succeed, even if you undoubtedly follow policies and have a high edit count, but rather if you make improving Wikipedia your goal then adminship shall come naturally.

The nomination process has clear instructions for constructing, accepting, and posting a nomination. A number of RfA contributors look askance at nominees who do not follow the instructions properly. Administrators are expected to read and follow policies. The inability to do this here is a bad sign. If something is unclear, then ask the person who nominated you, put a message on the discussion page ofWP:RFA, or ask a user who has nominated someone else. Avoid mistakes rather than making them and then fixing them.

RfA contributors want to see a record of involvement and evidence that you can apply Wikipedia policies calmly, maturely and impartially. What are often looked for are:

• Strong edit history with plenty of well referenced material contributions to Wikipedia articles.
• Varied experience. RfAs where an editor has mainly contributed in one way (little editing of articles, or little or no participation in AfDs, or little or no participation in discussions about Wikipedia policies and processes, for example) have tended to be more controversial than those where the editor's contributions have been wider.
• User interaction. Evidence of you talking politely and helpfully to other editors on talk pages.
• Trustworthiness. General reliability as evidence that you would use administrator rights carefully to avoid irreversible damage, especially in the stressful situations that can arise more frequently for administrators.
• Helping with chores. Evidence that you are already engaging in administrator-like work and debates such asRC Patrol andarticles for deletion.
• High quality of articles. A good way to demonstrate this is contributing to gettingarticles featured, althoughgood articles are also well-regarded.
• Observing consensus. A track record of working within policy, showing an understanding ofconsensus.
• Edit summaries. Constructive and frequent use of edit summaries is a quality some RfA contributors want to see. If you haven't already set your defaults to force an edit summary with every edit, it is worth doing so before RFA and stating this in your application. SeeWikipedia:Edit summary.
• A clean block log as evidence of good editing behavior (if you have any blocks from more than one year ago, people will expect an explanation as to how your editing has changed to make this unlikely to happen again).

These points are not mandatory and there are always exceptions, but if you think back over your contributions and any of these is missing, it may be better to broaden your experiencebefore an RfA.

There are also several other things that contributors will raise, such as whether you have anemail address set. This is important for administrators, who may need to be contacted by users who have been blocked from editing.

• Complete answers to the RfA questions. Curt or uninformative answers to the standard questions are mildly offputting for some RfA contributors. Spend a bit of time preparing your answers; there is no time limit to the acceptance of a nomination.

Some editors have listed their individual rough criteria for support on theAdvice for RfA candidates page.

No matter how experienced you are, some actions will cause problems. In roughly decreasing order of seriousness, here are some things which, if seen in your edit history, will be raised and thoroughly discussed:

• Vandalism: A persistent and unreformed vandal will never be made an administrator; one of the primary tasks of administrators is fighting vandalism (and a truly bad administrator could cause serious damage to the site). Even a relatively minor disruption, like making a joking edit to an article, can cause problems.
• Incivility: If a nominee has responded to unpleasant or irritating users by leaving insulting messages which violate the spirit ofcivility.
• Intransigence: If a nominee has ever refused to be involved in good faith efforts to reachconsensus on talk pages, and instead engaged in edit wars.
• Controversial activity on AfD: Voting according to criteria not relevant to the purpose of AfD, persistently starting AfDs on articles on the kinds of subjects generally (let alone explicitly) recognized as worth an article.
• Incorrectly nominating articles for speedy deletion: Nominating articles for speedy deletion when they don't meet thecriteria for speedy deletion can disturb many contributors to the RfA, due to fear that the nominee will wrongly delete articles without review.
• Abuse of process: If a nominee has ever started an inappropriateRfC, or made seemingly frivolous complaints via official channels.
• Edit wars: If a candidate is prone to repeating a single edit after it becomes obvious that there is a disagreement with it. To most RfA contributors, it does not matter who isright, it matters how a candidate handles themselves during a debate.
• "Advertising" your RfA: Some editors do not like to see an RfA "advertised" by the nominee on other people's talk pages or onIRC. RfA is not a political campaign. The intent is to developconsensus. Impartial evaluation of a candidate is the goal, rather than measuring their popularity.Canvassing is generally looked down upon. Consider using{{RFA-notice}} on your userpage, which is a more neutral way to communicate your RfA to other users.
• Use ofsockpuppet accounts to avoid scrutiny, or to mislead the community about your past editing history.
• Blocks: If you've been blocked, voters will want to know why and what you've learned from this, especially if you've been blocked in recent months.
• Elaboratesignatures: Some have a low opinion of editors who create fancy signatures, especially ones with special characters and images.
• Long gaps in editing: Unless you have a good reason that you state on your page, a steady edit history in recent months is preferred.
• Over-eagerness: Multiple RfAs in a short timespan can be interpreted by some as being 'power-hungry'.
• Biting newcomers: Administrators are expected to treat editors equally and acknowledge the opinions of all Wikipedians.

However, many RfAs have succeeded despite some of the above. The important factors are:

• Time. If a nominee has demonstrated high standards of conduct for a few months, the RfA contributors may discount earlier undesirable behaviour.
• Disclosure. If a nominee brings up past missteps themself, and either apologizes or explains how such missteps will be avoided in the future, the candidacy will be more likely to succeed.
• Approach to opposing votes. Responding in a calm, rational, and (if needed) apologetic manner will be to a candidate's credit. A candidate who shows anger or frustration or makes insults when presented with opposition is likely to engender more opposition.

Most users are sympathetic to special circumstances or serious conditions. However the well-being of the project and ability of a candidate to carry out adminship without undue stress and problems are paramount. The communityhas endorsed adminship for people who have chronic or serious clinical conditions, schizophrenia being one example. Such conditions are not necessarily "blockers" at RFA. Legitimate concerns would include impact on the project, impact on your judgment and interactions, capacity to cause "blow-ups" or other problems, evidence it can be managed so as not to cause a problem, etc.

If you are affected by a condition or circumstance that affects your editing or could do so, then you may wish to disclose it. If you do then readers will probably look for three main things:

1. Brief information, what the condition is and the effect it may have on your work as an editor or admin
2. Examples or information how it has impacted you in past editing (if it did) or on other projects and examples how you handled it
3. Steps you will take to minimize any impact if RFA is successful.

Depending on the condition you might consider things like these in your nomination or in a disclosure statement:

1. Matter-of-fact-ness, stating the issue and its impact in a sentence or two. Most people don't need an essay.
2. What effect does the condition, or "bad periods/days" have on you in terms of Wikipedia, stress, judgment, admin tools, "drama" and "fairness" (if applicable), or whatever else is relevant at RFA?
3. Is it ongoing or does it have "good" and "bad" days or periods? If the latter, can you usually recognize onset and take action before they can be a problem?
4. Steps you would take to ensure the condition doesn't impact your editing or conduct if you pass RFA? For example, would you cease editing if you feel a bad period coming on, or would you be competent to decide not to use tools or take part in some issues, or disengage?
5. If your condition requires absence or non-responsiveness or disengagement at times, what steps have you taken to ensure these don't disrupt Wikipedia? (Everyone takes breaks but some conditions cause absence or disengagement at zero notice)
6. If your condition has already been coped with during your editing history, can you show this? Users will be more convinced you can cope well in future (and it won't be disruptive) if you can show you have coped as an editor in the past.

Even if you disclose an issue,nobody needs to know actual specifics of treatments, names of medications etc. If a treatment has helped prevent symptoms then it's enough to say (eg) "since 201x meds have kept me largely free of symptoms". You don't need to disclose your entire medical history or describe your whole offline life. Users just need the information that lets them assess the degree of risk of impact, severity, mitigation and management for the project. You may want to ask another user you trust about the level of detail before you post.

If you have been involved in discussions on very controversial articles, your adminship may be a target for heated objections on the basis of your involvement in those pages. This may reduce your chances of becoming an administrator. In some cases, voters may attempt to maintain a "balance of power" across controversial subjects by opposing all potential admins involved on the opposite sides of controversial edit wars.

It may be a good idea for you to highlight the controversy in answering the standard question"Have you been in any conflicts over editing in the past or do you feel other users have caused you stress? How have you dealt with it and how will you deal with it in the future?". You can note how you dealt with the controversy, cite example edits by you and your responses to uncivil comments made by others. In referring others to a past edit it can be useful to provide a "diff", a unique and durable link to a post. However, if youhave been involved in edit wars (other than against blatant vandalism), or been uncivil on those pages, it may adversely affect your RfA.

Nominators should be careful in their decision to nominate someone for administrator status. As noted above, the RfA process can lead to unsavory results. A nominator should consider the possibility of the negative impact on a nominee, and ensure they are making appropriate nominations.

A nomination consists of anintroductory nomination statement (example here), followed bythree initial questions (shown here) to be answered by the nominee. When you craft a nomination for someone, including yourself, you should outline in the nomination statement why you think the nominee should be an administrator. You might offer some information on where the nominee has done significant work, areas where the nominee has already helped out with administrator appropriate tasks, how long they have been with the project, and their ability to handle stressful situations. Single-line nomination statements will do little to aid the nominee, and may hinder the RfA.

When nominating someone, it is generally a good idea to ask them if they would like to be nominated before crafting an RfA nomination per the instructions atWikipedia:Requests for adminship/Nominate. If the person you want to nominate is willing to accept the nomination, you may place the{{subst:RfA-nom|YOUR USERNAME}} template on their talk page. This provides some basic information on what the nominee should do.

Once the RfA has been created, it is a good idea to work in concert with the nominee to carefully craft the nomination before listing it atWP:RFA. You can advise the nominee on their answers to the questions, fix any errors that might have been made on the RfA either by yourself or the nominee, and generally prepare the RfA for a successful run. Common errors include not formatting the closing date properly, not officially accepting the nomination on the RfA, and the nominee voting for themselves. Poorly prepared RfAs are not looked upon well by RfA contributors as for some this shows a lack of careful attention to process and detail and a lack of respect for the RfA process.

While voting is in progress, be ready to answer any enquiries the applicant puts to you. Should the process go sour, consider advising the applicant of the option to withdraw (asClosure below).

The RfA nomination process evolves. Initially nominations were an ad hoc assemblage of comments made on a mailing list. Later, the process became more formalized as theWP:RFA page. As time has gone on, efforts have been made to improve the process. The process we have in place now is relatively straightforward.

Either you or another editor may nominate you to be an administrator. Anyone can be an administrator, and anyone can nominate a candidate. However, keep in mind that nominees who have not been on Wikipedia for very long are not necessarily well regarded, as they are less likely to perform effectively as administrators and they are not widely known by RfA voters. It's considered good practice to approach the nominee first to find out whether they would accept the nomination.

To nominate yourself, follow the instructions as they are outlined atWikipedia:Requests for adminship/Nominate. For someone else to nominate you, they should likewise follow the appropriate instructions on that page. There is also a list of editorswilling to consider nominating you. If you have been nominated, then again follow the instructions on that page. Once, by following the instructions, an RfA has been transcluded (i.e. posted) toWP:RFA, the nomination is open for discussion. RfA subpages should not be commented on before being posted to RfA, nor should votes be cast on the RfA subpage until the nomination is posted to the RfA page.

Administrator nominees should move slowly in this process. There is no deadline, and no need to rush. It is better to get it right than to move too quickly and make errors.

An RfA remains open for seven days, beginning from when the nomination is posted toWP:RFA. RfA contributors will make comments when they wish. RfA contributors will generally add additional questions to the standard three questions that currently are part of every RfA. Administrator nominees should stay involved on their RfAs so that they may answer these questions or any other comments raised on their RfA. Absence by the nominee from the RfA process during the seven days it is open can harm the chances of success. While it is appropriate to respond to comments and questions raised on the RfA, it is important to keep in mind that the RfA is not a forum for debate except as it closely relates to the nominee's acceptability as an administrator. Poor behavior by an RfA candidate will generally have negative consequences.

Sometime after the seven days for the RfA have elapsed, abureaucrat will review the RfA and close it. A bureaucrat will close the RfA as soon as this is feasible, which may be hours or even a day or two after the formal closing date. Do not remove your own RfA fromWP:RFA unless you are intentionally withdrawing your nomination from consideration.

Currently, there is an open-ended debate regarding whether a nomination that is going poorly should be removed fromWP:RFA. There is no standard by which such nominations are removed, nor anyconsensus on whether they should be removed. Nevertheless, some bureaucrats and other parties occasionally do remove RfAs that are going poorly. You should not take offense if this happens; it is being done to protect you from ill will that may be generated by the RfA. If you did not wish to have your RfA prematurely removed, you may petition the person who removed it to reinstate it. You may find who removed the RfA by reviewing the page history ofWP:RFA.

If you would like to withdraw your nomination after it has opened, you may do so simply by editing the RfA to strike out your acceptance of the nomination and indicating your desire to withdraw instead. To do this, place <s> before your nomination acceptance, a closing </s> after your acceptance, and indicate your desire to withdraw. This might look like this:

Candidate, please indicate acceptance of the nomination here:I accept the nomination.I withdraw my nomination.

If you'd like, you may remove the RfA fromWP:RFA on your own, but you are not required to do so. If you do so (though again you are not required to), you should edit the RfA after you have removed it fromWP:RFA and place{{subst:rfaf}} at the very top of the page,{{subst:rfab}} at the very bottom of the page, remove the entire line that contains the "Voice your opinion on this candidate" link and replace it with '''Final''', change the ending date to the date you withdrew, and update the final tally of votes. Additionally, you should editWikipedia:Unsuccessful adminship candidacies appropriately to include your nomination. The date you should use on that page is the date you withdrew.

The community is divided about successful candidates posting unpersonalised "thanks for voting" messages to voters' talk pages, though personalised thanks for particular reviews, comments and questions are perfectly in order. If you do send a message to everyone please respect those editors who have put "no Thankspam" messages on their talk page, and make sure your thank you does not look like a barnstar. A perfectly acceptable alternative is to post a thanks message insteadon your own talk page and/or the talk page of your RFA.

It is the job ofbureaucrats to determineconsensus when closing a request for adminship. As RfA is not a straightforward majority vote, there is no precise "pass" or "fail" percentage, and the bureaucrat may discount comments which were made in bad faith or are of questionable validity. However, as an approximate guide, you are likely to pass if you achieve at least 75% support. Nominations which receive less than 65% support are unlikely to be successful, except in exceptional circumstances.

If you feel that a nomination is wrongfully declared as unsuccessful, you may petition the bureaucrat who made the decision. This can usually be determined by looking at the page history ofWP:RFA and seeing which bureaucrat removed the RfA from the page. Bureaucrats do have the option of extending RfAs where they think this is necessary. Another possibility is to wait for some time and either renominate yourself or have someone else nominate you for a second time. Many current administrators did not pass their first nomination, yet had a later nomination easily succeed. In some cases, administrator nominees have tried more than twice. In one case, a nominee tried seven times. Your first nomination is not your only chance to become an administrator.

Bureaucrat nominations (RfB) are also considered onWP:RFA. Bureaucrats are at present responsible for the following tasks: determiningconsensus on RfA and RfB, and granting rights on successful nominations; processing the removal of administrator rights due to inactivity or arbitration committee requests; determining consensus forbot approvals group membership applications; and assigningbot flags. The RfB process is similar in nearly all respects to the RfA process with a few exceptions:

• Bureaucrat nominations are generally done only by request of the nominee.
• The bar for determination of consensus for acceptance as a bureaucrat is higher than for an administrator. ("In general around 85%")
• Bureaucrat nominees typically undergo significantly more scrutiny than an administrator nominee.
• Bureaucrat nominees are expected to be fully aware of current debates around RfA and of its guidelines.

As a result of the higher level of consensus required, almost half the requests for bureaucrat status have been rejected, whereas more requests for adminship are approved.

• A strong participation in requests for adminship, with sensible rational reasoning for opinions.
• History of productive administrator work, especially with regards to determining consensus (e.g. in XfDs).
• Civility.
• A good record as an administrator.
• A need for bureaucrats.
• A full understanding of what consensus to promote is, and understanding of when to and when not to promote under extraordinary circumstances.
• A good record of providing clear reasoning for their actions.

Former administrators may seek reinstatement of their privileges through RfA unless prohibited from doing so by an arbitration remedy.

Admins who resigned voluntarily, under uncontroversial circumstances, can ask to skip RfA. Upon a review to confirm that the user both was in good standing at the time of the de-adminship and is in good standing currently, a bureaucrat may restore access rights. If there is any question that reinstatement would lack communityconsensus, the user will be referred to RfA. The guiding principle for such decisions, perWikipedia:Bureaucrats, is that bureaucrats may grant adminship only when doing so reflects the wishes of the community.

• Wikipedia:Miniguide to requests for adminship – a compressed summary version of this guide
• Wikipedia:Administrators – the admin policy, including requirements
• Wikipedia:Administrators' reading list – read before and use as a reference list later
• Wikipedia:Administrators' guide – the how-to collection for admins
• Wikipedia:Advice for RfA candidates – also includes a list of individual users' criteria for admin candidate assessment
• Wikipedia:RfA cheatsheet – advice on the questions you'll be asked as a candidate
• Wikipedia:Arguments to avoid in adminship discussions
• Wikipedia:Requests for adminship/Debriefs – post-RfA thoughts from RfA candidates
• Category:Matters related to requests for adminship – lists many essays and other materials of use to candidates
• Wikipedia:Requests for adminship – when you're ready

• User:EVula/admin/Premature RfA, a useful template forWP:NOTNOW closures.

• Wikipedia information pages
• Wikipedia adminship
• Wikipedia how-to
• Requests for adminship
• Wikipedia administrator help
• Matters related to requests for adminship