|
|
| Line 1: |
Line 1: |
| − | ==1. Structure==
| + | #REDIRECT [[Office of Public Relations Standing Orders]] |
| − | #'''Director''' - the Director is responsible for the overall management of the Department of Personnel & Recruitment. S/He will have the following duties: | |
| − | ##Serve as a voting member of the Pegasus Fleet Admiralty;
| |
| − | ##Facilitating the transfer of a player from one simulation to another;
| |
| − | ##Managing the crew of a simulation where the Commanding Officer has resigned;
| |
| − | ##Maintaining Pegasus Fleet’s online presence;
| |
| − | ##Operating the Fleet’s Community Engagement outlets;
| |
| − | ##Serve as a resource for Commanding Officers in need of help with recruitment/other community related issues;
| |
| − | ##Managing the Fleet’s Awards.
| |
| − | #'''Deputy Director''' - the Deputy Director is a member of the Department of Personnel & Recruitment who is responsible for aiding and assisting the Director with his/her duties. In the event of Director taking a (E)LOA, the Deputy Director can assume all responsibilities of the Director, except for those related to the Pegasus Fleet Admiralty.
| |
| − | | |
| − | ===Departmental Procedures===
| |
| − | #'''Transfer of Players'''
| |
| − | ##Once a request has been made by a player to transfer from one simulation to another, the Director must seek approval from the following parties:
| |
| − | ###The Commanding Officer of the departing simulation;
| |
| − | ###The Commanding Officer of the receiving simulation;
| |
| − | ###The Task Force Staff of the departing simulation;
| |
| − | ###The Task Force Staff of the receiving simulation.
| |
| − | ##Move the player’s character on IFS from the departing simulation to the receiving simulation.
| |
| − | #'''Simulation Closures'''
| |
| − | ##Upon the resignation of a simulation’s Commanding Officer, the Department Staff will contact the crew of said simulation with a seven day deadline for the following options:
| |
| − | ###Take command of the simulation, if eligible;
| |
| − | ###Transfer to another simulation within Pegasus Fleet (Section 2.1);
| |
| − | ###Resignation (Removal of character from the active character’s list on IFS)
| |
| − | ##Should a player request option I, the Department Staff shall refer the process to the relevant Task Force Staff.
| |
| − | ##Should a player not respond within the allotted time, the Director shall remove the character from the simulation’s listing on IFS.
| |
| − | ###Only the director is allowed to remove a character from the IFS active list in this situation.
| |
| − | #'''Recruitment Aid'''
| |
| − | ##Should the Commanding Officer of a simulation email the Department Staff for assistance recruiting, the Department Staff are responsible for aiding said Commanding Officer at the discretion of the Director.
| |
| − | ##The Department Staff are able to conduct the following procedures:
| |
| − | ###Support the Commanding Officer in writing a recruitment advertisement for his/her simulation;
| |
| − | ###Relay the advertisement to the various recruitment on behalf of the Commanding Officer;
| |
| − | ###Provide the Commanding Officer with the resources s/he needs to conduct recruitment efforts independently.
| |
| − | #'''Community Relations'''
| |
| − | ##The Department Staff is responsible for representing Pegasus Fleet in the greater community. This representation includes the following aspects:
| |
| − | ###Managing the Fleet’s Social Media (Twitter, Facebook, Google+, etc);
| |
| − | ###Operating the Fleet’s Internet Relay Chatroom (IRC);
| |
| − | ###Posting recruitment advertisements for the Fleet;
| |
| − | ###Attracting new players to the fleet.
| |
| − | ##The Department is also responsible for managing the Fleet’s internal community by the following:
| |
| − | ###Encouraging participation of Fleet members on social media, IRC, or the forums;
| |
| − | ###Driving activity on social media, IRC, or the forums with fleet members;
| |
| − | ###Hosting events with the fleet’s community to further bond the community together.
| |
| − | #'''Leave of Absences'''
| |
| − | ##The Department Staff is responsible for maintaining a list of members of the Fleet (Commanding Officers and up) who are on a Leave of Absence. This list must include the following:
| |
| − | ###The member’s name;
| |
| − | ###The member’s position;
| |
| − | ###The member’s LOA start date;
| |
| − | ###The member’s expected return date;
| |
| − | ###The person to contact in the member’s absence for all official duties.
| |
| − | #'''Response'''
| |
| − | ##Each member of the Department Staff shall be required to respond to any inquiries within 24 hours of receiving said inquiry, unless on (E)LOA.
| |
| − | ##A response may only be an indication of receiving the inquiry and that the staff are working hard on completing the action.
| |
| − | | |
| − | Issued July 10, 2016
| |
