diff --git a/docs/adr/index.md b/docs/adr/index.md
index 8d97c823d..2f26ec915 100644
--- a/docs/adr/index.md
+++ b/docs/adr/index.md
@@ -1,6 +1,6 @@
 ---
 has_children: true
-nav_order: 12
+nav_order: 13
 ---
 
 # Architecture decisions
diff --git a/docs/documentation_website.md b/docs/documentation_website.md
index 9f29505ba..728038fc5 100644
--- a/docs/documentation_website.md
+++ b/docs/documentation_website.md
@@ -1,5 +1,5 @@
 ---
-nav_order: 13
+nav_order: 14
 ---
 
 # This documentation website
diff --git a/docs/exports.md b/docs/exports.md
index 1588defc2..a35d7632e 100644
--- a/docs/exports.md
+++ b/docs/exports.md
@@ -141,6 +141,10 @@ Full exports can only be run via a **rake task**.
 
 <!-- Update this section when sales exports are added, as they will affect rake tasks -->
 
-If the collection size is very large, full exports may fail due to memory issues. In such cases, it is better to batch exports into chunks of ~60,000 records and run several partial exports over multiple days. The `values_updated_at` field can help with this.
+If the collection size is very large, full exports may fail due to memory issues. In such cases:
+
+- Delete the incomplete export files from the S3 bucket.
+- It is better to batch exports into chunks of ~60,000 records and run several partial exports over multiple days. The `values_updated_at` field can help with this.
+- Rerun the task with more memory allocated, see 'Running Rake Tasks'.
 
 The simplest approach is to mark a batch of logs for export each day and allow scheduled morning exports to handle them.
diff --git a/docs/rake.md b/docs/rake.md
new file mode 100644
index 000000000..0fc28eb5c
--- /dev/null
+++ b/docs/rake.md
@@ -0,0 +1,74 @@
+---
+nav_order: 11
+---
+
+# Running Rake Tasks
+
+On CORE, we sometimes need to run a Rake task manually on one of our deployed environments.
+
+## Rake Tasks
+
+Rake tasks are defined in the `lib/tasks` directory of a Rails application.
+
+## Running Rake Tasks locally
+
+This can be done from the command line:
+
+```bash
+bundle exec rake <task>
+```
+
+## Running Rake Tasks on CORE infrastructure
+
+### Get access to an AWS CLI
+
+TODO docs on this
+
+### Set up environment variables
+
+Set the env as appropriate:
+
+```bash
+export env=prod
+```
+
+Other options are `staging` or `review-XXXX`, where `XXXX` is the review app number.
+
+Set up the Rake Task as appropriate:
+
+```bash
+export rake_task=<task>
+```
+
+Where `<task>` is the name of the Rake task you want to run, local equivalent would be `bundle exec rake <task>`.
+
+Set up the CPU and memory requirements for the task:
+
+```bash
+export cpu_value=1024
+export memory_value=2048
+```
+
+See [the AWS documentation](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#task_size) for valid CPU and memory pairs.
+
+Set the other environment variables:
+
+```bash
+export cluster=core-$env-app
+export service=core-$env-app
+export ad_hoc_task_definition=core-$env-ad-hoc
+export network=$(aws ecs describe-services --cluster $cluster --services $service --query services[0].networkConfiguration)
+export overrides="{ \"containerOverrides\" : [{ \"name\" : \"app\", \"command\" : [\"bundle\", \"exec\", \"rake\", \"$rake_task\"], \"memory\" : $memory_value, \"cpu\" : $cpu_value }] }"
+```
+
+### Start the Rake Task
+
+```bash
+aws ecs run-task --cluster $cluster --task-definition $ad_hoc_task_definition --network-configuration "$network" --overrides "$overrides" --launch-type FARGATE --query tasks[0].taskArn
+```
+
+The task ARN will be printed to the console.
+
+### View the Task progress
+
+This can be viewed in the AWS console by navigating to the ECS cluster specified in the environment variables, listing all tasks in the cluster, and selecting the task with the ARN printed in the previous step.