Already on TutorCruncher? Here's the One Thing It Still Can't Tell You

Does TutorCruncher track student progress and learning outcomes?

No — not in the sense most tutoring company owners mean. TutorCruncher tracks the operations around learning: it records that a session happened, who attended, who was invoiced, who paid, and what each tutor is owed. What it does not track is whether the student actually learned anything in that session, which topics they’re still weak on, or which students are quietly disengaging and about to cancel. That’s not a flaw in how you’ve set it up — it’s a boundary of what the product is built to do. If you’re on TutorCruncher and you’ve felt this wall, you’ve found the one thing it still can’t tell you.

First, credit where it’s due

TutorCruncher has been in this market for over a decade, and 1,800+ businesses run on it globally. There’s a reason for that.

For pure operations, it’s the benchmark:

• Automated invoicing and payroll — set pay rates once, and it calculates what each tutor is owed and what each client owes. No spreadsheets.
• Xero and QuickBooks integration — your accounts export directly, which saves a bookkeeper hours a week at scale.
• GoCardless and Stripe — direct debit collection built in, so fewer failed payments and less chasing.
• A CRM and prospect pipeline — enquiries come in, get tagged, get converted.
• Built-in video — its own integrated room, no third-party licence needed.
• Transparent pricing — three public tiers (£25, £60, £200/month), so you know what you’re paying before you sign.

If your problem is admin overwhelm, TutorCruncher solves it. None of what follows is a knock on the ops. It’s about the part of the job that sits after the invoice goes out.

The question your software can’t answer

Picture the end of a month. TutorCruncher tells you, cleanly, that your company ran 200 sessions. It tells you who attended, who was billed, who paid, and which tutors worked which hours. Everything reconciles.

Now a parent emails: “We’ve been coming for three months. Is my daughter actually improving?”

Open TutorCruncher and try to answer that. You can confirm she attended eleven sessions. You can confirm the invoices were paid. You might even have eleven lesson reports — a free-text note each tutor wrote up afterwards. What you can’t do is turn those into a straight answer: which topics she’s mastered, where she’s still dropping marks, whether the trend line is up or flat. That was never captured as structured data — it lives in eleven tutors’ wording, and free-text notes don’t add up into a progress picture.

That’s the gap. It has nothing to do with how well you run the business. It’s that session data and learning data are different things, and an operations tool only holds the first one.

The cost of that gap is not abstract:

• You can’t see churn coming. A student who’s plateaued looks identical to a thriving one in your billing system — right up until the cancellation email arrives. By then it’s too late to intervene.
• You can’t prove your value. Parents don’t renew because sessions ran on time. They renew because they can see their child improving. Without evidence, every renewal is a leap of faith — and faith is the first thing to go when household budgets tighten.
• You can’t manage quality across tutors. With ten tutors, the hardest thing to keep consistent is teaching quality. If all you can see is hours worked, you can’t tell the tutor who’s genuinely moving students forward from the one who’s just showing up.

To be fair to TutorCruncher, it does have reporting — it’s just the reporting an operations tool is built for. Its analytics track the health of your business: revenue, lesson hours, tutor performance, client spend. Its lesson reports are those free-text notes. What it doesn’t have is a gradebook or a topic-by-topic view of whether a student is actually mastering the material over time. That’s not a flaw, it’s a different job. TutorCruncher was built to run your operations, not to measure the learning — and it’s genuinely good at the first one.

What does closing the learning-visibility gap look like?

The fix isn’t a better report inside your ops tool. It’s a different layer entirely — one that captures whether learning happened, the same way TutorCruncher captures whether a session happened. That layer needs to do three things your operations software structurally can’t.

Tutors should walk into every session already knowing where the student dropped marks. Not from notes they remembered to write — from marked homework and practice already sitting in the system. The tutor sees the weak spots before the student arrives, so the session starts where it’s actually needed instead of with ten minutes of “so, where did we get to?”

Homework should mark itself and feed a live mastery picture. Here’s the part almost every tutor feels but few tools solve: they want to give students extra questions to work on — it’s how you actually lift a result — but sourcing them, writing them, and marking them by hand takes time no tutor has spare. So a good learning layer does that for them: a tutor sets homework once from a curriculum-aligned question bank, the student submits, it’s auto-marked, and the result updates that student’s topic-by-topic mastery immediately. No red pen, no manual entry, and — crucially — no learning data that evaporates at the end of the session.

Parents and tutors should see the evidence without anyone writing it up. This is the dashboard an ops tool doesn’t have: per student, it shows their weak topics, how they’ve improved over time, how many questions they’ve done and which ones — the whole picture of the learning, not the billing. From that same data it generates automated progress summaries that go straight to the parent, by email or inside the app, without a tutor staying up to write them. That is the single most powerful retention tool a tutoring company has, and right now most companies are trying to produce it by hand, inconsistently, if at all.

Put together, that’s learning visibility — and it’s the layer that turns “we ran 200 sessions” into “here’s exactly what those 200 sessions produced, student by student.”

Do you have to replace TutorCruncher to close the gap?

No — you don’t. Here’s the part that matters if you’re already on TutorCruncher: closing this gap doesn’t mean replacing your ops stack. The invoicing, payroll, Xero export and scheduling you’ve already set up are genuinely good — keep them. The learning layer sits on top, adding what an operations tool was never built to provide. Plenty of operators run both: TutorCruncher for the money and the schedule, a learning layer for the part that decides whether parents renew.

The simplest way to put it:

Already on TutorCruncher? They run your operations. We show you whether students are actually learning.

If that’s the wall you’ve hit, the next step is to see the two side by side — what each tool is for, where the line sits, and what the learning layer puts in front of you that your billing system can’t.

See the full ClassQuill vs TutorCruncher comparison → — the head-to-head feature breakdown and which tool fits which problem.

Book a 20-minute demo → — we’ll show you the owner dashboard and the parent progress view using a real (anonymised) student, so you can judge the gap for yourself.