Split-shift calendar: keep two work periods and the gap separate
A split shift has two separate scheduled periods. Representing the whole span as one event can hide a genuine gap; representing only the two work blocks can hide travel commitments. Keep each kind of time explicit.
Worked example to check against your calendar
| Quantity | Calculation | Result |
|---|---|---|
| Two scheduled periods | 4 + 4 | 8 hours |
| Overall span | 06:00 to 19:30 | 13.5 hours |
| Middle gap | 10:00 to 15:30 | 5.5 hours |
| Gap after the example buffers | 10:30 to 15:00 | 4.5 hours |
Calculate the intervals before choosing busy status
Take a hypothetical roster on 2 November 2026: 06:00–10:00 and 15:30–19:30 in one unchanged time zone. The two periods total eight planned hours. The overall first-start-to-last-end span is 13.5 hours, and the gap between periods is 5.5 hours.
Those numbers describe calendar intervals only. They do not establish compensation, breaks required by law or time actually worked. Likewise, an app’s export or report may use different fields; do not assume it calculates payroll from visible event bars.
Create two records with a shared identifier
Use titles such as Roster 42: morning and Roster 42: afternoon, so a future change can be matched to the same approved shift. Give each record its exact start and end. If your editor offers free/busy controls, choose them according to your real scheduling constraints and verify what a colleague or booking tool actually sees.
When the two periods change independently, edit the affected record rather than expanding one continuous event across the gap. If a repeated shift has an exception, check both halves on that date so an old afternoon block is not left behind.
Add only real buffer commitments
Suppose you separately plan travel from 10:00–10:30 and 15:00–15:30. Those buffers occupy one hour of the 5.5-hour gap, leaving a 4.5-hour interval from 10:30 to 15:00. That is a calculation for this example, not a recommendation that the remaining time is suitable for a particular activity.
A decorative all-day roster label can help identification, but keep it separate from the timed blocks. Before sharing, compare the day’s occupied intervals with the actual roster and avoid exposing unnecessary workplace details.
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
- Create two exact timed records, not one full-span block.
- Use a common roster reference in both titles.
- Record travel or other commitments separately if they apply.
- Inspect both halves after a change and check actual free/busy output.
Questions
- Is the middle gap automatically free?
- No. Travel or other commitments may occupy it, and availability depends on your actual constraints.
- Does eight scheduled hours mean eight paid hours?
- No. The calendar example measures planned intervals, not payroll or legal entitlements.