diff --git a/docs/issue_template.md b/docs/issue_template.md
new file mode 100644
index 000000000..dcba8f960
--- /dev/null
+++ b/docs/issue_template.md
@@ -0,0 +1,33 @@
+## Description
+
+<!--
+PLEASE NOTE: Issues relating to the 'playing for data' fork or any issues
+relating to capturing copyrighted games that you are not the author of will be
+closed.
+-->
+
+<!--
+Here you can enter a short description of either the bug that you are
+encountering, or the feature/improvement you'd like to see happen.
+
+If you are requesting a feature please provide as much information as you can
+about what you'd like to do and also why you'd like to do it - sometimes an
+alternative approach would better address the need.
+-->
+
+## Repro steps
+
+<!--
+This only applies for bugs - please outline the steps you took to hit the bug.
+
+If you are able to share a capture or an application that demonstrates the bug,
+please upload and link it here.
+-->
+
+## Environment
+
+* RenderDoc build: e.g. v1.0, or 2018-03-12 nightly build.
+* Operating System: e.g. Windows 10, Windows 7, Ubuntu Linux, etc
+* API: e.g. Vulkan, D3D11, OpenGL, etc
+
+<!-- More details here never hurt! For example your GPU, driver version, etc. -->
diff --git a/docs/pull_request_template.md b/docs/pull_request_template.md
new file mode 100644
index 000000000..81ec5cbe8
--- /dev/null
+++ b/docs/pull_request_template.md
@@ -0,0 +1,16 @@
+<!--
+Before submitting a pull request you are strongly recommended to read the
+CONTRIBUTING.md file which gives some information on how to prepare a change.
+
+For small changes you don't have to read the document end to end, but should at
+least look at the sections on how to ensure your code and commits are formatted
+according to the style requirements.
+-->
+
+## Description
+
+<!--
+Describe here what your pull request changes and why it should happen. For small
+changes which are obvious this can just be a line or two - even the commit
+message is sometimes enough.
+-->