diff --git a/docs/source/pillars/supporting.md b/docs/source/pillars/supporting.md
index 8b61d55e..6aa2cf8f 100644
--- a/docs/source/pillars/supporting.md
+++ b/docs/source/pillars/supporting.md
@@ -189,24 +189,24 @@ How the {ref}`TRE operator <infrastructure_roles>` involves the public in its pr
   - Guidance
   - Importance
 * - 4.8.1.
-  - All public engagement activities must be representative and inclusive.
+  - All public engagement activities must be representative and inclusive (\*optional for TREs without public sector data).
   - Any public engagement activity carried out by TREs should involve diverse participants and that activities are accessible.
     Recruitment plans should consider how to proactively reach a representative sample of people or target particular groups of people where relevant
     This could include following guidelines such as [PEDRI](https://www.pedri.org.uk/).
-  - Mandatory (for TREs with public sector data), otherwise Optional
+  - Mandatory\*
 * - 4.8.2.
-  - Details of TRE operations, data available and projects which have accessed the data should be publicly available.
+  - Details of TRE operations, data available and projects which have accessed the data should be publicly available (\*optional for TREs without public sector data).
   - TREs should be as transparent as possible by providing information online.
     Where information is made available online this should be written in clear language understandable to general public.
     A record of projects which have accessed data via the TRE should be kept and made available.
     Where possible it should include name, summaries, public benefit (if relevant) and organisations involved
-  - Mandatory (for TREs with public sector data), otherwise Optional
+  - Mandatory\*
 * - 4.8.3.
-  - Members of the public should be included in TRE operations and/or oversight.
+  - Members of the public should be included in TRE operations and/or oversight (\*optional for TREs without public sector data).
   - Members of the public can be involved via presence on steering groups or project approvals panels.
     Alternatively TRE's can establish separate public panels available for both researchers and TRE staff to consult.
     This is especially relevant for TREs with public sector data.
-  - Mandatory (for TREs with public sector data), otherwise Optional
+  - Mandatory\*
 * - 4.8.4.
   - You should publicly share details of incidents, near misses, and mitigations in a timely fashion, in line with good practices for responsible disclosure.
   - This may be via the TRE website or annual reports.
diff --git a/docs/source/specification.md b/docs/source/specification.md
index d62cbca4..b60ff538 100644
--- a/docs/source/specification.md
+++ b/docs/source/specification.md
@@ -73,6 +73,9 @@ These components are each labelled with an importance:
 :Recommended: Most TREs should have this component, but it is not essential.
 :Optional: Many TREs would benefit from this component, however, we recognise there are reasons a {ref}`TRE operator <infrastructure_roles>` may actively choose not to implement it.
 
+Some components are mandatory in some circumstances but not others.
+These are indicated by an asterisk `Mandatory*`, with details provided in the statement.
+
 {ref}`TRE operator <infrastructure_roles>`s are able to demonstrate that they meet the specification by showing they can fulfil all **mandatory** components.
 Future versions of the specification may introduce more granular levels of evaluation, for instance tiered level of accreditation based on fulfilment of mandatory, recommended and optional components respectively.