diff --git a/doc/source/train/schedule.rst b/doc/source/train/schedule.rst
index 3038acbfcc..c4e36dc810 100644
--- a/doc/source/train/schedule.rst
+++ b/doc/source/train/schedule.rst
@@ -180,6 +180,19 @@ intermediary releases before release week. During release week, only
 final-release-critical releases will be accepted (at the discretion of the
 release team).
 
+.. _t-cycle-highlights:
+
+Cycle highlights marketing deadline
+-----------------------------------
+
+Cycle highlights need to be added to the release deliverables by feature freeze to
+be included in any marketing release messaging. Highlights may be added after
+this point, but they will likely only be useful for historical purposes.
+
+See the `project team guide <https://docs.openstack.org/project-team-guide/release-management.html#cycle-highlights>`_
+for more details and instructions on adding these highlights.
+
+
 .. _t-final:
 
 Train release
diff --git a/doc/source/train/schedule.yaml b/doc/source/train/schedule.yaml
index 3e83ec4b86..cff1d2d9f6 100644
--- a/doc/source/train/schedule.yaml
+++ b/doc/source/train/schedule.yaml
@@ -100,6 +100,7 @@ cycle:
     - t-soft-sf
     - t-rf
     - t-goals-complete
+    - t-cycle-highlights
   project-specific:
     - t-keystone-ffreeze
     - t-nova-ffreeze