RT2410- P24.02.01

RT2410- P24.02.01

Proposal P24.02.1
Title: "Proposed Amendment to ASR’s Standard Operating Procedures – Abandonment Clause"
Author: Michael Dailey

                              ASR Policy and Procedure for Abandoned Player Characters.

1.0  Should any player, regardless of rank or position, fail to contribute for more than thirty (30) days AND has not 
     communicated to his/her chain of command the intent of a ‘leave of absence’ due to any number of personal matters  
     AND has not respond to two emails sent with a 15-day gap between them from his/her Command Team, that player’s 
     character will be transferred to an administrative NPC role at Star Fleet Academy, Star Fleet Command, etc. and  
     removed from the unit’s roster until such time as the player can resume consistent participation. The NPC billet will
     be determined by the CSFO and/or CINCSF and will reflect the spirit of the character.

     1.1  This policy will be applied uniformly to all unit members, without exceptions in order to establish a fair, 
          consistent and transparent process.

     1.2  Players having characters in multiple units will be transferred as per above as well.

2.0  The first email will be sent to the absent player, CC-ing the unit CO, XO and 2O (as applicable in the appropriate 
     chain of command). Fleet Commanders (as applicable) may be included as well.

     2.1  The second email will be sent in NRPG format to the entire unit.

3.0  For consistency in communications efforts, emails will use a standard template which explains the expectations and 
     process of reestablishing communications with the player.

     3.1 Email Template:
***************************************************************
SUBJECT: ASR Hailing Frequencies #1 (and subsequently #2)
Dear Jane/John Doe;

It has been thirty (30) days since your last post and we as a club are concerned about you AND miss your participation. This is our first attempt at communication, we would like to hear from you, reaffirming your intent to continue role-playing your character "PC RANK-NAME" in "UNIT NAME".

If no response is received within fifteen (15) days of this email, another final attempt will be made.

At fifteen (15) days from the date of the second email, if no response is received, the above character will be transferred to NPC status, removed from the unit's roster and assigned an administrative role until such time as you are able to return.

ASR values your contributions and wants to help in any way possible. Please let your CO know if you need an extended leave of absence for any personal reasons, or anything else your fellow players can do to assist. We look forward to your response.
**************************************************************

4.0 Abandonment of a Unit’s Command Team

     4.1  This process will apply equally to the unit CO, XO and 2O (as applicable).

     4.2  One of the Command Team members stops writing while the other(s) continue;

          4.2.1  In this case, ASR follows the same process outlined in sections 1.0 and 2.0  above for handling extended
                 absences.

     4.3  More than one Command Team members stops writing;

          4.3.1  In this case, if two members of the CT are absent, an active character within the unit should inform the                   
                 Fleet Commanders (as applicable) and/or the Flag Council about the absence of those members.

          4.3.2  Once notified, it would be up to senior officers, including Fleet Commanders (as applicable) and/or the 
                 Flag Council, to initiate the two-email process: one personal message to each inactive CT member and a
                 second to the unit.

          4.3.3  If the absent members do not respond after the designated time, we would proceed as in the first case: 
                 their characters would no longer be part of the active narrative, and their roles as CO and XO would be  
                 officially vacated.

5.0 Reinstatement

     5.1  At any time after this process has been completed, a player wishing to return to active ASR participation may
          petition the club administrators to reinstate their character(s) if the billet(s) are open, or create a new
          character(s).

     5.2  The Flag Council reserves the right to approve or reject applications for reinstatement.

          5.2.1  Factors to consider reinstatement approval may include, but not be limited to, sincerity in gameplay,
                 and unforeseen real-life events.

          5.2.2  Factors to consider reinstatement rejection may include, but not be limited to, a demonstrated lack of
                 communication and/or behavior contrary to any other ASR guidelines.

6.0 Future Revisions

     6.1 The Flag Council shall retain the authority to review and revise the language of this policy as necessary 
         (outside of the Round Table process), ensuring that it remains relevant, effective, and responsive to the 
         evolving needs and conditions of ASR. Any amendments will be made with careful consideration of the club’s goals,
         values, and the best interests of its members, allowing for adaptable governance that supports a positive,
         dynamic and fun writing environment.