diff --git a/.gitlab/issue_templates/deploy-new-stack-version.md b/.gitlab/issue_templates/deploy-new-stack-version.md
index 46b2670..e8bee64 100644
--- a/.gitlab/issue_templates/deploy-new-stack-version.md
+++ b/.gitlab/issue_templates/deploy-new-stack-version.md
@@ -1,28 +1,32 @@
 /title Deploy new <project> <version>
 
 /milestone %"MRO 2023"
 
 /labels ~"activity::Deployment"
 
 *Note* This proposes a plan to deploy a new version for a given stack (Arch
 Linux, AUR, ...). Please, drop the unneeded actions from the plan.
 
 
 staging:
 - [ ] [swh-apps](https://gitlab.softwareheritage.org/swh/infra/swh-apps/-/tree/master/apps?ref_type=heads): Build image (if required because of new deps for example)
 - [ ] [swh-charts](https://gitlab.softwareheritage.org/swh/infra/ci-cd/swh-charts/-/merge_requests): Merge MR with image versions updates triggered by the CI
 - [ ] Push branch 'staging' && Let argocd deploy and do its job
-- [ ] Checks pods are doing their jobs without crashing
+- [ ] Checks
+  - [ ] pod images are pulled correctly
+  - [ ] pods are running without issues (rpc starts, celery workers consume messages, ...)
 - [ ] Tag grafana with "deployment service=<service> service=<service2> ... environment=staging" [1] [2]
 
 production:
 - [ ] Merge 'staging' branch into 'production' (it should/must be a fast-forward)
 - [ ] Push branch 'production' && Let argocd deploy and do its job
 - [ ] Tag grafana with "deployment service=<service> service=<service2> ... environment=production" [1] [2]
-- [ ] Checks pods are doing their jobs without crashing
+- [ ] Checks
+  - [ ] pod images are pulled correctly
+  - [ ] pods are running without issues (rpc starts, celery workers consume messages, ...)
 
 [1] https://grafana.softwareheritage.org/goto/e-c3EAWIz?orgId=1
 
 [2] Only reference impacted services (e.g. storage, lister-cran, loader-git, scheduler, vault, ...)
 
 Refs. <issue>