diff --git a/doc/4.7-final.md b/doc/4.7-final.md
index 8bc495527af3591ed407ac84c23f62f15c6991ec..e3e6cc28d195c925cbdbb8ab7530d82fd3de9fcf 100644
--- a/doc/4.7-final.md
+++ b/doc/4.7-final.md
@@ -18,7 +18,19 @@ eval "$(ssh-agent -s)"
 ssh-add ~/.ssh/id_rsa
 ```
 
-## 1: Identify the final RC
+## 1: Sanity checks
+
+   * Compare the git revisions
+     * https://download.civicrm.org/latest/civicrm-RC-drupal.tar.gz/inspect
+     * https://github.com/civicrm/civicrm-core/commits/4.7.X-rc
+     * https://github.com/civicrm/civicrm-drupal/commits/6.x-4.7.X-rc
+     * https://github.com/civicrm/civicrm-drupal/commits/7.x-4.7.X-rc
+     * https://github.com/civicrm/civicrm-joomla/commits/4.7.X-rc
+     * https://github.com/civicrm/civicrm-packages/commits/4.7.X-rc
+     * https://github.com/civicrm/civicrm-wordpress/commits/4.7.X-rc
+
+
+## 2: Identify the final RC
 
 Determine the identity of the final release candidate:
 
@@ -28,7 +40,7 @@ gsutil ls gs://civicrm-build/*rc/*json
 
 For example, we might pick `gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json`.
 
-## 2: Publish
+## 3: Publish
 
 You can do the full process in one command:
 
@@ -72,7 +84,7 @@ You might want to spot-check a few URLs to ensure the tags were published, e.g.
  * https://github.com/civicrm/civicrm-packages/tree/4.7.X
  * https://github.com/civicrm/civicrm-wordpress/tree/4.7.X
 
-## 3: Update `versions.json`
+## 4: Update `versions.json`
 
 Services such as the `civicrm.org` download page and the in-app version
 check depend on a file named `versions.json`. Update this.
@@ -91,7 +103,7 @@ git commit versions.json
 git push origin master
 ```
 
-## 4: Set default on `sourceforge.net`
+## 5: Set default on `sourceforge.net`
 
 Log into https://sourceforge.net/projects/civicrm/files/civicrm-stable and set the latest Drupal version to be the default download.