Grade 38 students in 12 minutes. One screen. One save. No notebook stack.

How most teachers grade homework today

It is Tuesday at 3:50 pm in a Class 6 staffroom in Kanpur. The maths teacher's desk has 38 notebooks stacked in two leaning piles. She has 40 minutes before her last period. She opens the first notebook, marks Q1 to Q8 with a red pen, writes "Good — 7/8" at the top, dates it, signs, closes. Notebook two: same routine. Notebook three is a student who is weaker in maths — she wants to write a one-line feedback ("Practice Q5 again"); she pauses, finds her pen ran dry, swaps it, finishes. By the time she has done eleven notebooks, the bell rings.

The remaining 27 go home with her. She grades fourteen on Wednesday, twelve on Thursday morning, and the last four on Saturday afternoon — those four students get their feedback five days late. By Friday, two parents have already called the school office. "Madam, ab tak Aarav ki homework check nahi hui hai — Tuesday ko submit ki thi." The principal pulls the teacher aside. The teacher is upset. Three other teachers in the same staffroom are looking at the same problem with their own classes. This is the single most reliable cause of friction between school and parent in India — not fee disputes, not exam tension. Slow grading.

Inkwelly's bulk homework grading workspace replaces the notebook stack with one screen. Every student in the class appears as a row — photo, roll number, submission status, and three small fields for marks, grade, and feedback. Your teacher fills the rows that matter, hits Save, and 38 students are graded at once. Parents get the marks and feedback on WhatsApp the same evening. Tested on real CBSE, ICSE and IB classes; tested on phone, iPad and laptop; tested on a real Class 7 batch of 47 students graded in 12 minutes flat — with one-line Hinglish feedback for the bottom-quartile six.

How bulk homework grading works

One homework, one screen, every student of that class in front of you — with three small fields per row. There is no "open submission, grade, save, close, next submission" loop because that loop is what costs four days.

One — open the homework you posted. Your teacher opens the homework she published yesterday. The Submissions tab shows every student in her class — even the ones who have not submitted yet (those rows are clearly marked "Not submitted"). Nothing is hidden. The teacher sees the whole class without filtering.

Two — pick the rows to grade. A select-all checkbox at the top covers the whole class. Individual checkboxes let her grade only those who actually submitted. She clicks Bulk Evaluate. A single dialog opens with one row per selected student.

Three — fill what matters. Each row shows the student's name, admission number, and three small fields: marks, grade, feedback. Marks accept any number from a half-mark to a hundred to two hundred and fifty. Grade accepts any short letter — A+, B-, S, IB 1-7, IGCSE A*-G, NCERT "Outstanding". Feedback accepts any one-liner in any language — Hindi, Hinglish, English, Marathi, Tamil, Bengali, Gujarati — with no language selector.

Four — save once. Hit Save. All 38 students are graded in one go. Parents get a WhatsApp the same evening with marks and feedback. The teacher closes the dialog, takes a sip of water, moves on with her day. The notebook stack does not exist.

Real classrooms, real ways teachers use bulk grading

End-of-day grading after a Tuesday assignment. The most common scene. Your teacher publishes a homework on Monday with Tuesday's due date. Tuesday afternoon she opens submissions, hits Bulk Evaluate, types marks for 38 students in 8 minutes, adds one-line Hinglish feedback for the bottom-quartile six, and saves. WhatsApp alerts go to all 38 parents by 5 pm. Notebook stack: zero.

Friday catch-up for a senior teacher. A Class 12 chemistry teacher takes the week's three homeworks together on Friday afternoon. She grades each homework in turn — about 15 minutes per homework — total under an hour for the entire week. Without bulk grading, the same workload meant carrying 84 notebooks home over the weekend.

Mid-term moderation by an HoD. The Maths HoD wants to standardise grading across Class 6-A, 6-B and 6-C — each section has a different teacher. She opens each class's homework, reviews the distribution of marks, and adjusts a few outlier rows. The history captures her edits separately, so the original teacher's grades remain attributed to the original teacher.

Special accommodation for absent students. A Class 9 student was absent for a wedding. Her row shows "Not submitted". Your teacher uses "Mark as Excused" from the row menu, types the reason "family event" in 4 seconds, and the student's row stops counting against the missing-submission rate. Parent disputes about "why is my daughter marked as Missing" disappear forever.

Returning work for revision. A Class 5 child's English homework needs to be redone. Your teacher opens her row, ticks "Return for revision", types one Hinglish line of feedback, and saves. Status changes to Returned. The parent gets a WhatsApp explaining what to redo. The child resubmits in two days. New status: Resubmitted. Your teacher grades the new attempt. Closed loop in under a week, no follow-up email needed.

Grading hundreds of students in one staffroom session. A senior subject teacher who teaches the same subject across five sections grades five classes of 40 each in one staffroom sitting. Total time: 50 to 60 minutes for 200 students. With paper notebooks the same load took 8 to 10 hours spread over the weekend. Eight hours of life back, every week.

See bulk grading on a real classroom

20-minute walkthrough on a real CBSE Class 7 dataset — grade 42 students, including a return-for-revision and an excused absence, in under 15 minutes. No sales pitch. Just the product.

What your principal and IT lead should know

Marks are checked before they save. If your teacher accidentally types 200 in a 100-mark homework, the system catches it and asks her to confirm. Half-marks and decimal grading (8.5, 33.25, 99.99) are supported — every scheme an Indian school uses, including rubric-weighted half points.

Grade is short by design. The grade field caps at 10 characters because longer grades almost never exist. Schools that use longer qualitative ratings like "Outstanding" or "Very Good" put those in the feedback field, not the grade field.

Feedback supports every Indian language. No length cap. No language tagging. Devanagari, Tamil, Telugu, Bengali, Gujarati, Kannada, Malayalam and Latin script all work. Emojis are supported — a Class 2 teacher who writes "⭐⭐ great work!" — fine.

Empty rows are skipped silently. If your teacher selects 40 students but only fills 28 rows, only 28 are saved. The other 12 stay in their previous state. Nothing is overwritten silently, nothing is forced.

Pass-rate is only counted when you set a passing threshold. If a homework was created without a passing-marks threshold (e.g., a project graded purely on rubric letters), pass and fail counts are simply not computed. Your dashboard's pass-rate metric skips that homework. No false data, no false alarms.

Attachments stay inside the workspace. When grading, your teacher can preview a student's submitted PDF, image or audio inline — no extra tabs, no file downloads, no "open in new window" trees. Lower primary classes that get photos of paper notebooks back use this constantly.

Permanent record for disputes. Every grading action is recorded forever — even if the student later resubmits. A parent calling about a 2024 grade in 2026 gets a precise, defensible answer in 30 seconds.

India-region storage, DPDP-aware design. All marks, grades, feedback and submission attachments live on Inkwelly's Mumbai servers. The system is built to align with the DPDP Act 2023 — parental consent for minor data is captured at admission and audit trails are maintained automatically.

Included in your Homework module. Bulk grading is part of the standard Homework module. No add-on fee. No per-grade charges. No caps on how many students you can grade in a save.