Skip to content
All modules HR & Payroll

Staff Attendance software for Indian schools

Review punches, leave, and substitute coverage

Feature identity

Staff Attendance

An illustration, not a screenshot. The interactive example below shows what this capability actually does.

Example view

Staff Attendance in a school workflow

Review punches, leave, and substitute coverage

HR & Payroll
Staff Attendance in a school workflow
HR & Payroll
  1. 01
    Required context

    HR & Payroll enabled for your school, plus governed workforce-time configuration and employee identities must be confirmed before rollout.

  2. 02
    Supported work

    Employee-code punches recorded in a filterable evidence log.

  3. 03
    Reviewable result

    Workforce presence evidence — still rolling out school by school — that authorised teams can compare with leave, schedules and exceptions.

Example record

Staff Attendance

Authorised view
  • Employee-code punches recorded in a filterable evidence log
  • An “on leave today” summary computed from approved leave
  • The substitute board fills an absent teacher's periods in one click
  • Punch logs do not automatically create payroll attendance or salary inputs
Workforce presence evidence — still rolling out school by school — that authorised teams can compare with leave, schedules and exceptions.
Code-native illustrative example · not live product UI · no customer dataExample labels and outcomes come from this capability's reviewed catalogue record.

Product scope

What it does

When the HR & Payroll workspace is enabled for your school (it's still rolling out school by school), review employee-code punch logs alongside approved leave and substitute coverage. Employee punches remain presence evidence: they do not create payroll-ready staff attendance or feed salary calculations automatically. The substitute board can rank available same-subject teachers for uncovered periods.

The school problem

School teams need a dependable way to handle Staff Attendance: Review punches, leave, and substitute coverage. The required records, assigned roles and review boundary must remain explicit.

Day-to-day work

How your school uses it day to day

Review punches, leave, and substitute coverage.

  1. Employee-code punches recorded in a filterable evidence log
  2. An “on leave today” summary computed from approved leave
  3. The substitute board fills an absent teacher's periods in one click
  4. Punch logs do not automatically create payroll attendance or salary inputs

Operational result

What your school gets

Workforce presence evidence — still rolling out school by school — that authorised teams can compare with leave, schedules and exceptions.

Access and ownership

Who typically uses it

  • HR administrator
  • Workforce manager
  • Principal
  • Employee

What each person can actually see depends on the role you give them and which classes or records you assign.

Availability and setup

What to confirm before rollout

Still rolling out school by school

Staff lifecycle, leave, compensation and payroll workflows.

  • HR & Payroll enabled for your school, plus governed workforce-time configuration and employee identities
  • Built — enabled school by school; confirm availability for your school
  • This capability is still rolling out school by school; ask us about availability before you plan it into your rollout.

Connected operating context

Available workflows

These are the documented neighbouring capabilities that school teams may review with this module. A related page does not imply that every hand-off is automatic or enabled in every plan.

Explore all modules

Buyer questions

Frequently asked questions

The questions school owners ask before they subscribe: what it does, who can see it, and what to set up first.

Does Staff Attendance work on its own?

Leave Management, Staff Shift Tracking, Biometric Attendance, Staff Reports are the documented neighbouring capabilities. They help a school evaluate the surrounding hand-offs, but a related page does not mean every integration is automatic or included in every plan.

What should our school prepare before enabling Staff Attendance?

Built — enabled school by school; confirm availability for your school. HR & Payroll enabled for your school, plus governed workforce-time configuration and employee identities. This capability is still rolling out school by school; ask us about availability before you plan it into your rollout.

Is AI used in Staff Attendance?

No AI capability is asserted for Staff Attendance. Its documented work remains controlled by school records, roles and permissions.

How do we confirm the plan and implementation scope?

Plan inclusion and rollout scope depend on the live plan matrix, readiness state and your school's written proposal. The demo team will confirm the applicable boundary before rollout.

Related evaluation guides

See it in your school context

Run staff attendance the connected way.

See how this workflow fits your school's current records, roles, plan and rollout requirements.