diff --git a/.github/ISSUE_TEMPLATE/controller_request.yaml b/.github/ISSUE_TEMPLATE/controller_request.yaml
index 8fdac40..7f8b2c0 100644
--- a/.github/ISSUE_TEMPLATE/controller_request.yaml
+++ b/.github/ISSUE_TEMPLATE/controller_request.yaml
@@ -14,12 +14,6 @@ body:
       description: The name and/or model number of the controller.
     validations:
       required: true
-  - type: input
-    id: vid-pid
-    attributes:
-      label: Controller vendor and product id.
-      description: The vendor and product id of the controller. If your controller can be paired to the console you can dump this information from the pairing database using my [btdb](https://github.com/ndeadly/MissionControl/releases/download/v0.3.0/btdb.nro) application.
-      placeholder: ex. 057e:2009
   - type: dropdown
     id: behaviour
     attributes:
@@ -32,6 +26,12 @@ body:
         - Other (please specify below)
     validations:
       required: true
+  - type: input
+    id: vid-pid
+    attributes:
+      label: Controller vendor and product ID
+      description: The vendor and product ID of the controller. If your controller can be paired to the console you can dump this information from the pairing database using my [btdb](https://github.com/ndeadly/MissionControl/releases/download/v0.3.0/btdb.nro) application.
+      placeholder: ex. 057e:2009
   - type: checkboxes
     id: features
     attributes:
@@ -42,6 +42,13 @@ body:
         - label: Motion Controls
         - label: Player Number Indicator
         - label: Battery Level Reporting
+  - type: textarea
+    id: report-format
+    attributes:
+      label: Input Report Format
+      description: If your controller can be paired to the console but the buttons aren't working you can save some time by noting down the raw input format of the controller using my [hid report viewer](https://github.com/ndeadly/MissionControl/files/6950590/hid_report_viewer_mc.0.5.0.zip) application before creating your report. 
+        With no other bluetooth controllers connected, either screenshot or note down the numeric input displayed as you press each button on the controller one-by-one. Do the same for the ±X/Y positions of the analog sticks and post your results here.
+      placeholder: Enter additional details here.
   - type: textarea
     id: details
     attributes: