Coordinator Bylaws

Updated 11/15/06

1) Elected Coordinator Positions

The Head Coordinator shall present the following positions for election as per the Administrative Bylaws, Section 4B:

A) Administrative:

i) Assistant Head Coordinators (2 positions)

ii) Admissions Coordinator

iii) Finance Coordinator

iv) Archivist

B) Genre Coordinators

i) Sect Coordinators

(1) Camarilla

(2) Sabbat

(3) Anarch

ii) Clan Coordinators

(1) Assamite

(2) Brujah

(3) Gangrel

(4) Giovanni

(5) Lasombra

(6) Malkavian

(7) Nosferatu

(8) Setite

(9) Toreador

(10) Tremere

(11) Tzimisce

(12) Ventrue

iii) Changing Breeds Coordinator

(1) The Changing Breeds Coordinator shall be accountable for all Changing Breeds as outlined by White Wolf.

2) Appointed Coordinator Positions

A) The following Coordinator positions shall be appointed by, and report to, the Head Coordinator and Assistant Head Coordinators as needed until such time as the Council feels the genre requires an elected Coordinator position:

i) Wraith

ii) Changeling

iii) Kuei-jin

iv) Mage

B) Appointed Genre Coordinators shall be the recognized authority on their respective genres and as such receive all rights and responsibilities under Section 3, Subsection C.

i) Appointed Coordinators may be removed from office at will by their respective elected Coordinator or by a majority vote of Council.

ii) Coordinators are responsible for all disputed issues that are brought before Council.

3) Coordinator Duties

A) Administrative Coordinators

i) Head Coordinator

(1) The Head Coordinator shall be responsible, to the best of their ability, for duties assigned to the position as outlined within the bylaws of the network.

(2) The Head Coordinator may be sought as a binding arbiter in a disputed between parties with the consent of all involved, as opposed to taking the matter directly to Council. The HC has the right to refuse.

(a) This responsibility may not be delegated without prior permission from all parties involved.

(3) The Head Coordinator may, at their discretion, delegate responsibilities to the Assistant Head Coordinators or duly appointed sub-coordinator.

ii) Assistant Head Coordinators

(1) Shall, to the best of their ability, carry out responsibilities as assigned by either the Head Coordinator or the Council.

iii) Admissions Coordinator

(1) The Admissions Coordinator shall oversee the Admissions process as outlined in the Administrative Bylaws, Section 7.

(2) The Admissions Coordinator may cast a tie-breaking vote in the case of a tie during voting on new chronicle admission. The Admissions Coordinator may not hold any other votes on the Council, such as being the council member for a chronicle.

iv) Finance

(1) The responsibilities and duties of the Finance Coordinator shall be:

(a) Maintain a bank account and financial records of all transactions on behalf of the network.

(b) Monitor and record all individual donations to the network.

(c) Provide consultation and research for the disbursement of all funds donated to OWBN.

(d) Present quarterly reports on the intake and output of the OWBN account to Council.

(e) Submit proposals to Council on any fiscal donation or payment policy or request.

v) Archivist

(1) Duties for Historical archival shall be:

(a) Catalog and report disciplinary actions as per the Administrative Bylaws, Section 6.F.i.

(b) Archive chronicle reports and policies as per the Administrative Bylaws, Section 8.

(2) Duties for Rare & Unusual archival shall be:

(a) Create and maintain a database listing of all approved Rare & Unusual characters and routinely-appearing/interacting NPCs as outlined in the Character Regulation Bylaws, Section 9.

(b) Report to the ST list/Council an overview of existing R&U characters within OWBN and offer the a global picture of the R&Us in the organization as well as an outline on how this does or does not mesh with existing White-Wolf published materials.

B) Sect Coordinators

i) Sect Coordinators are responsible for:

(1) Monitoring and advising on status issues within the sect

(2) Provide guidance for Storytellers on the goals and activities of the sect as a whole.

(a) Sect Coordinator and Genre Coordinators shall share joint control over NPCs deemed important to the Sect as a whole, regardless of clan.

(b) The executive team shall mediate disputes of control and portrayal of these NPCs.

ii) To this end, Sect Coordinators shall receive all powers outlined in Section 3.C.ii as directly related to the duties outlined in Section 3.B.i.

C) Genre Coordinators

i) Genre Coordinators are responsible for:

(1) Providing local STs with informational resources regarding the clan, sect, bloodlines, or species for which they have responsibility.

(2) At their discretion, providing local Storytellers with the portrayal of NPCs of that clan, sect, or species, within the bounds of OWBN wide consistency and genre concerns.

(3) Providing OWBN with the occasional presence of NPCs of their clan, sect, or species on the OWBN lists, or in person at OWBN events, within the bounds of OWBN wide consistency and genre concerns.

(4) Providing OWBN with guidance regarding the general direction of their clan, sect, or species, and with plots which may enhance OWBN’s usage of that clan.

(5) Maintaining the consistency and genre appropriateness of the genre resource under their care.

(6) Keeping local STs and other appropriate Coordinators appropriately informed of their activities. This includes informing local STs of communications with PCs.

(7) Monitoring chronicle adherence to the Character Regulation Bylaws, Section 9.

ii) To this end, Genre Coordinators have the following powers:

(1) They may create and portray, or delegate the portrayal of, NPCs as appropriate to their position.

(a) Delegated NPCs, however briefly portrayed, must be included in reports to Council outlined in the Administrative Bylaws, Section 8.D.iv.

(b) Council may remove any of these NPCs with a majority vote, at which time the Coordinator will be permitted to script a suitable IC disappearance.

(c) Delegated NPCs requested by STs for use in a particular chronicle are primarily subject to the authority of those STs but may be removed at any time by the Coordinator.

(d) Coordinator NPCs cannot be used in any Chronicle without the permission of the Coordinator, his/her delegate, and the local STs.

(e) Coordinator NPCs become subject to local ST authority when they appear in person in a chronicle, but the Coordinator or his or her delegate shall remain free to refuse to take any action if it introduces a vital inconsistency of character or a breach in global genre in the Coordinator or delegate’s opinion.

(i) If STs feel they require an action, which the Coordinator has refused, they may appeal the matter to Council, whose decision shall be final.

(ii) If the Coordinator feels the St(s) of a chronicle have tampered with, or hampered, the actions of a Coordinator office NPC in such a way that prevents the Coordinator from enforcing their area of Genre, they may address Council for official Disciplinary action to be taken against said ST(s) or the Chronicle as a whole.

(f) Coordinator NPCs are subject to Administrative Bylaws Section 1.D constraint except where otherwise noted in the bylaws.

(g) Coordinator NPCs that fall under an R&U category must be passed as normally for that category through Council.

(2) Cast a tie-breaking vote on R&U characters they coordinate.

(3) Genre Coordinators may collect information on clan/sect/species activities (or in the case of the Justicar Coordinators, on matters which have been brought IC to the Justicar’s attention) from the STs or other Coordinators, who shall not misrepresent such information.

(a) Failure to provide necessary information to a Coordinator or intentional misrepresentation of information shall be brought before Council and considered appropriate grounds for punitive measures.

(4) They may request permission of the appropriate STs to take any actions through clan NPCs towards PCs.

(a) The appropriate STs shall be deemed to be the STs with OWBN jurisdiction over the PC at the time and chronicle at which the action is to occur.

(b) If the action is foreseeable in advance, permission should also be sought from the PC’s home chronicle STs.

(c) If permission is granted, they may take those actions.

(d) If permission is not granted, the Coordinator may take their case before Council. Council’s rulings will be binding to the Coordinator and the chronicle(s) in question.

(e) If Head Storytellers make agreements with Coordinators concerning PCs, those agreements shall be binding on both the Coordinator and the chronicle, regardless of who holds the Coordinator position or the ST positions (though agreements may be altered if both STs and Coordinators agree).

(f) Failure to keep such agreements shall be brought before Council and considered appropriate grounds for punitive measures.

(5) Advise Coordinators and STs on ways to leverage R&U related backgrounds and plotlines on a global level, if desired.

(a) For example: in the Midwest, it’s quite possible that various PCs in Kenosha, Milwaukee and Green Bay all have a 5-pt. Mentor who is a Samedi. Instead of having 3-5 7th generation Samedi, it would make sense for the various Mentors to be combined into a single NPC, and used as a plot device at ST discretion.

(6) They may delegate any of the above powers to one or more Sub-Coordinators, who they will hold responsibility over.

(a) They may remove these Sub-Coordinators at will, and Council may remove these Sub-Coordinators with a majority vote.

(b) Coordinators are responsible for all disputed issues that are brought before Council.

iii) Genre Coordinators must pass before Council any plot, enforced policy, or binding edict they wish to use which they can reasonably expect to affect multiple chronicles and these proposals need not be

seconded, but go immediately into discussion.

(1) If no opposition is voiced during the week of discussion, the proposal is considered passed and enforceable. Once passed these are considered binding to all chronicles and a chronicles refusal to adhere is grounds for OWBN disciplinary measures.

(2) Those that seem to affect only one chronicle only need local ST approval. In this case, conflicts with the chronicle are subject to point three above.

(3) Coordinators may bring before Council any dispute between themselves and another Coordinator or ST in which they feel OWBN wide consistency or global genre is at stake, and Council shall make a timely investigation and judgment.

(4) Passing new R&U Named characters before council is to be treated as something which affects multiple chronicles.

iv) Abuses of the limits of these powers may be addressed with local strikes or brought before Council and considered appropriate grounds for punitive measures. This applies to both Coordinators and their staff, and chronicles and their ST’s