diff --git a/reference/emerging-technology-and-inactive-projects.rst b/reference/emerging-technology-and-inactive-projects.rst
index 82cd3622f..571d067f0 100644
--- a/reference/emerging-technology-and-inactive-projects.rst
+++ b/reference/emerging-technology-and-inactive-projects.rst
@@ -74,6 +74,12 @@ If project is not able to become an official OpenStack project within that
 timeframe, TC will discuss with the team if more time is required for the
 project to meet the :doc:`new-projects-requirements` or will retire the project.
 
+The TC will monitor the existing projects at different stages of the development
+cycle and if any project becomes inactive due to lack of maintainers and is not
+able to do the mandatory activities then the project will be marked as inactive.
+We will try to detect and mark a project inactive in the early stage of the
+development cycle but it can happen at any phase of development cycle.
+
 An existing project should be reinstated as an active OpenStack project before
 the release milestone-2 of the cycle they entered the ``inactive`` state to
 become ``active`` again and to be released in that cycle.  In the case where an
@@ -88,6 +94,13 @@ state, the TC will discuss with the team if project will be retired before the
 release milestone-2 of the cycle. In such a case there will be no new releases
 of that project.
 
+If any project becomes inactive after the release milestone-2 of the cycle, the
+TC will inform release team so that they can decide on their release for that
+cycle.
+
+For inactive project, we can try (if their gate allow us) to add an inactive status
+warning in the project ``README.rst`` file.
+
 Tracking
 ========