User Story
As a Rota Administrator or Team Lead,
I want to group clusters into Pools and assign those Pools to one or more Teams (instead of assigning individual clusters directly to teams),
So that the system can intelligently allocate clusters for checking while ensuring fair coverage across all clusters, including those in shared pools.
Key Features
I can create Pools that contain one or more clusters.
A Pool can be assigned to one team or multiple teams.
When generating or updating the rota, the system considers cluster allocation at the Pool level rather than individual cluster assignments.
Clusters that belong to Pools assigned to only one team are prioritised for that team’s rota.
Clusters that belong to Pools assigned to multiple teams can be allocated across those teams, while still maintaining fair checking frequency.
The allocation logic ensures no cluster is over- or under-checked compared to others, even when pools are shared between teams.
The system prevents a cluster from being assigned to a team unless it belongs to a Pool that has been allocated to that team.
I can view which Pools a cluster belongs to and which teams have access to each Pool.
When viewing or editing team responsibilities, I can see the Pools (and therefore clusters) a team is responsible for checking.
User Story
As a Rota Administrator or Team Lead,
I want to group clusters into Pools and assign those Pools to one or more Teams (instead of assigning individual clusters directly to teams),
So that the system can intelligently allocate clusters for checking while ensuring fair coverage across all clusters, including those in shared pools.
Key Features
I can create Pools that contain one or more clusters.
A Pool can be assigned to one team or multiple teams.
When generating or updating the rota, the system considers cluster allocation at the Pool level rather than individual cluster assignments.
Clusters that belong to Pools assigned to only one team are prioritised for that team’s rota.
Clusters that belong to Pools assigned to multiple teams can be allocated across those teams, while still maintaining fair checking frequency.
The allocation logic ensures no cluster is over- or under-checked compared to others, even when pools are shared between teams.
The system prevents a cluster from being assigned to a team unless it belongs to a Pool that has been allocated to that team.
I can view which Pools a cluster belongs to and which teams have access to each Pool.
When viewing or editing team responsibilities, I can see the Pools (and therefore clusters) a team is responsible for checking.