.last-branch

@@ -1 +1 @@
-main
+v20260101-03-run-checks-page-guide-text

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 %}

docs/changelog.md

@@ -105,6 +105,17 @@
 - Updated report generation logic to handle single-customer, multi-customer, and all-customer scopes.
 - Prepared reporting output for use cases such as account management and operations-wide overviews.
 
+---
+
+## v20260101-03-run-checks-page-guide-text
+
+- Added a workflow guide to the Run Checks page explaining its purpose in daily operational triage.
+- Emphasized that the main objective is to keep the Run Checks page as empty as possible.
+- Clarified that every run must be marked as reviewed to demonstrate that backups are actively checked.
+- Explicitly stated that after adding a ticket number or remark, the run must still be marked as reviewed.
+- Explained the role of the resolved status within the Run Checks workflow.
+- Placed the guide directly on the Run Checks page (no popup), aligned with the dashboard explanation style.
+
 ================================================================================================================================================
 ## v0.1.14