What Is an Overnight Shift Wrap-Around in Scheduling?

An overnight shift wrap-around is how a scheduler interprets a shift whose end time is earlier in the clock than its start time, recognizing that it crosses midnight rather than treating it as a negative span. The duration becomes the time from the start to midnight plus the time from midnight to the end, and the shift's finish is understood as falling on the following calendar day. The hours are attributed to the day the shift started. Handled badly this produces zero or negative capacity for an entire crew, which is why it is worth understanding rather than assuming. EDGEBIC by User Solutions applies the same convention in capacity math and in reporting.

How it works

A shift is stored as a start time and an end time per weekday. For a day shift these are in the obvious order and the duration is a straightforward subtraction. For a night shift they are not.

The comparison detects the wrap. When the end time is at or before the start time, the shift is understood to cross midnight. Ten at night to six in the morning is not a minus sixteen hour shift; it is eight hours spanning two dates.

The duration is computed in two pieces. The time from the start to midnight, plus the time from midnight to the end. Ten at night gives two hours to midnight; six in the morning gives six hours after it; the shift is eight hours long.

The finishing moment moves to the next day. For any date the shift runs on, its start is that date at the start time and its end is the following date at the end time. This matters for every calculation that asks whether a moment falls inside the shift, because without the day advance every instant after midnight would appear to be outside it.

The hours belong to the starting day. This is the convention that everything downstream follows. A shift beginning Tuesday night books its full length against Tuesday, including the portion that physically occurs on Wednesday. Capacity figures, daily hour breakdowns, and reports all read the same way, so a day's capacity is the sum of the shifts that began on it.

That last rule is a choice rather than a necessity, and it is the right one because it matches how plants already talk. Nobody describes the Tuesday night crew as working half of Tuesday and half of Wednesday. They work Tuesday night. Attributing the hours to Tuesday keeps the schedule speaking the same language as the roster and the crew.

A concrete example

A machining center runs two shifts. Days run 06:00 to 14:00 and nights run 22:00 to 06:00, both configured Monday through Friday.

Tuesday's capacity is the sum of the shifts that begin on Tuesday. The day shift contributes eight hours from Tuesday 06:00 to 14:00. The night shift contributes eight hours from Tuesday 22:00 to Wednesday 06:00. Tuesday's total is sixteen hours, four of which are physically worked on Wednesday morning.

An operation scheduled into Tuesday's night shift shows a start of Tuesday 22:00 and an end of Wednesday 06:00, spanning two dates on the board exactly as it does in reality. Its hours appear against Tuesday in the daily breakdown.

Now close Wednesday for a plant holiday. Wednesday's day shift and Wednesday's night shift both disappear. Tuesday night's shift is untouched, so the crew still works from Tuesday 22:00 through Wednesday 06:00 and the plant is genuinely quiet from six on Wednesday morning. If the intention was to have nobody in the building on Wednesday at all, the closure needed to include Tuesday, because Tuesday is the day that owns the shift that runs into Wednesday morning.

The same logic explains a configuration mistake people make once. A shift meant to cover Sunday night into Monday morning must be enabled on Sunday. Enabling it Monday to Friday gives you a shift that starts Monday night and runs into Tuesday, and leaves Sunday night with no coverage at all.

How EDGEBIC uses it

The wrap-around is applied wherever a shift's span is needed: computing the day's capacity, deciding whether a proposed start falls inside a shift, and working out how many hours remain from a given moment. Setting one up is covered in how to set up an overnight shift in EDGEBIC, and the scheduling consequences are worked through in how a schedule handles a shift that crosses midnight.

The wrapped span is one input to the capacity a day actually offers, which also subtracts downtime and any partial closure before applying machine counts and utilization. That chain is covered in what is a work center shift and in how EDGEBIC resolves capacity day by day.

Because an overnight shift already spans two dates, a long operation placed in one frequently spills into the next available shift as well, which is the ordinary behavior described in what is a cross-shift operation in scheduling. And because closures act on the day a shift starts, the interaction with the calendar is worth reading alongside what is a plant holiday in scheduling and what is holiday scope in scheduling calendars.

The takeaway

An overnight shift wrap-around is two rules held together: the duration spans midnight, and the hours belong to the day the shift began. Almost every question a night-shift plant asks about its schedule resolves against one of those. Capacity that appears on the wrong date is usually the second rule working correctly; a shift with no capacity at all is usually the weekday configuration rather than the times, because a shift covering Sunday night must be enabled on Sunday. Configure to the day the crew clocks in, and the rest follows. For the wider vocabulary see the manufacturing glossary, and for the product itself see EDGEBIC.