TurtleDock
SchoolDeck · Guide

How to evaluate a school ERP, and what a demo will not show you

Most evaluations compare feature lists, which every vendor passes. The questions that separate systems are about what happens when things go wrong: what a bad network does to attendance, what a board format change costs, who can see a fee ledger, and whether you can get your data out without asking.

We sell one of these, so read this knowing that. The questions below are ones we are happy to be asked, and you should ask them of us too.

Written by Checked by Kalyan SundaramLast reviewed

A demo is a rehearsed path through a working system on good wifi with clean data. Nothing about that resembles a Tuesday in October, which is why feature-list evaluations mislead so reliably.

Feature lists
Every vendor passes them
Ask instead
What happens when it goes wrong
Non-negotiable
Export you can run yourself
Test with
Your own fee structure and report card
01

Eight questions worth asking

  • Show me attendance with the network off. Then reconnecting. If the register needs a signal at 7:50, it will be abandoned by week three.
  • Change a report card format in front of me. Is it configuration or a support ticket? Boards revise formats, and a ticket means waiting.
  • Reprint a card from last year. Does it come back in last year’s format, or this year’s applied retroactively?
  • Can a class teacher see the fee ledger? Permissions should be per field, not per screen — a screen that mostly should be visible ends up entirely visible.
  • Who changed this mark, and when? An audit log nobody can edit, including the vendor.
  • Export everything, now. A button, not a request. Test it during evaluation, not at the end of the relationship.
  • Model my actual fee structure. With concessions, siblings, RTE and part payments. This is where generic systems fail and it is not visible in a demo of a simple structure.
  • What happens during results week? Release freezes and who is on call when a result release is blocked.
02

The three commitments to get in writing

Data export on demand, in a structured format, without a support request. Response time when something that blocks money or results breaks. And what happens to your data if you leave — how long it is retained and how it is returned.

A vendor unwilling to write those down is telling you something. So is one whose export is a PDF.

03

What we would not argue with

If you need a content library, a learning marketplace or a system that files your returns for you, we are the wrong choice and say so on the relevant pages. If your school runs on one desk and a receipt book and is content, software will add work before it removes any.

FAQ

Questions people ask

Phrased the way they arrive, answered so each one stands on its own.

What should a school ERP cost?

Per student per year is the common basis for schools. Compare on what is included rather than the headline rate — implementation, migration, messaging credits and support are where quoted prices diverge.

How long does implementation take?

Two to three weeks for a single school is realistic where the school can supply its structure and data. Longer for groups. Any quote that ignores your data quality is optimistic.

Should we run a pilot?

Yes, on one real class with your real fee structure and report card format — not a sample school. A pilot on sample data tests nothing you need to know.

Related

Read next

Provenance

Who checked this, and against what

Accountability

Checked by the Implementations desk on 7 September 2026. Corrections go in the page, dated, rather than quietly.

No call required

Tell us your enrolment, we will tell you the number.

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 pricing

Bring your own structure. We configure it live on the call.

Forty minutes with an implementation engineer — your classes, your fee heads, your grading scheme, entered as we go. No slides, no sample school.