Preamble. This document is designed with the intention of defining the Roles and Responsibilities for all elected officials of the Phoenix Roleplay online community, which will be referred to as the General Membership in this document. The Roles and Responsibilities of appointed Officers, are set out briefly in the listing on the Coordinators thread.

Our basic assumption is that the site's team of Coordinators, Deputy Coordinators, Officers, Junior Officers, Sim Leaders, and others engaged in oversight, will function best through partnership, in a climate of mutual respect, recognition, and proactive communication.

Section I - Legalities of this document
Article 1. This document may be amended only by a majority vote by the General Membership.
Article 2. The responsibilities delegated by this document are conferred at the moment the elected office-holders are announced by the incumbent Elections and Voting Coordinator and are binding for the official positions named and conferred to the office-holder of the named position for so long as they retain their office. Should an office-holder resign their office, then they also forfeit the responsibilities that were delegated to them as an office-holder.
Article 3. Wherever this document names an official position - e.g. G(eneral)C(oordinator) (see Section II below) or E(lections &)V(oting)C(oordinator) (see Section IV below) - the name should also be taken to apply to an appointed Deputy/Assistant of that official to whom the official has delegated that responsibility.
Article 4. Any Coordinator, Officer, SL, etc., may be removed from their positions for violation of policies or inappropriate behaviour either by the GC, or by a 2/3 vote of the membership if motioned and seconded.
Article 5. Bans and suspensions from the community are the purview of the GC, but any such action may be overturned by a 2/3 if motioned and seconded.
Article 6. Any responsibilities delegated by this document may not infringe upon the rights of members or other officials as both members and as human beings with inalienable rights and as residents of a City, Region, or Nation with its own governing laws. If a responsibility delegated by this document infringes upon the rights of members or officials in this way, then the General Membership has the right to decide by majority vote if the infringement was circumstantial or an inherent flaw in the wording of this document, and if it is found that a flaw in the wording of this document exists, then the General Membership also has the right to initiate a second vote on appropriate changes as per Article 1.
Article 7. All rights that pertain to the amendment of this document extend to all other Phoenix Roleplay documents, including the right to amend, suspend, or revoke those documents.

Section II - The General Coordinator
Article 1. The office of General Coordinator shall last a term of 12 months running from as early in May as is convenient to the General Membership, and the office-holder shall be decided by the General Membership by majority vote as conducted by the Elections & Voting Coordinator (see Section IV below), and shall be referred to as the GC in this document.
Article 2. The GC is responsible for overseeing Phoenix Roleplay and for promoting progress within the Phoenix Roleplay community.
Article 3.1 The GC is responsible for including the Contender (see below) in all discussions related to the site and community in which the GC is also involved, the Technical Coordinator when discussion concerns subjects for which the Technical Coordinator is responsible, and the Elections and Voting Coordinator when discussion concerns subjects for which the Elections and Voting Coordinator is responsible. Any discussions made in public forums on the Phoenix Roleplay site must still be brought directly to the attentions of the Contender, Technical Coordinator, and Election Coordinator when appropriate, as defined above.
Article 3.2 The specifics of how the Contender is included and how much involvement they will have with any discussions is determined by the current Contender and lasts up to the end of their GC's term of office. If the Contender chooses, they may opt out of being included in any discussions or can choose to limit their own inclusion as they see fit. The Contender may require of the GC full inclusion in the discussions, summaries, etc., but there are no restrictions on what information the Contender has access to provided that the information is pertinent to the office of GC and not invasive to privacy.
Article 4. The GC is responsible for facilitating and expediting the transfer of office for the EVC at the start of a new elected term in accordance with "Policy 1: At the Start of Term of Office".
Article 5. The GC acts as Phoenix Roleplay's chief official, representing the General Membership in any external affairs concerning Phoenix Roleplay except in matters delegated to other officials or members as decided by this document.
Article 6. The GC reports to the General Membership on all changes implemented by the office of GC, any progress decided upon or implemented by elected officials or the General Membership, or any external affairs concerning Phoenix Roleplay. A maximum time of 2 weeks may pass before the GC must report such changes to the membership, in this way allowing for but not necessarily requiring a regular two-weekly update of administrative events.
Article 7. The GC is required to use tact when reporting information to the General Membership sensitive to any members of Phoenix Roleplay.
Article 8. The GC is responsible for resolving disputes between members and handling complaints made by the membership when issues cannot be resolved between those involved or when the GC decides the issue is causing harm to Phoenix Roleplay or is otherwise causing trouble for the site or the General Membership.
Article 9. The GC is responsible for moderating the Management Forum.
Article 10. Starting with May, shortly after their election, and then roughly every three months thereafter (so August, November and, finally, February shortly before elections), the GC or a relevant delegate (e.g. the GM Officer) will ask the Coordinators, Deputy/Assistant Coordinators, Officers, Junior Officers, Sim Leaders, and GMs to review their office/sim to identify any problems which need resolving and to share best practice across our site. This review will generally be carried out by email, and reported to the general membership upon completion.

Section III - The Contender
Article 1. The role of Contender shall last a term of 12 months shadowing the GC, and the Contender shall be decided by the General Membership as being the candidate to accrue the 2nd most votes in elections for the office of GC. If the candidate to accrue the 2nd most votes declines to serve as Contender, the role may be offered sequentially to the runners up. The role being left unfilled does not mean new elections may be called for.
Article 2. The Contender reports to the General Membership on any issues concerning Phoenix Roleplay both on and off-site as often or as little as they so choose.
Article 3. The Contender may choose to be responsible for identifying flaws in the existing Admin Team but must report any findings to the General Membership for their review so that the General Membership may be aware of inefficiencies or counter-productive action being taken by Coordinator or Officer office-holders so that the General Membership can address these issues.

Section IV - The Elections and Voting Coordinator
Article 1. The office of Elections and Voting Coordinator shall last a term of 12 months running from as early in April as is convenient to the General Membership, and the office-holder shall be decided by the General Membership by majority vote as conducted by the incumbent EVC overseen by the GC, and shall be referred to as the EVC in this document.
Article 2. The EVC reports to the membership on all things for which the EVC is responsible.
Article 3. The EVC is responsible for overseeing all Elections and Votes conducted for Phoenix Roleplay, and is responsible for making sure the results are easily available to the General Membership.
Article 4. The EVC is responsible for moderating the nomination process and campaigning done for elections being run for Phoenix Roleplay.
Article 5. The EVC is responsible for facilitating and expediting the transfer of office for all other elected Coordinators (i.e. all elected officials other than the EVC) at the start of a new elected term in accordance with "Policy 1: At the Start of Term of Office".
Article 6. The EVC is responsible for handling complaints and issues the General Membership has with the Voting Booth and will relay any of these complaints as appropriate to the Technical Coordinator if necessary.
Article 7. The EVC is responsible for maintaining the Voting Booth or any equivalent voting process during an election or vote, as well as ensuring that a voting process is in place for each election or vote.
Article 8. The EVC is responsible for moderating the Elections and Voting Forum.
Article 9. The incumbent EVC may not run for a position other than EVC in elections.

Section V - The Treasurer
Article 1. The office of Treasurer shall last indefinitely until such time as the holder wishes to vacate it, is removed by the General Membership by majority vote, or is banned from the site. The office-holder shall be decided by the General Membership by majority vote as conducted by the EVC.
Article 2. The Treasurer holds final responsibility for the fiscal wellbeing of Phoenix Roleplaying.
Article 3. The Treasurer has the right to, in coordination with the General and Technical Coordinators (or their appointed deputies) organise fundraising efforts to aid in this duty, but must be prepared to pay "out of pocket" if necessary.
Article 4. The Treasurer shall receive no rights or privileges from their position. In particular, the Treasurer shall in no way be considered the "owner" of Phoenix Roleplaying - our site is collectively owned by the General Membership.

Section VI - The Technical Coordinator
Article 1. The office of Technical Coordinator shall last a term of 12 months running from as early in May as is convenient to the General Membership, and the office-holder shall be decided by the General Membership by majority vote as conducted by the EVC, and shall be referred to as the TC in this document.
Article 2. The TC reports to the General Membership on all things for which the TC is responsible.
Article 3. The TC is responsible for maintaining the Phoenix Roleplay site in all aspects related to coding and availability of the site and its services to the General Membership.
Article 4. The TC is responsible for handling technical complaints and issues the General Membership has with the Phoenix Roleplay site and its services.
Article 5. The TC is responsible for relating to the GC their professional opinion on the technical aspect of changes to the site as required.
Article 6. The TC must report to the General Membership of all technical issues which concern the General Membership and likewise must report to individual members all technical issues which concern those individual members.
Article 7. The TC is responsible for moderating the Tech Support Forum.

Section VII - Deputy Coordinators
Article 1.1 All Coordinators must appoint and publicly announce a Deputy within 10 days from the date of their election (the date of their election, i.e. when the voting results are announced, not the date they accept office).
Article 1.2 The EVC has the authority to declare the candidate's election or indeed the entire election void if a new Coordinator fails to appoint a Deputy within the required timeframe.
Article 1.3 It is good practice for Candidates in elections for Coordinator positions to declare their 'running mate' (i.e. their Deputy-to-be, should they be elected), ideally not less than 10 days before voting concludes.
Article 1.4 The term of office for a Deputy expires when the term of office for its superior position expires.
Article 2.1 Deputies will assist their Coordinator in their duties as assigned by their Coordinator, sometimes serving as 'line managers' on projects the Coordinator is responsible for.
Article 2.2 Newly appointed Deputies are allowed a three-month probationary period before being expected to cover any of the responsibilities of their appointing Coordinator.
Article 2.3 The appointing Coordinator must 'train' their Deputy in the role during this period so that if the Coordinator suddenly goes AWOL, the Deputy would be able to take over. Likewise the Deputy will serve as Acting Coordinator if required by their Coordinator during any LOA.
Article 2.4 If the Coordinator goes on LOA or leaves their office before their Deputy's three-month probationary period is over, then the responsibilities of that office are given to the General Coordinator to fulfill or delegate as they see fit.
Article 3.1 If a Coordinator permanently vacates their post either by resignation or by falling AWOL according to the site-wide AWOL policy, the GC must appoint a replacement upon the absent Coordinator's resignation or becoming AWOL, or in the case of the GC resigning/becoming AWOL, the EVC must call another election as soon as possible and appoint an Acting GC until the election concludes. The EVC may appoint him/herself Acting GC in this situation, but may not run for the position of GC in the election.
Article 3.2 It is good practice for the GC/EVC to appoint the vacating Coordinator's recommendation if the Coordinator is leaving on good terms.
Article 3.3 In all other situations, it is generally good practice to appoint the vacating Coordinator's Deputy. However, the Deputy of the now absent Coordinator need not necessarily be appointed by the GC/EVC to replace the now absent Coordinator.
Article 3.4 If the Deputy has completed their probationary period as set out in article 2.2 above, however, the Deputy does have to serve as Acting Coordinator until a replacement Coordinator is appointed by the GC/EVC.
Article 3.5 What defines 'absence' in the case of a Coordinator is set out in the Site-wide AWOL Policy; i.e. members who go 30 days without posting, or 30 days over their LOA expiration date if they posted an LOA with an expiration date, are considered AWOL.
Article 3.6 In the event that a Deputy leaves their office, the superior Coordinator must select a new Deputy within 1 month.

Section VIII - Sim Leaders
Article 1. 'Sim Leader' (SL) is the title of the person who is responsible in real life for the sim's success and for moderating the posts in their sim's forum.
Article 2. The SL may or may not have a position of leadership in-character in the game as well.
Article 3. The SL is responsible for appointing a Gamesmaster ('GM'; they may appoint themselves or delegate the task to someone else) and a second in command 'Assistant Sim Leader' (ASL). In the interests of the sim's success, the Sim Leader can overrule the GM.
Article 4. Appeals regarding an SL's moderating or concerns regarding their stewardship of the sim can be directed to the GC.
Article 5. It is the GC's responsibility to appoint Sim Leaders to sims lacking a Sim Leader, and to appoint SLs to new sims.
Article 6. It is good practice for the GC to appoint the out-going Sim Leader's preferred candidate as their replacement if the out-going SL vacated the position on good terms. The preferred candidate may often but not necessarily be the standing Assistant Sim Leader.
Article 7. It is good practice for the GC to appoint the sim creator or a person of the sim creator's choice as the Sim Leader of a new sim.
Article 8. It is the GC's responsibility to remove Sim Leaders who fail to perform their duties.
Article 9. The duties incumbent on an SL are set out in broad sweep in articles 1 and 3, above.

Section IX: Duties of Thread Moderators (e.g. Sim Leader, Coordinator, Officer, etc.)
Article 1. Thread Moderators must permit every player and every point of view in discussions to have a fair hearing. Some people are better at putting a case than others and the moderator ought to allow reasonable latitude to the less articulate.
Article 2. Thread Moderators must ensure that opinions expressed are relevant to the matter in hand.
Article 3. Thread Moderators must to ensure that business is conducted with reasonable speed.
Article 4. Thread Moderators must ensure that as far as possible proceedings are friendly and free from personalities.*
Article 5. Thread Moderators must to co-operate with other Officers and Coordinators to these ends.
*When differences of opinion develop in a discussion, as per Section VIII Article 1 above it is the duty of the moderator to give a fair hearing to all points of view, including his or her own, if he or she has one. It is not the duty of the moderator to suppress his or her own convictions, nor is it the moderator's privilege to impose his or her opinions. It is therefore good practice for the moderator, when voicing strong opinions (especially opinions which others might reasonably disagree with), to call on members to express opinions each way and to him- or herself avoid arguing one side first or last.