diff --git a/conservancy/usethesource/templates/usethesource/ccirt_process.html b/conservancy/usethesource/templates/usethesource/ccirt_process.html
index e5c4326c..40bcbfda 100644
--- a/conservancy/usethesource/templates/usethesource/ccirt_process.html
+++ b/conservancy/usethesource/templates/usethesource/ccirt_process.html
@@ -5,6 +5,18 @@
 {% block content %}
   {{ block.super }}
 
-  <h1>CCIRT Process</h1>
+  <h1>Timelines for CCIRT email submission and notifications</h1>
+
+We at SFC are providing an opportunity for companies who want to be notified of source candidates of theirs that we plan to post to <a href="..">Use The Source</a> to provide us with the email address of their Copyleft Compliance Incident Response Team (CCIRT), which we will email when we receive a new source candidate for the company that we plan to post.  If we have a CCIRT email address on a file for a given company, we will email this address if we receive a source candidate from that company, and then wait at least 7 days for a reply - if an updated candidate is received, we will post that, otherwise we will post the candidate that we notified the CCIRT team about as-is.
+
+As discussed in our [FIXME: link] blog post, the CCIRT is an important part of an organization's OSPO or cybersecurity team.  SFC hopes that companies will treat any reports from SFC with the same urgency as any security vulnerabilities they are made aware of, since failure to provide complete source code severely impedes users' and third party repair companies' ability to fix them.
+
+Based on our decades of GPL compliance experience, we expect that many of the source code candidates we receive from the public will be incomplete.  SFC cannot immediately validate nor invalidate any of those claims due to the vast number of devices on the market.  But we are willing to engage with companies' CCIRTs so they have a chance to (re-)review these candidates if they wish, before SFC publishes them.
+
+We are providing a 30-day window, starting on February 3, 2024 (and ending at 23:59 AoE FIMXE:abbr on March 4, 2024), in which companies can send us the email address of their CCIRT (to compliance@sfconservancy.org with Subject "CCIRT contact") so we can contact this team about any source candidates we receive, giving them 7 calendar days to confirm all potential copyleft licenses issues are resolved.  At the end of these 7 days, we will publish the updated source candidate (if we receive one), or the original (if no update is received).  If we have no contact registered, the source candidate will be published without any grace period following the initial 30-day window.
+
+After this initial 30-day window, companies can still send us the email address of their CCIRT and, after we receive this email address, we will give them 7 calendar days from the first notification of an incomplete source candidate to resolve the issue.  However, it is best for companies to let us know about their CCIRT before this 30-day window ends in case there are any pending source candidates to publish when that 30-day window ends.
+
+For the avoidance of doubt, and to hopefully prevent a wave of last-minute CCIRT submissions on the final day of this 30-day window, SFC is providing for 7 calendar days after the 30-day window ends (so 37 days from February 3, or until 23:59 AoE FIMXE:abbr on March 11, 2024), to any company that provides the email address of their CCIRT at any time during this 30-day window, the option to correct its source candidates before we publish them.  So it is beneficial for companies to inform us of their CCIRT sooner rather than later, so they have as much of that 37 days as possible to correct all copyleft compliance issues.  SFC looks forward to working with all the CCIRTs who register with us.
 
 {% endblock content %}