"AI-generated lesson" can sound like a black box — type something in, get something vague and generic out. That's not particularly useful for makeup work, where the whole point is that the lesson has to match exactly what a specific class covered on a specific day. So it's worth walking through, step by step, what actually happens when a teacher generates a catch-up lesson, because the mechanics matter more than the buzzword.
Step 1: The absence gets recorded
It starts with the everyday reality of a classroom — a student wasn't there. A teacher uploads a daily absence list, or marks it directly against synced Google Classroom rosters, noting who was out and for which class. This is the same information a teacher would jot down anyway; nothing new is being asked of them here.
Step 2: The system pulls the actual day's content
This is the part that makes the difference between a useful catch-up lesson and a generic study guide. Because EduCatchUp is connected to Google Classroom, it can look at exactly what was posted, assigned, or covered for that course on that date — announcements, materials, coursework — rather than guessing at a topic from a syllabus written back in August. The lesson is built from what actually happened in the room, not from what was supposed to happen according to a pacing guide.
Step 3: A lesson is generated — explanation, not just a worksheet
The AI produces a short, readable explanation of the material, written at a level appropriate for the course, along with a small quiz that checks whether the student actually understood it rather than just skimmed it. It's built to be something a student can sit down with independently — in study hall, at home, or during an advisory period — without needing a teacher standing over their shoulder to interpret it.
Step 4: A teacher reviews before it goes out
This is the step that matters most, and it's easy to overlook. The lesson doesn't go straight from AI to student. A teacher sees it first, can edit the explanation, regenerate the quiz, or adjust the framing if something doesn't sit right — the AI drafts, the teacher decides. For a five-minute review, that's a meaningfully different experience than writing the whole thing from scratch, but the teacher's judgment is still the last word on what a student actually receives.
Step 5: Delivery and tracking
Once approved, the lesson can be delivered straight into Google Classroom as an assignment, so it shows up exactly where a student already looks for their work — no new app to check, no separate login. From there, a teacher can see who's completed it and who hasn't, which turns "did Maya ever catch up on that unit?" from a guess into an actual answer.
What this replaces
Before something like this, catching a student up meant one of a few things: a teacher rewriting yesterday's lesson from memory during their prep period, a hallway conversation that covers maybe 30% of what was actually taught, or — realistically, most of the time — nothing at all, because there simply wasn't time. None of those options scale to a class of thirty, let alone a school of a thousand.
What it doesn't replace
It's worth being direct about the limits here too. This isn't a substitute for a teacher's relationship with a student, and it's not meant to be the only intervention for a student who's chronically absent for reasons that need a counselor or an attendance officer, not a lesson summary. What it's built for is the much more common case — a student out for a day or two who just needs a clear, accurate way to catch up on what they missed, so a short-term absence doesn't turn into a long-term gap.
Five minutes, in practice, covers the upload, the review, and the send. That's the whole point: not to make catch-up work perfect, but to make it fast enough and consistent enough that it actually happens every time, for every student, instead of only when a teacher has a spare planning period and a good memory.