Engineering & Security Wage & Hour Audit Checklist

Engineering and security keep the building alive around the clock — which is precisely the problem. On-call rotations with 20-minute response windows, overnight engineers sleeping on premises, a salaried "chief" who spends the shift on a ladder, day-rate guards from a contract firm, and a biometric clock at the loading dock: every one is a known wage-hour failure mode. This checklist covers in-house engineering, security, and their vendors. Check items as you verify them — progress saves in this browser — and bold flags mark state and local items. Print it for the back-of-house walkthrough; the page is print-optimized.

On-call & overnight coverage#

• On-call programs are scored against the engaged-to-wait test: anyone required to remain on property is paid for all such hours, full stop.Why: 29 CFR 785.15 and Armour v. Wantock — waiting on the employer's premises at its disposal is worktime even if the engineer naps between calls.
• Off-property on-call terms — response-time windows, geographic radius, alcohol bans, call frequency — are reviewed annually, because tight tethers convert the whole waiting period into hours worked.Why: 29 CFR 785.17 — on-call time is compensable when the employee cannot use it effectively for personal purposes; a 20-minute response radius is a leash.
• Time on calls — including phone and remote-system troubleshooting from home — is logged from call receipt through resolution, with a practical mechanism for recording it.Why: 29 CFR 785.11–.12 — remote work the employer knows or should know about is compensable, and unlogged midnight calls are textbook off-the-clock claims.
• Call-back minimums are applied per policy, CBA, and state law — and in California, an employee called back for a second reporting in one workday receives at least two hours' pay.Why: IWC Wage Order 5 §5 reporting-time rules cover the second report; contractual call-back guarantees are enforceable wage obligations.
• Sleep-time deductions for overnight engineers exist only on shifts of 24 hours or more, under an express agreement, capped at 8 hours, with interruptions paid and the whole night paid if interruptions prevent 5 hours of sleep.Why: 29 CFR 785.22 — every element is mandatory; an invalid sleep-time agreement converts the full overnight into hours worked.
• On-call stipends and premiums are included in the regular rate for overtime weeks.Why: 29 CFR 778.223 — payments for on-call status are remuneration that inflates the overtime rate; see the regular rate.

Classification#

• The chief engineer's exemption is duties-tested: management of the department as primary duty, customary direction of two or more FTEs, real hire/fire authority — not a working lead with a title and a ladder.Why: 29 CFR part 541 — hands-on repair work as the primary duty defeats the executive exemption no matter the salary.
• Exempt salaries meet the $684/week federal floor (the 2019 level, restored effective May 15, 2026) and the higher state floors where they apply.Why: the 2024 rule's $844/$1,128 thresholds were vacated and are dead; California, New York, Washington, and Colorado set substantially higher floors that control.
• No engineer or security lead is paid a day rate or shift rate while classified exempt, absent a guaranteed weekly salary satisfying the regulation.Why: Helix Energy v. Hewitt (2023) — day rates flunk the salary-basis test even at six-figure earnings, exposing years of back overtime.
• Security supervisors claimed exempt actually manage — scheduling, directing, and evaluating guards as their primary duty — rather than standing the same posts with a different shirt.Why: 29 CFR 541.100 — directing two guards while working the door is a non-exempt lead, a recurring misclassification in contract and in-house security alike.
• Licensed trades on staff — electricians, HVAC techs, plumbers, carpenters — are non-exempt regardless of skill, licensure, or pay level.Why: 29 CFR 541.3 — the white-collar exemptions do not apply to manual and skilled-trade work, period.

Timekeeping#

• Radio, key, and tool pickup and the pre-shift security briefing follow the punch — they are the first principal activities of the day.Why: the continuous workday rule (IBP v. Alvarez) — once the first integral activity starts, everything after is compensable.
• Travel between buildings, towers, or sister properties during the shift stays on the clock.Why: 29 CFR 785.38 — travel between job sites within the workday is worktime; campus properties leak minutes here daily.
• California: end-of-shift security screenings and bag checks are paid time, even though federal law excuses them.Why: Frlekin v. Apple (Cal. 2020) makes employer-controlled exit checks compensable under state law, while Integrity Staffing v. Busk holds the opposite federally — the state rule controls.
• Illinois (and TX/WA): biometric timeclocks operate under written notice and consent, a published retention-and-destruction schedule, and no vendor disclosure beyond the policy.Why: Illinois BIPA carries $1,000/$5,000 statutory damages per violation — timeclock vendors and their hotel customers are primary targets, and Texas and Washington have parallel biometric statutes.
• Incident reports, log entries, and end-of-shift paperwork are written on the clock.Why: required reporting is part of the principal activity — "finish your report after you punch out" is an off-the-clock instruction.

Breaks#

• California: solo-coverage shifts (one engineer or one guard for the building) use valid on-duty meal agreements — written, employee-revocable, meal paid — or relief coverage is rostered instead.Why: IWC Wage Order 5 §11 permits on-duty meals only where the nature of the work prevents relief, and the agreement's formalities are mandatory.
• California: rest breaks are duty-free — no radio monitoring, no remaining on call.Why: Augustus v. ABM Security (2016) decided exactly this for security guards: an on-call rest break is no rest break, at one premium hour per day.
• Interrupted meals — a radio call mid-break — restart the break or trigger pay (and the premium where state law provides one).Why: an unpaid meal requires complete relief from duty (29 CFR 785.19); a meal cut short by a call was a paid working meal.

Contractors#

• Long-term on-site "contractors" — the handyman who works five days a week under the chief's direction — are reality-tested against the economic-reality factors, not grandfathered.Why: DOL enforces the pre-2024 framework (FAB 2025-1) and a replacement rule is pending, but private misclassification claims never paused; see independent contractors.
• California: engineers or guards supplied by a labor contractor trigger Labor Code §2810.3 shared liability for their wages, managed through records access and monitoring.Why: §2810.3 attaches by statute to client employers using contracted labor in the usual course of business.
• Contract security firms are joint-employment audited — who sets posts, schedules, and training — and the hotel verifies the firm pays overtime correctly for guards rotating across the firm's client sites in the same week.Why: joint employers share liability and the 40-hour workweek (29 CFR part 791); the guard's fourth site of the week is everyone's overtime problem.
• State/local: where panic-button ordinances apply (Los Angeles, Santa Monica, West Hollywood, Glendale, Seattle, Chicago; statewide Washington, New Jersey, Illinois), device testing and repair is an assigned, logged engineering PM task.Why: these laws require functioning devices — New Jersey alone fines $5,000 per first violation — and engineering's maintenance logs are the hotel's compliance proof.

Scope notes#

Unflagged items state the federal baseline; bold-flagged items apply only in the named jurisdictions, and exempt-salary floors, break premiums, and biometric statutes vary by state — confirm each property on its state page. For the underlying law, see off-the-clock work, exemptions, meal & rest breaks, and recordkeeping. Educational tool, not legal advice — see the disclaimer.