diff --git a/content/handling_data/_index.md b/content/handling_data/_index.md
index 4a75d8e8e20f7f43b6a823367b516363f8e5b3b6..852eacba3930c69f48f011e58aa0a1ee6a34424c 100644
--- a/content/handling_data/_index.md
+++ b/content/handling_data/_index.md
@@ -6,6 +6,14 @@ weight = "30"
{{% panel theme="danger" header="**Sensitive and Protected Data**" %}}HCC currently has *no storage* that is suitable for **HIPAA** or other **PID** data sets. Users are not permitted to store such data on HCC machines.{{% /panel %}}
+{{% notice warning %}}
+The Common filesystem will be retiring on June 30th, 2025!!! Any data under `/common` or `$COMMON` will be lost if it is not moved to another location before the retirement.
+
+It is strongly recommended to begin moving data and updating workflows as soon as possible to avoid lossing data or disrupting workflows.
+
+More information on the retirement is available on the [Common Retirement FAQ Page]({{< relref "../FAQ/common_retirement" >}}). If you have any questions about the retirement, please email <a href="mailto:hcc-support@unl.edu" class="external-link">hcc-support@unl.edu</a>.
+{{% /notice %}}
+
All HCC machines have three separate areas for every user to store data,
each intended for a different purpose. The three areas are `/common`, `/work`, and `/home`, each with different functions. `/home` is your home directory with a quota limit of **{{< hcc-quota "swan.home.block" >}}** and is backed up for best-effort disaster recovery purposes. `/work` is the high performance, I/O focused directory for running jobs. `/work` has a **{{< hcc-quota "swan.work.block" >}} per group quota**, is not backed-up and is subject to a [purge policy]({{<relref "data_storage/#purge-policy" >}}) of **{{< hcc-quota "swan.work.purge" >}} of inactivity on a file**. `/common` works similarly to `/work` and is mounted with read and write capabilities on all HCC clusters, meaning any files on `/common` can be accessed from all of HCC clusters unlike `/home` and `/work` which are cluster dependant. More information on the three storage areas on HCC's clusters are available in the [Data Storage]({{<relref "data_storage">}}) page.
{{< figure src="/images/storage_overview_graphic.png" height="500" class="img-border">}}
diff --git a/content/handling_data/data_storage/_index.md b/content/handling_data/data_storage/_index.md
index a3346eb35ef672a0c7974131df798c5e3af06730..83c00480d545a571218ad619d26bf34876bfdfff 100644
--- a/content/handling_data/data_storage/_index.md
+++ b/content/handling_data/data_storage/_index.md
@@ -29,6 +29,14 @@ intended as an area for I/O to active jobs.
---
### Common Directory
+{{% notice warning %}}
+The Common filesystem will be retiring on June 30th, 2025!!! Any data under `/common` or `$COMMON` will be lost if it is not moved to another location before the retirement.
+
+It is strongly recommended to begin moving data and updating workflows as soon as possible to avoid lossing data or disrupting workflows.
+
+More information on the retirement is available on the [Common Retirement FAQ Page]({{< relref "../../FAQ/common_retirement" >}}). If you have any questions about the retirement, please email <a href="mailto:hcc-support@unl.edu" class="external-link">hcc-support@unl.edu</a>.
+{{% /notice %}}
+
{{% notice info %}}
You can access your common directory quickly using the $COMMON
environmental variable (i.e. '`cd $COMMON`')
diff --git a/content/handling_data/data_storage/preventing_file_loss.md b/content/handling_data/data_storage/preventing_file_loss.md
index a580b3bca2f904d6aff208ef94cd276ddd28e176..2c43f71459e1de2a01cbf34bbbf65f30ac0c5e97 100644
--- a/content/handling_data/data_storage/preventing_file_loss.md
+++ b/content/handling_data/data_storage/preventing_file_loss.md
@@ -18,6 +18,14 @@ needs. For truly robust file backups, we recommend combining multiple
methods. For example, use Git regularly along with manual backups to an
external hard-drive at regular intervals such as monthly or biannually.
+{{% notice warning %}}
+The Common filesystem will be retiring on June 30th, 2025!!! Any data under `/common` or `$COMMON` will be lost if it is not moved to another location before the retirement.
+
+It is strongly recommended to begin moving data and updating workflows as soon as possible to avoid lossing data or disrupting workflows.
+
+More information on the retirement is available on the [Common Retirement FAQ Page]({{< relref "../../FAQ/common_retirement" >}}). If you have any questions about the retirement, please email <a href="mailto:hcc-support@unl.edu" class="external-link">hcc-support@unl.edu</a>.
+{{% /notice %}}
+
---
### 1. Use your local machine:
diff --git a/content/handling_data/data_storage/using_the_common_file_system.md b/content/handling_data/data_storage/using_the_common_file_system.md
index ec9946c4da297689c777c73ad2365a95771378fd..c7ade850ed1dc10e8500b1e5c75f5ace3e0a2b23 100644
--- a/content/handling_data/data_storage/using_the_common_file_system.md
+++ b/content/handling_data/data_storage/using_the_common_file_system.md
@@ -4,6 +4,14 @@ description = "How to use HCC's /common file system"
weight = 30
+++
+{{% notice warning %}}
+The Common filesystem will be retiring on June 30th, 2025!!! Any data under `/common` or `$COMMON` will be lost if it is not moved to another location before the retirement.
+
+It is strongly recommended to begin moving data and updating workflows as soon as possible to avoid lossing data or disrupting workflows.
+
+More information on the retirement is available on the [Common Retirement FAQ Page]({{< relref "../../FAQ/common_retirement" >}}). If you have any questions about the retirement, please email <a href="mailto:hcc-support@unl.edu" class="external-link">hcc-support@unl.edu</a>.
+{{% /notice %}}
+
### Quick overview:
- Connected read/write to all HCC HPC cluster resources – you will see