Key takeaways

  • Store the complete start and finish date-time as one shift.
  • Separate real timestamps from the day used for payroll grouping.
  • Keep breaks and pay segments visible.
  • Review workweek, month and daylight-saving boundaries.

1. Keep the overnight shift as one interval

Store start date, start time, finish date and finish time together. If the selected finish time appears earlier than the start, the interface should offer the next calendar day instead of silently rejecting or shortening the shift.

Artificially clocking out at 23:59 and back in at 00:00 can separate breaks, notes and automation events. Split the record only when the work itself contains distinct shifts or a verified payroll process genuinely requires separate entries.

2. Decide which day displays the shift

The underlying record should always retain both timestamps. A calendar can then group the shift by start day, finish day or the day containing most of the duration. Changing the display rule must not rewrite the actual event.

If payroll assigns night work to a particular business day, save that as a workplace reporting preference. You can then compare like with like while retaining the original evidence.

3. Separate breaks and premium windows

Record an unpaid break explicitly and subtract it from working time. When several breaks exist, keeping their actual times can help explain which pay window they affected.

Night, weekend, public-holiday and overtime premiums may overlap inside one shift. Keep the raw interval intact and let the calculation divide it into rule-based segments. That creates a clearer audit trail than editing the original timestamps to force a desired total.

4. Handle workweek and month boundaries

A Sunday-night shift can touch two workweeks, and a shift on the final night of a month can touch two payroll periods. The applicable method determines how those hours are allocated.

A report should name the allocation rule rather than silently placing the whole shift in the start period. Otherwise the total duration may look right while weekly overtime or monthly payroll comparisons remain wrong.

5. Preserve time zone and daylight-saving context

In places that change clocks, an overnight shift can contain a repeated or missing local hour. Store a real timestamp and time-zone context so the duration is not based only on what the clock face shows.

Travelling workers and manually changed device clocks introduce similar ambiguity. Flag a time-zone change for review instead of silently adjusting the record after it has been saved.

6. Use the record to spot unusual patterns

NIOSH notes that nonstandard schedules and extended hours can contribute to work-related fatigue, which can affect attention and judgment. A time tracker is not a medical or safety decision-maker, but it can make unusually long and repeated shifts easier to notice.

HourTally preserves overnight intervals, breaks and workplace-specific rules. Warnings for an unusually long or unfinished shift help prevent one forgotten clock-out from corrupting an entire period.

FREQUENTLY ASKED

Questions you may still have

How long is a 22:00–06:00 shift?+

The elapsed interval is eight hours before subtracting any break that is not treated as working time.

Which date should an overnight shift use?+

Keep both timestamps. The calendar or payroll grouping can use a separate workplace rule without changing the original record.

What happens when clocks change overnight?+

A reliable system preserves the time zone or offset so duration is not calculated only from the displayed local times.

PRIMARY SOURCES

Sources and further reading