Skip to content
All modules Academics

Period Attendance software for Indian schools

Subject and class-level marking

Feature identity

Period Attendance

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

Example view

Period Attendance in a school workflow

Subject and class-level marking

Academics
Period Attendance in a school workflow
Academics
  1. 01
    Required context

    Period configuration, timetable/teacher scope and student roster must be confirmed before rollout.

  2. 02
    Supported work

    Per-period registers living alongside the whole-day register.

  3. 03
    Reviewable result

    A subject-period register that remains reviewable beside the whole-day register and rolls up by a documented rule.

Example record

Period Attendance

Authorised view
  • Per-period registers living alongside the whole-day register
  • A clear, fixed day roll-up rule — present in any period counts the day
  • Cross-period alert damping: one parent alert per student per day
  • The month grid can show a single period's register
A subject-period register that remains reviewable beside the whole-day register and rolls up by a documented rule.
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

Whole-day and period-wise registers coexist: any timetable period (1-12) can keep its own register beside the day register, and the day rolls up as present-if-present-in-any-period. Subject teachers mark their own period, and absence alerts stay damped to one per student per day.

The school problem

School teams need a dependable way to handle Period Attendance: Subject and class-level marking. The required records, assigned roles and review boundary must remain explicit.

Day-to-day work

How your school uses it day to day

Subject and class-level marking.

  1. Per-period registers living alongside the whole-day register
  2. A clear, fixed day roll-up rule — present in any period counts the day
  3. Cross-period alert damping: one parent alert per student per day
  4. The month grid can show a single period's register

Operational result

What your school gets

A subject-period register that remains reviewable beside the whole-day register and rolls up by a documented rule.

Access and ownership

Who typically uses it

  • Subject teacher
  • Class teacher
  • Attendance coordinator
  • Student

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

Academics catalogue capability

  • Period configuration, timetable/teacher scope and student roster
  • Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

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 Period Attendance work on its own?

Student Attendance, Timetable Management, Teacher Mapping, Monthly Attendance Report 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 Period Attendance?

Period configuration, timetable/teacher scope and student roster. Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Is AI used in Period Attendance?

No AI capability is asserted for Period 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.

See it in your school context

Run period attendance the connected way.

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