AVKUL ERPDocs
SCREEN GUIDE · 11 OCT 2026

Student attendance

Use student attendance in the school workspace. Complete a daily class register and review attendance history, shortages and family alerts.

Try guided demo →Download guide ↓
Student attendance — illustrated workflow banner
OVERVIEW

What you can do

01

Mark all present

02

Students of a section + their status for a date

03

Mark/replace attendance for a section + date

04

Tell absent students' guardians, once per student per day

05

Students below the required attendance percentage

06

Warn guardians of students below the required percentage

07

What has already been sent to families

BEFORE YOU BEGIN

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
attendance:viewattendance:createattendance:manage

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

STEP BY STEP

How the workflow works

  1. 01

    Choose a permitted section and date

    A school account with the permissions shown below.

  2. 02

    Mark the roster and review the section completion summary

    Students of a section + their status for a date is part of the documented workflow.

  3. 03

    Save the register and inspect corrections/history

    Mark/replace attendance for a section + date is part of the documented workflow.

  4. 04

    Review shortages and recorded alerts before reminding families

    Review the result in the connected record or workspace before moving on.

Fields & controls

The screen exposes the following context or input controls. Required fields are validated by the live application.

  • Class / section
  • Attendance date
  • Session
  • Correction reason
  • Notify absent students’ guardians in-app on save
CURRENT BEHAVIOUR

Rules & current limits

  • Holiday and attendance policy affect denominators. Only permitted sections are visible; recording an absence is distinct from approving leave.

Source inventory checked on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

LEARN BY DOING

Try student attendance

Open a guided sample workspace, try the available actions, then reset whenever you like. No login required.

Launch guided demo →
FOR IMPLEMENTERS

API & permissions reference

These are the source-matched API operations connected to this guide. Reading this reference does not execute any request.

6 source-declared operations
GET/api/v1/attendance/roster

Students of a section + their status for a date

attendance:view
POST/api/v1/attendance/mark

Mark/replace attendance for a section + date

attendance:create

Declared request fields: sectionId (required), date (required), session (optional), records (required), version (optional), correctionReason (optional), force (optional), notifyGuardians (optional).

POST/api/v1/attendance/alerts/absence

Tell absent students' guardians, once per student per day

attendance:manage

Declared request fields: date (required), sectionId (optional), message (optional).

GET/api/v1/attendance/shortages

Students below the required attendance percentage

attendance:view
POST/api/v1/attendance/alerts/shortage

Warn guardians of students below the required percentage

attendance:manage

Declared request fields: studentIds (optional), message (optional).

GET/api/v1/attendance/alerts

What has already been sent to families

attendance:view

Open the actual application

ERP links use your assigned account. Record-specific pages start from the list so you can choose a real record.

/en/school/attendanceOpen ↗

Keep exploring

Module guideStudent attendance →