FIELD GUIDE / EVIDENCE FIRST
Questions to Ask in a School Platform Demo
Treat a school platform demo as an evidence session, not a feature tour. Give the vendor one real school scenario, ask to see it in every relevant role, separate released functions from concepts or planned work, and record the exact configuration, evidence, exclusions, owner and follow-up test before deciding on a pilot.
Reviewed draft · 14 September 2026
KEY TAKEAWAYS
What should the reader carry into the decision?
- Send the scenario and questions before the meeting so the vendor can prepare the right configuration.
- Ask whether each screen is a concept, a configured demonstration or a released workflow available in the proposed package.
- Test one record from creation to correction, notification, export and closure instead of viewing disconnected screens.
- Record what was shown, the evidence date, exclusions and the person responsible for each unanswered point.
- Move to a pilot only when the most important claims have a repeatable test and a named acceptance rule.
Method and scope. Prepared from the cited public sources and the verified client facts available for this article.
What decision must this demo help the school make?
Begin with one decision and one ordinary school-day scenario. For example: a teacher records an absence, an authorised person corrects it, a parent or guardian sees the permitted update, and an administrator produces the record needed for follow-up. Name the year group, devices, connection conditions, languages and people involved. A broad request to ‘show the platform’ gives the presenter control of the agenda and leaves the school with little comparable evidence.
Write the acceptance question before the meeting: what must the school see to decide whether a controlled pilot is justified? UNESCO puts it directly: “The first question should be: What are the most important challenges in education?” Use that principle to keep the demonstration anchored to a real problem, while recognising that general UNESCO guidance does not validate any particular vendor or product.
Is the vendor showing a concept, a demo configuration or a released workflow?
Ask the presenter to label every important item as one of three things: an illustrative concept, a configured demonstration, or a released function included in the exact offer under review. Then ask for the product name, version or release date, package or licence level, dependencies and written documentation. A polished screen can communicate an idea without proving that the workflow is available to a school.
For anything described as planned, record the dependency and proposed date separately from the purchasing decision. Do not score planned work as if it exists. For anything described as released, ask a second person to repeat the action in the same configuration or capture a dated support page that explains it. The result should be a claim register with evidence, not a collection of screenshots without context.
Can the vendor show the same record through each relevant role?
Choose one sample record and follow it through the role views the vendor says are available. For each role, record whether the person can view, create, correct, approve, download or share the item. Ask what happens when a student changes class, a staff member changes duties, a parent or guardian relationship changes, or an administrator delegates work temporarily. The school should define the roles it needs; the vendor should demonstrate how the proposed configuration handles them.
Ask who can see personal data, why that access is needed and who approves an exception. Malaysia's Personal Data Protection Department publishes seven principles as general context for personal-data handling. Those principles do not prove that a platform has suitable access controls, and they do not determine the parties' legal roles without the actual arrangement, so keep the answer as a documented question for the vendor and the school's advisers.
How are accounts created, changed, recovered and closed?
Ask for four short account tests: create a user with the minimum intended access, change that user's role, recover access without bypassing approval, and close the account while preserving any record the school must retain. Include temporary staff, leavers, transferred students and changed parent or guardian relationships. Record which tasks require a central administrator, which can be delegated and what evidence remains after a change.
NIST SP 800-53 provides neutral vocabulary for account management, access enforcement and least privilege. Use it to make the questions precise, not to claim that the vendor follows NIST. The useful evidence is product-specific: the configured permission, the change history, the person who approved it and the result when a user attempts an action outside the agreed role.
What data, export, retention and deletion answers belong in the record?
Ask the vendor to name the data categories used in the scenario, their purpose, who can access them, where each answer is documented and what happens at the end of service. Request an export demonstration that includes the format, attachments, identifiers, timestamps and any information that is excluded. Ask how the school checks completeness, how long the export takes, who can request it and whether a fee or service window applies.
Separate retention, deletion and backup questions. Ask what event starts each period, who approves deletion, how archived or backup copies are treated, what exceptions may apply and what evidence confirms completion. The Malaysian regulator's FAQ lists six data-subject rights as general context. It does not establish which organisation has a particular role in this proposal, so the school should take appropriate advice on the actual contract and data flow.
Does each claimed integration work in the proposed configuration?
For every claimed integration, name the sending system, receiving system, data fields, direction, trigger, identity method and failure behaviour. Ask the vendor to run a transaction, deliberately cause a safe failure, show the error and explain who retries or reconciles the record. A logo, marketplace listing or standards badge is not proof that the exact versions and configuration in the proposal work together.
1EdTech describes Learning Tools Interoperability as a technical standard for connecting learning tools with an institution's learning environment. If LTI is relevant, ask which version and services the products support and request evidence for that combination. Do not infer LTI support from this article or from a general product category; the vendor must identify and demonstrate it in writing.
What should the school record before agreeing to a pilot?
Close the meeting with one evidence register. For each important claim, capture the exact wording, status, product and package, evidence link or file, date, limitation, owner and next test. Mark unanswered questions as open; do not turn a verbal ‘yes’ into a confirmed capability. Ask the vendor to correct the record if the school's notes do not match what was intended.
Define the pilot gate from that register. State which workflows will be tested, who may use sample or real data, how issues will be recorded, what counts as acceptable performance and what will stop the pilot. A demonstration can justify further testing, but it cannot prove implementation quality, user adoption or future service.
QUICK ANSWERS
Frequently asked questions
How many scenarios should a school ask to see in a platform demo?
Use a small number of representative scenarios and take at least one of them end to end. The right number depends on the decision, but each scenario should expose roles, data movement, corrections, approvals, export and failure handling rather than adding more disconnected screens.
Is a live demo enough evidence to choose a school platform?
No. A demo shows what happened in one prepared configuration. Confirm the exact product and package in writing, test the important claims again in a controlled pilot, and review contractual, privacy, support, export and exit answers before adoption.
What should go into the demo evidence register?
Record the claim, product and configuration, whether it is released or planned, what was shown, the evidence link, date, exclusions, answer owner, follow-up test and decision status. Keep unresolved items open rather than converting them into assumptions.
See every guide in the insights index →
EXTERNAL CONTEXT
- UNESCO Global Education Monitoring Report 2023 — Technology in education
- Principles of Personal Data Protection
- NIST SP 800-53 Rev. 5
- Personal Data Protection Department — Frequently Asked Questions
- 1EdTech — Learning Tools Interoperability
External sources explain category or evaluation context. They do not endorse Easy Edu or prove its product capabilities.
NEXT MOVE
Choose the next check
Use the related guide and verify the exact facts that apply.
Send Easy Edu a written evidence request