9(k) - Advisory Board

PREFACE

This policy outlines the powers and responsibilities of the Paralake Police Department Advisory Board, the intention behind this board is not to have a hand in the day to day operations of the PLPD, and is designed to serve as the final office of accountability for all those within the department, including the Chiefs of Department.

DEFINITIONS

For the purpose of this document:

1.1 - 'PLPD' will represent the organization: Paralake Police Department.

1.2 - 'PLPD personnel' refers to any whitelisted persons involved in the activities of PLPD either directly or indirectly.

1.3 - ‘Advisory Board’ refers to the body described in detail within this document whose purpose aligns with the preface of this document.

1.4 - ‘Advisory Board Member’ refers to a member of the body described within 1.3 of this section

1.5 - ‘Large Scale Policy Change’ is any change in policies within the PLPD that would result in the material change in the duties of any role within the PLPD, or whose change requires the modification of Server or Website code.

1.6 - ‘A Hold’ means the prevention of a action within the PLPD from being formally enacted

1.7 - ‘Blocked’ or ‘Block’ means a permanent hold as described within 1.6 of this section being placed upon an action within the PLPD.

1.8 - ‘Command’ refers to any individual within the PLPD who holds the rank of Staff Sergeant or higher

1.9 - ‘Community Management’ refers to anyone holding one of the following ranks within the PERPHeads Official Staff Team; Owner, Community Manager, or Developer

1.10 - ‘Senior Management’ refers to any individual within the PLPD who holds the rank of Major or higher

MEMBERSHIP

2.1 Members of Community Management will be granted the rank of Advisory Board Member

2.2 Members of Community Management who hold any command rank are prohibited from holding the rank of Advisory Board Member regardless of any situation that may arise

2.3 Members of Community Management may choose not to be a Advisory Board Member for any reason

2.4 Members of Community Management may be prohibited from being a Advisory Board Member by Server Ownership

2.5 Upon approval from Server Ownership someone who was previously a member of Community Management may hold the rank of Advisory Board Member while not being a member of Community Management

POWERS

3.1 This section of this document supersedes any other relevant policy within the PLPD with no exceptions.

3.2 An Advisory Board member may put a hold on any of the following actions; discipline of a member of the Chiefs of Department, any large scale policy change, or promotion of anyone to a senior management position. This hold is established to ensure a formal review process of the action may be conducted, where any actions that are a part of the initial action can be reviewed by members of the Advisory Board. If agreed upon by at least two members of the advisory board the action can be formally blocked, if the action is a promotion, then the selection process should be resumed with any suitable candidates. In a situation where a promotion is blocked Advisory Board Members can make a case for the promotion of a candidate but cannot push through a promotion on their own accord.

3.3 When using the power described within 3.2 of this section a written reason must be provided to any person(s) involved in the action that is being targeted who holds a rank described as Senior Management.

3.4 Server Ownership may block, or perform any action within the PLPD, without regard to standing policies including those described within this document.

3.5 If deemed necessary by a Advisory Board Member, and only for the purposes of completing a review of a action placed on hold using the power described 3.1 in this section, a Advisory Board Member can request access to any relevant information, this can include relevant chats, records logs, to be used to assist in the review.

3.6 Advisory Board Members have full authority superseding that of any PLPD personnel who are not Advisory Board Members in the modification, deletion, or addition, or any Server or Website code.

CHIEFS OF DEPARTMENT

4.1 This section of this document supersedes any other relevant policy within the PLPD with no exceptions.

4.2 The promotion of anyone to the rank of ‘Chief of Department’ can only be approved by Server Ownership.

4.3 Unless an exception is granted by Server Ownership no attempts to recruit a Chief of Department should be conducted beyond advising Server Ownership, this includes opening public applications.

4.4

(I)  The promotion of anyone to the rank of ‘Deputy Chief of Department’ can only be approved by Server Ownership, however, upon approval from Server Ownership this policy can instead become the following;

(II) The promotion of anyone to the rank of ‘Deputy Chief of Department’ can only be approved by anyone holding the rank of ‘Chief of Department’. Upon the promotion of anyone to the rank of  ‘Deputy Chief of Department’ this policy will return to its original wording described in Section I of this policy.

4.5 For the purposes of this section of this document, and only this section of this document, the word ‘Approved’ is to mean the selection, or approval of a suggestion for selection.

4.6 There can only be, at most, three members of PLPD personnel who hold the rank of ‘Deputy Chief of Department’, and there can only, at most, be one member of PLPD personnel who holds the rank of ‘Chief of Department’

4.7 If at anytime two PLPD personnel who hold the rank of ‘Deputy Chief of Department’ vote to remove anyone holding the rank of ‘Chief of Department’, a written reason must be submitted to a Advisory Board Member, who will then contact Server Ownership who will review the reason and decide if the ‘Chief of Department’ in question should be removed from their role.

4.8 Anyone holding the rank of ‘Chief of Department’, may remove anyone holding the rank of ‘Deputy Chief of Department’ for a violation of any PLPD Policy, only after seeking approval from the advisory board.