Attendance by session.
Accurate, always.

The hidden cost of attendance registers

Most schools in India take attendance with a paper register or a simple tally on a whiteboard. The process is familiar and feels fast — until you need the data. When a parent disputes an attendance record, there is no timestamped evidence. When an administrator needs an attendance report for a specific student over three months, someone has to page through registers by hand. When the same student is marked in two different places for the same period, there is no system to catch it.

These are not rare edge cases. They happen weekly in any school operating at scale. The cost is not just the time spent resolving disputes or compiling reports — it is the erosion of trust. Parents who cannot verify their child's attendance record independently will call the school. Teachers who cannot correct an accidental entry will leave the wrong data in place. Administrators who cannot query attendance history will make decisions based on incomplete information.

Why session-based attendance is structurally better than daily roll calls

Most digital attendance systems mirror the paper register: one attendance record per student per day. This is simple, but it loses information. A student who is present in the morning and absent after lunch has a different record from a student who is absent all day — but both get recorded the same way. A student who skips a specific class period regularly is indistinguishable from one who misses only on illness days.

Session-based attendance — where each class period generates a separate session with its own records — captures the real picture. Teachers take attendance for their specific period, not a generic daily status. A student who attends 8 periods but skips one is recorded at that level of granularity. Patterns visible only in period-level data — selective absences, class-specific behaviour — become visible and actionable.

The timetable integration makes this practical. Without timetable integration, session-based attendance would require teachers to manually recreate the class structure for every entry. With it, teachers open a timetable entry and start the session in one tap — the class, date, and period are already populated. This removes the friction that would otherwise make granular attendance impractical.

Parent visibility changes the dynamic entirely

When parents can check their child's attendance independently — without calling the school — the nature of the conversation about attendance changes. In the old model, a parent calls the front office to ask whether their child was marked absent last Tuesday, the staff member checks the register, finds the entry, and relays the information. This exchange happens hundreds of times per week across any moderately sized school.

In the Knwdle model, that call never happens. The parent opens the Connect app, sees the attendance summary for the week, taps on Tuesday, and sees the session records for each period. If the record shows absent and the parent believes their child was present, they have a specific data point to raise with the school — not a vague dispute about "last week." The conversation is shorter, more productive, and resolved faster.

The filter-by-date-range feature in the Connect app serves a less obvious but equally valuable purpose: it lets parents review attendance before parent-teacher meetings. Instead of arriving at a meeting and hearing about attendance issues for the first time, parents arrive already informed. The conversation shifts from information transfer to action planning — which is a significantly better use of both the teacher's and the parent's time.

Why data integrity features matter as much as the marking interface

Most schools evaluating attendance software focus on the marking interface — how fast can a teacher mark attendance? This is important, but it is only half the picture. The other half is data integrity: what prevents bad data from entering the system, and what tools exist to correct it when it does?

Knwdle addresses both sides. The uniqueness constraint on class, date, and period combination prevents duplicate sessions at the database level — not through a warning dialog that can be clicked past, but at the point of insertion. This means that a teacher who accidentally tries to create a second session for the same period is stopped before any data conflict is created.

Correction is handled through direct record editing — any teacher with access to a session can update individual student records at any time. There is no approval queue, no request form, no IT support ticket. If a student was marked absent by mistake, the correction takes three taps and is saved immediately. The history of corrections is preserved in the record metadata, so the corrected state is always transparent.