About DraftGrade
Built by watching a teacher grade papers at 11pm.
DraftGrade exists because grading shouldn't be the reason a teacher's day never ends.
Our story
Grading is the part nobody automated.
Every part of a teacher's job has gotten a piece of software built for it: lesson planning, attendance, communication with parents. Grading, the part that actually eats the evenings and weekends, mostly hasn't changed in decades: a rubric, a red pen, and a stack that only gets taller.
We started by asking teachers directly what a tool like this would need to get right, before writing a line of code. The answer was consistent: keep it close to how they already grade, respect the rubric they already use, and never make a student's private work feel less private.
DraftGrade is the result: a tool that reads handwritten work the way a teacher would, scores it against the rubric they already trust, and hands back feedback worth reading, in minutes instead of days.
What we believe
The principles behind the product
Teacher judgment stays final
DraftGrade proposes a score and feedback. A teacher decides what actually reaches a student.
Privacy is architecture, not a promise
Student work isn't persisted on our servers. That's a design decision, not a policy we're asking you to trust.
Fit the rubric, not the other way around
Teachers shouldn't have to reformat years of rubrics to fit a tool. DraftGrade reads what they already have.
Want to pilot DraftGrade at your school?
We're onboarding a small number of new classrooms each month while we build toward general availability.