Put each office and its local hours on one clock. The planner shows the world at any minute of the UTC day, who is on watch and who is asleep, every seam in order with who is left and for how long, and what happens to all of it when the clocks change.
It is a projection of the hours you configure, not of shifts anyone worked. Whether someone was actually on watch at 03:00 on a Tuesday is measured from the rota as it ran — that part is what SOC Rotate does →
| Office | Now | Sunrise | Sunset | On watch |
|---|---|---|---|---|
| Singapore | 14:00 · daylight | 06:54 local · 22:54 UTC | 18:52 local · 10:52 UTC | 08:00–17:00 local · on now |
| London | 07:00 · dark | 07:22 local · 06:22 UTC | 18:16 local · 17:16 UTC | 09:00–18:00 local |
| New York | 02:00 · dark | 07:06 local · 11:06 UTC | 18:22 local · 22:22 UTC | 09:00–21:00 local |
A chain spans time zones, so there is no shared midnight to reason in. The product measures a client’s coverage the same way, and for the same reason.
This shows what the offices are meant to cover. SOC Rotate measures what they did cover, from the rota as it ran, and reports it per client against the hours they are owed.