How to evaluate a school platform before you buy
Compare verified workflows, role permissions, implementation effort, support, privacy, data ownership, exports and exit conditions against the school’s actual needs.
Insights · Guides for schools
School platform evaluation guides
Easy Edu publishes seventeen vendor-neutral guides for schools choosing a digital platform, in three groups. Seven cover choosing and rolling out a platform: the main evaluation guide, a self-run evaluation session, demo questions, telling a concept screen from a real feature, integrated platform or separate apps, a pilot before buying, and an onboarding checklist for after the decision. Four cover role information flow, role access, duplicate entry and what parents see. Four cover data export, governance, ownership, deletion, privacy and moving records into a new platform. Each guide gives a school questions it can put to any supplier.
Reviewed 20 October 2026
7 guidesChoosing and rolling out a platformEvaluation, session agenda, demo questions, concept screens, architecture, pilot, onboarding
4 guidesRoles and accessWho sees, changes and approves each record, what parents see, and how to test it
4 guidesSchool dataExport, governance, ownership, deletion, privacy and moving records
Unsure?Match your situation to a guideSeventeen common situations, one guide each
Vendor-neutralFor school decision-makers
All seventeen guides
Which guides does Easy Edu publish?
Every guide on the site is listed here, grouped by the decision it supports. Each label names its group; each line says what that guide actually asks a school to do.
How to run a school platform evaluation session
A self-run agenda: define the decision, map the four roles, trace one ordinary school scenario, inspect the data path and close with an owned evidence register.
Questions to ask in a school platform demo
Give the vendor one real school scenario, ask to see it in every relevant role, and separate released functions from concepts or planned work.
Concept screen or real feature in a school demo?
Spot the signs of a mockup, match the evidence to each of the four states, and test a demo feature inside the meeting before anything is signed.
Integrated school platform or separate apps?
Weigh both options against source-of-record decisions, identity and access, data movement, support ownership, verified integrations, full cost and exit path.
Should a school run a school platform pilot?
Pick one small slice of the school, agree the scope, measures and end date in writing, and set the decision rule before the first login.
School platform contract checklist before signing
Renewal and notice dates, what the price covers, the uptime figure, backups, the processing terms and the exit, checked in writing before anyone signs.
A school software onboarding checklist
Roll out in controlled phases, from an accountable owner and frozen scope through a limited pilot to a support, export and exit handover.
School platform usage review after go-live
Whether the platform is really used after go-live: active accounts by role, work still done outside it, the yearly records check and the renewal decision.
School role map: who sees, changes and approves each record
Map what teachers, students, parents or guardians and administrators can view, create, change, approve and export, including temporary access and corrections.
Reduce duplicate school record entry
Count the places one fact is entered today before buying anything, ask six questions of any vendor, and test an enter-it-once claim on a single record.
How to evaluate teacher, student, parent and administrator access
Build a school-owned access matrix, then test account creation, role changes, exceptions, recovery and closure in the exact proposed configuration.
What should parents be able to see in a school platform?
Sort the record into what parents see, what the school releases by decision and what stays internal, then test the parent view in the demo.
School software data export and governance questions
Ask for written evidence on ownership, controller and processor roles, hosting, subcontractors, audit records, retention, export, deletion and incident handling.
School platform privacy questions for a first vendor meeting
Settle who is data controller, turn Act 709’s seven principles into one question each, ask where the records sit and who may reach them, and leave the meeting with the answers written down.
School data ownership, export and deletion questions
Get product-specific answers on export content and format, retention triggers, backups and end-of-service handover, then test the promised export path.
How to move school records into a new platform
Audit what the school holds, decide group by group what crosses, agree the field mapping in writing, then check one test import against the source.
01
Which guide should a school open first?
Start from the situation the school is in today, not from the order of the list. The table matches each common situation to one guide and to the working document the school should have in hand when it finishes.
| The school’s situation | Open this guide | What the school leaves with |
|---|---|---|
| A first vendor meeting is booked and the school has to ask about privacy and its PDPA duties | Privacy questions | A written record of who controls the data, where it sits and who may reach it |
| Needs are not yet written down and product status is unclear | Platform evaluation | A matrix separating released, planned and illustrative items |
| The team must agree its questions before meeting a supplier | Evaluation session | An ordered agenda and an owned evidence register |
| A vendor presentation is booked | Demo questions | A note of what was shown, in which role and configuration |
| A screen in the demo may be a concept rather than a released feature | Concept screen or real feature | A state, its evidence and the vendor person who confirmed it, for each screen |
| One platform or several apps is still open | Integrated or separate apps | A weighted comparison that includes full cost and exit |
| The school wants to try a platform in a few classes before it commits | Platform pilot | A written scope, measures, end date and decision rule, agreed before day one |
| A contract or order form has arrived and is waiting to be signed | Contract checklist | A written answer to each of the six core terms, and the renewal notice date in a named person’s calendar |
| Permissions, corrections or guardian access are unclear | Role information flow | A permission map for each school record |
| The same fact is being typed into more than one place | Duplicate record entry | A count of where one fact is entered today, and six questions for the vendor |
| A shortlisted product must be tested account by account | Role access | A role-access matrix ready for sign-off |
| The school must decide what parents will see | Parent view | A parent-view list: what parents see, what the school releases by decision and what stays internal |
| Governance or IT reviewers need written data answers | Data questions | A data evidence register |
| Contract terms on ownership and exit are being drafted | Ownership, export and deletion | A tested export and a written deletion route |
| The school is switching platforms and its records must move across | Moving records | A written field mapping and one test import checked against the source |
| The decision is made and rollout comes next | Onboarding checklist | A stop-or-proceed decision for each phase |
| The platform is live and the school wants to know whether it is used | Usage review | Active accounts counted by role against licences, and a written keep, retrain, resize or exit decision before renewal |
02
How are these guides written?
The guides are written for school leaders, administrators, teachers and governance reviewers who have to choose, or say no to, a school platform. They describe how to evaluate any supplier. They are not product pages: the timetables and class views on the Easy Edu homepage are illustrative interface examples, and none of these guides describes a released Easy Edu feature.
Where a guide relies on an outside source, such as Malaysia’s Personal Data Protection Department on the principles of Act 709, it names and links that source in the text. Terms that recur across the guides are defined in the school platform glossary.
Four rules apply in every guide:
- Start from the school’s current problem, not from a supplier’s feature list.
- Ask to see a workflow in every affected role before accepting it as released.
- Keep each unanswered question visible, with an owner, until it is resolved.
- Date every piece of evidence and note which product version it describes.
EVERYTHING ON THIS SITE
Every EASY EDU guide and page
- About EASY EDU SDN BHD
- Contact Easy Edu
- Easy Edu FAQ: company, product status and platform evaluation
- School platform evaluation glossary
- Privacy notice for easyedu.com.my
- How to run a school platform evaluation session
- How to evaluate a school platform before you buy
- School role map: who sees, changes and approves each record
- School software data export and governance questions
- Questions to ask in a school platform demo
- Reduce duplicate school record entry
- A school software onboarding checklist
- Integrated school platform or separate apps?
- How to evaluate teacher, student, parent and administrator access
- School data ownership, export and deletion questions
- School platform privacy questions for a first vendor meeting
- Concept screen or real feature in a school demo?
- What should parents see in a school platform?
- Should a school run a school platform pilot?
- How to move school records into a new platform