diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 0000000..3b3f86e
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,33 @@
+<!--
+Please complete the following sections when you submit your pull request. You are encouraged to keep this top level comment box updated as you develop and respond to reviews. Note that text within html comment tags will not be rendered.
+-->
+### Summary
+
+<!-- Describe the problem you're trying to fix in this pull request. Please reference any related issue and use fixes/close to automatically close them, if pertinent. For example: "Fixes #58", or "Addresses (but does not close) #238". -->
+
+Fixes #<NUM>
+
+*Lorem ipsum dolor sit amet, consectetur adipiscing.*
+
+### List of changes proposed in this PR (pull-request)
+
+<!-- We suggest using bullets and filled checkboxes [x] here -->
+
+* *Lorem ipsum dolor sit amet, consectetur adipiscing.*
+* *Lorem ipsum dolor sit amet, consectetur adipiscing.*
+
+### Some housekeeping checks
+
+- [ ] All ok when you run `devtools::check()` after the changes you have made?
+- [ ] Have you updated the `.Rd` files using `devtools::document()`?
+- [ ] If there were changes to `README.Rmd`, did you build and render it using `devtools::build_readme()`?
+- [ ] If you added a new function or changed an existing function, have you created a (or updated an existing) unit test for it using `usethis::use_test()`?
+
+### What should a reviewer concentrate their feedback on?
+
+<!-- This section is particularly useful if you have a pull request that is still in development. You can guide the reviews to focus on the parts that are ready for their comments. We suggest using bullets and filled checkboxes [x] here -->
+
+- [ ] *Lorem ipsum dolor sit amet, consectetur adipiscing.*
+- [ ] Everything looks ok?
+
+Thank you!