diff --git a/indicator_templates/quarto/5_reproducibility/impact_of_open_code_in_research.qmd b/indicator_templates/quarto/5_reproducibility/impact_of_open_code_in_research.qmd
index 3b8bc72..f305c54 100644
--- a/indicator_templates/quarto/5_reproducibility/impact_of_open_code_in_research.qmd
+++ b/indicator_templates/quarto/5_reproducibility/impact_of_open_code_in_research.qmd
@@ -32,6 +32,10 @@ The impact of Open Code in research aims to capture the effect of making researc
 
 This indicator can be used to assess the level of openness and accessibility of research code within a specific scientific community or field and to identify potential barriers or incentives for the adoption of Open Code practices. It can also be used to track the reuse and subsequent impact related to reproducibility of Open Code, as well as to evaluate the effectiveness of policies and initiatives promoting Open Code practices.
 
+### Connections to Academic Indicators
+
+This indicator examines the broader effects of making code or software openly accessible, focusing on its role in fostering transparency, collaboration, and reproducibility across the scientific community. This builds upon the [Use of Code in Research](https://handbook.pathos-project.eu/indicator_templates/quarto/2_academic_impact/use_of_code_in_research.html), which assesses the initial incorporation of code or software into research, and the [Reuse of Code in Research](https://handbook.pathos-project.eu/indicator_templates/quarto/5_reproducibility/reuse_of_code_in_research.html), which measures the extent to which existing code or software is adopted in subsequent studies. Together, these indicators provide a comprehensive view of how code or software contributes to research outputs, reusability, reproducibility, and the wider adoption of Open Code practices.
+
 ## Metrics
 
 ### NCI for publications that have introduced Open Code
@@ -168,4 +172,4 @@ To ensure that a code repository (i.e. Github, Gitlab, Bitbucket) primarily cont
 -   Documentation: Some repositories include extensive documentation that provides details on the software, its usage, and how to contribute to the project. This indicates a greater likelihood that the repository primarily contains code.
 -   Existence of script and source folders: In some cases, the existence of certain directories like '/src' for source files or '/scripts' for scripts can indicate that the repository is primarily for code.
 
-By considering these checks, we can ensure that the repository primarily contains code rather than data or datasets.
\ No newline at end of file
+By considering these checks, we can ensure that the repository primarily contains code rather than data or datasets.