diff --git a/sites/docs/src/content/docs/tutorials/adding_a_pipeline/first_release.md b/sites/docs/src/content/docs/tutorials/adding_a_pipeline/first_release.md
index 82c8bb20c9..58d1923bd2 100644
--- a/sites/docs/src/content/docs/tutorials/adding_a_pipeline/first_release.md
+++ b/sites/docs/src/content/docs/tutorials/adding_a_pipeline/first_release.md
@@ -37,10 +37,15 @@ Not to worry, we're a friendly bunch.
 
 To get your pipeline reviewed for its initial release, do the following:
 
-1. Make a pull-request from the `dev` branch to `master` on the nf-core fork. This is a
+1. Create a new branch based on `TEMPLATE`, called `TEMPLATE_<TOOLS_VERSION>` from the version of the TEMPLATE (i.e., latest tools sync) that is in the `dev` branch you wish merge into `master`.
+   The commit message from @nf-core-bot will help you figure what was the tools versions used.
+   For example, if this commit message `Template update for nf-core/tools version 1.13` is the one that used for a tools sync,
+   the branch should be called `TEMPLATE_1.13`.
+
+2. Make a pull-request from the `dev` branch to this `TEMPLATE_<TOOLS_VERSION>` branch on the nf-core fork. This is a
    special case and all of the tests should pass.
 
-1. Once the tests are passing, request a review from the core team. You can use the
+3. Once the tests are passing, request a review from the core team. You can use the
    [#request-review](https://app.slack.com/client/TE6CZUZPH/CQY2U5QU9) slack channel for this.
 
 What happens next depends on the state of your master branch: