WoW Raid Officer
From OiWiki
The Raid Captain/Council Position has been replaced by the Raid officer. **RC dissolved Sept 20th, 2009**
The Raid Officer Position was established October 1st, 2009.
Contents |
The Oi Raid Officer: Duties/Description
- Raid Officer will be equivalent to the position of Officer.
- Raid Officer will focus the vast majority of their time & work specifically on the raiding aspect of the guild.
- Raid Officer will focus 90% of their efforts on Raid Related Topics, thus allowing the other 11 officers to focus the vast majority of their time/efforts on guild management & other officer responsibilities.
- Raid Officer replaces RC (RC, by definition, is retired & non-existent).
- All Previously known/defined RC "duties" now fall under the Raid Officer.
- Raid Officer may appoint/manage volunteer Raid Leaders to assist, as needed.
- Raid Officer may request Generals Tent Forum Access for those interested in assisting/volunteering as Raid Leaders
- Raid Officer may delegate projects & responsibilities to Raid Leaders for support - as needed.
- Raid Officer may also request support/assistance from other officers, as needed - on a case by case basis.
- Raid Officer, equivalent to other officers, will serve 18months and will be an elected position moving forward.
- Raid Officer will be the "spokesperson" for the Officer Core & Raid Leaders to general membership (via D.I.R.T.) when it comes to Raid & Loot Related Policies, Topics, & Concerns.
- Raid Officer will be the primary point of contact for raid related topics/issues.
- Raid Officer will be the Officer responsible for posting raid related policy polls within the GT.
- Raid Officer will have only 1 vote: again, equivalent in "power" & "say-so" to all other officers.
CURRENT RAID OFFICER: Aliasbristow (Term 10/1/09 - 4/1/2011) <updated 10/01/09>
THE RAID OFFICER – Definition & Job Description
The first 4 sections and information were voted on by the Oi Draka Officer Core in August 2009 and implemented 08/17/09. Guild Raid Officer (RO) position replaced the previous Raid Council (RC) effective 10/1/09 & ratified by officer vote on 10/23/09
Section 5 (amendment) was voted on by the Oi Draka Officer Core in October 2009 and implemented 10/20/09
Section 1 - THE REASONS FOR THE CREATION OF A RAID OFFICER:
1. Officers were literally burdened with raid related issues. The Raid Officer (RO) will take on the burden; formulate proposals, policies, & solutions for OC vote/approval.
2. Officer responsibilities are vast, as many are already aware, and the RO will take care of Raid Related business thus allowing officers more time to focus on other areas of guild management.
3. The raid related topics need focused on, but have historically been listed in bits and pieces everywhere (GT, OL, & DIRT). There are so many ideas but they start at point one and end up going off entirely somewhere else. The RO would offer focused ideas, compiled plans, and proposals to the OC for approval.
4. The RO will provide the OC the opportunity to look at a finished proposal, vote, and communicate via the Discussion thread housed on the topic in the GT.
5. With every complied plan, some concern is expected, as we are a very large guild and opinions will vary no matter what is proposed.
6. People have to remember that there will be arguments for every case in point; nothing will make every 100 percent happy. Proposals that receive simple majority vote by the OC will be implemented.
Section 2 – DEFINITION OF RAID OFFICER
1. Raid Officer will be equivalent to the position of Officer.
2. Raid Officer will focus the vast majority of their time & work specifically on the raiding aspect of the guild.
3. Raid Officer will focus 90% of their efforts on Raid Related Topics, thus allowing the other 11 officers to focus the vast majority of their time/efforts on guild management & other officer responsibilities.
4. The Raid Officer will take on the responsibilities of the previously known Raid Captain & Raid Council, thus replacing the Raid Captain/Council & retiring the term/reference to Raid Captain/Council.
5. The Raid Officer will be responsible for counseling individuals that have been recognized as requiring such (in regards to raid related issues only, such as poor performance issues).
6. The Raid Officer will handle complaints pertaining to raids and field suggestions to make raiding & progression better.
7. The Raid Officer is responsible for overseeing the Raid Leaders and managing/maintaining the list of DiscipleR toons.
8. The Raid Officer is also responsible for communication & posting raid related information in DIRT for our members: Including - a. Officer Core (OC) approved changes to raid, DKP, & loot rules. b. Informative updates about game patches & content changes. C. Any other non-policy specific information about raids & Oi raiding.
Section 3 – SPECIFIC DUTIES
1. Keep track of who is attuned, geared, and ready for each raid; help organize runs for attunement and gear when appropriate.
2. Appoint raid leaders based on who is interested & available (interested parties must speak to the RO to put their name in the hat, so to speak).
3. Develop and maintain a monthly raiding schedule and publish it to the boards.
4. Help create and maintain a guild knowledge base on each boss we will encounter in our raids.
5. Be ready and willing to help raid leaders learn & prepare for each 25 man raid encounter we will be facing as a guild.
6. Keep raid policies and procedures current based upon changes in the game (ie new patches & content releases).
7. Submit proposals for any changes/amendments to raid related policies & rules to the OC for vote, via a Poll thread posted on the General's Tent forum.
8. A link to a Generals Tent discussion thread will be required for all Polls posted in the GT so the communication channel is available for officers and raid leaders to post their opinions, concerns, thoughts, & ideas.
9. Maintain & uphold existing loot rules. Proposed changes to loot rules must go through the Proposal, Poll & Discussion Process (see Sec 3 #7 & 8)
10. Maintain & uphold existing DKP rules. Proposed changes to DKP rules must go through the Proposal, Poll & Discussion Process (see Sec 3 #7 & 8)
11. Maintain & uphold the raider rank/agreement. Proposed changes to Raider Rank must go through the Proposal, Poll & Discussion Process (see Sec 3 #7 & 8)
12. Maintain the list of signed DiscipleR toons,
13. Proactively plan for the future of Oi raiding and upcoming WoW patches & game changes in addition to anything else deemed necessary to keep Oi raiding a positive, fun, & successful part of Oi Draka.
Section 4 – ADDITIONAL INFORMATION
1. The Raider Rank "contract" is in the Wiki: Click Here The significance of it being in the wiki, is that any modifications or changes to the current raiding contract should be voted upon & approved by the OC before implementation.
2. The DKP info & Loot Rules are in the Wiki: Click Here Again - The significance of it being in the wiki, is that any modifications or changes to the current DKP & Loot rules should be voted upon & approved by the OC before implementation.
3. Any raid related topics & issues that are not currently in the wiki/guild charter can be discussed, planned out, formulated, and presented to the OC - along with “expressed intent”. Depending on if it’s a “small/trivial” change or a “big” change – the need to have the OC vote on it would be answered in one way: “it depends”.
4. The RO will have the latitude & authority to put together action plans, strategies, & concepts to improve Oi raiding. The Raid Officer LOVES this guild and understands our community nature and has thoroughly read our charter/wiki – the OC should feel free to offer opinions and suggestions, but should also be willing to take a step back and not suffocate the RO nor wrap things up in red tape.
5. The OC, raid leaders, and RO ALL need to know that not only can we not make 100% of our members happy, but we’ll be hard pressed to make all of us happy either. We will do nothing but spin our wheels if we (as guild leadership) send the RO back to the drawing board on every little thing because one of us or a handful of us don’t like a piece or part of a proposal/idea.
6. Each of us will “win one & loose one” – “give one & take one on the chin” – “agree a little & disagree a little”. The OC should let the RO do their job (as listed above) and present plans without fear of being ripped apart and attacked. The RO is working for the guild and handling raid related issues so other officers can focus on guild business.
7. The RO will present their “final proposals” to the OC for a YES (implement) or NO (reject) vote in the GT when they have “final proposals/revisions” to submit for approval. Poll should also have a link to the Discussion thread on the topic housed in the GT.
8. The OC will abide by a simple majority, in regards to votes/polls as listed in #7 above. Again, not every officer will like or agree with everything, but the RO just needs to get the majority approval prior to implementation and announcement of changes to guild membership via D.I.R.T.
9. Once a final plan/product/revision has been voted upon and passed by the OC – One of the officers (or GL) can ensure that the changes are made, if needed, to the wiki/charter. The RO will then post the voted upon & approved items in the DIRT for guild membership to see, using “stickies”.
(Implemented 9/17/09 by a majority vote passed by guild officers)
Section 5: GENERAL'S TENT GUIDELINES
Regarding communication using Generals Tent Forums and a clearer separation of raid management & guild management.
Privacy
When the General's Tent was pitched, it was with the thought that the information stays confidential until it is decided to be made public. Therefore, it is a mandatory expectation that all members NEVER share information discussed within the GT with others outside of the GT, until the decision is made to publicize information within the DIRT or DIPS. "What is discussed here - stays here."
If evidence is received to convince the Guild Leader that trust has been broken & information from the GT leaked/shared by a member of the General's Tent, the Guild Leader will consult the Raid Officer to determine if the information “leaked” is harmful to the guild or may cause drama, problems, or unrest among membership. If the shared information is problematic (in any way), the Guild Leader will contact the GT member who leaked/shared the information and request an explanation & request that the leaked/shared information be removed from public view. If the GT member refuses or is clearly attempting to stir trouble & cause unrest among our members, their GT access will promptly be removed. We do not need our guild leadership creating problems, stirring trouble, or adding fuel to any fires within the forums and/or among our guild membership.
If you feel that you cannot use discretion & handle information with the GT confidentially, please notify the Guild Leader immediately so your access to the GT can be removed proactively.
Access to the Generals Tent will be made available to any member willing to volunteer & commit to assisting in PvP or PvE Planning & Leading.
The Guild Leader will grant access upon request from the Raid Officer and/or with OC support.
Additionally
1. GT (General's Tent) forum threads: The forum threads within the GT will be read & reviewed by officers at any time - However; Officers should use discretion and avoid constant “peanut gallery” input when a discussion is between the Raid Officer & Raid Leaders. Please, when posting, stick to the facts and avoid blanket accusational statements, name calling, finger pointing, etc – as this tends to be counterproductive. All those with GT access should be respectful, thoughtful, courteous, and constructive while posting.
2. GT Poll/Vote threads: ALL raid related polls (Loot Policy adjustments, Changes to the Wiki, Raider Rank changes, Raider Contract Changes, etc)will be posted within the GT. Polls that require officer votes must clearly state that within the Poll Thread. Any Opinion Polls that require only Raid Leader Involvement - will state that clearly as well, so the OC (Officer Core) members know not to vote/post.
3. Generals Tent/Officers Lounge separation: Since the Generals Tent was established & designed for PvP & PvE related planning, discussion, & policy making - the OL (Officers Lounge) should remain relatively free from Raid Related discussions and the OC focused more on guild related business. This will also allow the Raid Officer & Raid Leaders to ability to perform their job duties with minimal & discretionary officer involvement/interruptions, thus better utilizing our Raid Officer, Raid Leaders, & the GT Forums while facilitating a better working environment in both forums.
