Team - Timezone Coverage.

Best for: Proving in a vendor review that someone is on during the buyer's working hours, negotiating support SLAs and the scope of after-hours incident response, reporting the handoff window and the unstaffed stretch of a remote or distributed organisation, and deciding whether to add a site or add a shift

Use: Use it when the question is not who is on the team but when they are on. A shared 24-hour axis carries each site's shift, so the staffed hours and the stretch with nobody on are legible as length without a sentence of explanation. Teams are separated by the label column instead of a colour key, which keeps four sites readable across all 41 themes, and only the overlap window becomes an accent band through every row, so the overlap reads as a property of the hour. A shift that runs past midnight splits into two pieces at either end of the axis. It fits support SLA negotiations in vendor reviews, explanations of after-hours incident coverage, and operating reports for distributed teams.

Avoid: Use company-global for the size of each site in revenue or headcount and visual-map-locations for pins on a map showing where you operate. Use timeline-parallel-tracks when the axis is a project calendar rather than a day, team-staffing-allocation when individual utilisation is measured on a 0 to 100% axis, team-expertise-matrix for who holds which skills, and process-escalation-path for who an incident passes to by severity. Past five teams the bars crowd the 24-hour axis until the labels collide, so group them down to four or fewer. Skip this slide when no reference timezone has been agreed, or when the roster varies so much week to week that no single day represents it. Coverage fixed on a slide reads as a commitment, so do not paint an hour you cannot staff.