The Domain Coordinator (DC) supervises the chapter coordinators within one domain. The emphasis of the duties of the domain coordinator is still on a localized level, however the scale of her locale is larger than that of a chapter coordinator. The specific duties of the domain coordinator differ depending upon whether the domain is comprised of chapters.
For a domain without chapters, the domain coordinator acts much like a chapter coordinator, and is the direct coordinator for each member within the domain. In a domain with chapters, the domain coordinator is responsible for coordinating activities between the chapters and helping to resolve any inter-chapter issues that may arise. Additionally, in a domain with chapters, the domain coordinator acts as the direct coordinator for the individual chapter coordinators as well as for any member that has not joined a chapter.
Any member of the domain may apply as a candidate in a domain coordinator election. Each member of the domain is eligible to vote in the domain coordinator election. Members who are not part of the domain may not apply as a candidate for DC and may not vote in the election. The election is administered by the regional coordinator (or a designated assistant).
The duties of the domain coordinator are to:
Facilitate communication between the chapters within the domain, as well as between the domain and the region.
Report monthly on the status of the domain to the organization.
Secure sites for domain events.
Help facilitate dispute resolution between members of separate chapters.
Track, and be liable for, the domain’s finances.
The DC also has authority to:
Award general prestige, within the limits presented in the Prestige section.
Review prestige logs for all member class advancements beyond MC 5 and award MC 6-8.
Provide disciplinary action of Domain members, including suspensions of up to two months and removal of up to two levels of member class.
Receive two loaned levels of member class while in office, up to MC 11. Can grant Assistants (primary) one loaned level of member class, up to MC 11.
Facilitating communication between a domain’s chapters is essential to keep the domain running smoothly. It is the domain coordinator’s responsibility to help the chapters publicize their events within the domain, and to attempt to coordinate all events within the domain to avoid conflicts. The domain coordinator should also act as a contact point between the region and members of the domain.
The monthly status report is necessary so that those in charge of broader areas can ascertain how the domains are faring. It should include a list of domain officers, the number of members in the domain, complete rosters and prestige information for chapter coordinators and members who are not part of a chapter, any goals or projects the domain is working toward, and questions from the membership. The regional staff is responsible for many domains and uses this report for a quick view of what the domains need or can offer the organization as a whole. These monthly domain status reports are due before midnight (GMT) on the 9th of the following month.
The domain coordinator is responsible for doing prestige reviews that have been passed up from the chapter level and, if the review is satisfactory, can award up to MC 8. For awards beyond that, the prestige review should be passed to the regional coordinator.
Within a domain, conflicts will occasionally arise among members from different chapters, and in this case it is the domain coordinator’s responsibility to try to resolve the issue. In some serious cases, the issue may escalate to the level where the dispute can become a conflict between chapters (or at least between a number of members of those chapters), and these issues must be quickly resolved to maintain the health of the Domain. Additionally, the domain coordinator handles disputes, as well as the first appeals, involving chapter coordinators.
The domain coordinator acts as the domain’s treasurer, and is responsible for tracking and maintaining the domain’s finances. While this duty may be delegated, the final financial responsibility remains the domain coordinator’s, should problems arise.
Unless the domain coordinator chooses to step down and relinquish his position early, a member serves a one-year term as DC. At the end of this term, a new election is held, though the same member may apply again. The DC may be removed from office before his term expires through a domain-level referendum, or by a supervising coordinator.

OOC Jeremy Hicks GWB2008011597

Domain Storytellers
As the first principal elected supervisor in the storytelling chain, the Domain Storyteller (DST) leads the storytelling activities of an entire domain and coordinates all of its venues. The domain storyteller is usually an experienced storyteller who can serve as mentor, mediator, and voice of reason for VSTs within the domain. While a venue storyteller runs games for a specific venue, the domain storyteller ensures that the venues within the domain run smoothly with each other and with the global sanctioned chronicle. The DST oversees all cross-venue stories, and handles all aspects of the domain’s story not contained within any venue. The DST may implement plotlines that affect more than a single venue or multiple genres.
Any member of the domain may be a candidate in a DST election, and every member of the domain may cast one vote in the DST election. This election is administered by the regional storyteller or their designated assistant. For more details on the application and voting process, see those sections of this membership handbook.
Once elected, a domain storyteller serves for one full year. At the end of this term, a new election must be called, but the same member may apply again. A DST may leave office early voluntarily, through a domain-level referendum, or removal by a supervising storyteller.
Each domain storyteller is loaned two additional member classes while in office, up to MC 11. This loan must follow the club's policies. May grant Assistants (primary) one loaned MC, up to MC 11.
Generally, a DST’s storytelling jurisdiction matches the boundaries of the domain, and it extends across all venues. A DST possesses all general storyteller authorities and supervising storyteller authorities within the boundaries of the domain. In addition, the DST has the following specific storytelling authorities within the domain:
Serve as the direct storyteller for any of the domain’s VSTs who have characters assigned to their venues.
Determine and maintain the history and vision for the domain’s chronicle.
Handle all cross-venue interactions, including influences, in order to ensure a single consistent chronicle across all venues and genres.
Serve as the direct storyteller for characters within the domain but that are not assigned to a venue.
Perform mid-level review for special character requests and venue style sheets.
Grant or deny Mid-level requests for characters within the domain.
Revoke or suspend any previously approved venue style sheet within the domain.
Establish policies for players and storytellers within the domain.
Each domain storyteller possesses the following specific duties and responsibilities to the domain’s members and to other storytellers:
Provide narrative consistency within and across the domain’s venues.
Coordinate the efforts of the domain’s VSTs.
Align local venues with the club’s global sanctioned chronicle, its rules, and policies.
Support venue storytellers and answer their questions.
Remove storytellers within the domain from office if necessary.
Promote fair and ethical game play within the domain.
Recruit and train new storytellers how to storytell in the club’s global sanctioned chronicle.
Organize and be responsible for the storytelling of any domain level events.
Establish policies for players and storytellers within the domain.
Collaborate with fellow storytellers.
File a monthly report to the regional storyteller on or before the 7th of each month.
Meet the ongoing requirements of supervising storytellers.
DST reports are due on the seventh day of each month and cover the details of the previous month. The monthly status report should include:
A list of assistants and their duties.
Prestige recommendations for all venue storytellers, assistant domain storytellers, and members who provided storytelling support.
A list of games hosted during the month.
A brief summary of major in-game events in each venue.
Details of ongoing projects.
Summary of active and proposed plotlines.
Any problems or questions for the regional storyteller.
Formal record of any investigations or disciplinary action.
Supervising storytellers may have additional requirements on where to file reports or information to include. Remember, storytellers cannot evaluate their own character’s special requests.

OOC Jeremy Hicks GWB2008011597

Venue Storytellers
A venue storyteller (VST) is the principal elected storyteller for a local venue within the global sanctioned chronicle. In the club, venue storytellers run the majority of sanctioned games and serve as the direct storyteller for most characters. The VST prepares and runs games that entertain the venue’s members as well as visiting members who bring suitable characters.
Most venue storytellers focus on one genre. However, it is possible for a member to hold multiple VST positions within the same domain or independent chapter, as long as each venue has an approved Venue Style Sheet (VSS).
Independent chapters and domains may host venues. When players decide to form a new venue, they must elect a venue storyteller. Any member of the club may be a candidate in a VST election (if the member is not a part of the chapter or domain they must gain approval of the Coordinator that presides over both chapters/domains, or in the case of cross affiliate both NCs). The domain storyteller (or regional storyteller if the venue is within an independent domain) conducts the election. Each member of the venue may cast one vote during the election, regardless of how many characters they have in the venue. For more details on the application and voting process, see those sections of this membership handbook.
Once elected, a venue storyteller serves for one full year. At the end of this term, a new election must be called, but the same member may apply again. A VST may leave office early voluntarily, through a venue-level referendum, or through removal by a supervising storyteller.
Each venue storyteller is loaned one additional member class while in office, up to MC 8. This loan must follow the affiliate's (or home affiliate's if not in the GIR) policies. Can grant assistants (primary) one loaned MC, up to MC 8.
Each venue storyteller must have an approved venue style sheet before running games in the global sanctioned chronicle. This document defines the local venue, its genre, scope, geographic boundaries, and game style. The VSS should clearly define the types of characters that are appropriate for the venue. The VST should be objective and consistent whenever a member of the venue creates a new character, a member requests to join the venue, or when a visiting member brings a character to a venue game.
The venue storyteller should regularly review and update the VSS of the venue, to account for changes in the mood, setting, or other details of the local chronicle. At minimum, the venue storyteller should review the VSS once every six months with the members of the venue to ensue that the VSS matches the style of game that the members prefer and the style of game the VST enjoys running. Additionally, a newly elected VST should review the existing venue style sheet and ensure that the VSS remains suitable.
Generally, a VST’s storytelling jurisdiction matches the boundaries of the domain or independent chapter where the venue is based, but her storytelling authority is limited to the genre defined within the approved VSS. A VST possesses all general storyteller authorities within the scope of the venue. In addition, the VST has the following specific storytelling authority to:
Serve as the direct storyteller for all characters assigned to the venue.
Act as the host storyteller for characters visiting the venue.
Create and maintain the history and feel for the local venue.
Approve new characters within the venue for participation in the global sanctioned game.
Evaluate character transfer requests from existing characters into the venue, following the guidelines in the GIR Handbook.
Grant or deny low-level requests for characters assigned to the venue.
Determine whether visiting characters are suitable for participation within the venue, based on the guidelines in the approved venue style sheet, club rules, and genre policies.
Establish policies for players participating in the venue.
Remember, storytellers may neither serve as the direct storyteller for their own personal characters nor evaluate their own special requests.
Whenever a city runs more than one venue, each VST must work together to ensure that the local continuity remains consistent from venue to venue. Sometimes a domain or independent chapter may wish to run two venues for the same genre. The two venue storytellers must regularly communicate and collaborate. These requests are reviewed on a case-by-case basis by the regional storyteller and are monitored closely.
A VST possesses the following specific duties and responsibilities to the venue’s members and to other storytellers:
Entertain the venue’s members and visiting members with great stories.
Help players learn MET rules, the genre’s details, and the club’s setting.
Organize and be responsible for the storytelling of all games within the venue.
Assist members to create characters appropriate to the venue.
Run games that fit with the style of the approved and published venue style sheet, updating the VSS whenever necessary or appropriate.
Maintain a venue chronicle.
Mentor new players and assistant venue storytellers.
Evaluate all special requests for characters assigned to the venue.
Ensure that the local venue remains aligned with the club’s global sanctioned chronicle, its rules, and policies.
Collaborate with fellow storytellers.
File a monthly report to the supervising storyteller on or before the 1st of each month.
Meet the ongoing requirements of supervising storytellers.
VST reports are due on the first day of each month, and cover the details of the previous month. The monthly status report should include the following details:
A list of assistants and their duties.
Prestige recommendations for all assistants and also members who provided storytelling support.
A list of games hosted during the month.
A brief summary of in-game events in the venue.
Details of ongoing projects.
Summary of active and proposed plotlines.
Any problems or questions for the supervising storyteller.
Formal record of any investigations or disciplinary actions.
Supervising storytellers may have additional requirements on where to file reports or on what information to include.

OOC Jeremy Hicks GWB2008011597