Why your lesson-package spreadsheet always ends up a mess
A very ordinary afternoon
A parent texts you: "Hi — we've got 4 lessons left, right? I thought we bought a pack of 20."
You open the spreadsheet you've kept all year, find the row, count the lessons already taught — 12. Twenty minus twelve is eight. But the parent says four.
That's a gap of four. Where did they go? You start scrolling back: that cancellation in March — did you deduct it or not? There was a makeup in April — was it a makeup, or did you charge it as new? Her younger sister came for two lessons somewhere in the middle — did those land on the same row?
Twenty minutes later you still aren't sure who's right. So you probably say, "Let's call it 8, and I'll keep a closer eye on it next time." Which is to say: you eat the difference.
This isn't because you're careless. Tracking lesson packages in a spreadsheet will go wrong past a certain size.
Why it always breaks
A lesson package looks like simple subtraction: buy 20, teach one, subtract one. But in real life "teach one" has too many variants, and for each one Excel makes you do the judgment call and you edit the cell:
- Does a cancellation count? Cancel 24 hours ahead — no charge; cancel same-day — charge. That rule lives in your head, not in the spreadsheet. The day you're busy and forget, you deduct wrong.
- How do you log a makeup? A makeup replaces a lesson cancelled earlier and shouldn't be deducted again — but when you open the sheet, all you see is "taught a lesson today," and it's easy to subtract one more.
- Two kids sharing one package. The older one takes 3, the younger takes 2, all from the same 20. Two rows or one? Sooner or later they get tangled.
- A mid-way price change or a renewed pack. The old pack has 3 left, the new one has 20 — which do you draw from first? A month later even you've forgotten where you left off.
- You can't edit it on your phone. Right after a lesson is the best moment to log it, but Excel is fiddly to open and edit on a phone, so you tell yourself "I'll do it tonight" — and then forget.
Each one is easy on its own. What's hard is that they stack up, span months, and rely on one person's memory to stay correct. Excel never reminds you "there's a judgment call here." It's just a quiet cell, waiting for you not to slip. People slip.
We got this wrong ourselves
A confession, so this doesn't read as armchair advice.
ActiKidz does automatic lesson deduction — finish a lesson, the system takes one off the package. Sounds trivial. But we had an early bug: when a teacher taught a cash-paid lesson, or a free makeup, the system, on marking it "complete," didn't check whether that lesson should come off the package at all — as long as the student had a package, it quietly deducted one.
The result: a student paid cash for that lesson, yet the package silently lost one. The same "numbers don't add up" the parent hit at the top of this post — except this time the mistake was ours.
The fix was to add a check to the deduction: only lessons settled via the package draw it down; cash and free makeups either don't, or require the teacher to explicitly tick "deduct this one from the package too."
The point: the hard part of lesson deduction was never the subtraction — it's the "should this one be deducted at all" judgment. In a spreadsheet you make that call in your head, and get it wrong one time in a hundred. Hand it to a system, and the system has to have thought through every case — which we only finished doing after we got it wrong.
How a system holds this together
Not the breezy "automatic" — it turns each of those judgment calls into one explicit rule plus one clear record:
- Deduct on completion, but check how it was paid. Package lessons deduct one on completion; cash and free makeups don't touch the package unless you say so. Double-deduction is prevented at the source.
- Cancellations and makeups have their own states. A cancellation is a cancellation, a makeup is a makeup — neither gets folded into "taught a lesson today" and accidentally deducted. Set the rule once; the system enforces it.
- The balance is one number everyone can see. You see it in your dashboard; the parent sees how many lessons are left on their end. They stop asking "how many left?" — they just check.
- A reminder 7 days before the pack runs out. No more awkwardly raising renewal only after a parent hits zero. The system warns ahead, and you both have time to plan.
The core isn't "less work" — it's moving the judgment and the memory out of your head. Your head is for planning and teaching lessons, not for remembering whether she cancelled that day in March.
But Excel isn't always wrong
No overselling. If this is you, a spreadsheet is genuinely fine — don't bother:
- Very few students (say, under 5), and you know everyone's balance with your eyes closed;
- No prepayment — you charge per lesson, so there's no "package" to track;
- No cancellation/makeup churn — your schedule is rock-steady.
Lesson-package tools solve the complexity that comes with scale. When you have few students and simple arrangements, the value isn't obvious, and forcing in a tool is just overhead. When you start thinking "I have to dig for ages just to tell a parent how many lessons are left" — that's the signal it's time.
tl;dr
A lesson-package spreadsheet ends up a mess not because you're careless, but because the "should this one be deducted" judgment — stacked with cancellations, makeups, shared packs, price changes, and months passing — eventually breaks when a human brain is the backstop. We got our own auto-deduction wrong once, for exactly that root cause.
The value of a tool isn't "automatic subtraction" — it's turning that judgment into a fixed rule, and the balance into one number everyone can see — so you and the parent never have to reconcile "how many left" again.
Few students, no prepayment? Keep using Excel. When you're spending ages just to answer a parent, come take a look.
Want to see how lesson packages deduct and remind in ActiKidz: Features / Pricing / Contact us.