diff --git a/.last-branch b/.last-branch
index ba2906d..328db20 100644
--- a/.last-branch
+++ b/.last-branch
@@ -1 +1 @@
-main
+v20260101-03-run-checks-page-guide-text
diff --git a/build-and-push.sh b/build-and-push.sh
old mode 100644
new mode 100755
diff --git a/containers/backupchecks/src/templates/main/run_checks.html b/containers/backupchecks/src/templates/main/run_checks.html
index 541a854..b9e946b 100644
--- a/containers/backupchecks/src/templates/main/run_checks.html
+++ b/containers/backupchecks/src/templates/main/run_checks.html
@@ -1,3 +1,27 @@
+
+<div class="info-block">
+    <h3>Run Checks workflow</h3>
+    <p>
+        The Run Checks page is used for daily operational triage. It lists job runs that need attention so they can be reviewed,
+        documented, and cleared from the active overview.
+    </p>
+    <p>
+        The primary goal is to keep this page as empty as possible. An empty Run Checks page indicates that backups are being actively
+        monitored and handled.
+    </p>
+    <ul>
+        <li><strong>Review:</strong> Every run on this page must be reviewed. The review process is used to demonstrate that backup
+        results are actively checked and validated by operations.</li>
+        <li><strong>Ticket / Remark:</strong> If a run requires follow-up, add a ticket number or a short remark to document the next
+        steps or ownership. After adding a ticket or remark, the run must still be marked as reviewed.</li>
+        <li><strong>Resolved:</strong> When the underlying issue is fixed or confirmed as no longer relevant, mark the run as resolved.
+        The resolved status remains until it is cleared by the normal workflow.</li>
+    </ul>
+    <p>
+        By consistently reviewing runs and documenting follow-up where needed, the Run Checks page provides both operational focus
+        and auditable proof that backups are being checked.
+    </p>
+</div>
 {% extends "layout/base.html" %}
 
 {% block content %}