Not a calendar problem.
A negotiation problem.
A calendar shows what has been agreed. The work in a tutoring centre is the agreeing: matching a tutor's hours to a family's inside the after-school window, then re-matching every week as life intervenes. Software that only shows the agreed sessions — a shared calendar, a spreadsheet, a whiteboard — leaves the agreeing where it was, in the owner's messages, and the owner remains the integration between every tutor and every family. The software that helps is the software that changes who does the agreeing: tutors publish availability, bookings are made against it, changes are made once, and everyone affected sees the result from their own side.
That reframing sorts the market. Any product can display a diary. Far fewer make published availability, one record per session and a family view the centre of the design, and those are the three that decide whether the owner gets their evenings back.
Seven things,
in the order they matter.
The first two carry most of the value. Published availability removes the negotiation; one record per session removes the re-keying. A centre that has only those two has already changed how it runs. The family view is third because it removes most of the inbound messages, and the tutor view fourth because it ends the private diary. Groups are fifth not because they matter less but because a centre can start without them; it cannot grow without them, and a product that treats a group as a hack — five one-to-one bookings at the same time — will hurt at exactly the point the centre needs it to help.
Packages and status is where scheduling meets billing, and it is the requirement most often missed on the demo. A session is not just booked or not; it is attended, cancelled inside the notice period, cancelled outside it, or a no-show, and each of those has a consequence for the package and the invoice. If the scheduling record does not carry the status, someone reconciles it by hand at the end of the month, which is the evening you were trying to get back.
The same session,
seen from three sides.
The design that works is one record seen three ways. The front desk sees everything: every tutor's week, every room or link, the empty slots where the next booking goes, the waiting lists. The tutor sees their own sessions and only their own — who, what subject, which room or link, what was covered last time — because a tutor who can see the whole centre's diary will, with the best intentions, start negotiating directly with families again. The family sees their sessions, the package balance, what is due and the policy that applies, so that "when is Tom's next session?" is a glance at a phone rather than a message to you.
When those three views are the same record, a session moved by the front desk appears moved to the tutor and the family without anyone being told. When they are three documents — a calendar, a message thread and an invoice — the move is made three times and one of them is wrong by Friday.
The honest list.
No product knows that your best tutor will not work Fridays, that two families on the waiting list would happily share a group, or that the evening slots should rotate between tutors for fairness. Those are decisions, and they are yours. No product decides your cancellation policy, and a product with a "no-show" button does nothing until you have decided what a no-show costs and told families before they booked. No product fills a group; it holds one you have filled. And no product makes tutors publish honest availability; it gives them a place to put it, and the centre's job is to make filling it in a condition of being on the rota.
On SprintUp, sessions and classes live in the campus with a tutor, a roster and, for online sessions, a live video link the platform generates; each student has one login to see their own sessions and what is due; tutors see their own classes; groups are classes with a roster, not a workaround. The solving is still yours, and this article's list of what software cannot do applies to it as much as to anything else on the market.
Run your own week through it,
not the vendor's.
Bring a real week to every demo: your tutors' availability, three real families including one that cancels late, one group that has four students and needs six, one no-show and one package about to run out. Ask the vendor to do each one live and count the screens. Then ask the three questions that decide most evaluations: what does the platform take from what families pay you, and at your volume in year three; can you export every family, session and payment if you leave; and where is the data hosted, under which law.
The dedicated tutoring products — Teachworks, TutorCruncher, TutorBird and others — are good at booking, and each prices differently: per student lesson, as a percentage of revenue, per tutor. We have compared SprintUp with each of them on the same criteria, with their published prices and the cases where they are the better choice: vs Teachworks, vs TutorCruncher, vs TutorBird. The buyer's guide has the full checklist and demo script.