diff --git a/.github/ISSUE_TEMPLATE/work_item.md b/.github/ISSUE_TEMPLATE/work_item.md
index 8330f2770b..e1f13c42ce 100644
--- a/.github/ISSUE_TEMPLATE/work_item.md
+++ b/.github/ISSUE_TEMPLATE/work_item.md
@@ -17,4 +17,6 @@ assignees: ''
 
 ## Test Plan
 
+## Compatibility Considerations
+
 ## Upgrade Considerations
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index dfd1094c8d..5325b35ef4 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -27,6 +27,13 @@ refs: #XXXX
 
 <!-- Every PR should of course come with tests of its own functionality. What additional tests are still needed beyond those unit tests? How does this affect CI, other test automation, or the testnet?  -->
 
+### Compatibility Considerations
+
+<!-- Does this change break any prior usage patterns? Does this change allow usage patterns to evolve? -->
+
 ### Upgrade Considerations
 
 <!-- What aspects of this PR are relevant to upgrading live production systems, and how should they be addressed? -->
+
+- [ ] Includes `*BREAKING*:` in the commit message with migration instructions for any breaking change.
+- [ ] Updates `NEWS.md` for user-facing changes.