All modules AcademicsOptional Aira or AI assistance

Homework & Assignments software for Indian schools

Assign, record submissions, grade, and remind

Feature identity
Homework & Assignments
An illustration, not a screenshot. The interactive example below shows what this capability actually does.

Homework & Assignments in a school workflow

Academics

01
Required context
Student roster and teaching assignment must be confirmed before rollout.
02
Supported work
Record received / not received status from the teacher's section-scoped roster.
03
Reviewable result
A section-scoped assignment register showing what was assigned, recorded as received, graded and still outstanding.

Example record

Homework & Assignments

Authorised view

Record received / not received status from the teacher's section-scoped roster
Grade recorded submissions with server-clamped marks and feedback
Generate a structured grading rubric (criteria × performance levels, weights summing to total marks) with AI
Queue non-submitter reminders with a per-assignment cooldown and messaging safeguards

Code-native illustrative example · not live product UI · no customer dataExample labels and outcomes come from this capability's reviewed catalogue record.

Product scope

What it does

Teachers assign homework with due dates and max marks, then record submission status and grades from an enrollment-backed roster limited to the sections they teach. The current student and parent portals show assignments read-only; they do not provide student self-submission. A teacher can queue a WhatsApp reminder for non-submitters' guardians, subject to provider configuration, consent and opt-outs.

The school problem

School teams need a dependable way to handle Homework & Assignments: Assign, record submissions, grade, and remind. The required records, assigned roles and review boundary must remain explicit.

Day-to-day work

How your school uses it day to day

Assign, record submissions, grade, and remind.

Record received / not received status from the teacher's section-scoped roster
Grade recorded submissions with server-clamped marks and feedback
Generate a structured grading rubric (criteria × performance levels, weights summing to total marks) with AI
Queue non-submitter reminders with a per-assignment cooldown and messaging safeguards

Operational result

What your school gets

A section-scoped assignment register showing what was assigned, recorded as received, graded and still outstanding.

Access and ownership

Who typically uses it

Teacher
Academic coordinator
Student
Parent or guardian

What each person can actually see depends on the role you give them and which classes or records you assign.

Availability and setup

What to confirm before rollout

Academics catalogue capability

Student roster and teaching assignment
Configured messaging provider and consent for guardian reminders
Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Flagship workflow deep dive

Homework, Submission Records & Follow-up

What was set, what came back, what is still missing.

Teachers set homework with due dates and maximum marks, then record submission status and grades from an enrolment-backed roster limited to the sections they teach. Student and parent portals show assignments read-only — there is no student self-submission — and a teacher can queue reminders for non-submitters' guardians through the school's configured channels.

Interactive operating model

From set work to recorded follow-up

Follow one assignment from the roster it is set against to the reminder a guardian receives.

Illustrative workflow · no customer data

Stage 1 of 5

Assignment set

A teacher creates the assignment against their own class-section and subject.

Control point

Record-level scoping keeps a teacher inside the sections they actually teach.

Evidence retained

Assignment record with due date and maximum marks.

Core workflows and features

The operational work behind the promise

Assignments with real deadlinesSet homework against a class-section and subject with a due date and maximum marks, so the register carries the same information the students were given.
Section-scoped rostersWork from an enrolment-backed roster limited to the class-sections the teacher actually teaches, rather than a whole-school student list.
Recorded submission statusMark each student received or not received from that roster, which turns a vague sense of who is behind into a countable register.
Graded with clamped marksGrade a recorded submission with marks the server clamps to the assignment maximum, so a typo cannot produce an impossible score.
Written feedback per studentAttach feedback to a graded submission so the comment lives with the record instead of only on a returned notebook.
AI rubric draftingGenerate a structured grading rubric of criteria and performance levels whose weights sum to the assignment's total marks, for the teacher to edit.
Non-submitter visibilitySee which students have nothing recorded against an assignment, as a working list rather than a calculation someone repeats by hand.
Guardian reminders with a cooldownQueue a reminder to non-submitters' guardians with a per-assignment cooldown, so the same family is not messaged repeatedly about one task.
Read-only family visibilityShow assignments to students and parents in their portals as reference, without implying an online submission route the product does not provide.
Subject-wise workload viewReview what has been set across a class's subjects, so the homework load on one section can be judged rather than assumed.

Optional AI drafting inside a teacher's workflow

Aira can draft a rubric; the teacher grades.

Assignment records, submission status and marks are entirely teacher-recorded. Where the assistant tier is enabled, AI drafts a rubric for review — it never marks work and never records a submission.

Draft a criteria-and-levels rubric whose weights sum to the assignment's total marks, for the teacher to edit.
Compile the non-submitter list for an assignment from the recorded register.
Queue a guardian reminder through the configured channel, subject to consent, opt-out and quiet-mode controls.
Hold a repeat reminder within the per-assignment cooldown window.

Human boundary

AI does not grade, does not decide who submitted, and does not message a family on its own. Submission status and marks are recorded by the teacher for their own sections, and a reminder is a deliberate action that still passes the school's messaging controls.

Key daily uses

What the school team does here

Set an assignment for a section with its due date and maximum marks.
Record who submitted and grade the work that came in.
Pull the current non-submitter list before a parent conversation.
Queue a guardian reminder for outstanding work.
Review the week's homework load across a class's subjects.

Used by

Subject teacher
Class teacher
Academic coordinator
Vice principal
Student
Parent or guardian

Actual access follows the school's plan, role permissions and record scope.

Measurable operating indicators

Metrics to track — not guaranteed ROI

Establish a baseline before rollout, agree the reporting period, then compare the school's own source evidence.

Submission rate

Submissions recorded received against students on the assignment roster

Reads as an engagement signal per section and subject, not as a judgement about a child.

Grading turnaround

Days between the due date and marks being recorded

Shows where feedback is arriving too late to change anything for the student.

Follow-up load

Reminders queued against non-submitters identified

Keeps outbound pressure on families visible and bounded rather than reflexive.

Prerequisites and availability

Confirm the operating context before rollout.

Core academic capability · guardian reminders need configured channels · AI drafting on plans that include the assistant

Student rosters, class-sections and teaching assignments configured, since the roster is scope-bound.
A configured messaging provider with consent and opt-out handling for any guardian reminder.
A plan that includes the Aira assistant if rubric drafting should be available.
Student self-submission is not part of this module; portals show assignments read-only.
Plagiarism checking and automated marking are not offered and are not implied anywhere here.

Connected operating context

Available workflows

These are the documented neighbouring capabilities that school teams may review with this module. A related page does not imply that every hand-off is automatic or enabled in every plan.

Explore all modules

Buyer questions

Frequently asked questions

The questions school owners ask before they subscribe: what it does, who can see it, and what to set up first.

Can students submit their homework in the app?

Not today. Student and parent portals show assignments read-only. Teachers record received or not received from their own section roster and grade what came in — we would rather say that plainly than imply a submission flow that does not exist.

Does AI grade the homework?

No. Where the assistant tier is enabled, AI can draft a grading rubric whose weights sum to the assignment's total marks, for the teacher to edit. Marks, submission status and feedback are all recorded by the teacher.

Does Homework & Assignments work on its own?

Teacher Mapping, Section Management, Homework Updates, Student App are the documented neighbouring capabilities. They help a school evaluate the surrounding hand-offs, but a related page does not mean every integration is automatic or included in every plan.

What should our school prepare before enabling Homework & Assignments?

Student roster and teaching assignment. Configured messaging provider and consent for guardian reminders. Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Is AI used in Homework & Assignments?

Optional Aira or AI assistance. Aira supports only the reviewed actions listed on this page, and authorised people remain responsible for confirming material actions.

How do we confirm the plan and implementation scope?

Plan inclusion and rollout scope depend on the live plan matrix, readiness state and your school's written proposal. The demo team will confirm the applicable boundary before rollout.

Related evaluation guides

See the Academics workspace Compare plans and commercial costs

See it in your school context

Run homework & assignments the connected way.

See how this workflow fits your school's current records, roles, plan and rollout requirements.