diff --git a/modules/release_guide/pages/release_eol.adoc b/modules/release_guide/pages/release_eol.adoc
index 653e265..98e552d 100644
--- a/modules/release_guide/pages/release_eol.adoc
+++ b/modules/release_guide/pages/release_eol.adoc
@@ -146,6 +146,12 @@ Syntax: sudo rbac-playbook groups/bodhi-backend.yml
 Send the final announcement to `devel@`, `devel-announce@`, `test@`, `test-announce@`, `announce@` lists.
 Use the https://pagure.io/releng/blob/main/f/mail-templates/08-end-of-life.txt[template] from release engineering repo.
 
+=== Other tasks
+
+==== Remove EOL release from Koschei
+
+The release going EOL must be removed from Koschei to prevent a flood of failed scratch builds.
+See the xref:sysadmin_guide:koschei.adoc#_removing_an_eol_fedora_release[Koschei sysadmin guide] for details.
 
 === Stage the EOL release to archive
 
diff --git a/modules/sysadmin_guide/pages/koschei.adoc b/modules/sysadmin_guide/pages/koschei.adoc
index f52b2bc..f5e7788 100644
--- a/modules/sysadmin_guide/pages/koschei.adoc
+++ b/modules/sysadmin_guide/pages/koschei.adoc
@@ -230,6 +230,18 @@ Then you can optionally verify that the collection configuration is
 correct by visiting https://koschei.fedoraproject.org/collections
 and examining the configuration of the newly branched collection.
 
+== Removing an EOL Fedora release
+
+When a Fedora release goes EOL its collection must be removed from Koschei.
+Otherwise Koschei will flood Koji with scratch build attempts that fail.
+To do this, from the admin pod, run:
+
+....
+koschei-admin delete-collection --force f39
+....
+
+with '39' changed to the number of the release going EOL.
+
 == Edit Koschei group to make it global
 
 To turn `mygroup` group created by user `someuser` into a global group