Hi MatildaWags,
That’s a really fair question, and what you’re expecting is generally how it should work. Once leave is approved, it should show on the roster automatically, and even pending leave can appear there as an indicator so managers can see someone has time away requested. If someone is rostered on a day they already have approved leave, the system can show a “Shift overlaps with leave” alert. When that alert is set as non-dismissible, the shift can’t be published until it’s fixed. So ideally, managers shouldn’t have to just remember who’s away and manually sort it out later in the pay run, especially for larger teams. If you’re still able to roster yourself on even after approving leave, that would usually suggest the roster alert/settings side needs to be checked, like overlapping leave alerts or whether publish override rules are allowing those shifts through. Also, if someone calls in sick after they’ve already been rostered, a manager can convert the published shift into leave from the roster and then approve the leave request.
So short answer: no, it shouldn’t rely purely on memory. If leave is approved and the right alerts are enabled, the roster should help flag that person as unavailable.
Regards,
Sai