Catch weekly overtime exposure before the 40-hour line is crossed.
Some weekly OT is intentional. Some is the result of last-minute schedule changes nobody noticed in time. The drift warning surfaces shifts that would push a worker toward weekly OT — typically at 36 hours scheduled — so managers can redistribute or accept the cost knowingly.
Weekly OT Drift Warning
Flags when a scheduled assignment trends a worker toward weekly OT before the 40-hour line is crossed. Manager can override.
What the rule does as a worker's scheduled hours approach 40.
The hero card configuration: Avoid at 36 hours scheduled. Here's what that does at runtime.
When a manager creates a shift that would push a worker's scheduled weekly hours past 36, a yellow indicator surfaces. "This addition trends toward weekly OT." The schedule saves; the exposure is logged for review.
Deploy OT drift warnings in your Teambridge.
Tell us about your workforce. We'll spin up the drift warnings — alongside the other 17 Colorado policies — in a sandbox tenant.
Drift warnings are an operational tool, not a legal requirement.
The 36-hour threshold isn't in any statute. It's a Teambridge default that surfaces OT exposure 4 hours before the line, giving managers time to react. The legal rule is the 40-hour weekly threshold itself.
Why 36 specifically
36 hours leaves 4 hours of buffer before OT triggers. For most frontline workforces, 4 hours is enough time for a manager to redistribute or accept the OT knowingly. Lower thresholds (e.g., 32) generate too many warnings; higher (38) cuts too close.
Manager-side warning, not worker-side
The drift warning fires for the manager building the schedule, not the worker. Workers don't see it. The point is to keep the operator informed of OT exposure they may not have noticed.
Teambridge surfaces OT exposure before it becomes a payroll surprise.
The drift warning catches OT exposure at the moment a manager can do something about it — schedule editing, shift assignment, swap approval — instead of at payroll close when it's too late.
Hour-running total visible.
When a manager builds a shift, the worker's running weekly total is visible inline. If adding the shift pushes past 36, the indicator surfaces.
Drift check on swap-in.
When approving a swap, Teambridge runs the drift check on the receiving worker. If the swap would push them past 36, the approval surfaces the OT exposure.
Drift checks all of an employer's locations.
If a worker is shared across multiple of your locations, the drift threshold applies to combined hours, not per-location. Cross-location exposure is the most common OT surprise.
Default 36, adjustable.
Some operators run leaner and want the drift warning at 32. Some run with intentional OT and don't want the warning until 38 or even 40. The threshold is configurable; the underlying 40-hour OT calculation is not.
Still evaluating? Get a free Colorado compliance audit.
Send us your existing Colorado scheduling and pay configuration. Our compliance team returns a written audit within 5 business days — every Colorado-specific exposure ranked by risk and back-pay liability.