What are Areas?
Areas let you organise your roster by a location or unit. When an area is applied to a shift, it appears as a prefix on the allocation, for example "ICU: Morning" or "Ward A: Night".
Areas are useful for:
Filtering - View just one area's roster at a time, which makes large rosters easier to read and check.
Optimisation structure - When the same shifts exist across multiple physical locations, areas let the solver treat "Morning in ER" and "Morning in ICU" as distinct allocations without you needing to create duplicate shifts.
Activating Areas
Areas are activated in the Settings menu under Location Behaviours.
Once active, an Areas tab will appear in your sidebar. This is where you create and manage your areas.
Assigning employees to Areas
Assign employees to areas on the Employees page. By default, employees are set to all areas, meaning they're eligible to work anywhere. To restrict an employee to specific locations, update their area assignment here.
Area settings
Each area can carry its own set of restrictions. You can restrict which shifts, skills, or tasks are valid within an area, and choose whether the solver can auto-assign staff to it.
Areas and Demands
Demands can optionally reference a specific area, which narrows where a staffing requirement applies:
A demand tied to "Area A: Morning" only counts people allocated with that area prefix. Someone working "Morning" in Area B doesn't count toward it.
A demand with no area reference applies across all areas, scoped only by whatever else it references (shift, task, skill).
This lets the same shift carry different staffing levels per area. For example, "need 3 on Morning in Area A" and "need 1 on Morning in Area B", even though it's the same shift definition.
Areas can be specified through both the demands table and demands sentence builder
When should I use Areas?
Areas work best for larger rosters where the same set of shifts repeats across multiple locations. For example, if Morning, Afternoon, and Night shifts exist identically in ER, ICU, and Ward A, areas let you model this cleanly with one set of shifts instead of nine.
Keep in mind that areas multiply the number of possible allocations in your model very quickly, so only add them where they're genuinely differentiating something. If you're unsure don't hesitate to reach out to a member of the Rosterlab team
When should I use Areas?
Areas work best for larger rosters where the same set of shifts repeats across multiple locations. For example, if Morning, Afternoon, and Night shifts exist identically in ER, ICU, and Ward A, areas let you model this cleanly with one set of shifts instead of nine.
Keep in mind that areas multiply the number of possible allocations in your model very quickly, so only add them where they're genuinely differentiating something. If everyone is left on the default "all areas" setting and no demands or rules reference specific areas, then areas aren't restricting or organising anything, and your roster may be simpler without them.
If you're unsure whether areas are doing anything in your model, or whether you need them at all, get in touch and a member of the RosterLab team can help you check.