diff --git a/schedule-europe.md b/schedule-europe.md
index 943ea00..4067253 100644
--- a/schedule-europe.md
+++ b/schedule-europe.md
@@ -26,7 +26,7 @@
 | 10:45 | [First-class Gerrit CI integration with Checks](sessions/first-class-ci-integration.md)      |
 | 11:45 | Gerrit goes multi-site                                                                       |
 | 12:45 | Lunch & Networking                                                                           |
-| 14:00 | [Prolog-less submit rules, easy and for everyone](sessions/prolog-less-submit-rules.md)      |
+| 14:00 | [Labels & Prolog-less submit rules](sessions/labels-and-prolog-less-submit-rules.md)      |
 | 15:00 | Gerrit at Volvo Cars                                                                         |
 | 16:00 | Break & Networking                                                                           |
 | 16:30 | Using Zuul CI with Gerrit                                                                    |
diff --git a/sessions/labels-and-prolog-less-submit-rules.md b/sessions/labels-and-prolog-less-submit-rules.md
new file mode 100644
index 0000000..7984533
--- /dev/null
+++ b/sessions/labels-and-prolog-less-submit-rules.md
@@ -0,0 +1,19 @@
+# Labels & Prolog-less submit rules - Control when changes become submittable
+
+For many teams it is important to customize the conditions that make a change
+submittable (e.g. to enforce non-author code reviews). The way to do this in
+Gerrit is via labels and submit rules.
+
+In this talk I explain how labels and submit rules work and what you can do with
+them.
+
+For submit rules the focus is on Prolog-less submit rules which are based on a
+[new extension point](https://gerrit-review.googlesource.com/admin/repos/plugins/simple-submit-rules).
+Using this extension point to implement submit rules is a good alternative to
+writing
+[Prolog submit rules](https://gerrit-review.googlesource.com/Documentation/prolog-cookbook.html#SubmitRule)
+which often cause trouble because most people are not familiar enough with
+Prolog. I will show an example implementation of a Prolog-less submit rule and
+explain how you can develop your own custom submit rules.
+
+*[Edwin Kempin, Google](../speakers.md#ekempin)*
diff --git a/sessions/prolog-less-submit-rules.md b/sessions/prolog-less-submit-rules.md
deleted file mode 100644
index 12a50e6..0000000
--- a/sessions/prolog-less-submit-rules.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# Prolog-less submit rules, easy and for everyone
-
-For many teams it is important to customize the conditions that make a change
-submittable (e.g. to enforce non-author code reviews). The traditional way to do
-this is via
-[Prolog submit rules](https://gerrit-review.googlesource.com/Documentation/prolog-cookbook.html#SubmitRule),
-but many project owners struggle with Prolog and find Prolog submit rules hard
-to use. Writing, testing and maintaining complex Prolog rules can be difficult
-and time-consuming. In this talk I want to introduce you to an alternative and
-show you how submit rules can be easily configured from the WebUI by using the
-[simple-submit-rules plugin](https://gerrit-review.googlesource.com/admin/repos/plugins/simple-submit-rules).
-The plugin is based on a
-[new extension point](https://gerrit-review.googlesource.com/admin/repos/plugins/simple-submit-rules)
-that allows to implement submit rules in Java. I will explain how you can use
-this extension point to add your own submit rules and how submit rules from
-different plugins can be combined.
-
-*[Edwin Kempin, Google](../speakers.md#ekempin)*