How to put overnight shifts in your calendar

A shift can start on one day and finish on the next. If you enter only two clock times without checking the dates, a calendar entry can land on the wrong day or have the wrong length. Use a timed event with a start date and an end date.

Give each endpoint its own date

These fictional examples assume ordinary dates with no daylight-saving clock change:

Do not enter Friday 22:00 to Friday 06:00. Do not use an all-day event to represent a timed shift. A weekly grid may place the entire overnight shift under its start day; confirm that convention with your workplace rather than guessing.

The same care applies to a shift ending at midnight. Confirm whether “midnight Friday” means the start of Friday or the end of Friday. In 24-hour notation, Saturday 00:00 is the beginning of Saturday. If the roster says “24:00,” clarify the intended date and record the next day's 00:00 when appropriate.

Check the workplace's time zone

Use the time zone where the job happens. If you travel, the calendar may display the same event using a different local clock time. That does not automatically mean the exported event is wrong. Inspect the event details and compare the display with the workplace's time zone before editing.

Apple documents both event time zones and a Time Zone Override display setting on iPhone. The display setting is separate from the underlying shift dates you confirm. Apple's time-zone guide.

Watch for daylight-saving transitions

On a night when clocks move forward, a local time can be skipped. On a night when clocks move backward, a local time can occur twice. An entry such as “01:30” may therefore need clarification about which occurrence your workplace means. Confirm with your manager rather than silently choosing one.

The number of clock hours between the displayed endpoints can differ from elapsed time on those nights. Your calendar is a planning aid; do not use this guide or an event duration to determine pay, paid breaks or overtime.

Shiftpup's web-beta specification requires ambiguous or nonexistent local times to be rejected for correction rather than guessed. If an export cannot resolve the time, confirm it and enter the event through a calendar path that lets you verify the intended instant. Do not shift a start time just to make an error disappear.

Review after importing

Check the full start date, full end date and clock times in the calendar event. Navigate across the month or year boundary when necessary. Some calendar views display an overnight event across both days; inspect the event details rather than relying only on its visual position.

Keep the source until you have checked the week. If an overnight shift is revised later, edit the affected event after comparing the new source; adding a second weekly file can create duplicates. See the revised-schedule checklist.

Try Shiftpup's free schedule tool to prepare editable shifts and a reviewed calendar file. Check both dates before exporting. Your shifts. Off your mind.