The rostered-but-absent report lists workers who were expected on a shift but did not swipe in. It turns a gap between roster and reality into a daily check, with safety value as well as attendance value.

This guide covers:

• Comparing the rostered pattern against recorded swipes
• Listing who was expected but has not arrived
• Prompting supervisors to confirm leave before chasing an absence
• Treating a no-show as a possible journey incident, not only a missed shift

Work the report daily and an unexplained absence is followed up while it still matters.

💡 Power User Insight: GSA holds no leave records, so a worker on approved leave still shows here. The production pattern is to confirm leave first, then chase — because a no-show can equally signal a journey incident.