Back to blog

From One Teacher’s Idea to a School-Wide Tool: The Story Behind EduCatchUp

August 4, 20265 min read

I didn't set out to build a piece of school software. I set out to fix one specific, small, recurring frustration I kept watching happen, over and over, in a classroom that wasn't even mine.

Where it actually started

I was helping out — informally, the way students sometimes do — in a teacher's classroom during a free period, and I watched the same scene play out more times than I could count. A student would come back from being out sick, or from a family thing, or from a doctor's appointment, and ask what they missed. And I'd watch a genuinely great teacher, someone who clearly cared about getting this right, have to choose between two bad options: take five or ten minutes away from the rest of the class to explain it properly, or give the student a quick, incomplete answer and hope they could piece the rest together on their own.

Neither option was really a choice. The class couldn't afford to lose ten minutes every time a student had been out. And the quick, incomplete version — "read chapter 4, ask a friend for notes" — clearly wasn't actually catching anyone up. It was just checking a box.

The part that stuck with me

What stuck with me wasn't the inconvenience — teachers deal with plenty of inconvenience and handle it fine. It was watching the same students fall behind, quietly, over and over, specifically because the system for catching up didn't really exist. Not because anyone didn't care. Because there wasn't time, and there wasn't a tool built for this specific, unglamorous problem. Most EdTech seemed to be solving flashier problems — grading automation, flashy analytics dashboards — while this genuinely disruptive, everyday issue went mostly unaddressed.

Building it, badly, first

The first version was rough. It didn't integrate with Google Classroom at all — it was a form a teacher had to fill out by hand, describing what was covered, which defeated a lot of the point, because it just moved the time cost from "explaining to the student" to "explaining to the tool." It took actually sitting with teachers, watching how they worked, and asking what would make them never open the thing at all, to understand that the integration with Classroom wasn't a nice-to-have — it was the entire point. If a tool needs a teacher to manually re-describe their lesson, it's not saving any time; it's just moving the same work somewhere else.

What changed once it actually connected to Classroom

Once the system could read what a teacher had already posted — the actual materials, the actual coursework — instead of asking them to describe it again, everything about the tool got faster and, more importantly, more accurate. A generated lesson wasn't based on what a topic was supposed to be that week according to a pacing calendar. It was based on what was actually taught, which is the only version of "catch-up" that's honestly useful to a student.

Why the teacher review step never went away

One thing that stayed constant from the very first version to today: a teacher always sees the lesson before a student does. Early on, that was mostly caution — I didn't fully trust the output yet, and neither should anyone building something like this without testing it thoroughly. Over time it became something closer to a principle. A lesson a teacher hasn't reviewed isn't something I'd want a student relying on, no matter how good the underlying generation gets. The tool's job is to make that five-minute review fast and accurate, not to skip it.

Where it's headed

EduCatchUp is still, at its core, trying to solve the same problem I first noticed watching that one teacher run out of time — just at a bigger scale now, across whole schools instead of one classroom. The lesson builder, the behaviour tracking, the admin dashboard — all of it grew out of the same underlying belief: the unglamorous, repetitive parts of a teacher's job are exactly where a well-built tool should be doing the heavy lifting, so teachers get their time back for the parts of the job that actually need a person.

It started as one student noticing one problem in one classroom. It's still driven by the same thing — just aimed, now, at every classroom where the same scene has been quietly playing out for years.