Overtime, PTO and Shift Bidding Rules at the Time Clock

You can run overtime, PTO and shift bidding policies from the time clock if you first rewrite each policy as a clear rule with a trigger, a threshold and an action. The clock then warns, routes or blocks at the moment of the punch, instead of payroll discovering the problem after the workweek has closed.

Disclosure: The author works at CloudApper, which makes CloudApper AI TimeClock, which is discussed in this article.

Key takeaways

• The time clock is the only system every hourly employee touches every shift, so it is the best place to enforce policy.
• Translate each policy into "when X happens, do Y" before you configure any software.
• Under the FLSA, overtime is owed for hours over 40 in a workweek even if it was not approved, so alerts must come before the threshold, not after.
• Shift bidding works only when the eligibility and tie-break rules are written down and visible to employees.

Why enforce policy at the time clock instead of in payroll?

Most overtime and PTO problems are discovered late. A supervisor approves a timecard on Monday and finds that two people crossed 40 hours on Saturday. A PTO request sits in an inbox while the schedule is already built. An open shift goes to whoever answers the group text first, and the people who missed the text file a grievance.

Moving the rule to the clock changes the timing. The employee sees their projected hours when they clock in, the supervisor gets an alert before the threshold is crossed, and the request lands in the system of record with a timestamp. Payroll still calculates pay, but it stops being the first place anyone notices a policy breach.

The CloudApper AI TimeClock is built around this idea. CloudApper lists a Shift Bidding Agent, a PTO and Overtime Agent, a Self-Service Agent, a Compliance Management Agent and an HR and Payroll Sync Agent, along with configurable prompts, attestations and overtime policies at the clock.

What does the FLSA require for overtime?

Start from the federal floor, then layer state rules and your own policies on top. According to the Department of Labor's FLSA overview and Fact Sheet #23:

• Covered nonexempt employees must receive at least one and one-half times their regular rate of pay for hours worked over 40 in a workweek.
• A workweek is a fixed and regularly recurring period of 168 hours. Averaging hours over two or more weeks is not permitted.
• The FLSA does not require overtime pay for work on Saturdays, Sundays, holidays or regular days of rest as such. Some states and union contracts add daily or premium rules, so check yours.
• The regular rate includes all remuneration for employment except payments the Act itself excludes.

Fact Sheet #22 adds the rule that catches most employers: work not requested but suffered or permitted is work time that must be paid. An employee who stays to finish a task after the shift has worked those minutes whether or not anyone approved them. That is why an approval workflow alone does not control overtime cost. Only a warning before the time is worked does.

Whether PTO hours count toward the 40 is a common follow-up. We answer it in detail in do employers have to count PTO toward weekly overtime.

How do you turn policies into rules a time clock can enforce?

Write each policy as a trigger, a threshold and an action. The table shows typical examples. Replace the thresholds with your own.

Policy	Trigger	Threshold (example)	Action at the clock
Overtime warning	Clock in	Projected week reaches 36 hours	Show hours to employee, alert supervisor
Unapproved overtime	Clock out after shift end	Weekly total above 40 hours	Require reason prompt, route to manager review
Early clock in	Clock in	More than the grace window before shift	Prompt to confirm start of work or wait
Meal break attestation	Clock out	Shift longer than your state's break trigger	Ask whether a full break was taken, log answer
PTO request	Employee request at kiosk	Accrual balance and blackout dates	Show balance, submit to approver
Open shift bidding	Shift posted	Eligibility and overtime impact	Show only to eligible employees, rank bids

Two cautions. First, an early clock in prompt must never stop someone from recording time they actually work, because suffered or permitted work is still payable. Use prompts to steer behavior, and handle repeated issues through coaching. Second, record the employee's answer to every attestation with the punch, so you have an audit trail if a claim arrives later.

How should shift bidding rules be designed?

Shift bidding replaces the group text with a visible, rules-based process. The software is the easy part. Agreeing on the rules is where the work is.

Decide eligibility

• Which roles, certifications or departments can bid on each shift.
• Whether a bid that would push someone into overtime is allowed, flagged or blocked.
• Minimum rest between shifts, if your policy or contract sets one.

Decide the award rule

• Seniority: common in union settings and easy to explain, but the same people tend to win every time.
• Rotation: spreads extra hours evenly, but needs a tracked rotation list.
• Lowest overtime cost: favors employees under 40 hours for the week, which controls cost but must be applied consistently.
• First come: fast, but favors whoever checks the app first, which creates fairness complaints.

Publish the rule and the tie-breaker, and show employees why a shift went to someone else. Transparency is what keeps bidding from becoming a grievance source.

How do PTO requests and accruals work at the kiosk?

Hourly employees rarely log in to an HR portal, but they see the time clock every shift. Showing the accrual balance at clock in and letting employees submit a request on the spot cuts down on paper forms and on questions to supervisors. The request still has to land in your HCM or payroll system so the balance stays correct, which makes the integration the deciding factor. CloudApper lists AI TimeClock integrations with UKG, Workday, Ceridian Dayforce, ADP, Oracle Cloud HCM, SAP SuccessFactors, Paylocity, Paycom and others. Confirm in a demo that approved requests update the balance in your system of record, not just in the clock.

Plan for unusual cases too, such as forced PTO during a site closure. Our guide on mandating PTO usage during unexpected closures covers the policy questions to settle before that day arrives.

Common mistakes to avoid

• Configuring rules before the written policy is final, which bakes ambiguity into the software.
• Using blocking rules that prevent employees from recording time they worked.
• Measuring overtime by pay period instead of by FLSA workweek.
• Rounding rules that always favor the employer. Check how hours are totaled with our guide on calculating time clock work hours.
• Launching shift bidding without telling employees how awards are decided.

Frequently Asked Questions

Can a time clock stop employees from working overtime?

It can warn employees and supervisors before overtime starts, and route unapproved overtime for review, but it should not block employees from recording time they actually work. Under the FLSA, work that is suffered or permitted must be paid. Control overtime through early alerts, schedule adjustments and consistent coaching instead of hard blocks.

Does the FLSA require daily overtime after 8 hours?

No. The federal rule is overtime for hours over 40 in a workweek, and the Department of Labor says the Act does not require overtime for weekends, holidays or rest days as such. Some states and collective bargaining agreements set daily thresholds or premiums, so configure your clock rules for each jurisdiction where you have employees.

What is the fairest way to award bid shifts?

There is no single fairest rule. Seniority is simple and common in union settings, rotation spreads hours evenly, and lowest overtime cost controls spending. Whatever you choose, publish the rule and the tie-breaker, apply it consistently, and let employees see why a shift was awarded so decisions can be checked.

Should PTO requests be approved at the kiosk?

Employees should be able to submit requests and see balances at the kiosk, but approval usually belongs to a manager who can see coverage. What matters is that the request and the decision both sync to your HCM so balances, schedules and payroll stay consistent. Test that sync during the pilot.

Next steps to put policy at the clock

1. List your overtime, break, PTO and open shift policies and rewrite each one as trigger, threshold and action.
2. Confirm your FLSA workweek definition and any state daily overtime or break rules with payroll.
3. Agree on a shift award rule and tie-breaker with operations, and with the union where applicable.
4. Pilot the rules at one site for a full pay period and compare alerts against actual overtime.

Browse our payroll compliance guides for related wage and hour topics. To see how these rules are configured in a tablet time clock, review the CloudApper AI TimeClock product page.

Last reviewed: October 2026.

Sources

• Wages and the Fair Labor Standards Act, U.S. Department of Labor
• Fact Sheet #23: Overtime Pay Requirements of the FLSA, U.S. Department of Labor
• Fact Sheet #22: Hours Worked Under the Fair Labor Standards Act (FLSA), U.S. Department of Labor
• Employee Time Clock Software (CloudApper AI TimeClock), CloudApper