Attendance and leave operations

The Attendance tab is a dense month matrix, not a high-level metric card. It lets teams move month by month, see present, absent, leave, holiday, and week-off status by employee and day, export the grid, and mark presence through badge scanning when the workflow needs real attendance evidence.

This matters because attendance quality is operational, not cosmetic. A monthly matrix makes gaps and patterns visible in a way that summary counts alone cannot, especially when presence marks need to be justified later.

Evidence should come from workforce overview, employee master state, attendance evidence, leave approval, payroll month, export state, or payout status. For Attendance as daily evidence, a strong answer names the visible cue, record, status, or reference that supports the next step and states what would pause the learner.

The Leave tab is the approval and history surface for time away from work. It supports request creation, status filtering, pending versus approved counts, approved days, badge-scan-assisted request entry, and explicit approve or reject actions against each pending row.

Attendance and leave should be read together. If attendance looks weak or staffing seems unstable, the next question is whether the absence belongs to approved leave, unresolved requests, or attendance exceptions that still need correction.

For Leave as controlled exception handling, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

Run the lesson as a people-operations control check. Start with the practical task: describe how the Attendance tab turns day-level presence into a visible monthly control surface. Ask the learner to name the role, surface, evidence, and state they would inspect before taking action.

Evidence should come from workforce overview, employee master state, attendance evidence, leave approval, payroll month, export state, or payout status. The practice should end with the learner connecting the action back to the lesson summary: show how attendance and leave remain trustworthy only when daily evidence, monthly visibility, and approval actions stay in the same workflow.

Close the exercise by asking the learner to restate the objective in operational terms: describe how the Attendance tab turns day-level presence into a visible monthly control surface. They should name what changed, what remains uncertain, and which surface or owner takes the next step.

Do not let HR or payroll decisions rely on informal memory. Employee identity, attendance, leave, and payroll state should stay traceable in the shared workspace. In this lesson, watch for that risk while learners work on this objective: describe how the Attendance tab turns day-level presence into a visible monthly control surface.

Do not mark the lesson complete because the learner can repeat terms. Completion means they can explain why the Attendance matrix is more than a summary dashboard and describe why the lesson matters in real work.

Review the answer for skipped ownership, missing evidence, or vague next steps. If the learner cannot explain why the Attendance matrix is more than a summary dashboard, keep the lesson in practice mode before marking it complete.