Questions to Ask in a School Software Demo

The demo is booked for Thursday at eleven. The principal, the bursar and one senior teacher will join, and the vendor will share their screen for an hour. If nobody prepares, the hour will follow the vendor's script: a tidy dashboard, a sample student called "Test Student", a fee receipt printed in two clicks. Everyone will nod. Nothing will have been tested.

A demo is the cheapest chance you will ever have to find out how a system copes with your real problems. This post gives you questions to bring, grouped by who should ask them, plus what a good answer sounds like.

Before the call: send your scenarios in advance

The single most useful thing you can do is email the vendor three or four real scenarios a few days before the demo and ask them to show those, not their standard tour. Good vendors welcome this. A vendor who refuses, or who "will get to it at the end" and never does, has told you something.

Examples of scenarios worth sending:

• "A family has three children in different classes. The youngest gets a sibling discount and the eldest has a partial scholarship. Show us the fee statement the family receives."
• "A teacher marks a student absent, then the student arrives late. Show us how that is corrected and who can see the correction."
• "A student moves from Grade 5A to 5B in the middle of term. Show us their attendance, marks and fees afterwards."

Questions for the bursar or accounts lead

1. "Show me a fee concession being granted, then reversed." You want to see that both actions are recorded with who did them and when.
2. "What happens when a payment is recorded against the wrong fee head?" Correcting mistakes is a daily task; watch how many steps it takes.
3. "How does a student who leaves mid-term get settled?" Partial terms are where many fee systems break down.
4. "Which payment methods work in our country?" Online payment options vary by region. Ask for a specific answer for your location, not a general yes.
5. "Show me the defaulters list and how reminders go out." Ask how messaging works in your country too, since SMS and messaging coverage also varies.

Questions for teachers

1. "Let me mark attendance for a class of 40 myself." Ask to take the controls, or at least to direct each click. Count the steps.
2. "How do I enter marks for an exam, and what happens if I make a mistake after submitting?"
3. "What does this look like on my phone?" Many teachers will use the system on a phone between lessons. Ask to see it on a small screen, live.
4. "What can I see about a student in my class, and what can I not see?" A good answer is specific, for example that teachers see their own classes rather than the whole school.

A teacher in the room is worth more than any feature list. If the senior teacher looks lost after twenty minutes, the other forty teachers will be too.

Questions for the principal or owner

1. "What will families actually see?" Ask for a walk through the parent view: fees, attendance, results, messages.
2. "How do I see the whole school on one screen?" And if you have several campuses, how do you compare them without asking each for a spreadsheet?
3. "Who controls what each member of staff can do?" Watch someone's permissions being changed. Ask whether a change takes effect straight away.
4. "Can we get all our data out if we leave?" Ask what format, how long it takes and whether there is a charge. A vendor who is confident in their product will answer this plainly.

Questions about support, onboarding and cost

• "Who will help us during the first month, and how do we reach them?" Ask for names or roles, response times and support hours in your time zone.
• "What does onboarding include?" Data import, configuration and staff training each take time. Find out which are included and which cost extra.
• "What will we pay in year two and year three?" Ask about price increases, per-student charges and anything charged separately, such as messaging.
• "What does the typical school get wrong in the first term?" An honest answer to this is one of the best signals you will get.

How to read the answers

Good answers share some traits. They are shown on screen rather than described. They name a limitation where one exists ("we do not support that today, here is how schools handle it"). They do not lean on "it is fully customisable" for every question, because customisation usually means time and money.

Warning signs worth noting:

• Repeated "that is on our roadmap" for things you need on day one.
• A switch back to the prepared script whenever a scenario gets awkward.
• Vague answers about data export or price in later years.
• No one able to say what support looks like after go-live.

Consider a school where the bursar, Rahul, asked to see a mid-term leaver settled. The first vendor said it was "simple" but never showed it. The second showed it in four steps, then pointed out a case it did not handle and explained the workaround. Rahul trusted the second vendor more, precisely because of the admitted gap.

After the demo: score it the same day

Memories blur after three demos. Within an hour of each call, have everyone score the system against your scenarios on a simple scale, for example 1 (could not show it) to 5 (showed it clearly and it fitted our process). Add one line of notes per scenario. Compare scores across vendors before anyone discusses impressions. This keeps the loudest opinion from settling the decision.

Common mistakes

• Only senior leaders attend. The people who will use the system daily spot problems leaders miss.
• Accepting a recording instead of a live demo. A recording cannot answer your questions.
• Asking "can it do X?" The answer is always yes. Ask "show me X" instead.
• Forgetting the family view. Families are the largest group of users and the loudest when something goes wrong.

Where to go from here

For the wider selection process, from defining needs to checking references, see our guide to choosing school management software. If you want to put these questions to Scolvia, you can book a demo and send your scenarios in advance; we would rather show you your hardest case than our easiest one.