diff --git a/docs/_includes/default_safety_values.md b/docs/_includes/default_safety_values.md
new file mode 100644
index 00000000..15d7b09a
--- /dev/null
+++ b/docs/_includes/default_safety_values.md
@@ -0,0 +1,6 @@
+!!! tip "Default Safety Values"
+
+    If the decision maker knows nothing about the environment in which the device is used, we suggest assuming a
+    [*marginal* *Safety Impact*](../reference/decision_points/safety_impact.md).
+    This position is conservative, but software is thoroughly embedded in daily life now, so we suggest that the decision
+    maker provide evidence that no one's well-being will suffer.
diff --git a/docs/howto/bootstrap/collect.md b/docs/howto/bootstrap/collect.md
index cc28d073..9691ce95 100644
--- a/docs/howto/bootstrap/collect.md
+++ b/docs/howto/bootstrap/collect.md
@@ -111,12 +111,7 @@ we can suggest something like defaults for some decision points.
     [*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).
 
-!!! tip "Default Safety Values"
-
-    If the decision maker knows nothing about the environment in which the device is used, we suggest assuming a
-    [*marginal*](../../reference/decision_points/safety_impact.md) [*Safety Impact*](../../reference/decision_points/safety_impact.md).
-    This position is conservative, but software is thoroughly embedded in daily life now, so we suggest that the decision
-    maker provide evidence that no one’s well-being will suffer.
+{% include-markdown "../../_includes/default_safety_values.md" %}
 
 !!! tip "Default Mission Impact Values"
 
diff --git a/docs/reference/decision_points/safety_impact.md b/docs/reference/decision_points/safety_impact.md
index 128275ba..047abd05 100644
--- a/docs/reference/decision_points/safety_impact.md
+++ b/docs/reference/decision_points/safety_impact.md
@@ -14,6 +14,8 @@ print(example_block(LATEST))
     - Safety Impact combines with [Mission Impact](./mission_impact.md) to 
       inform [Human Impact](./human_impact.md).
 
+{% include-markdown "../../_includes/default_safety_values.md" %}
+
 We take an expansive view of safety, in which a safety violation is a violation of what the United States [Centers for Disease Control (CDC)](https://www.cdc.gov/hrqol/wellbeing.htm) calls **well-being**. Physical well-being violations are common safety violations, but we also consider economic, social, emotional, and psychological well-being to be important. Weighing fine differences among these categories is probably not possible, so we will not try. Each decision option lists examples of the effects that qualify for that value/answer in the various types of violations of well-being. These examples should not be considered comprehensive or exhaustive, but rather as suggestive.
 <!--The CDC webpage is better called a lit review. It has 74 citations on well-being across various fields. The following citations could reasonably be cited directly, rather than just referencing the CDC page:
 Frey BS, Stutzer A. Happiness and economics. Princeton, N.J.: Princeton University Press; 2002.
@@ -47,6 +49,8 @@ Aggregation suggests that the stakeholder’s response to this decision point ca
 
 ## Gathering Information About Safety Impact
 
+{% include-markdown "../../_includes/default_safety_values.md" %}
+
 The factors that influence the safety impact level are diverse.
 This paper does not exhaustively discuss how a stakeholder should answer a question; that is a topic for future work.
 At a minimum, understanding safety impact should include gathering information about survivability of the vulnerable component, determining available operator actions to compensate for the vulnerable component, understanding relevant insurance, and determining the viability of existing backup measures.