diff --git a/Home.md b/Home.md
index 2a9c5ec..43f9ba1 100644
--- a/Home.md
+++ b/Home.md
@@ -63,3 +63,20 @@ After the (successfull) release, the Milestone must be closed.
         - If not, move the unresolved issues to another milestone
     - Click the action "Close"
 - In working Eclipse Workspace make PULL (this prevents future conflits, and updates the pom version)
+
+### Revert release
+
+Procedures to execute when something go wrong in the release
+
+1. Delete the Tag
+- Goto https://git.oguerreiro.com/root/resilient/tags
+- Delete the tag with release version. In this case : v1.0.99
+2. Delete the Branch
+- Goto https://git.oguerreiro.com/root/resilient/branches
+- Delete the tag with release version. In this case : release/v1.0.99
+3. Evaluate master pom.xml version
+The update to master\pom.xml is the last thing done. In case of error in the release workflow its VERY unlike to after master\pom.xml change. That being sayed, validate:
+- Is master\pom.xml changed to the next working version? (Example: 1.0.100-SNAPSHOT)
+- If already is, manually change back and commit
+4. Make any necessary corrections to solve the problem in the release
+5. Now, just repeat the release