Clopen When Scheduling
New York City
Warns when the gap to the prior shift is under 11 hours at an org meeting NYC's 20-employee gate, clears once it's long enough
Scheduling a shift starting only 7 hours after the prior one ends triggers a warning.
Moving the start time to 11+ hours after the prior shift clears the warning.
Doesn't warn for the same tight gap when the org is under NYC's 20-employee coverage gate
Scheduling the same 7-hour-gap shift shows no clopen warning — this org is under NYC's 20-employee gate.
Oregon
Warns when the gap to the prior shift is under 10 hours at an org meeting Oregon's statewide 500-employee gate, clears once it's long enough
Scheduling a shift starting only 7 hours after the prior one ends triggers a warning.
Moving the start time to 10+ hours after the prior shift clears the warning.
Seattle
Warns when the gap to the prior shift is under 10 hours at an org meeting Seattle's 500-employee gate
Scheduling a shift starting only 7 hours after the prior one ends triggers a warning.

Philadelphia
Warns when the gap to the prior shift is under 9 hours at an org meeting Philadelphia's 250-employee-AND-30-location gate, clears once it's long enough
Scheduling a shift starting only 7 hours after the prior one ends triggers a warning.
Moving the start time to 9+ hours after the prior shift clears the warning.
Doesn't warn for the same tight gap when the org is under Philadelphia's employee-AND-location coverage gate
Scheduling the same 7-hour-gap shift shows no clopen warning — this org is under Philadelphia's coverage threshold.
The District of Columbia
Warns when the gap to the prior shift is under 10 hours at an org meeting D.C.'s 50-employee gate, clears once it's long enough
Scheduling a shift starting only 7 hours after the prior one ends triggers a warning.
Moving the start time to 10+ hours after the prior shift clears the warning.
Chicago
Warns when the gap to the prior shift is under 10 hours at an org meeting Chicago's 100-employee gate, clears once it's long enough
Scheduling a shift starting only 7 hours after the prior one ends triggers a warning.
Moving the start time to 10+ hours after the prior shift clears the warning.
Los Angeles
Warns when the gap to the prior shift is under 10 hours at an org meeting LA's 300-employee gate, clears once it's long enough
Scheduling a shift starting only 7 hours after the prior one ends triggers a warning.
Moving the start time to 10+ hours after the prior shift clears the warning.
Los Angeles County (unincorporated)
Warns when the gap to the prior shift is under 10 hours at an org meeting LA County's 300-employee gate, clears once it's long enough
Scheduling a shift starting only 7 hours after the prior one ends triggers a warning — East Los Angeles is matched by name as an unincorporated LA County community, not as the city of Los Angeles.
Moving the start time to 10+ hours after the prior shift clears the warning.
Berkeley
Warns when the gap to the prior shift is under 11 hours at an org meeting Berkeley's 10-employee gate, clears once it's long enough
Scheduling a shift starting only 7 hours after the prior one ends triggers a warning.
Moving the start time to 11+ hours after the prior shift clears the warning.
Emeryville
Warns when the gap to the prior shift is under 11 hours at an org meeting Emeryville's 56-employee gate, clears once it's long enough
Scheduling a shift starting only 7 hours after the prior one ends triggers a warning.
Moving the start time to 11+ hours after the prior shift clears the warning.