diff --git a/containers/backupchecks/src/templates/documentation/customers-jobs/job-schedules.html b/containers/backupchecks/src/templates/documentation/customers-jobs/job-schedules.html
index a700bf5..4d30202 100644
--- a/containers/backupchecks/src/templates/documentation/customers-jobs/job-schedules.html
+++ b/containers/backupchecks/src/templates/documentation/customers-jobs/job-schedules.html
@@ -173,8 +173,14 @@
   <li>The job was recently approved and doesn't have enough run history yet</li>
   <li>The job has an irregular pattern that the system cannot predict</li>
   <li>The job hasn't received enough consistent backup runs to establish a pattern</li>
+  <li><strong>Information jobs:</strong> Jobs like "SSL certificate updated" or one-time maintenance tasks that run irregularly</li>
 </ul>
 
+<div class="doc-callout doc-callout-info">
+  <strong>💡 Information Jobs:</strong><br>
+  Some jobs are informational in nature (e.g., SSL certificate renewals, system updates) and do not run on a regular schedule. These jobs will never learn a schedule pattern and will not appear on the Daily Jobs page.
+</div>
+
 <p>In these cases:</p>
 <ul>
   <li>The job will <strong>not appear</strong> on the Daily Jobs page (since we don't know when it's expected)</li>
@@ -199,32 +205,57 @@
   <thead>
     <tr>
       <th>Job Status</th>
+      <th>Color</th>
       <th>Meaning</th>
       <th>Action Needed</th>
     </tr>
   </thead>
   <tbody>
     <tr>
-      <td><strong>Ran successfully</strong> (green)</td>
+      <td><strong>Ran successfully</strong></td>
+      <td>Green</td>
       <td>Job ran today and completed successfully</td>
       <td>No action needed</td>
     </tr>
     <tr>
-      <td><strong>Ran with failure</strong> (red)</td>
+      <td><strong>Ran with failure</strong></td>
+      <td>Red</td>
       <td>Job ran today but failed</td>
       <td>Investigate failure, create ticket if needed</td>
     </tr>
     <tr>
-      <td><strong>Expected but not run</strong> (yellow/gray)</td>
-      <td>Job is expected to run today based on schedule, but hasn't run yet</td>
-      <td>Wait if still early in the day, investigate if overdue</td>
+      <td><strong>Expected but not run yet</strong></td>
+      <td>White</td>
+      <td>Job is expected to run later today (time hasn't arrived yet)</td>
+      <td>Wait - job is not yet overdue</td>
+    </tr>
+    <tr>
+      <td><strong>Expected but overdue</strong></td>
+      <td>Gray</td>
+      <td>Job was expected to run but hasn't (time has passed)</td>
+      <td>Investigate - job may have failed to start</td>
     </tr>
   </tbody>
 </table>
 
 <div class="doc-callout doc-callout-tip">
   <strong>💡 Workflow Tip:</strong><br>
-  Use the Daily Jobs page as your primary monitoring dashboard. Check it daily to ensure all expected backups have run successfully. Any job showing as "expected but not run" late in the day should be investigated.
+  Use the Daily Jobs page as your primary monitoring dashboard. Check it daily to ensure all expected backups have run successfully. Jobs showing in <strong>white</strong> are not yet due, while jobs showing in <strong>gray</strong> are overdue and should be investigated.
+</div>
+
+<h3>Multiple Runs Per Day</h3>
+
+<p>Some jobs run multiple times per day (e.g., hourly backups, multiple backup sets):</p>
+
+<ul>
+  <li>The schedule displays the expected time(s) only once</li>
+  <li>A <strong>run counter</strong> appears next to the time indicator showing how many runs have occurred</li>
+  <li>Example: A job running 3 times per day at 10:00 might show "10:00 (3)" indicating 3 runs</li>
+</ul>
+
+<div class="doc-callout doc-callout-info">
+  <strong>💡 Run Counters:</strong><br>
+  The number in parentheses after the time indicates how many backup runs have been received for that job today. This helps you track jobs that run multiple times per day.
 </div>
 
 <h2>Schedule Learning Best Practices</h2>