Overnight shift calendar: put the end on the next date
An overnight shift is one timed interval across two dates. If you start Monday evening and finish Tuesday morning, both dates belong in the event details. A roster’s label is not a substitute for those endpoints.
Worked example to check against your calendar
| Record | Start | End |
|---|---|---|
| Correct timed shift | 2 November 2026, 19:00 | 3 November 2026, 07:00 |
| Incorrect same-date endpoint | 2 November, 19:00 | 2 November, 07:00 |
| All-day context label | Date-based | Does not express exact working hours |
Write the two endpoints before creating the event
Suppose the approved shift is Monday 2 November 2026, 19:00, to Tuesday 3 November, 07:00, in America/New_York. This particular interval is 12 elapsed hours. Using 07:00 on Monday as the end would place the endpoint before the start.
Give the event a label that makes its convention clear, such as Monday night: 19:00–Tuesday 07:00. A workplace might call it Tuesday’s shift; keep that reference in the title or notes while preserving the actual start date.
Check details rather than the month-grid shape
A calendar can draw a cross-midnight event differently in month, week or agenda views. Open the saved event and verify its dates, times and zone. A short bar or a split visual segment does not by itself prove the stored interval is wrong.
An all-day event is a date-based item, not an exact night-shift block. A label covering Monday and Tuesday can provide context, but it cannot replace a 19:00–07:00 timed record when someone needs to know which hours are occupied.
Repeat the start pattern and audit transitions
In iCalendar, DTSTART identifies a recurring series’ first start; any BYDAY selection refers to occurrence starts. A Sunday-night start therefore belongs to Sunday even when most of its hours fall on Monday. The standard allows DTEND or DURATION; DTEND is not mandatory for every timed event.
For repeated shifts, inspect the first occurrence after midnight and the next daylight-saving weekend. The same displayed start and end hours can represent seven, eight, nine or other elapsed lengths depending on the actual interval and zone rules. Use the approved endpoints rather than silently compensating an hour.
What it looks like
Cloud Calendars overview, using our product images. Provider settings and protocol examples described in this guide are separate from the screens shown here.
What to do
- Write both dates, both times and the location’s time zone.
- Save a single occurrence before repeating it.
- Reopen it in event details and verify the following-date end.
- Check one cross-midnight repeat and any clock-change occurrence.
Questions
- Should the event be split into two?
- One continuous interval can cross midnight. Split it only when the underlying schedule actually has separate periods or your workflow requires separate records.
- Does an off day mean no shift appears on that date?
- Not always: the previous night’s event can end that morning.