A 22:00–06:00 shift must belong to the correct work date and feed approved overtime or attendance outcomes downstream.
Shift-based workforce operations
Handle midnight shifts without breaking attendance, overtime or payroll context.
Configure work-date handling, rotating rosters, breaks, overtime windows and comp-off for shifts that cross midnight.
Representative operating scenario Current boundaries stated clearly
Policy resolverIllustrative · effective-dated
Assign a rotating midnight roster without losing the correct attendance work date.
Resolved outcome
Pattern assigned
Operations Group B · October
Individual override availableNight shift resolved
22:00–06:00 belongs to start date
Payroll input remains alignedSwap request routed
Employee → Manager
Roster history retainedPaid break applied
Included in scheduled hours
Thresholds can vary by shiftWho this page is for
For manufacturing, healthcare, logistics, hospitality and other businesses with night and rotational shifts.
The operating problem
What usually breaks before the software conversation begins.
Use these symptoms to determine whether the issue is data, policy, ownership, monthly closure or an unsupported product requirement.
01
Punches are split across two calendar days.
02
Night-shift attendance is corrected manually.
03
Overtime and comp-off are calculated outside the HRMS.
04
Roster changes do not reach employees or payroll owners in time.
A practical operating approach
Resolve the policy first, then automate the cycle.
The exact product setup is validated during discovery and demonstration. The sequence below keeps the rule, owner and downstream result connected.
Define the shift
Set start, end, break and work-date behaviour for midnight-crossing shifts.
Assign the roster
Use fixed, flexible or rotational patterns with approved individual overrides.
Resolve attendance and overtime
Evaluate punches, thresholds and eligible pre- or post-shift time.
Feed approved outcomes
Move accepted attendance, overtime or comp-off into the connected monthly process.
Connected product scope
View the full product The outcome depends on more than one isolated feature.
Review the upstream source, policy resolver, approval path and downstream output together.
Shifts & Rosters
Create shift patterns, publish rosters, manage changes and connect planned schedules to attendance, overtime and payroll.
ExploreTime & Attendance
Apply configurable rules to punches, shifts and work patterns, explain why each day resolved as it did, and close exceptions before they become payroll corrections.
ExploreTimesheets & Overtime
Collect timesheets, overtime and compensatory-off requests, route them through policy-led approvals and pass approved values into payroll, project or reporting workflows.
ExplorePayroll
Connect effective-dated salary structures, attendance and leave inputs, earnings, deductions, reimbursements, recoveries and statutory calculations in a payroll run that can be reviewed and rolled back before finalisation.
Explore
Evaluation questions
Bring this use case into a demo Confirm the exact policy, evidence and product boundary.
The answers below reflect the supplied product source. Customer-specific commitments still require live-product and commercial validation.
Can duoHR handle shifts that cross midnight?
The product material explicitly includes midnight-crossing shifts and work-date handling.
Can overtime become comp-off?
Yes. Documented treatment includes paid overtime or conversion into comp-off with expiry, flowing into Leave.
Is overtime rounding a separate configurable layer?
No. The documented current scope says a separate overtime-rounding layer is not available.
Shift-based workforce operations
Validate this use case with one real policy or transaction.
Bring a representative employee, location, shift, payroll month or output. We will shape the walkthrough around the exact operating case.