Skip to content

Guide · Platform evaluation

How to evaluate a school platform before you buy

To evaluate a school platform, test the product that exists today against the school’s own work. Confirm the product name and release status, trace ordinary workflows across teacher, student, parent and administrator roles, count the implementation work, and obtain written privacy, export and exit evidence for the exact service. Easy Edu’s timetable screens are illustrative, so its modules must be confirmed first.

Reviewed 14 October 2026 · Published by EASY EDU SDN BHD

On this page8 sections

Key takeaways

What should a school carry into the decision?

  1. Confirm the product name, release status and current module list before treating any screen as a capability.
  2. Test ordinary workflows and their exceptions across every role that creates, approves, corrects or reads a record.
  3. Count configuration, migration, identity setup, training, support and school staff time as part of the cost.
  4. Get written privacy, retention, export and deletion evidence for the exact service, and test the export before signing.

Scope. A vendor-neutral method for schools. External sources are cited as context only; none of them describes, validates or partners with Easy Edu.

Download the evaluation worksheet Email Easy Edu an evidence request
01

Which school problem should the platform solve?

Name the work that causes delay, duplicate entry, missed messages or uncertainty today, who does it and who lives with the result. Then write one acceptance statement the school can observe, for example: an authorised staff member corrects a timetable change once, every affected role sees the approved value, and the earlier value stays visible in the history. That is a test, not a promise from any vendor.

Buying is not the same as using. The UNESCO 2023 Global Education Monitoring Report notes that in one United States analysis about two-thirds of education-software licences went unused.

  1. 01Current process. The steps staff follow today, including the workarounds.
  2. 02People affected. Who enters, approves, corrects and reads the record.
  3. 03Decision test. The observable result that would change the decision.
  4. 04Evidence window. The dates on which the school will test and decide.
The four parts of a problem statement, written before any vendor demonstration.
02

How can a school separate product status from product vision?

Ask for the product name, release status, supported devices and the current module list, then give every item one of four labels. A released item needs a current demonstration and a dated document. A planned item needs a written commitment before it can enter the contract. A good visual concept is useful for discussion, but it is not proof of working software or of current customers. How to tell a concept screen from a real feature sets out the signs of a mockup and how to test a demo screen inside the meeting.

Status key
Evidence each label needs
01ReleasedCurrent demonstration plus a dated product documentShow it
02PlannedWritten commitment and date before procurementCommit
03IllustrativeA design concept; supports no capability claimNot a feature
04Out of scopeNamed and excluded so nobody assumes it laterExcluded
The four status labels. Easy Edu’s timetable screens sit in row 03, Illustrative, until the company publishes a dated product record.
03

Which complete workflows should a school test?

Pick two or three ordinary scenarios, such as a timetable change, an attendance correction or a result release, and follow each one from first entry to the last person who reads it. Run the normal path and one exception. Success for one role does not prove the experience for another, so the teacher, student, parent and administrator access guide and the role information-flow map set out who to include.

Input
Who enters the change, on which screen, and when in the school day.
Permission
Which roles may view, change or approve it, and who grants that right.
Exception
A guardian of several children, a transferred student or a substitute teacher.
Correction
Who fixes a wrong value, and whether the earlier value stays visible.
Notice
How each affected role learns that the record changed.
04

How should implementation effort be evaluated?

Ask for a written implementation plan and cost the work around the software, not only the fee. For each task, name who does it at the school and who does it at the vendor, and ask what happens if the academic calendar moves. Easy Edu has not published a delivery model, so treat the table below as questions to put to any vendor. The school software onboarding checklist covers the rollout itself.

Work itemQuestion to askEvidence to request
ConfigurationWho sets up classes, roles and timetables?Written plan with milestones
Data preparationWhich records move, and who cleans them?Migration scope and a test import
Identity setupHow are accounts created and ended?Account lifecycle description
TrainingWho trains staff, and for which workflows?Training plan per role
SupportWho answers, how, and within what time?Support terms in the contract
Implementation work to cost before signing; each row needs a named school owner and a named vendor owner.
05

Which privacy and security evidence should be requested?

Ask each vendor for its own current documents; Google for Education’s privacy and security material shows the topics buyers typically examine, such as administration, privacy settings and data ownership, but says nothing about Easy Edu. Malaysia’s Personal Data Protection Department sets out seven principles under section 5(1) of Act 709, which gives general context for the questions; the actual arrangement still needs contractual and professional review. The school data questions guide turns the list into requests.

The first-meeting privacy question set covers what to ask before any evidence is produced.

The law may not do this work for the school: UNESCO’s 2023 report found only 16% of countries explicitly guarantee data privacy in education by law.

  • Privacy notice and a data-flow diagram for the proposed service
  • Who decides and who processes, hosting location and subcontractors
  • Access controls, audit history and the retention period for each record type
  • Incident process, with the contact and the notice the school would receive
06

How should a school test export and exit before adoption?

Define the exit test before entry. Request a sample export using invented data, open it in the tools the school actually uses, and check that identifiers, fields, attachments and timestamps still make sense. Then ask how live data, backups and logs are deleted and who proves it. The data ownership, export and deletion guide gives the full question set.

Exit testWhat to requestPasses when
Export formatSample export of invented recordsFields and attachments open intact
Timing and costWritten time and fee for a full exportBoth are stated in the contract
DeletionProcess for live data, backups and logsWritten confirmation is provided
HandoverNamed contact for the transitionAn owner and a date are agreed
A sample exit test: format, timing, deletion and handover, each passed only on written evidence.

Quick answers

What do schools ask about platform evaluation?

Does a concept screen prove that a school-platform feature is live?

No. Label every item released, planned, illustrative or out of scope, then request a current demonstration and dated documentation for anything described as released. Easy Edu’s timetable screens are illustrative and do not establish live modules, integrations, users or controls. Spotting a mockup in a demo lists the signs and the in-meeting tests.

Which workflows should a school test?

Choose ordinary scenarios such as a timetable change, an attendance correction, a result release or a guardian query. Trace each input, permission, exception, correction and notice across roles, and note the product version you saw.

What exit evidence should be requested before adoption?

Request a sample export, the formats and fields included, the time and cost of a full export, the deletion process for live data, backups and logs, written confirmation of deletion, and a named owner for the handover.

Sources

Which sources informed this guide?

These sources give general context. They do not endorse Easy Edu or describe its products. More guides are listed in the Easy Edu insights index.

Next step

Ready to run the evidence check as a session?

Use the self-run agenda to assign roles, trace one scenario and record every evidence gap in a single register.

EVERYTHING ON THIS SITE

Every EASY EDU guide and page