24/7 Global Coverage Calculator
Determine the minimum staffing per location needed to maintain uninterrupted 24/7 operations, factoring in shift length and handoff overlap. Use it when planning a global support, security, or NOC team that must always have someone awake and on duty.
Last updated: September 2026
Formula below · 3 sources (CDC, atlassian.com, shrm.org) · Updated Sep 2026
Compare with similar
About this calculator
The calculator returns the minimum people each location needs: peoplePerLocation = ceil(shiftsPerDay × shiftLength × 7 / 40), where shiftsPerDay = ceil((24 / timeZones + overlapHours) / shiftLength). Each location covers its share of the day (24 / timeZones hours, e.g. 8 hours for 3 locations) plus the handoff overlap, which is filled with whole shifts; those shift-hours are needed 7 days a week, and one full-time person works about 40 hours a week. Multiply by the number of locations and compare with your total team size to see whether the plan is staffed. The formula assumes 100% utilization, no PTO, no sick days, and no surge - realistic capacity planning multiplies the result by 1.25-1.4 to cover vacation, sickness, training, and attrition. It does not model on-call escalation, where a single primary handles the bulk of incidents and a secondary is paged only on miss - that pattern can run leaner than full active coverage. It also assumes one person on duty per shift; multiply by the number of people needed on each shift for larger desks. In practice, time-zone gaps often force one location into 12-hour rather than 8-hour shifts.
How to use
Example 1 - 3 locations (Americas, EMEA, APAC), 8-hour shifts, 2 hours of handoff overlap. Each location covers 24 / 3 + 2 = 10 hours a day, which takes ceil(10 / 8) = 2 shifts. Weekly hours = 2 × 8 × 7 = 112, and 112 / 40 = 2.8, so 3 people per location (9 in total) with one person on duty. A 12-person team covers this with 3 spare people for leave. Example 2 - 2 locations (follow-the-sun), 12-hour shifts, 2 hours of overlap. Each location covers 12 + 2 = 14 hours, which takes ceil(14 / 12) = 2 shifts. Weekly hours = 2 × 12 × 7 = 168, and 168 / 40 = 4.2, so 5 people per location (10 in total), before adding the usual 25-40% for PTO and sickness.
Frequently asked questions
Why does the calculator tell me I need more people per location than I have in total?
That outcome is a useful diagnostic: it means your planned headcount is insufficient for 24/7 coverage with the inputs given. Either total team size is too small, shift length is too short (more shifts = more headcount), location count is wrong, or handoff overlap is too generous. Try increasing shift length from 8 to 12 hours (halves the number of shifts needed per day), reducing locations from 3 to 2 (each location now covers more of the day), or trimming overlap. If none of those changes are acceptable, the honest answer is that you need to hire more people or accept that you cannot run true 24/7 with the current team. Many organizations confronting this math fall back to follow-the-sun with extended business hours plus on-call escalation outside those hours - a much leaner staffing model than continuous active coverage.
What is a realistic PTO and sick-leave buffer to add to the calculator output?
Real-world staffing for 24/7 operations typically multiplies the bare coverage number by 1.25-1.4 to absorb vacation (4-5 weeks/year in EU, 2-3 in US), sick leave (averaging ~5 days/year), training time, parental leave, and unplanned attrition. Highly regulated industries (nuclear, healthcare, aviation) use 1.5-1.8x because mandatory rest periods and certification training take additional time off the line. The calculator returns the minimum - never staff at exactly that number, or you will be forced to deny PTO requests or run shifts uncovered. A practical rule: take the calculator's per-location result, multiply by 1.35, and round up. If the math then exceeds available budget, the next step is structural - convert continuous coverage to follow-the-sun-plus-on-call, or accept reduced coverage hours rather than running unsustainably thin.
When is a 2-location follow-the-sun pattern better than 3-location 8-hour shifts?
Two-location follow-the-sun with 12-hour shifts works well when your team total is below ~30 and you need at least 80% of the day covered actively. It halves the management overhead of running three separate site teams and avoids the brutal night shift in any one geography. Three-location 8-hour-shift coverage becomes worth it above ~50 total headcount, when shift length matters more than location count for fatigue and quality (research shows error rates climb significantly past 10 hours on shift). The asymmetry of time zones matters too: there is no single Asia-Pacific population center 8 hours offset from US East Coast, so 3-shift coverage often forces unnatural location choices (Manila is +12 from NY, not +8). Many global teams compromise with 2 location-anchored shifts plus a small follow-the-sun on-call rotation for handoff windows.
What are common mistakes when planning 24/7 coverage?
The most common mistake is staffing exactly to the calculator's bare-coverage number, which leaves no slack for vacation, sickness, or attrition and creates burnout pressure within months. Another frequent error is ignoring shift fatigue: 12-hour shifts are widely used but research shows alertness and accuracy drop significantly after 9-10 hours, so safety-critical roles (medical, aviation, nuclear) cap at 8 hours for good reason. Teams often underestimate handoff time too - a real handoff for complex operational state takes 30-45 minutes, not the 15 minutes typically planned, leading to silent rushed transitions and missed context. Mixing geographic and follow-the-sun shifts without explicit handoff documentation produces a knowledge-loss tax that compounds over months. Finally, ignoring weekend and holiday differences (different holidays in different regions; weekends are days 1-2, 5-6, or 6-7 depending on locale) leads to overstaffing some weeks and gaps in others.
When should I NOT use a 24/7 coverage calculator?
Skip it if your actual requirement is response not coverage - most non-customer-facing operations only need active staff during business hours and an on-call rotation for after-hours alerts. On-call models can run 70-90% leaner than continuous staffing and are appropriate when off-hours volume is low and predictable. The calculator is also wrong for highly variable workloads (security incident response, trading desks during market hours) where peak-load staffing matters more than steady-state coverage; queue theory models like Erlang-C are better suited. Do not use it for short-term projects (launch weekend, migration window) where temporary 24/7 is needed for under a month - in that case, paid overtime and contractor coverage are usually cheaper than re-staffing. Finally, it is not useful for fully automated systems with human oversight only on exception - that is monitoring, not coverage, and the math is completely different.