About
Built in London, Ontario, for teachers who mark math.
Why we built Markscanner
Grading a class set of handwritten math takes too long, and the part that takes longest is the part nobody wants: the repetitive first pass where you’re mostly writing the same comments on the same mistakes for the twentieth time. We built Markscanner to take that first pass off the teacher’s plate, so the time left goes to the judgement calls and the conversations that only a teacher can have.
The deeper case — why frequent assessment is better teaching than one big exam at the end, and what that means for teachers, students, parents, and schools — lives on the Why Markscanner page.
What we believe about AI in grading
AI should draft, not decide. The model suggests, the teacher reviews and approves, and nothing gets returned to a student until a real person has signed off on it.
Markscanner is deliberately designed as a teacher-in-the-loop tool. Low-confidence answers get flagged; they don’t get silently guessed.
We don’t use student work to train models. The content goes to the grader, does its job, and that’s where it stops.
About the founder
I’m Oscar ONeill. I live in London, Ontario, and I’m the person on the other end of every email you send to Markscanner. I’m not a math teacher myself — I built Markscanner after watching too many teacher friends spend evenings and weekends marking papers, with no time left for the parts of their job that matter most: working one-on-one with students, figuring out which topics the class is struggling with, and knowing when to reteach versus when to move on.
The goal is simple — give teachers their time back, get feedback to students sooner, and help teachers see what the class is actually struggling with so they can focus on what students need.
Email me anytime — [email protected]. Feedback, feature requests, weird edge cases from your own marking — I want to hear them. The product gets better the more teachers push on it.