A Teacher's Homework Tracker: Weekly Template and Practical Guide
A teacher needs to distinguish work that has not arrived, work awaiting marking, and work revised after feedback. A single check mark beside a student's name hides these differences. This template helps you track submission and review without turning the table into a complicated record.
A template you can copy
The identifiers below are fictional. Replace them with student identifiers within your school's environment, and do not publish student records on a public page.
| Student ID | Subject | Assignment | Deadline | Status | Next note or action | Follow-up |
|---|---|---|---|---|---|---|
| Student 01 | Mathematics | Lesson 3 problems | Sunday | Submitted | Awaiting review | Monday |
| Student 02 | Arabic | Descriptive paragraph | Sunday | Revision needed | Add a sentence explaining the idea | Tuesday |
| Student 03 | Science | Experiment summary | Monday | Not yet due | No action needed yet | Tuesday |
| Student 04 | Mathematics | Lesson 3 problems | Sunday | Overdue | Find out why it was not submitted | Monday |
| Student 05 | Arabic | Descriptive paragraph | Sunday | Complete | Feedback sent | — |
To start from scratch, copy the blank row for each student or assignment:
| Student ID | Subject | Assignment | Deadline | Status | Next note or action | Follow-up |
|---|---|---|---|---|---|---|
| … | … | … | … | … | … | … |
Define the statuses
“Not yet due” means the submission window is still open. “Submitted” means the work has arrived; it does not judge whether the answers are correct. “Revision needed” means there is specific feedback the student can act on. “Complete” means the required review process has finished. Use “Overdue” after the deadline, taking any agreed extension into account. Add “Exempt” when an exemption applies, and do not count it as a failure to submit.
A weekly follow-up routine
At the beginning of the week, enter assignments and specify what is required and when it is due. Give each task a distinctive title, such as “Fractions problems 1–5,” instead of “Maths homework.” Update its submission status when it arrives, then add feedback after marking.
Midweek, review items needing revision. Make feedback actionable: “Add an example to explain the idea” is more precise than “Improve your answer.” At the end of the week, review overdue work to identify the reason. Were the instructions unclear, did the student find the task difficult, or was there a problem accessing it? The table alone cannot establish why a submission is late.
Calculate submission rate without confusing it with achievement
Submission rate = assignments received ÷ assignments that are due and required of the student × 100.
For example, suppose five assignments are due, the student is exempt from one, and three have been submitted. The rate is 3 ÷ 4 × 100 = 75%. Work needing revision counts as submitted, but not complete. If no required assignments are due, enter “Not applicable” rather than dividing by zero.
This rate describes submission behavior, not understanding or answer quality. Review the actual work and learning feedback separately.
When do you need a platform instead of a table?
As the number of classes and teachers grows, maintaining one up-to-date version of a table can become difficult. A platform combining homework, students, communication, and follow-up may help. Schoolizer presents features for homework, classes, and parent reports; review the available functions to decide what fits your school's way of working.
