diff --git a/.github/ISSUE_TEMPLATE/RELEASE_GO_NOGO_TEMPLATE.md b/.github/ISSUE_TEMPLATE/RELEASE_GO_NOGO_TEMPLATE.md
new file mode 100644
index 00000000000..608aed263aa
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/RELEASE_GO_NOGO_TEMPLATE.md
@@ -0,0 +1,60 @@
+---
+name: 🚀 Release Go/No-Go Vote
+about: Async Go/No-Go decision for OpenSearch release
+title: '[RELEASE] Go/No-Go Vote - OpenSearch <VERSION>'
+labels: 'release'
+assignees: ''
+---
+
+## Voting Window
+
+**Date:** <DATE>
+**Time:** 8:00 AM PST – 8:00 PM PST
+
+## Release References
+
+- **Release Issue:** [opensearch-project/opensearch-build#XXXX](https://github.com/opensearch-project/opensearch-build/issues/XXXX)
+- **Release Notes Draft:** <LINK>
+- **Build Status:** <LINK>
+
+## How to Vote
+
+- **Go:** React with 👍 on the **Go** comment below
+- **No-Go:** React with 👎 on the **No-Go** comment below **and** leave a comment with your reasoning so we can follow through
+
+## Mandatory Votes
+
+| Role | GitHub Handle | Vote |
+|------|--------------|------|
+| Release Manager | @ | |
+| OS Core Maintainer (1+) | @ | |
+| Documentation Maintainer | @ | |
+| Website Maintainer | @ | |
+| Release Blog Owner | @ | |
+
+## Voting Rules
+
+- A No-Go vote from any mandatory voter or maintainer of any `opensearch-project` repo blocks the release. No-Go votes must include an explicit comment with reasoning.
+- A No-Go vote from any community member or OpenSearch user will be reviewed, with the final decision resting on the maintainer of the respective repo related to the concern.
+
+## Discussion
+
+For questions and discussion, use the Slack thread in #releases: <SLACK_THREAD_LINK>
+
+> The Release Manager is responsible for surfacing any No-Go concerns raised in Slack as comments on this issue to ensure they are formally captured.
+
+## Other Maintainers & Contributors
+
+All maintainers and community members are encouraged to vote using 👍 (Go) or 👎 (No-Go) reactions on the respective comments below.
+
+## Release Checklist
+
+- [ ] All release-blocking issues resolved
+- [ ] Documentation ready
+- [ ] Release blog drafted
+- [ ] Website updates prepared
+- [ ] CI/CD pipelines green
+
+## Additional Context
+
+_Add any relevant links, notes, or context for this release._