Temp Check Schedules

Purpose

This page defines recurring temperature check windows so compliance routines happen consistently across shifts and locations.

Prerequisites

• Locations/devices should be mapped correctly.
• Required check frequency should be defined by policy.
• Users need permission to manage schedule settings.

Main Actions

• Create and update recurring check schedules.
• Set frequency, due windows, and responsible groups.
• Enable or pause schedule rules.
• Review overdue patterns and tune timing.

Field/Status Reference

• Schedule Name: Identifier for the recurring routine.
• Frequency: How often checks are due.
• Due Window: Time range for expected completion.
• Assigned Group/User: Who is responsible for execution.
• Schedule Status: Active, paused, or inactive.

Workflow

1. Create or select the schedule rule.
2. Define frequency and due window.
3. Assign responsible users or teams.
4. Activate and monitor completion behavior.
5. Refine timing if overdue patterns appear.

Connections

• Drives recurring work in daily tasks/checklist workflows.
• Supports compliance evidence in logs and reports.
• Pairs with Notification Manager for reminders/escalations.

Common Mistakes

• Setting unrealistic intervals for operational capacity.
• Assigning schedules to inactive or incorrect users.
• Overlapping schedules that duplicate work.

Troubleshooting

• If checks are not generated, verify schedule status and assignment.
• If due times look off, confirm timezone and shift settings.
• If completion rates are poor, adjust window length and reminder routing.

Quick Tips

• Align schedules with real shift patterns.
• Keep naming clear so owners know exactly what is due.
• Review overdue trends weekly and adjust quickly.