Your school register, on a screen. Every day. Every cell. Editable.

How most Indian schools keep the monthly register today

In the Class 5 B classroom, the attendance register is a hardbound book about 14 inches long. Roll numbers run down the left edge — 1, 2, 3, Aarav Sharma, Aaradhya Patel, Aayush Singh, all the way to 47. Across the top, in the class teacher's handwriting, the days of the month run left to right — 1 to 31. Every cell on this 47×31 grid holds a tick, a slash, a tiny L, or sometimes a remark squeezed into the margin. The first row of the page lists the dates the school was closed — a Sunday with a slash through it, the second Saturday with 2nd Sat, 26 Jan — R Day, Holi, 2 days school function.

At the end of every month, the head clerk takes the register, opens an Excel sheet, and copies it cell-by-cell. Class-wise totals — working days, present days, absent days, percentage. By the 5th of the next month, this Excel goes to the principal. By the 10th, a sub-set goes to UDISE+. By the 15th, a parent in Lucknow asks for her daughter's percentage report — the office assistant has to find the register, find the Excel, find the sub-totals, and recompute. Every step is paper-to-paper-to-Excel-to-letter. Every step has a chance to lose a date or count it twice.

The Monthly Attendance Register in Inkwelly is the same 47×31 grid — with the same row order, the same column order, and the same one-letter cell codes — but on a screen the class teacher can open from her phone or the staff-room laptop. Edit any cell. Bulk-mark a column. Filter to absent students only. Print the page. Export to Excel. Submit to UDISE+. The register-book mental model the school has used for fifty years stays exactly intact — the data layer below it just stops being paper.

How the monthly register works

The class teacher opens the Student Attendance dashboard, clicks her class, and clicks Register. The screen shows the current month — say, March 2026 — with the month picker in the toolbar. Forty-seven student rows on the left, thirty-one day columns across the top. Every cell is colour-coded with the five-status legend — green for Present, red for Absent, amber for Late, half-amber for Half Day, blue for Leave — with grey shading on Sundays, second Saturdays and any date the school calendar marks as HOLIDAY.

She scrolls down the row for roll number 28 — the chronic absentee her principal asked her about. The right edge of the row shows 13 / 22 working days, 59%. She clicks the cell for 18 March. A popover opens — status dropdown, remarks field, optional reason. She changes Absent to Leave, types 'sister's wedding, full week', clicks Save. The cell turns blue. The row total updates to 18 / 22, 81%. The chronic-absentee watchlist on the dashboard refreshes — the flag against roll number 28 disappears.

The head clerk needs to mark the entire 19 March column as HOLIDAY because the state board declared a sudden holiday. She clicks the column header for 19 March. A menu appears — Mark all P / A / L / HD / LV / Holiday / Week off. She clicks Mark all → Holiday, types 'State board declared holiday' in the reason. Every cell in that column turns grey across all 47 students in one frame. The audit log records changed by Head Clerk, 47 cells, reason: state board declared holiday.

On her phone in a parent-teacher meeting, the class teacher switches to the Mobile Day View — same grid, but pivoted: one column on the left is the day, every student of the class on the right with their status dot. Tapping a student's row shows the same cell popover. Editing on mobile updates the master grid in real time — there is no separate phone vs desktop data.

See the register on real classroom data

“Pehle har month ke 2 tareekh ko clerk ko register de ke Excel banwana padta tha. Ab register hi screen pe hai, woh print karke principal ko de dete hain. Aadhe ghante ka kaam dus minute mein ho jata hai.”

Five real-world months on this grid

1. End-of-month closure (the 1st of the next month). The head clerk opens the previous month's grid for every class, scans for blank cells (a class teacher who forgot to mark one day), fills them with the correct status, then exports the Excel for the principal. Three classes had one missing day each; the head clerk filled them in 90 seconds without leaving her chair.

2. UDISE+ submission window (October). The school is filing the UDISE+ Student Attendance schema. The office opens the consolidated register view, exports the prescribed Excel format — student-wise totals for the months till date, including the social-category and gender splits UDISE+ asks for. No re-keying, no separate export request to a vendor; the same register grid the class teacher edits drives the submission file.

3. Mid-year teacher transfer. A Hindi teacher leaves and a substitute teacher takes over Class 5 B from 1 December. The new teacher opens the register for December onwards. The previous months' data is still visible (read-only for her, editable for the head clerk). The audit log shows which entries were made by which teacher — useful when a parent later disputes a September entry.

4. Affiliation renewal (CBSE / ICSE). The school is renewing CBSE affiliation. The board asks for the 'Pupil Attendance Profile' for the past three academic sessions. The office picks the three sessions in the register module's archive view; the system generates a consolidated PDF with month-by-month totals per class for each session. What used to take a week of office work is a 10-minute job.

5. Parent dispute over a chronic-absenteeism letter. The school sent a 75%-shortage letter to a Class 9 parent in February. The parent comes in furious — 'mera bachcha kabhi nahin bunked'. The principal opens the register, sees nine specific dates marked absent, hovers each cell to see the original remark the teacher typed that morning. Six of the nine were 'no notice from parent, called home, line dead'. The parent reads them and the conversation moves from disputing data to discussing follow-through. No paper hunt; no Excel disagreement.

See your school's register on a screen

20-minute walkthrough on the Inkwelly demo school. Bring last month's paper register and an Excel export — we will load the same data into the grid live and show you the row-totals and audit log instantly.

Limits, safety and the small print

Roll numbers and dates are the only axes. This grid is rows = students sorted by roll number, columns = working days of the month. There is no pivot to 'hours of the day', no period-wise attendance, no subject-wise attendance on this screen — those are deliberate exclusions. The Indian register-book layout the school has used for fifty years is what teachers eye-scan in seconds; we keep it.

Past-month edits require permission. The school can lock past months from the calendar admin panel. Once locked, only a head clerk or principal can edit a cell — with mandatory reason. Class teachers see a read-only view of locked months. This stops accidental overwrites of last term's data when a teacher is correcting today's data.

Bulk delete needs an explicit reason. Deleting a cell, a column, or a row uses the Delete with reason dialog. The reason is mandatory. The audit log records who deleted, what was deleted, and why. Bulk delete of a whole class's entire month is intentionally a multi-step confirmation — the screen will ask twice and require typing the class name to confirm, because that is a 47×31 = 1,457-cell delete.

Mobile day view supports edits, but slow networks see the desktop grid as a paginated table. When the bandwidth is low, the desktop grid auto-paginates by 10 students at a time; mobile day view always paginates by date. No screen ever loads more than a thousand cells at once, even on a 3G connection from a tier-3 town. The audit log writes happen on save — not on every key-press — so the network round-trip count stays low.

Calendar updates flow downstream automatically. If the calendar admin marks a previously-working day as a new HOLIDAY retroactively, every register grid for that date auto-shades on next open and the row-totals recompute. If a previously-holiday day becomes a working day mid-year (rare — e.g., a board exam re-scheduled), the same flow applies in reverse. The school never has to manually update fifty class registers when one day's status changes.

Trade the hardbound register for an editable grid

The register grid is one of seven [Student Attendance](/modules/students-attendance) features Indian schools rely on every day. Book a demo and see it on your school's data.