diff --git a/meetings/2026-04-07.md b/meetings/2026-04-07.md
new file mode 100644
index 0000000..0ed8abb
--- /dev/null
+++ b/meetings/2026-04-07.md
@@ -0,0 +1,27 @@
+# Meeting on 2026-04-07
+
+Present: Adrian, Cornelius, Florian, Frederik, Loïc, Max, Peter, Stephanie, Tristram
+
+## Agenda
+
+* Project proposal: https://github.com/OpenRailAssociation/technical-committee/pull/321
+* Cleaning up playground: https://github.com/OpenRail-Playground
+* Business indicator scaling: https://github.com/OpenRailAssociation/technical-committee/pull/322
+* Document how we use publiccode.yml (https://github.com/OpenRailAssociation/technical-committee/pull/324)
+
+## Protocol
+
+* Project proposal: https://github.com/OpenRailAssociation/technical-committee/pull/321
+  * We need to find (potential) users of the tool in our companies, experts on GSM-R/FRMCS
+  * We would like to invite the maintainer to the next TC meeting to discuss the project in more detail
+* Cleaning up playground: https://github.com/OpenRail-Playground
+  * There are 32 repositories which are mostly artifacts from Hackathons which are only interesting for historical reasons. They are not active.
+  * We should make it transparent what the state of the projects is
+  * Decision: We archive the repositories with a note in the README and setting the GitHub archived state (Cornelius takes care of the archiving)
+  * We will revisit the question in a year or so to see if deleting projects to clean up is helpful
+* Business indicator scaling: https://github.com/OpenRailAssociation/technical-committee/pull/322
+  * Review of the PR is welcome
+* Document how we use publiccode.yml (https://github.com/OpenRailAssociation/technical-committee/pull/324)
+  * Review of the PR is welcome
+  * It documents why and how we use publiccode.yml
+  * publiccode.yml files should also be added to the other OpenRail projects