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:
- Propose Change
- Discussion
- Command Vote
- Preparation
- 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.
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.