diff --git a/RFC.md b/RFC.md
new file mode 100644
index 0000000..cab4a78
--- /dev/null
+++ b/RFC.md
@@ -0,0 +1,29 @@
+---
+title: An RFC
+date: "YYYY-MM-DD"
+author: An Author
+type: <Organisation|Discord>
+---
+
+# Summary
+
+A short introduction to the intentions of the RFC
+
+If someone only reads this far, what do you want them to know?
+
+# Goal
+
+What problems are you trying to solve? What problems are you not trying to solve?
+
+# Background & Motivation
+
+What is the current state or process? Why is this change being proposed?
+
+# Resolution
+
+Describe the proposed solution to the achieve the goal.
+
+Where relevant this RFC should be submitted with the relevant changes to
+supporting documentation or configuration, e.g. if the resolution is related to
+Discord, then it's [configuration file](./discord/config.yml) should also be
+updated.
\ No newline at end of file
diff --git a/discord/config.yml b/discord/config.yml
index 8b1bb4b..fa76616 100644
--- a/discord/config.yml
+++ b/discord/config.yml
@@ -1,40 +1,45 @@
 channels:
+  - information/rules-and-info
+  - information/roles
+  - announcements/server
+  - announcements/social
+  - announcements/promo
   - Secrets/committee
   - Secrets/moderators
   - Secrets/sponsors
   - Secrets/community-heroes
-  - Text Channels/general
-  - Text Channels/promo
-  - Text Channels/worklog
-  - Text Channels/rage-room
-  - Text Channels/random
   - Development/getting-started
-  - Development/development
-  - Development/game
-  - Development/web
+  - Development/general
+  - Development/back-end
+  - Development/front-end
   - Development/mobile
   - jobs/job-advice
   - jobs/job-adverts
   - jobs/job-discuss
-  - topics/current-affairs
-  - topics/pets
-  - topics/food
-  - topics/coffee
-  - topics/battlestations
-  - topics/sofa-studies
-  - topics/music
-  - topics/gaming
-  - topics/tech-news
-  - topics/blockchain
-  - topics/fitness
-  - topics/art
-  - topics/sports
+  - jobs/worklog
+  - Social/introductions
+  - Social/general
+  - Social/personal-finance
+  - Social/rage-room
+  - Social/food
+  - Social/pets
+  - Social/sofa-studies
+  - Social/music
+  - Social/battlestations
+  - Social/sports
+  - Social/blockchain
+  - Hobbies/fitness
+  - Hobbies/gaming
+  - Hobbies/art
+  - Hobbies/coffee
+  - News/current-affairs
+  - News/tech-news
   - nordevcon/nordevcon
   - nordevcon/track-1
   - nordevcon/track-2
   - nordevcon/track-3
-  - nordevcon/staff
   - nordevcon/pioneering
+  - nordevcon/staff
   - 🔊 Voice Channels/voice-chat-text
   - 🔊 Voice Channels/watercooler
   - 🔊 Voice Channels/committee-voice
@@ -43,4 +48,3 @@ channels:
   - 🔊 Voice Channels/gaming
   - 🔊 Voice Channels/gaming-two
   - 🔊 Voice Channels/events
-  - archive/sevices
diff --git a/rfc/0001-an-rfc-schema.md b/rfc/0001-an-rfc-schema.md
new file mode 100644
index 0000000..78e6d95
--- /dev/null
+++ b/rfc/0001-an-rfc-schema.md
@@ -0,0 +1,46 @@
+---
+title: An RFC Schema
+date: "2022-08-05"
+author: Alex Scotton
+type: Organisation
+---
+
+# Summary
+
+Introduce a schema and process for handling RFCs within the community.
+
+# Schema
+
+This document represents the schema for a nor(DEV): RFC in some strange
+self-propagating nature.
+
+Updates to the schema will occur in subsequent RFCs if and when required.
+An example of the current schema is [at the root of this repository](../RFC.md).
+The document should then be referred to when proposing a new RFC.
+
+[YAML front matter](https://assemble.io/docs/YAML-front-matter.html) should be
+used to provide metadata for the RFC. The body of the RFC is currently open to
+the author's discretion but should be used to explain the change desired.
+
+```yml
+---
+title: An RFC
+date: "2022-08-05"
+author: An Author
+type: <Organisation|Discord>
+---
+```
+
+If the RFC proposal includes updates to features already tracked within this
+repository, then the [Pull Request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)
+should also include these changes when relevant or possible.
+
+# Process
+
+The process for accepting and implementing RFCs is:
+
+1. Create Pull Request (or remove the draft status from the PR)
+2. RFC is open for discussion
+3. The RFC is merged and applied given:
+  - All (upto a max of 5) colloborators have approved
+4. The RFC is applied by the admin team and "merged"
\ No newline at end of file
diff --git a/rfc/0002-discord-community-update.md b/rfc/0002-discord-community-update.md
new file mode 100644
index 0000000..db3cc07
--- /dev/null
+++ b/rfc/0002-discord-community-update.md
@@ -0,0 +1,34 @@
+---
+title: Discord Community Channel Update
+date: "2022-09-03"
+author: Will Corrigan, Alex Scotton
+type: Discord
+---
+
+# Summary
+
+Ensuring Discord channels are fit-for-purpose, and ensuring seperation between
+support & social conversation.
+
+_This RFC is being submitted on behalf of Will by Alex, the changes described
+are his_
+
+# Goal
+
+Make dedicated spaces for conversation around Development & those is search of
+help.
+
+# Background & Motivation
+
+The intention behind #development and similar channels is to seek help & advice.
+
+It is currently used for both discussion and help. It's also quite opinion
+driven.
+
+# Resolution
+
+The re-architecture and creation of appropriate channels to help in creating
+this seperation.
+
+Please see the [updated configuration](../discord/config.yml) contained within
+to review these updates.
\ No newline at end of file