You say bell schedules can be set at an OU level. The way you have defined OU level is, in my opinion, not well thought out . My "OUs" according to your definition are Google and Active Directory top level. We have our district broken out into buildings and grade levels, but they aren't considered an OU in your system despite being one in AD and Google's systems. I therefore cannot define schedules per building. You still have districts pigeonholed into poor schedule design. Admins still cannot make multiple schedules for each building while also selecting the same days for different schedules. You are locking out days when they are used in one schedule so they can't be replicated in a different schedule. I would understand the logic behind that if I could apply the schedule to an OU of my choice, but your definition of an OU prevents that. For example, grades 7-8 share a building with grades 9-12. The schedules for those two sets of students are slightly different. I have an OU for each grade level, but since it isn't recognized as such I am knee capped from being able to set more than one schedule. The dev team needs to revisit scheduling again because having teachers create custom schedules every single year is silly. I should be able to set them according to building/grade level and have it automatically apply. The original intent of scheduling was designed to do that in theory but is still failing on a functional level.