diff --git a/release-team/role-handbooks/communications/README.md b/release-team/role-handbooks/communications/README.md
index dd42c9b2f15..8e8e4c76825 100644
--- a/release-team/role-handbooks/communications/README.md
+++ b/release-team/role-handbooks/communications/README.md
@@ -114,6 +114,10 @@ It helps to work closely with the Release Lead and use the respective SIG Slack
 
 When a placeholder PR is created, make sure the PR has been opened using a `draft:true` parameter in its metadata. Feature blogs should not be merged **until after the release date and the comms team has assigned a publication date**.
 
+Once the placeholder PRs are open, **assign a writing buddy to each PR as needed**. Select the writing buddy from the KEP authors of the other open placeholder PRs and pair them up. The writing buddy will act as a peer reviewer and provide support for the main author of the feature blog. Some feature blog PRs are written collaboratively within SIGs or are opened with the blog content already complete; these may not need a writing buddy.
+For more information about the writing buddy assignment process and their role, please refer to [this documentation page](https://kubernetes.io/docs/contribute/blog/writing-buddy/).
+Example messaging can be found [here](/release-team/role-handbooks/communications/templates/writing-buddy-assignment.md).
+
 #### Creating a blog publication schedule
 
 **The Comms team establishes the feature blog publication schedule.** Other members of the release team or blog reviewers may contribute ideas and feedback on the schedule, but ultimately the schedule is determined by the Comms team. 
diff --git a/release-team/role-handbooks/communications/templates/writing-buddy-assignment.md b/release-team/role-handbooks/communications/templates/writing-buddy-assignment.md
new file mode 100644
index 00000000000..587867c0d11
--- /dev/null
+++ b/release-team/role-handbooks/communications/templates/writing-buddy-assignment.md
@@ -0,0 +1,21 @@
+# Writing Buddy Assignement
+
+This is a message to send to the owners of the Feature Blog in the placeholder PRs to assign them a writing buddy.
+
+```
+Hi @xx 👋 vx.yy Communications team here,
+
+@BUDDY as author of #BUDDY-PR, I'd like you to be a [writing buddy](https://kubernetes.io/docs/contribute/blog/writing-buddy/) for @xx on this PR.
+
+Please:
+
+- Review this PR, paying attention to the [guidelines](https://kubernetes.io/docs/contribute/blog/guidelines/) and [review hints](https://kubernetes.io/docs/contribute/blog/writing-buddy/#pull-request-review)
+- Update your own PR based on any best practices you identify that should be applied
+- Remember to be compassionate with your fellow article author
+```
+
+You'd need to update the following placeholders:
+- `@xx`: Mention PR's author
+- `x.yy`: The upcoming Kubernetes version, such as 1.33, 1.34, etc.
+- `@BUDDY`: Mention the choosed writing buddy to pair to this PR
+- `#BUDDY-PR`: Link the buddy's PR
\ No newline at end of file