Workforce overview and employee master control

The Overview tab is the first read for People because it combines employee count, probation count, present today, attendance percentage, approved and pending leave, payroll month to date, and average tenure in one place. Department Distribution, Leave Mix, Weekly Attendance, and Recent Activity make that summary concrete enough to decide where the real issue lives.

Use the Scan Badge action here when the immediate question is identity or fresh activity. The overview should answer whether the workforce posture is healthy before the team jumps into an individual record or a monthly payroll run.

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

The Employees tab is the controlled master list for workforce records. It is not just a directory: it supports employee search, department filtering, add-employee flow, badge scanning, QR display, attachments, and transaction workflow so HR teams can maintain identity, contact, and supporting documents in one place.

When a KPI or recent-activity signal looks wrong, move from Overview into Employees and resolve the underlying record there. That keeps the summary honest instead of turning the overview into a place where teams only notice problems without correcting them.

For Employees as the operating record, 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: explain why the Overview tab is the entry point for workforce posture. 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: teach people-operations teams to start with workforce signal and then move into the employee master when a headcount, identity, or personnel record needs action.

Close the exercise by asking the learner to restate the objective in operational terms: explain why the Overview tab is the entry point for workforce posture. 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: explain why the Overview tab is the entry point for workforce posture.

Do not mark the lesson complete because the learner can repeat terms. Completion means they can explain when to stay in Overview versus move into Employees 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 when to stay in Overview versus move into Employees, keep the lesson in practice mode before marking it complete.