Teachmint began as a teaching and classroom platform and expanded into school administration. SchoolDeck has only ever been the administrative record and carries no teaching layer at all. The comparison is therefore between two different centres of gravity rather than two versions of the same product.
Products are shaped by the problem they were built for first, and that shape persists long after the feature lists converge. A platform that began in the classroom organises itself around a class; a system that began in the office organises itself around a student record.
The right-hand column below is what to ask them, not what we claim about them. We publish SchoolDeck and do not track other vendors’ current feature sets; anything material should be verified with the vendor directly.
If your pressing problem is teaching — content, assignments, online classes — a teaching-first product is the right shortlist and we are not on it. If it is fees that do not reconcile, report cards that take three weeks, or marks nobody can audit, buy the record. Schools needing both properly should expect to run two products.
| What you are comparing | TurtleDock | Teachmint |
|---|---|---|
| Content and online classes | None. We integrate; we do not host teaching | Teaching is where the product started |
| Central object | The student record — one row per person | Ask which object everything hangs off: the class, or the student |
| Offline attendance | Works with no signal; syncs on return, conflicts surfaced | Ask what happens when a teacher marks a register with no connectivity |
| Fee concession following a family | Sibling concessions modelled natively | Ask to see a sibling concession configured live |
| Audit trail on a changed mark | User, time, before, after, reason — immutable | Ask them to show the trail for a mark changed last week |
| Report card scheme versioning | Per academic year; reprints match the original | Ask them to reprint a card from two years ago |
Schools frequently buy the half that is more visible rather than the half that is more expensive. Teaching problems are visible daily; administrative problems surface twice a year and cost far more when they do.
If both hurt, the record is the one to fix first, because its errors compound into documents a student carries for life.
Two products is a normal arrangement, not a failure. The one thing to settle on day one is which system owns attendance, because both will offer to and two attendance registers is worse than either alone.
Our recommendation is that the record owns it, because attendance feeds fee eligibility, board returns and the report card. Teaching platforms can read it; they should not be a second source of truth for it.
Phrased the way they arrive, answered so each one stands on its own.
No. We integrate with meeting tools but do not host classes, and we carry no content library. We are the record, not the syllabus, and that is a deliberate boundary rather than a gap we intend to close.
Yes. Decide the attendance boundary before the second product goes in rather than after, because unwinding two divergent registers mid-year is the hardest version of this problem.
Checked by the Implementations desk on 7 September 2026. Corrections go in the page, dated, rather than quietly.
Pricing is on the page, in the open, with the counting rule written next to it. Nobody has to book a call to find out what it costs.
See pricingForty minutes with an implementation engineer — your classes, your fee heads, your grading scheme, entered as we go. No slides, no sample school.