Weekly hour visibility helps managers understand the schedule before it becomes a problem. When teams assign shifts, approve coverage, or accept swaps, a worker's weekly total can change quickly.
This article is operational guidance, not legal, employment, immigration, labor, or university policy advice. Teams should configure thresholds and review workflows based on their own internal policies and qualified guidance.
Why weekly hour visibility matters
Managers often need to understand weekly scheduled hours before publishing or changing a schedule. Without visibility, a schedule can look covered while still requiring review against team-specific limits or internal policies.
Visibility helps managers catch concerns earlier, before the team relies on a schedule that may need correction.
Scheduled hours vs worked hours
Scheduled hours and worked hours are related but different. Scheduled hours show planned assignments. Worked hours reflect what actually happened after attendance, timekeeping, or corrections.
Managers need scheduled-hour visibility because decisions happen before work is performed: publishing, assigning, swapping, and approving coverage.
Why coverage requests can change weekly totals
Coverage requests can add hours to the replacement worker and remove responsibility from the original worker. If the system only checks the original schedule, managers may miss the impact of the coverage change.
A useful workflow shows weekly-hour impact before the coverage request becomes final.
Why shift swaps can create hidden hour issues
A swap may look balanced at the shift level while changing weekly totals for one or both workers. The impact can depend on shift length, timing, existing assignments, and other pending changes.
Managers need to see the result of the swap, not only the fact that two workers agreed.
Configurable thresholds
Teams should be able to configure thresholds that match internal policies, program rules, or manager review preferences. This article does not define those limits for any organization.
The operational value is that thresholds make review visible at the moment a schedule is built or changed.
Manager review before publishing
Before publishing, managers should be able to scan workers whose scheduled hours require attention. That review can happen while the schedule is still easy to adjust.
This is especially useful for semester-based teams where student availability, class schedules, and returning worker patterns change together.
Warnings vs hard blocks
Some teams may prefer warnings that require manager review. Others may use hard blocks for selected thresholds. The right configuration depends on the team's internal process and policy environment.
The system should make the difference clear: a warning asks for review, while a hard block prevents the action unless the configured process allows an override.
Audit trail for hour-related decisions
Hour-related decisions should leave a record when managers approve, override, or correct schedule changes. That record should show the action, timestamp, manager, reason if provided, and final schedule state.
Audit history helps the team understand why a schedule was published or changed after a warning appeared.