User:Barkeep49/RfA checklist

When deciding whether or not to run:

• Are you prepared mentally for people to oppose you? And oppose you for things that can cut against what you (and others) view as your strengths and/or because the community is divided about the right way to implement our policies, guidelines, and procedures? Even successful RfAs will have people opposing or at least bringing up forceful concerns. Even unsuccessful RfAs of serious candidates like yourself will generally have more than 50% support. The more you are able to keep the opposes, which can weigh on even the most grounded and stable of editors, in perspective the happier you will be during (and after) your RfA.
• Completely read through at least a couple of RfAs to get a sense of what the experience might be like and consider reading the RfA debriefs others have written.

Before the RfA:

• What from your past, especially your recent (last 3-6 months), might be brought up as a question or concern that we haven't already discussed? Often we can't predict what will be an issue but where we can it is good to have a plan for how we want to handle it if it comes up.
• Read through the questions asked at least the last 5 RfAs (and more if you want). For any questions which have been asked regularly, begin to think (or even write out - this is what I did), how you would answer them if they were asked of you.

During the RfA:

• Do answer the questions carefully and promptly without rushing. Take the time to double check applicable policies/guidelines. Feel free to reach out to me to run by a draft answer.
• Don't respond to opposes - typically little good comes of this. To the extent that opposes needed to be addressed, better for you to discuss with me a strategy or to trust that other users will just come to your aid