Administrative Policy

Voting Procedures

Voting Procedures

• Commanders, Captains, Officers, and NCOs can each vote. Each member has only one vote.
• A clear agenda or proposal should be presented for each vote. Members are able to vote "For," "Against," or "Abstain."
• Majority vote is required for the measure to pass. Abstentions do not count. Only "For" and "Against" votes determine the outcome.
• The total number of eligible voters determines majority. In general, all officers and NCOs are counted for votes, the only exception is promotion votes, which only counts Lieutenants and NCOs. Example: With 15 Lieutenants and NCOs , 8 "For" are votes needed for a majority.
• Results announced after voting ends and the majority decision is implemented.
• In the event of a Tie, Admirals and Captains will convene and vote within themselves to determine the outcome.
• Admirals reserve the right to veto decisions in exceptional cases that go against Organizational interests or policies.
• Confirming an NCO promotion will be a vote withheld to Officer and above.
• Disciplinary votes are unique and will generally be comprised of only Officers.

	Remember, voting promotes fairness and collaboration within Rescue Squad One. Respect the outcome, even if it differs from personal preferences. Let's work together for success in Star Citizen!

Lower Command (Ensign / Lieutenant) Rules

Promotion Tickets

Promotion tickets must be left up for at least 24 hours. However the submitter of the ticket can close the ticket after the promotion is given (or not given) using the button on the command that the NCO posts. Promotion tickets should be closed by: Command, the person that opened the ticket or the NCO+ that processed the ticket.

You must wait at least 12 hours from the start of a promotion ticket before awarding the approved new rank. Once the promotion is approved the NCO processing the ticket will use the "/closerequest" command, while making sure to include a description and a close time of 12 hours from the use of the command. If the creator of the ticket doesn't use the "close" button, the ticket will automatically close 12 hours after the command was used.

Steps to Process Non-Command Promotion Tickets

1. Input intro comment for the appropriate rank.
2. Check all qualifications (rescues, events, TIG, etc) and post voting poll.
3. After 12 hours have passed since the ticket was opened and the poll is finished, the team will approve or deny promotion.
4. Post the promotion comment, congratulating them.
5. Post in Promotion Tracker as well as Promotion Announcements.
6. Use the "/closerequest" command, making sure to include the description/summary and the auto-close time of 12 hours.
7. Submitter can then use the close button you posted, when they are ready.

Steps to Process Ensign Promotion Tickets

1. Command inserts intro comment for Ensign Application
2. Command check all qualifications (rescues, events, TIG, etc)
3. Command informs Lower Command that a member has applied for Ensign.
4. Lower Command holds a vote.
5. If the NCO Vote passes, Command will be notified. Command will hold a final vote.
6. After the Command vote has passed, Command will approve or deny promotion.
7. Post the promotion comment, congratulating them.
8. Post in Promotion Tracker as well as Promotion Announcements.
9. Use the "/closerequest" command, making sure to include the description/summary and the auto-close time of 12 hours.
10. Submitter can then use the close button you posted, when they are ready.

• All discussions regarding promotion applicants are to be conducted in a respectful and professional manner.
• All information regarding the deliberation of a vote is to be kept strictly confidential.
• Coaching Ensign applicants in order to give them an unfair advantage will render the ticket null and void.

Event Tickets

Once an event ticket is approved and on the calendar, you are welcome to use the "close command" and the applicant can then close it using the button you provided. This means that event tickets no longer have a minimum time to be open, however if the applicant does not use the provided button, then the ticket will stay open for 12 hours. The command used to force close it will close it at that time.

Rescue Medal Awards

As soon as the medal (role) is awarded, use the "close command". The applicant can then click close on your provided button. If they don't click "close", the ticket will remain open until it force closes at the 12 hour mark.

Awards

	Join us in our exciting journey of saving lives and making a difference in Star Citizen!

The Rescue Achievement System is our recognition and reward system for members who go above and beyond in rescue operations.

Starting from 10 rescues, each milestone unlocks a unique badge role on our Discord server. Here are the names for each achievement:

Badge	Rescues	Award
	10	Lifesaver
	20	Guardian Angel
	30	Heroic Medic
	40	Valiant Protector
	50	Fearless Defender
	60	Courageous Medic
	70	Noble Rescuer
	80	Gallant Protector
	90	Indomitable Guardian
	100	Legendary Medic
	130	Supreme Saver
	160	Honorable Protector
	190	Hero of Heroes
	200	The Doctor
	230	Radiant Rescuer
	260	Heroic Luminary
	290	Exemplary Rescuer
	300	The War Doctor
	330	Paragon of Valor
	360	Super "Person of Steel"
	390	Majestic Medic
	400	Mythical Medic

All ranks can participate, and you can count up to 20 rescues which occurred prior to 6 May 2023 for the "Guardian Angel" achievement. To request your achievement, submit a ticket.

Disciplinary Process

	Note: Repeat offenses may skip over the process

Do not close ticket without explicit permission given from an officer. will result in another ticket with escalation.

Warning

You may receive a verbal or written warning. Warning will be logged. If the warning is ignored, then an offense ticket will be created.

Level 1: Minor Offense

Your Rights

• 48 Hours of open communication via this ticket. You can bring in witnesses that can have attendance verified. Voice chat is not required but in some cases, voice chats can be granted.

Possible Outcome

• Timeout up to 24 hours
• Offense is recorded in command logs
• On your record for 2 weeks

Level 2: Moderate Offense

Your Rights

48 Hours of open communication via this ticket. You can bring in witnesses that can have attendance verified. You may ask for a voice chat in addition to the ticket

Possible Outcome

• Single-rank demotion
• Timeout up to 1 week
• Offense is recorded in command logs
• On your record for 1 month

Level 3: Major Offense

Your Rights

48 Hours of open communication via this ticket. You can bring in witnesses that can have attendance verified. Voice Chat is Required.

Possible Outcome

Timeout up to 2 weeks

Offense is recorded in command logs

On your record permanently

Demotion befitting of the offense will be determined by vote

Possible removal from Discord and RSI Org with ban length in writing

Level X Offense

Immediate removal from Discord and the RSI Org

Disciplinary Appeals.

Any member of the organization has the right to appeal the results of a disciplinary action brought against them, up to and including a Level X Offense. Appeals should be initiated through a ticket submission whenever possible, or via direct communication with a member of RS1 Command if the accused has been removed from the server. The purpose of an appeal is to ensure due process, just causation, and fair treatment for the appellee.

---

Proceedings:

1. Ban Status:

- If the appellee is currently banned, the ban will be temporarily lifted, and the Quarantine role will be applied to provide limited server access. This will allow the appellee to participate in the appeal process via the designated ticket.

2. Appeal Submission:

- Upon submission of an appeal, Command will acknowledge receipt within 24 hours.

- Three randomly selected NCOs will be assigned as the Appeals Committee, and a Command member will be appointed to represent the Command team and act as the primary liaison throughout the process.

3. Deliberation Period:

- The Appeals Committee, supported by the appointed Command representative, will have 3 days to deliberate and review all relevant facts presented by Command and the appellee.

- Only evidence and information available at the time of the original disciplinary action may be considered.

- The committee may request a one-time extension of 24-72 hours if deemed necessary to reach a thorough conclusion.

4. Communication Protocols:

- The appointed Command representative will serve as the sole point of contact between the Command team, the Appeals Committee, and the appellee.

- To ensure streamlined communication, other Command members not directly involved in the appeal are prohibited from engaging in the appeal ticket.

- Once the appeal process begins, the appellee must direct all communications regarding the appeal exclusively to the designated liaison within the ticket.

5. Responsibility for Evidence:

- Both Command and the appellee are responsible for presenting all relevant materials related to the disciplinary action for review by the Appeals Committee.

6. Decision Announcement:

- After reaching a consensus, the Appeals Committee and the appointed Command representative will present their findings to the full Command team.

- The final decision will be communicated to the appellee within 48 hours of the conclusion of deliberations.

7. Outcomes:

- If the appeal is successful, the appellee will be reinstated fully, with a clean record and all ranks/roles restored (excluding restricted or limited-access roles).

- In rare and extreme cases, a veto motion supported by a majority Command vote may override the committee’s decision.

8. Exceptional Circumstances:

- Situations not covered by this policy may require precedent-setting actions. Any exceptions will be handled on a case-by-case basis by the Command team.

---

Record Keeping:

Following the appeal, regardless of the outcome, a summary of the Appeals Committee’s findings and the final decision will be added to the

-

-

-

The total time to process at its longest is 9 days. Keep In mind these are high priority tickets and should take precedence over nearly any other. Setting a week and 2 day deadline to process a discipline appeal is a fair amount of time for all parties.

Policy Change & Implementation

Change Management

In order to improve communication, increase transparency, and reduce surprise changes within RS1, we have decided to implement major changes once a month. The process of discussing major changes, scheduling the changes, and applying the changes is outlined as the Change Management process.

RS1 Patch Day

Any Major changes within the ORG will be applied at the 1st of the month. This will prevent sudden jarring changes to the ORG, as well as allow members to have better awareness of recent changes by reading the RS1 Change Log.

RS1 Change Log

The RS1 Change log is where Major changes are published.

Major vs Minor Changes

Major changes will go through the Change Management process. Minor changes may happen at any time.

Examples of a Major Change

• Uniform Updates
• Rank Requirement Changes
• Squad Requirements
• Platoon Changes
• Rules and Regulations
• Event or Rescue Requirements

Examples of Minor Changes

• SOP Clarification or Polish
• Error Corrections
• Re-wording of existing policy
• Organizing or channel cleanup
• Minor non-policy driven Discord Changes

Change Management Workflow

Changes within RS1 go through a Change Management Process outlined below:

1. Propose Change
2. Discussion
3. Command Vote
4. Preparation
5. Application

Propose Change

Any member of the ORG may suggest a change via "Make A Suggestion" within the Ticket Center on Discord. This will create a ticket where the NCOs and Command staff may review it. Depending on the viability of the suggestion, the command may proceed to the Discussion step.

Some suggestions come from within discussions on various threads. Any major changes are recommended to be submitted via a Ticket so proper discussion can be had.

Discussion

Any Major Changes should be discussed within a Ticket. Depending on the nature of the change, NCOs may or may not be included within the discussion. Sensitive items will often be discussed within Command exclusively, where as ORG changes may include NCOs within the discussion as necessary. During the discussion, the viability of applying the change will be determined. If a consensus is made and a change is desired, the change must then be submitted to be voted on.

Command Vote

Major Changes which have completed the Discussion process will be voted on under Command-Voting. It is important that once a vote reaches this step that it is understood when the change will be applied. Command should reference the discussion within the vote as well as reference the desired date of change. For example:

Command Vote on Uniform Changes. (ticket-uniform-discussion) (Change 1DEC2023) (Description of Change) YES / NO / Abstain

More information can be provided in a Thread under the Poll if required.

Once a majority vote is obtained, the change moves on to the Preparation Step.

See Voting Procedures above for Vote Pass / Fail conditions and rules.

Preparation

After a Vote is passed and a change is ready, it may be added to the queue for upcoming changes. These changes are currently listed within the Pending Org Changes - Change Log Drafts channel.

Application

On the 1st of the month, changes which are queued within the Pending Org Changes - Change Log Drafts channel will be applied where required, and the changes will be outlined within the RS1 Change Log.