User:Murph146/advice for RfA candidates

 Becoming an Administrator RFAs Policies & Guidelines Tutorials & Resources 

 Administrators The Nomination Process Requests for Adminship (RfA) Advice for RfA Candidates New Admin School Policies and Guidelines Tutorial Based Information (Videos & PDFs) 

No big deal

The process of becoming an administrator is described on Wikipedia:Requests for adminship. The tasks that admins actually do are described at Wikipedia:Administrators. Candidates for adminship must be nominated (either by another user or by themselves), answer a series of questions, and then be subjected to a 7-day community discussion as to whether they will be accepted as admins by the community. Successful candidates will almost always have edited Wikipedia for at least several months and will have thousands of edits in various 'maintenance' areas of the project, and will have made measurable contributions to articles. Solid preparation is absolutely essential in order to have any chance of success.

See also: Guide to requests for adminship, Miniguide to requests for adminship, Administrators' reading list, and What adminship is not

More essays (especially those on users' !voting criteria) and advice pages are listed at the end of this page

The footnotes contain links to important examples. Viewed separately, they are an integral part of this advice.

Note: If you are below the age of majority (18 in most countries) you should read Guidance for younger editors first.

Two thirds of all RfAs fail – mainly because candidates did not read the instructions and advice pages.

Preparing yourself for adminship

If you would like to be an admin someday, you should preferably begin preparations at least six months before making your application. You should thoroughly read the instructions and advice listed above, and on the RfA pages. Review as many old successful and unsuccessful RfAs as possible, and be absolutely sure to generally meet the criteria required by regular !voters (See the list of essays at the end of this page). Users who are not likely to pass may be considered by the community to be immature, or time wasters who are just seeking feedback on their editing. Some candidates whose first RfA failed, pass a second run with flying colours, but previous attempts will be closely looked at again by the community. If after reading this you feel you are still not ready to be an admin, you may wish to consider joining the Admin coaching scheme – do bear in mind however, that it will not be a shortcut to adminship, and it will not alter any personal traits that are incompatible with being an admin.

• Basics: Although administrators are responsible for blocking users, protecting and deleting pages, and closing some debates, some other actions can have an effect on the entire Wikipedia web site. Whichever areas candidates want to specialise in, they must convince the community that they can be trusted to use all the tools responsibly and intelligently. They must also demonstrate that they act civilly in an adult and mature manner at all times.
• Length of membership: Simply being a Wikipedian for a long time may not count for much. The criteria are based on what the candidate has actually done in that time. In contrast, being a Wikipedian for too short a time is usually an issue. It is extremely rare to become an Admin within less than six consecutive months of activity. Individuals who might have the right temperament from day one must still demonstrate a broad knowledge of procedures and policies.
• Content: Edits to article space that are mainly minor additions or clean ups will not generally be taken into consideration. Content is the body of encyclopedia articles. Although it is possible to achieve a high edit count without ever creating pages or contributing to articles, building an encyclopedia is the sole object of Wikipedia. Many editors believe that it is essential to adminship and that only significant content work, especially on near perfect articles such as Good Articles and Featured Articles, can adequately demonstrate sufficient knowledge of many of the policies and principles that admins must observe.
• Diversity: Candidates who have only been active in a limited number of areas (see pie chart) may incur opposition. As the tools can also be used in many areas in which the candidate is less familiar, a relatively broad scope of previous activity in policy and decision making is expected.
• Speciality: Unless candidates have demonstrated a very high level of specialisation and contribution in some areas needing advanced knowledge such as bots, scripts, complex templates, copyright, etc., it is unlikely that they will be elected based on a 'need' for the tools for a single purpose.
• High edit count: A high edit count (see pie chart) does not always demonstrate experience. The criteria are based on what and where those edits were. Editors with a high number of edits, especially automated ones, have been known to fail.
• Low edit count: A low edit count (see pie chart) will obviously be regarded by most as evidence of insufficient experience. Contributions are the only available basic metric of performance. Editors with low counts generally fail.
• Judgment: Candidates should be able to demonstrate that they can make carefully considered contributions. The criteria are based on the ability to assess consensus in areas that will require admin decisions, input, and discussion closures; and especially to correctly implement deletion and blocking policies.
• Civility: Candidates should demonstrate cool headed participation in discussions, and to have overcome earlier lapses in civility. They should never have engaged in making personal attacks.
• Creations: Candidates' own creations should demonstrate a knowledge of article policies, guidelines, and style and the pages should be free of old tags. A high number of creations that are mainly stubs, redirects, or disambiguation pages, might not be taken into consideration.
• Talk: charts that reveal an overwhelming majority of edits to user talk pages may demonstrate that a user's participation at Wikipedia is more for social or off-topic purposes than for building an encyclopedia.
• Blocks: Users who have been previously blocked for any legitimate reason(s) will be required by the community to have learned from their block(s), and have been block free for a considerable length of time (often 1 year).
• Fresh start: It is generally expected that 'fresh start' users have declared their intention by closed communication to Arbcom.
• User page: !Voters look at user pages. An uncluttered page with intelligent content goes a long way to demonstrating maturity. An untidy user page may signify an untidy mind and careless work. A lot of highly self promotional content, userboxes, and/or excessive external links to one's own private and working life could be seen as the sign of a bighead and a possible power pusher.
• Maturity: There are no age restrictions for being an admin. The criteria are based on the users' common sense, good judgment, and good prose. 'Cool-talk' and 'teen-talk' may win fan club !votes, but may not go down so well with older editors. Wikipedia has several very young successful admins; it also has a lot of older people who behave like children.

Specific points

1. Your username should not be unusual or overly long, and should respect Wikipedia user name conventions. Some !voters will oppose if they feel a name does not look serious enough for an editor of an encyclopedia.
2. Flamboyant signatures are seen by some as ostentation. There are absolutely no rules against custom signatures, but there are guidelines: Readability (it might look fine in your browser and on your computer, but not on others). It should be pronounceable: non-Roman fonts, symbols, and Dingbats are discouraged. Fancy signatures are seen by many !voters as a lack of maturity.
3. Talk page clean up is not recommended. Removing warnings or contentious discussions leaves them in the page history where they can still be easily accessed by anyone. The many admins who !vote at RfA also have the advantage that they can view any pages that you have asked to be deleted.
4. Barnstars should not be left on your talk page. There are absolutely no rules against having barnstars on a user talk page, however, some !voters may see this as unnecessary ostentation. Most users move their barnstars to their user page or sub page. Transfer barnstars to your user page.
5. Userboxes that express opinions on politics, religion, or sexual orientation have been known to be reasons for 'Strong oppose' !votes based on fears of a potential risk of tendentious editing or systemic bias.
6. Humour (especially sarcasm, cynicism) and even friendly banter are often seen as bad form. Unless you are extremely popular and chances are very low of not being successful, however lighthearted you may think your comment is, it will be wrongly interpreted by some. Most RfA commentators will instantly recognise humour, but !voters seeking reasons to oppose may not see them as such.
7. Conspiracies: Some editors may not be regular contributors to RfA. They may bear a grudge that may even go back a long time (see note 2 below). They might cherry-pick diffs and take them out of context. They may have a history of gaming the system and/or combative commenting. Rebuke with utmost care, or preferably ignore.
8. Old enemies may also have an axe to grind, and although they may never have !voted at RfA before, they might !vote on yours. Examine your past and try to iron out any old differences. This should be done at least three months before the RfA.
9. Canvassing. Wikipedia policy on Canvassing for RfA is clear; RfA is not a popularity poll and it should not be done, either on or off Wiki. Consider using {{RFA-notice}} on your userpage, which is a more neutral way to communicate your RfA to other users.
10. Copyright. The use of unauthorised content is a major policy issue. The most innocent copyright violations that you have added – even older ones – especially to Did You Know, good articles, and featured articles will almost certainly be detected, and will seriously compromise your RfA.

Are you ready?

Click to zoom

Every RfA needs a strong, convincing nomination. Generally, self-nominations are only likely to succeed from long-term, very experienced editors. Young or new users who have an I want to be an admin userbox may wait a very long time before they are proposed, at least until they have met the basic criteria demanded by the regular !voters. Nevertheless, the user category the box added your name to is regularly reviewed by experienced editors and admins who are actively looking for suitable candidates to nominate. If they believe you to be a potential candidate, they will contact you – probably by email, so be sure to have Wikipedia email enabled. If you have not already done so, you should opt in for your edit count details to be shown in addition to your pie chart. As previously recommended, review the nominations of previous RfA that have passed and failed.

• Self-nomination: Self-nominations get mixed reception. In fact, some editors systematically oppose self nominations. Some nominations are too short, some are too long, some are too witty, some are too bold, and some candidates simply inadvertently shoot themselves in the foot in their nomination statement. A self-nom must be strong, but not too long, and not sound self-promotional. Candidates who intend to self-nom are welcome to ask an experienced friend for advice on their draft. At Wikipedia all editors are considered equal; what a candidate has done in real life is of little importance for being an administrator.
• User nominations: Being nominated by another user demonstrates that at least another Wikipedian has confidence that the candidate will be successful. Strong nominations come from experienced users who have done significant research to be sure that the nomination will not backfire on them. Many successful candidates are those who have been nominated by an admin or co-nominated by a second experienced user. See: Requesting an RfA nomination.
• Timing: Don't imagine for a moment that everyone lives in the USA or the UK. Regular contributors to the English Wikipedia live in every corner and time zone of the world (two well known British admins live in Thailand). Choose a 7-day period that is not interrupted by public holidays in most countries, and perhaps avoid busy exam periods when many college students and professors may not have time to be online much. Many candidates admit to not getting much sleep while their RfA is running, but it's perfectly acceptable to maintain your normal 24-hour rhythm.
• Transcluding your RfA: When you enter 'edit' mode for the RfA page, you will be asked one last time if you are really ready – remember, there is one thing that nearly all editors are unanimous about: they don't like having their time wasted. Most important however, is to consider waiting another couple of months rather than submitting yourself to a lot of unkind comments and an embarrassing failure. Transclusion is a frequently used process for combining elements of electronic documents, especially at Wikipedia. If you don't know how to do it, you are free to ask your nominator to do it for you, but it may demonstrate to the !voters that you are not entirely familiar with an operation that admins are expected to do with ease.

During your RfA

1. At the start, unless there are obvious reasons why the RfA should fail, most RfA typically begin with a number of 'support' !votes, but seven days is a long time and !voting patterns can change dramatically. The more experienced participants will often hold off their comments until later in the process. These could be a either an influx of supports or opposes, thus making the outcome unpredictable until near the end. Many of the later participants !vote 'as per user X' (often referred to as 'pile-on') without bringing fresh rationale to the discussion.
2. The three standard questions are easy enough and the replies can be prepared before you transclude the process. If you are nominating yourself, your answers can be an opportunity to expand (rather than duplicate) some of the things you have said in your nomination statement.
3. !Voters' questions are unpredictable. RfA is an open book exam, and Wikipedia is a huge repository of policies, guidelines, and help pages. Careful phrasing of the answers is however required to demonstrate that the candidate knows how to apply the policy in question. Misinterpretation of candidates' correct answers has been known to incur a pile-on of 'oppose' !votes. Many questions may not appear to be relevant to becoming a sysop, but the posers will sometimes argue that the answers demonstrate a candidate's capacity to act under stress or to address silly comments from other users. Although such questions often cannot have a 'correct' answer, many !voters will not see them as so and will oppose based on the answer; in the worst case scenario such questions may even cause pile-on oppose !votes. Advice varies from either putting on a brave show of making an answer, or ignoring the question. Nothing in RfA process policy suggests that the questions are other than optional, but not answering can also create pile-on oppose !votes.
4. Many RfA are not a fair process. (See also 'Rebuttals' below') The community is working to make the process as fair as possible, but there are no guarantees. Some candidates with tens of thousands of edits fail as a result of concern expressed about isolated minor issues, or pile-on opposition following deliberate improper !votes or inappropriate !votes made in good faith.
5. Answering every !vote (1). Comments that are short and to the point and demonstrate integrity and good faith on the part of the !voter do not need a response. Users looking for reasons to oppose will see too many comments as being too chatty.
6. Answering every !vote (2). Candidates should avoid making lengthy rebuttals. They will be considered TLDR, and assumed to be a demonstration of excess verbosity that would be used on future talk page discussions and debates. Most people tend to regard 'intelligent' language as simply being pompous and authoritative, commanding, and overly self-confident from someone expecting to be respected and obeyed. Sysops lead by example and are trusted with some tools, but they do not command or issue orders.
7. 'KISS' your use of language. Candidates may believe that sounding intellectual will put them in good stead. It does not. While many Wikipedians are academics and intellectuals, research has shown that most are not.
8. Diffs of candidates' comments taken out of context: Cherry-picked diffs that do not reveal the full story in the thread they were taken from. This can be apparently deliberate, or innocently made. In all cases assume good faith.
9. Diffs of candidates' comments made longer than 3 months ago: It is recommended that unsuccessful candidates do not attempt a further RfA before 3 months have elapsed. It can therefore be assumed that candidates will have addressed any previous negative aspects of their editing and commenting.
10. Citing unrelated diffs: Many participants cast their !votes based entirely on other !voters' comments. It is possible that they will take these comments on face value without verification.
11. Rebuttals are dangerous (1): No users like their 'oppose' votes being disputed. Many 'oppose' votes have comments that are short and to the point and demonstrate integrity and good faith on the part of the !voter. If the claims are reasonably accurate, they do not need a response.
12. Rebuttals are dangerous(2): Some 'oppose' votes may be based on vengeance, extreme inaccuracies, and sometimes even lies. Rebuttals should be considered with utmost caution. They should be extremely polite, even if the !voter is calling the candidate an 'obtuse jerk'. The solution is a short, concise answer that contains extremely well researched diffs. In the worst case scenarios, candidates have been told by other users to shut up and put up, and not question !voters' motives or integrity. Candidates who lose their cool or who demonstrate frustration or lack of patience with !voters will incur opposition and pile-on oppose !votes.
13. Closure: Most RfA with a final tally of 80% support or more will close as successful, while those under 70% will generally not pass. There have however been important exceptions, with candidates passing with as low as 70.7%. The 70–80 'grey' zone is subject to the bureaucrat's discretion after taking into account the quality of the arguments made by the !voters, the strength of comments in the 'neutral' section, and after discounting any !votes they consider to be invalid. In extremely close calls, an extension to the 7-day !voting period may be accorded, or a discussion ('crat chat) may take place among the bureaucrats.

After your RfA

If you passed

• Relax – it's over. Have a shower and get rid of the blood.
• Enjoy the congratulations and pints of beer, don't get drunk, and wear the T-shirt with pride.
• Read all these links, learn to use the tools slowly, and watch out for some unexpected new links in strange places, especially in the Twinkle CSD menu!
• Be a role model and lead by example.
• Never hesitate to ask another admin for an opinion or advice.

If your RfA does not succeed or if you withdrew

• Have a shower, get rid of the blood, then READ THIS
• Don't be disheartened.
• Don't cry and don't get drunk.
• Learn from the advice
• Keep editing, don't retire from Wikipedia, and try again another time.

RfA essays and criteria

Wikipedia

• Adminship is not for new users
• Requesting an RfA nomination
• What adminship is not
• Advice for younger editors
• RfA cheatsheet

Users

• America69: RfA criteria – (2008) Criteria, and advice for candidates
• Animum: RFA – (2008) Addresses top-level issues that are still unresolved
• Davidwr: Administration is not for new users advice for WP:NOTNOW failures
• Dayewalker: My RfA, and good faith advice on yours - (2011) A critical look at the RfA process and what to expect
• Juliancolton: Cluefull RfA quotes
• Juliancolton: No Big Deal
• Juliancolton: Why I hate RfA
• Pedro: RfA review – major contributor to RfA and WT:RfA
• SilkTork: administration – (2010) Criteria, and advice for candidates
• Sven Manguard: Failed RfA Advice
• Tisane: Self-nominations for adminship as prima facie evidence of power hunger
• WereSpielChequers: RFA changes – major contributor to RfA and WT:RfA
• Worm That Turned: Magic Formula for becoming an admin

Users' criteria

• User:A Nobody, RfA Standards – (2009) Comprehensive
• User:Acalamari/RfA views – (2007) Short view, mainly on civility.
• User:Animum/RfA criteria – (2008) User 'Has no criteria'.
• Bearian's RfA Standards – (2010) Precise
• CT Cooper
• Dlohcierekim – (2008) Comprehensive. Regularly updated
• Dlohcierekim – In tabular form
• Fastily – Short, concise. Major contributor to RfA and WT:RfA
• Giggy
• Kudpung – Detailed. Major contributor to RfA and WT:RfA
• MJ94 – Short, concise.
• Next-Genn-Gamer
• User:NoSeptember/Adminship_is_a_big_deal
• Orfen
• PeterSymonds
• Porchcrop
• Red Phoenix
• Richard0612
• Sephiroth_BCR
• Swarm – (2011) – very up-to-date
• Tomtomn00 - (2012)
• T-rex
• Thorncrag
• Tisane: criteria

• User:WereSpielChequers/RFA by month
• Winger84
• Wisdom89

Older pages

• RfA !voters' brief comments on standards. The pages A–Z are classed as 'inactive'. The comments have mostly petered out since around 2006–2007, but may be helpful for research.
• Category:Matters related to requests for adminship

Related projects

• Wikipedia:RfA reform 2011
• See also articles listed in Category:Matters related to requests for adminship