diff --git a/src/pages/docs/projects/variables/system-variables.md b/src/pages/docs/projects/variables/system-variables.md
index 9396134e10..83a4356126 100644
--- a/src/pages/docs/projects/variables/system-variables.md
+++ b/src/pages/docs/projects/variables/system-variables.md
@@ -315,7 +315,7 @@ These variables are available during Azure deployment actions.
 
 ## Output variables
 
-Output variables are collected while a step runs and made available to later steps.
+Output variables are collected while a step runs and made available to later steps. For output variables from steps in a process template, see [Output Variables](/docs/platform-hub/templates/process-templates/troubleshooting#output-variables).
 
 | Variable | Description | Example |
 | --- | --- | --- |
@@ -347,6 +347,15 @@ You can also read these variables for a different step using indexed notation, f
 
 The status codes returned by `Octopus.Step.Status.Code` are `Pending`, `Skipped`, `Abandoned`, `Canceled`, `Running`, `Succeeded`, and `Failed`.
 
+## Process template variables
+
+Process template-level variables are available in all steps within a process template.
+
+| Variable | Description | Example |
+| --- | --- | --- |
+| `Octopus.ProcessTemplate.Slug` | The slug of the process template. | `configure-infrastructure-template` |
+| `Octopus.ProcessTemplate.Version` | The version of the process template used. | `1.2.3` |
+
 ## Tracking deployment status {#tracking-deployment-status}
 
 During a deployment or runbook run, Octopus provides variables describing the status of each step and action, including ones other than the one currently running. This lets you reference another step or action's outcome, for example when writing a [run condition](/docs/projects/steps/conditions).