diff --git a/.github/ISSUE_TEMPLATE/ui-copy-request.yaml b/.github/ISSUE_TEMPLATE/ui-copy-request.yaml
new file mode 100644
index 000000000..416e1c27d
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/ui-copy-request.yaml
@@ -0,0 +1,81 @@
+name: "UI copy request"
+description: Submit a UI copy-related request to the documentation team.
+title: "[UI copy]: "
+labels: "ui-copy"
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Hello! Use this form to submit a UI copy related request to Elastic's documentation team. You should also directly contact the specific writer or docs team that's responsibile for the applicable part of the product, especially for time-sensitive requests. 
+        > [!WARNING]  
+        > THIS IS A PUBLIC REPO. DO NOT INCLUDE SENSITIVE INFORMATION HERE.
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Summarize your request here. What is the work and how can we help? Do we need to write new copy, or edit existing copy? Feel free to include screenshots.
+      placeholder: |
+        What: We're introducing new feature A. We need a writer to review the UI copy.
+        When: This feature will launch at the completion of project B.
+        Why: This feature will make X, Y, and Z easier for the user.
+    validations:
+      required: true
+  - type: textarea
+    id: related
+    attributes:
+      label: Related links / assets
+      description: Where can the documentation team learn more about this feature?
+      value: |
+        Please include each of the following, if applicable:
+        Figma link(s):
+        Github epic link(s):
+        Github issue link(s):
+        How to find the text in a production environment:
+        Testing environment information:
+        NOTE: To keep sensitive information such as credentials secure, do not include it in this form.
+    validations:
+      required: true
+  - type: dropdown
+    id: product-area
+    attributes:
+      label: Which product area does this mainly concern?
+      options:
+        - Cloud UI
+        - Search solution
+        - Observability solution
+        - Security solution
+        - Kibana Analytics (Discover, Dashboards...)
+        - Kibana Management
+        - Something else
+      default: 0
+    validations:
+      required: true
+  - type: textarea
+    id: collaborators
+    attributes:
+      label: Collaborators
+      description: Please include contact information for the responsible product manager, designer, and developer.
+      value: |
+        PM:
+        Designer: 
+        Developer:
+        Others (if applicable):
+    validations:
+      required: true
+  - type: textarea
+    id: timeline
+    attributes:
+      label: Timeline / deliverables
+      description: When would it be ideal for for us to complete the request? What deliverables do you need, and when? If applicable, how do the release timelines for this feature differ between serverless / stateful? 
+      placeholder: |
+        For example:
+
+        We need a final draft of the new UI copy no later than December 5, ideally by December 1. No differences between serverless/ESS. 
+
+        This is an urgent request, it would be great to have updated copy for A and B ASAP, since the original copy is already in production. No differences between serverless/ESS. 
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for submitting this issue! We'll be in contact shortly. 
\ No newline at end of file