diff --git a/docs/_includes/default_automatable_values.md b/docs/_includes/default_automatable_values.md
new file mode 100644
index 00000000..3f18db82
--- /dev/null
+++ b/docs/_includes/default_automatable_values.md
@@ -0,0 +1,5 @@
+!!! tip "Default Automatable Values"
+
+    If nothing is known about [*Automatable*](/reference/decision_points/automatable.md), the safer answer to assume is [*yes*](/reference/decision_points/automatable.md).
+    [*Value Density*](/reference/decision_points/value_density.md) should always be answerable; if the product is uncommon, it is probably
+    [*diffuse*](/reference/decision_points/value_density.md).
diff --git a/docs/howto/bootstrap/collect.md b/docs/howto/bootstrap/collect.md
index cc28d073..075d764d 100644
--- a/docs/howto/bootstrap/collect.md
+++ b/docs/howto/bootstrap/collect.md
@@ -105,11 +105,7 @@ we can suggest something like defaults for some decision points.
     means they do not know where the devices are or how they are controlled, so they should assume
     [*System Exposure*](../../reference/decision_points/system_exposure.md) is [*open*](../../reference/decision_points/system_exposure.md).
 
-!!! tip "Default Automatable Values"
-
-    If nothing is known about [*Automatable*](../../reference/decision_points/automatable.md), the safer answer to assume is [*yes*](../../reference/decision_points/automatable.md).
-    [*Value Density*](../../reference/decision_points/value_density.md) should always be answerable; if the product is uncommon, it is probably
-    [*diffuse*](../../reference/decision_points/value_density.md).
+{% include-markdown "../../_includes/default_automatable_values.md" %}
 
 !!! tip "Default Safety Values"
 
diff --git a/docs/howto/gathering_info/automatable.md b/docs/howto/gathering_info/automatable.md
index d8ba917c..aa5a1c10 100644
--- a/docs/howto/gathering_info/automatable.md
+++ b/docs/howto/gathering_info/automatable.md
@@ -20,3 +20,5 @@ Liveness of Internet-connected services means quite a few overlapping things [@b
 For most vulnerabilities, an open port does not automatically mean that reconnaissance, weaponization, and delivery are automatable.
 Furthermore, discovery of a vulnerable service is not automatable in a situation where only two hosts are misconfigured to expose the service out of 2 million hosts that are properly configured.
 As discussed in in [Reasoning Steps Forward](../../topics/scope.md), the analyst should consider *credible* effects based on *known* use cases of the software system to be pragmatic about scope and providing values to decision points.
+
+{% include-markdown "../../_includes/default_automatable_values.md" %}
diff --git a/docs/reference/decision_points/automatable.md b/docs/reference/decision_points/automatable.md
index c20ce7c1..1a2b527f 100644
--- a/docs/reference/decision_points/automatable.md
+++ b/docs/reference/decision_points/automatable.md
@@ -11,6 +11,8 @@ print(example_block(LATEST))
 
       See this [HowTo](../../howto/gathering_info/automatable.md) for advice on gathering information about the Automatable decision point.
 
+{% include-markdown "../../_includes/default_automatable_values.md" %}
+
 !!! tip "See also"
 
     Automatable combines with [Value Density](./value_density.md) to inform