One screen. One class. Roll call done in 90 seconds.

How most Indian classroom teachers mark attendance today

It is 8:05 a.m. The Class 5 B teacher walks in, opens a hardbound register on the second page from the back, and starts calling roll numbers. Roll number 1 — Aarav Sharma — yes ma'am. Tick. Roll number 2. Tick. Roll number 3 — silence. Question mark. By the time roll number 47 is called, the first bell for the next period has already rung. The same scene plays out in 38 other classrooms in the school, in registers that look identical.

Thirty minutes later a peon collects the registers and stacks them on a shelf in the staff room. By 9:30 a.m. the office assistant is typing the day's totals into an Excel sheet — class-wise, section-wise, gender-wise, by social category if the school is on UDISE+. By the time a parent calls the office at 11:00 a.m. asking 'Aarav aaye hain kya?', the data has been copied twice and is already a guess. By Friday, three of those forty registers have ink smudges over an entire week. By March, two have completely disappeared and a teacher has retired with whatever was inside them.

The job is small. The system is heavy. Mark Daily Class Attendance is the screen we built to replace that 30-minute morning routine with a 90-second one — without giving up a single thing the register actually does. It runs on the class teacher's phone or the staff-room laptop, syncs to the school's Student Attendance dashboard instantly, and produces every report the principal, accountant and UDISE+ submission needs.

How Mark Daily Attendance works

A class teacher opens Inkwelly on her phone and taps Mark Today on her dashboard. The class she is assigned to opens directly — no class picker, no list to scroll. She sees every student of Class 5 B sorted by roll number, each with their photo, full name and student ID, and a row of five status buttons: P · A · L · ½ · LV. The default for every student is Present, because in most classes most students are present.

She scans the room. The two empty seats are roll numbers 12 and 28. She taps A on those two rows. Roll number 19 walked in five minutes late — she taps L. Roll number 33 has come for the morning assembly only — she taps ½ and types 'half-day, mother's hospital visit' in the remarks field. She taps Save. The screen shows: Attendance saved for 47 students. Total elapsed: 90 seconds.

Back in the principal's office, the attendance dashboard updates immediately. The principal sees Class 5 B's marking-coverage circle move from grey to green. Today's pulse grid shows 38 of 39 classes have marked. The office assistant doesn't have to type anything. The chronic-absentee watchlist refreshes — roll number 28 has now crossed the 75% RTE threshold and a flag appears next to her name.

No paper register, no Excel transcription, no double entry. The same data feeds the monthly register grid, the per-student attendance profile, the UDISE+ export and the parent communication queue — all from this one screen the class teacher uses every morning.

See the full marking flow

“Pehle 8:05 se 8:35 tak register hi bharte the. Ab 8:05 mein khol ke 8:07 mein save ho jata hai. Tees minute miljaate hain Maths padhane ke liye.”

Five real-world classrooms, one screen

1. The 8:05 a.m. roll call (everyday). Class teacher opens her phone, sees Class 5 B, taps Mark-All Present, changes the two absent rows to Absent, types a remark on the half-day case, taps Save. Total time: 90 seconds. Done before the morning prayer ends.

2. The substitute teacher (Tuesday). The regular Hindi teacher is on a planned leave — the head clerk has assigned a substitute for two periods. The substitute opens her phone, sees Class 5 B in her assigned-classes list, marks the class normally. The audit log records recordedBy = substitute teacher against today's date, and the next-day report still rolls into Class 5 B's monthly summary correctly.

3. The post-lunch correction (same day). A student marked Absent at 8:05 actually walked in at 9:30 with a late note from the school gate. The teacher reopens the screen at 11:00 a.m., changes the row from A to L, taps Update. The change is timestamped and visible in the audit trail — useful when a parent later asks why the morning SMS said absent.

4. The annual function (Saturday). The school is open but the entire Class 8 attended a city-level cultural function. The teacher opens the mark screen, taps Mark-All Leave, types 'Inter-school cultural function — Lucknow Mahotsav' in the remarks of the first row to mark the day's reason, taps Save. The principal's report shows 'Class 8 — full leave (event)' without ambiguity.

5. The chronic-absentee follow-up (October). The chronic-absentee watchlist flags roll number 28 below the 75% RTE threshold. The principal opens her per-student summary, sees every absent date with the original remarks the teacher typed in real time. Two were 'sister's wedding', one was 'fever', four had no remark — those are the four the principal calls the parent about. Without the per-row remarks, the call would have been a guess.

See the daily mark screen on your school's data

20-minute walkthrough on the Inkwelly demo school. Bring your own register layout — we will show how it maps onto the daily-mark screen, the [monthly register](/features/monthly-attendance-register), and the chronic-absentee dashboard.

Limits, safety and the small print

Roll-number sort is the only built-in sort order. Students are always shown in roll-number sequence — the same order the paper register and CBSE/ICSE official report formats use. Sorting by name or admission date is not exposed on this screen, on purpose. The teacher's eye-memory of 'roll number 12 sits in the second row' is the fastest possible scan, and we do not break it with a sort menu.

Default status is Present. This matches the reality that 90%+ of students are present on a typical day. Teachers who prefer to start with everything Absent and tap up can use Mark-All → Absent at the top of the screen. Either approach gets to a saved attendance in under two minutes.

No bulk import on this screen. This is the single-class, single-day surface. Bulk-mark across multiple classes lives on the monthly register grid. Backfilling a full month of past data is done from the per-class register, not here, on purpose — a pattern that prevents accidental mass overwrites of the morning's correct data.

Holiday list is school-controlled. The school's calendar admin sets which dates are holidays. The mark screen reads from that list — if a date is missing from the calendar, the screen will allow marking. We recommend the office adds the school's full annual holiday calendar at the start of the year so the lock works for every Republic Day, Independence Day, Diwali, Holi, Eid, Christmas, Guru Nanak Jayanti, Teachers' Day and the school's own annual function.

Mobile-first but works on every device. The screen is built mobile-first because the class teacher's phone is the most common device. It works equally on the staff-room laptop, the principal's iPad and the school's shared tablet — same five-status layout, same Mark-All bar, same save flow. There is no separate desktop UI to learn.

Replace the 30-minute register with a 90-second screen

Inkwelly's daily mark screen is one of seven [Student Attendance](/modules/students-attendance) features Indian schools rely on every morning. Book a demo and see it on your own class data.