How a Schedule Handles a Shift That Crosses Midnight

A shift that crosses midnight, such as a night shift running 20:00 to 04:00, spans two calendar dates, and EDGEBIC by User Solutions handles it by recognizing that a shift whose end time is earlier on the clock than its start time ends on the following day. The engine computes the shift's true end datetime accordingly, places work continuously across the midnight boundary, and attributes each hour to the date it actually occurs on. The result is that round-the-clock operations schedule naturally, without work being severed at 00:00 or a short night job appearing to take a whole day.

Most shifts sit inside one calendar day: 08:00 to 16:00, start before end, no ambiguity. Night shifts break that assumption. A shift that starts at 20:00 and ends at 04:00 has an end clock time that is numerically earlier than its start. Read naively, that is a negative-length shift. Read correctly, it is an eight-hour block that happens to straddle midnight. Getting this right is what lets a night operation behave like any other.

Recognizing a shift that wraps

A shift is defined by a start time of day and an end time of day. EDGEBIC compares them. When the end is later than the start, the shift is an ordinary same-day block. When the end is earlier than or equal to the start, the shift is understood to end on the next calendar day.

So a shift defined 20:00 to 04:00 resolves to a true window from 20:00 on its date to 04:00 the following morning, which is eight hours. A shift defined 16:00 to 00:00 resolves to 16:00 through midnight, also treated as ending on the following date, eight hours again. The engine builds the shift's real end datetime from that rule, so every downstream calculation, available hours, where an operation lands, when it finishes, works from a correct window rather than a broken one.

This is the same shift-capacity machinery described in how capacity is computed for a work center, shift, and day. The midnight-crossing rule simply ensures the shift's length and boundaries are right before that formula runs.

Placing work across the boundary

Once the shift's true window is known, the multi-shift allocator treats it like any other slot. An operation placed on the night shift can begin at any point in the window and run forward. If it starts at 22:00 and needs four hours, it runs to 02:00 the next morning, straight through midnight. The operation does not stop and restart at 00:00; midnight is not a boundary the work cares about, only one the calendar cares about.

What does change at midnight is which date the hours belong to. The two hours from 22:00 to 00:00 fall on the first date, and the two from 00:00 to 02:00 fall on the second. EDGEBIC attributes each hour to the date it actually occurs on, so a per-day load report shows two hours on each of the two dates, summing to the correct four. The operation is continuous; the accounting is split. Both are true at once, and both need to be, because the floor experiences one continuous run while a daily capacity report needs honest per-date totals.

A worked example: a night-shift job through midnight

Take a work center with a night shift defined 20:00 to 04:00, a true eight-hour window from 20:00 to 04:00 next morning. A job needs six hours and cannot start before 22:00.

The 22:00 constraint clips the first two hours of the window, so from 22:00 the shift offers six usable hours to 04:00. The operation places all six:

The job started Monday 22:00 and finished Tuesday 04:00. The job row shows a Monday-to-Tuesday span, which is correct: the operation was six continuous hours, but the calendar boundary fell in the middle. A planner glancing at the two dates should read "ran across midnight," not "took most of a day."

Now extend it. Suppose the job needed ten hours instead of six. Eight fit in the night shift's window (22:00 to 04:00 is only six after the clip, so it fills those six and needs four more). If a day shift begins at 06:00, the remaining four hours flow into it, so the job runs 22:00 Monday to 04:00 Tuesday on nights, then 06:00 to 08:00 Tuesday on days. The midnight crossing did not interrupt anything; the operation simply flowed across each shift boundary in turn, the night-shift one of which happened to contain midnight.

Why this matters for round-the-clock shops

For a single day-shift operation, none of this ever comes up. It matters the moment a shop runs nights or a full three-shift pattern. Without the wrap rule, a night shift would be mis-measured, work near midnight would be severed, and every night job would carry confusing dates. With it, a night shift is just another eight-hour slot that happens to straddle a date line, and a job can start one evening and finish the next morning as smoothly as any daytime job finishes in the afternoon.

The two things to keep straight are the operation and the accounting. The operation is continuous and does not care about midnight. The accounting attributes hours to real dates, so daily reports stay correct. EDGEBIC keeps both true, which is why a night-shift schedule reads sensibly rather than looking like a string of one-day jobs that all somehow finish at dawn.

For the wider mechanics, the complete scheduling engine guide shows how shift windows feed the allocator, and finite versus infinite capacity scheduling covers why an accurate shift window is the foundation of an honest plan. To see how your own night and rotating shifts place work across the day boundary, explore the EDGEBIC engine or bring your data to a demo.