Overnight Shift Hours: Which Day Do They Count On?

Overnight shift hours belong to the day the shift started. Under the federal FLSA there is no daily overtime, so midnight changes nothing; in the states that pay overtime by the day, splitting one shift across two calendar days can erase overtime the employee earned.

Kloqk counts a night shift as one shift on the day it began, and lets a business with a legal reason to split at midnight switch that on instead.

That is the short answer. The long one matters because a 10-hour shift that runs 10 p.m. to 8 a.m. looks like two ordinary days on a timesheet that cuts at midnight (2 hours, then 8 hours), and looks like what it is on a timesheet that doesn't (10 hours, 2 of them overtime in California). Same punches, different paycheck. This article covers what the law says a "workday" is, which states care, what the popular time clocks do by default, and how we decided to handle it after a customer's night crew showed us the problem.

TL;DR

• Federal overtime is weekly only. The FLSA defines a fixed 168-hour workweek that may begin at any hour of any day, and it never mentions midnight. 29 CFR 778.105, 778.102.
• California, Alaska, Nevada and Colorado pay overtime by the day. In those states the day boundary decides whether a night shift earns overtime at all.
• A "workday" is any consecutive 24 hours starting at the same time each day, and the employer picks the start time. California says so in Labor Code 500. Nevada goes further: the workday "begins when the employee begins work" (NRS 608.0126).
• Time clocks disagree with each other. Buddy Punch credits the clock-in day by default; When I Work, Jibble and Redcort split at midnight by default; Connecteam, QuickBooks Time and Deputy make you pick.
• Kloqk treats a clock-in to clock-out as one shift, on the day it started, up to 24 hours. Breaks belong to the shift, not the calendar date. A business that defines its workday at midnight can turn on a split instead.

Why is this a question at all?

Because 15% of American workers don't work days. The Bureau of Labor Statistics' Job Flexibilities and Work Schedules release for 2024-25 puts 85% of wage and salary workers on a regular daytime schedule, 5% on evenings and 3% on nights, with the rest on rotating or irregular hours. In leisure and hospitality the non-daytime share is 40%. Transportation and utilities, 25%. Wholesale and retail trade, 20%.

Those numbers have barely moved in twenty years. The same survey in May 2004 found almost 15% of full-time workers on an alternative shift, with protective service (security guards, correctional officers) at 50.6% and food preparation and serving at 40.4%.

So the overnight shift is not an edge case. It's a bar, a hotel front desk, a 24-hour gym, a security post, a bakery that starts at 2 a.m. And nearly every one of those businesses records hours on a timesheet that has one row per calendar date, which forces a decision nobody made on purpose: which row does 12:01 a.m. go in?

What does federal law say about a shift that crosses midnight?

Nothing about midnight, and that's the point. The FLSA overtime rules set one trigger: more than 40 hours in a workweek, paid at time and a half. 29 CFR 778.102 says the Act "does not generally require" overtime for hours past eight in a day. If the week's total is 38 hours, it doesn't matter how those hours were distributed across calendar dates.

The one federal boundary that does matter is the start of the workweek. 29 CFR 778.105 defines it as "a fixed and regularly recurring period of 168 hours, seven consecutive 24-hour periods," and says it "need not coincide with the calendar week but may begin on any day and at any hour of the day." Recordkeeping rules in 29 CFR 516.2 require you to write down the time of day and day of the week your workweek begins, plus hours worked each workday and the total for each workweek.

Two practical consequences:

1. If your workweek starts Sunday at 12:00 a.m. and a shift runs Saturday 10 p.m. to Sunday 6 a.m., the federal rule does split that shift: two hours in one workweek, six in the next. That's the only federal split, and you can avoid it by starting your workweek at an hour when nobody is on the clock (Sunday 6 a.m., say).
2. The FLSA already has a rule for hours that straddle a boundary. When an employer changes its workweek, 29 CFR 778.302 says overlapping hours are paid at whichever computation gives the employee more. The federal instinct, when a boundary cuts through a shift, is to resolve it in the employee's favor, not to let the calendar decide.

The federal definition of a "workday" comes from 29 CFR 790.6, and it is the span from the start of an employee's principal activity to its end, rest and lunch periods included. A workday is the shift. It is not a date.

Which states pay daily overtime, and how do they define the day?

Four states have a general daily overtime rule, and one has a narrow one. Each defines the workday a little differently, and the definition is where night shifts get decided.

State	Daily overtime trigger	How the workday is defined	What it means for a night shift
California	1.5x after 8 hours in a workday, 2x after 12 (Labor Code 510)	"Any consecutive 24-hour period commencing at the same time each calendar day" (Labor Code 500). The employer sets the start time and may set different workdays for different shifts (DLSE glossary).	If you never define a workday, each calendar day is one, and a shift across midnight is two workdays. Define the workday to start at, say, 6 p.m. and the whole night shift lands in one.
Alaska	1.5x after 8 hours in a day or 40 in a week (Alaska Wage and Hour FAQ)	Not spelled out on the state's FAQ page.	Same practical advice as California: define the workday in writing so the shift stays whole.
Nevada	1.5x after 8 hours in a workday for employees earning under 1.5x minimum wage (NRS 608.018)	"A period of 24 consecutive hours which begins when the employee begins work" (NRS 608.0126).	The day starts at clock-in by statute. A night shift is never split at midnight in Nevada.
Colorado	1.5x after 12 hours in a workday, 12 consecutive hours regardless of workday, or 40 in a week, whichever pays more (COMPS Order Rule 4.1.1)	"Any consecutive 24-hour period starting with the same hour each day and the same hour as the beginning of the workweek" (COMPS Rule 1).	The "12 consecutive hours" rule ignores the day boundary entirely, so a 13-hour overnight shift earns an hour of overtime however you slice the calendar.
Oregon	1.5x after 10 hours in a day, manufacturing only (ORS 652.020)	Follows the general workday definition.	Relevant to a plant running a night line; the same define-your-workday advice applies.

Nevada is the one to remember. Its legislature wrote the clock-in rule straight into the statute: the workday is 24 hours from the moment the employee starts. That is the cleanest statement anywhere in US law of the principle this article argues for, and it's the rule Kloqk follows everywhere unless a business turns on the split.

What does splitting at midnight actually cost an employee?

Take a line cook in California on a $20 per hour rate, working 10 p.m. to 8 a.m. with no break, four nights a week.

	Split at midnight	Whole shift on the clock-in day
Hours recorded on day 1	2	10
Hours recorded on day 2	8	0
Daily overtime per shift	0 hours	2 hours
Overtime premium per shift	$0	$20 (2 hours at the extra $10)
Per week (4 shifts)	$0	$80
Per year (50 weeks)	$0	$4,000

The split version shows two perfectly legal-looking days, 2 hours and 8 hours, neither over the threshold. The employee worked ten hours in a row. Under Labor Code 510 that is eight hours of straight time and two of overtime (the full California overtime rules are here), and a timesheet that says otherwise is a wage claim waiting for a lawyer. At $4,000 per year per cook, before penalties, the software default is not a small thing.

It cuts the other way too. Say the same cook works 10 p.m. to 6 a.m. on Monday night and picks up a 6-hour day shift Tuesday afternoon. Split at midnight, Tuesday shows 6 + 6 = 12 hours and the clock flags 4 hours of daily overtime that the law does not owe, because the two stretches were separate workdays once you define the day properly. A split doesn't just hide overtime. It invents it.

Does the day boundary change break and lunch rules?

Yes, and this is the version of the problem that first reached us. California requires a 30-minute meal break before the end of the fifth hour of work (Labor Code 512) and a paid 10-minute rest break per four hours. Those rules run on the shift, not the date. A timesheet that shows 2 hours on Monday and 6 hours on Tuesday reports two short stretches that never needed a meal break, when the person worked eight hours straight and was owed one.

The reverse happens as well. Take a 30-minute lunch at 12:15 a.m. on a shift that started at 6 p.m. Split at midnight, that break now sits in the "next day" row, attached to a two-hour stretch that didn't need one, and the six-hour stretch before midnight shows no break at all. Every compliance report built on those rows is wrong, and the punches were perfect. (The California lunch break rules are worth reading next to this.)

How do the popular time clocks handle overnight shifts?

We went through the help centers rather than the marketing pages, and only report what each page says. The pattern: some split by default, some don't, and several leave the decision to whoever set the account up on day one.

Time clock	Setting	Default	Source
Buddy Punch	"Split Shifts at Midnight" toggle; overnight hours go to the clock-in day unless it is on. Only affects future punches.	Clock-in day	Buddy Punch help
Connecteam	Checkbox: "Overnight shifts total hours will be assigned to the day the shift started." Their own example is a Sunday 10-hour shift paid as 8 regular and 2 overtime.	Not stated; the timesheet shows two rows until it's on	Connecteam help
QuickBooks Time	"Split timesheets at midnight" so hours after midnight count for the following day. Their time-of-day overtime rule depends on it being on.	Not stated	QuickBooks Time settings
Deputy	"Overnight shift allocation": split across two days, or allocate all hours to the first day.	Not stated	Deputy release note
When I Work	Hours are counted from the account's workday start time; daily totals split there. Changing it means contacting support.	Split at 12 a.m.	When I Work help
Jibble	Adjustable "end of workday" that splits timesheets.	Split at midnight	Jibble help
Redcort Virtual TimeClock	"Include hours worked past midnight with prior day" option.	Split at midnight	Redcort knowledge base

Read that table as an owner who just moved a bar's schedule from closing at 11 to closing at 2. Three of the seven tools would silently start splitting your closers' shifts, and the ones that ask you to choose asked during setup, months ago, when you had no night shifts to think about. The safest assumption is that your time clock is doing something, and you don't know what.

How does Kloqk handle a shift that crosses midnight?

A shift is one thing from clock-in to clock-out, and it belongs to the day it began. That's the rule, and everything else follows from it.

We didn't start there. Kloqk's timesheet used to be a grid of calendar dates, like everyone else's, and a shift that crossed midnight got cut in two. A customer with an overnight crew told us their break reports were nonsense: lunches showing up on the wrong day, attached to stretches of work that never needed one. Digging in, we found the owner had been entering every night shift by hand as two shifts, out at 11:59 p.m. and in at 12:00 a.m., because that was the only way the day-bound editor would take it. Every one of those hand-split shifts was quietly under-reporting overtime.

So we rebuilt the rule rather than patch the report. What Kloqk does now:

• One shift, one day. Clock in Sunday at 10 p.m., clock out Monday at 6 a.m., and the timesheet shows eight hours on Sunday, labelled as ending the next day. Breaks and lunches attach to that shift, so a 12:30 a.m. lunch is the Sunday shift's lunch. Overtime, daily and weekly, is computed from the shift.
• Clocked in until clocked out. There is no midnight cut-off and no fixed look-back window. A person on the clock at 12:01 a.m. is still on the clock, and the kiosk offers them Clock Out, not a fresh Clock In. If somebody forgets, a shift past 24 hours is flagged for a manager to fix rather than silently paid.
• The editor knows about tomorrow. When a manager adds or fixes a punch, each row carries a date as well as a time. Enter a clock-in at 10 p.m. and Kloqk assumes the clock-out is the next day, shows the real date next to it, and refuses a sequence that doesn't make sense (a clock-out before the clock-in, two clock-ins in a row) with a plain sentence about what's wrong.
• Split at midnight is a setting, not a default. Some businesses have defined their workday as midnight to midnight, in writing, and their payroll provider expects the split. Payroll settings has one switch: count overnight shifts whole on the day they started, or split them at local midnight. The punches are never changed. Kloqk never writes a fake 11:59 p.m. clock-out; the split, when you turn it on, happens in the arithmetic, so the record of what actually happened stays intact.
• Every report reads the same shift. The timesheet, the detailed and summary reports, the payroll estimate, the Paychex and CSV exports and the pay-history page all consume one calculation. They cannot disagree about which day a shift belongs to because none of them decides that on its own.

The default is whole-shift because it's the interpretation that is correct under federal law, correct in Nevada by statute, correct in California, Alaska and Colorado for any employer who has defined a workday that contains the shift, and the one that never erases overtime by accident. If you're in a daily-overtime state and you've never written down when your workday starts, do that this week: pick an hour when nobody is on the clock, put it in your handbook, and set Kloqk to match. The overtime calculator will show you what a night crew's week comes to under either rule.

What should an employer with night shifts do this week?

1. Define the workweek in writing. Day and hour. 29 CFR 516.2 requires it in your records anyway. Start it at an hour when nobody is working so no shift straddles the week.
2. Define the workday if your state pays daily overtime. California lets you set a different workday per shift; a 6 p.m. start for the night crew keeps every overnight shift whole. Change it only when you mean it to be permanent; the DLSE and the FLSA both say a change "designed to evade" overtime doesn't count.
3. Check what your time clock does today. Find the setting from the table above. If it's splitting and you didn't choose that, look at last month's timesheets for closers and night staff and count the days that show 2 or 3 hours.
4. Look at breaks by shift, not by date. If your meal-break report is built on calendar-day rows, it's reporting on stretches of work that don't exist.
5. Tell the crew which day their shift counts on. Employees checking their own hours will see one shift on Sunday, not two on Sunday and Monday, and they'll ask. A one-line note saves twenty conversations.

None of this needs a new system. Kloqk is free for one location with no cap on employees, and the overnight setting is on the same payroll settings page as your workweek start day. Turn on the time clock, set the two dates, and the night shift takes care of itself.