diff --git a/RELEASE.mb b/RELEASE.mb
new file mode 100644
index 00000000..05ad829f
--- /dev/null
+++ b/RELEASE.mb
@@ -0,0 +1,11 @@
+Every new version always follows these steps in order:
+
+1. Create a Pull Requirest upgrading JS packages, mobile version count and release template: https://github.com/RoboSats/robosats/pull/2015
+2. Merge to main and add a new tag to the commit following our versioning structure: https://github.com/RoboSats/robosats/blob/main/.github/workflows/release.yml#L7
+3. Monitor the triggered action until it's done. A new release draft will be created.
+4. Fill the missing points in the release description.
+5. Sign all the assets and upload their signatures.
+6. Usually Coordinators are prompted to upgrade before publishing the new release.
+7. Mark the release as the latest and publish.
+8. Every day at 19:00 GMT IzzyDroid checks automatically for new releases and download it to their repositories.
+9.