diff --git a/Scrapy-release-procedure.md b/Scrapy-release-procedure.md
index 7c8749e..482235c 100644
--- a/Scrapy-release-procedure.md
+++ b/Scrapy-release-procedure.md
@@ -143,6 +143,10 @@ it, even though the GitHub online editor).
 
 If you’ve released a patch version, you should merge its branch into the main branch, making sure you exclude version-bumping changes (`git merge --no-commit`).
 
+## Prepare the new Scrapy Cloud stack
+
+As a different team produces images for [Scrapy Cloud stacks](https://github.com/scrapinghub/scrapinghub-stack-scrapy), you should ping them to do that (preferably before the release so that they can plan in advance) and start the process by making a PR following the procedure at https://github.com/scrapinghub/scrapinghub-stack-scrapy#setting-up-local-environment-to-update-requirements.
+
 ## Upgrade CI packages
 
 To avoid the risk of CI suddenly failing and confusing pull request authors, we freeze some CI packages in `tox.ini` and `tests/requirements.txt`.