Rostering defines recurring shift patterns for crews and groups, so the site knows who is expected on site and when. It gives the fatigue checks and the absence report a baseline of expectation to work against.

This guide covers:

• Defining recurring patterns such as 7-on/7-off for crews and groups
• Feeding the pre-entry and rest-gap fatigue checks against that pattern
• Driving the rostered-but-absent exception report
• Switching rostering on per deployment where a site runs it

Define the pattern once and both fatigue enforcement and absence checking draw on the same expectation.

💡 Power User Insight: Workers do not see their roster inside GSA — it is admin-facing. Not every site runs rostering, so confirm it is enabled for your deployment before relying on the absence report.