How to Track a Student's Submissions Across Assignments
Use a stable student identifier across assignments, then bring the relevant records together in a simple tracker. Names alone can vary or be shared by several students. Keep submission receipt, lateness and academic performance as separate pieces of information.
Different questions need different records
“Has this student submitted?” is different from “Has this student's work been marked?” or “Does this student understand the topic?” A single tick cannot answer all three and can hide either missing work or unfinished teacher review.
Create a useful cross-assignment tracker
Use the same roll-number and class conventions in every assignment and explain them to students.
Keep one row per student and identify assignments clearly by title or date in your own tracker.
Import or copy verified submission details, resolving name variations and duplicates before counting completion.
Review patterns over time and follow up on specific missing work without treating submission frequency as a complete measure of learning.
Put it into practice
Example: separating completion from attainment
A student may submit every assignment but repeatedly misunderstand a method. Another may submit fewer tasks because of access problems. Record the missing work, then look at feedback and responses before deciding what support each student needs.
Before you share
- Avoid storing more personal data than the task requires.
- Do not merge students merely because their names match; verify the class and roll number.
How EduVetta helps
EduVetta's assignment results include student details and can be exported to Excel. Use those exports with your class roster to build a cross-assignment tracker. This is a teacher-managed workflow, not a claim that EduVetta automatically creates a longitudinal submission dashboard.