THE PROBLEM
Grading is not one action. It is submissions, missing work, checking, feedback, tracking and then figuring out what the class needs next.
A grading workflow concept built around a simple idea: teachers should spend less energy managing the grading process and more energy on the judgement that actually needs a teacher.

Grading is not one action. It is submissions, missing work, checking, feedback, tracking and then figuring out what the class needs next.
Pull that operational mess into one place so the teacher can see what is done, what is pending and where attention is needed.
Automate admin before judgement. The product should support the teacher, not cosplay as the teacher.
The dashboard puts the current state first: total submissions, pending submissions, performance context and a to-do list. The point is to answer “what needs my attention now” before showing anything fancy.
A tighter review flow with rubrics, teacher override, side-by-side answer context and a clear audit trail for any automated suggestion. If AI is involved, every recommendation should be inspectable and easy to reject.
Where teachers actually lose time. It might be marking. It might be chasing missing submissions. It might be writing repetitive feedback. The next version should be shaped by that evidence, not by whichever feature looks best in a mockup.
Concept work only. No deployment, no fake “saved 40% of grading time” metric, no made-up user quote. The value of the project is the workflow thinking and what I would test next.