A demonstration should let your team observe real workflows and ask about exceptions. Prepare questions that connect the platform to daily teaching and administration.
A practical starting point
A centre sees an impressive sales tour but never checks how a teacher corrects an attendance mistake or shares a portfolio privately.
Turn the idea into a working routine
- Prepare three fictional journeys covering a normal lesson, a correction and a parent query.
- Ask the presenter to show each task from the relevant staff or parent role rather than only an administrator’s account.
- Record confirmed capabilities, limitations and follow-up questions separately before comparing options.
Measure what matters
Review whether the team can explain how each required task works. An unanswered question should remain visible in the decision record.
Assuming every demonstrated feature is included in every plan can lead to an inaccurate comparison.
What should the team agree before putting this into practice?
Agree which features, support arrangements and costs require written confirmation before making a purchase decision.
MAKE IT PRACTICAL
Your planning checklist
Use this checklist during a team discussion. It tracks your planning progress, not a score of your institution’s quality. Selections stay in this page and are not submitted.
A good demonstration answers your team’s questions.
About this archive: 22 July 2024 is the collection’s reference date. This article was prepared and published on 7 November 2026. It is AI-assisted editorial content; examples are illustrative and do not describe a specific customer deployment.
