Field guide · Comparison

Integrated school platform or separate apps?

Neither architecture wins by default. Compare an integrated platform and separate apps against the school’s own workflows: where each record is created and corrected, how sign-in and roles work, what evidence backs each integration, who owns support and outages, the full cost and the exit path. Agree the weights before scoring, and keep unproven answers visibly open.

Published by EASY EDU SDN BHD · 14 September 2026 · Reviewed 18 September 2026

On this page12 sections

Who publishes this guide. EASY EDU SDN BHD, part of ES PRODUCATION GROUPS BERHAD, publishes this guide. Its stated mission is to develop integrated digital learning solutions, so this page sets out how a school should test that approach, or any other, against its own workflows. The timetable screens elsewhere on this site are illustrative design concepts.

Method and scope. Prepared from the public sources listed below; they do not describe or endorse Easy Edu.

Key takeaways

What should a school know before comparing?

01
Start from school workflows and authoritative records, not the number of applications.
02
One interface can still hide several data stores, owners and support paths.
03
Separate apps can fit specialist needs, but every handoff between them is one the school must test and own.
04
A standards claim matters only when the exact products, versions and services support the required configuration.
05
Score evidence, operating responsibility and exit cost; do not declare a universal winner.

VIDEO

Watch: Integrated School Platform or Separate Apps? A Malaysian School Guide

Neither an integrated school platform nor separate apps wins by default. Start from your school's own workflows, such as attendance, timetable changes, assessment, parent information and reporting. Map where each record is created and corrected, test every integration claim with a real record and a deliberate failure, get support and exit terms in writing, count the full cost over the same period, and agree your scoring weights before you see any vendor's score.

Read the video transcript

Integrated platform or separate apps?

Should your school run one integrated platform, or separate apps for attendance, timetables and parents? Here is how to decide, and what to test before you sign anything.

The short answer: neither wins by default. The right choice is the one that fits your school's own work, and proves it.

One platform may remove some handoffs between systems, but more of your school then rests on one vendor. Separate apps can keep a specialist tool a department relies on, but every connection between them is one your school has to test and own.

And one thing catches schools out. One login on screen doesn't prove there is one set of records behind it.

Which school problem should it solve?

So start with the problem, not the number of apps.

List the work that drives the decision. Attendance. Timetable changes. Assessment. Information for parents and guardians. And reporting.

For each one, write down who does it today, every handoff between people and systems, where it goes wrong, and how much time it costs.

If the same information is typed into several places, say so plainly. That becomes your first test.

And if one department can't give up a specialist tool, say that too. Your honest problem decides what matters most.

Where does each school record live?

Next, follow your records.

For every important record, like a student's details, name where it is first created, which system wins when two copies disagree, who is allowed to correct it, and every place a copy is sent.

Then test a correction, not just a new entry. Fix a record at the source, and check the fix reaches every copy.

How do you test an integration claim?

Integration claims need the closest checking, whichever option you pick.

Ask the vendor to run four tests in front of you. Send one real record, and check it arrives complete. Break the connection on purpose, and see what error staff are shown. Correct the record at the source, and watch the fix travel. Then ask who maintains the connection after either product updates.

Few buyers do this. In one survey in the United States, only eleven percent of teachers and administrators asked for peer-reviewed evidence before adopting.

So ask for the exact products, versions and data fields in writing, and score nothing until you've seen it work.

Who fixes it, and what does it cost?

Now the questions schools forget until something breaks.

Get four answers in writing from each vendor: support hours, who a problem escalates to, how much notice you get before planned downtime, and who is responsible when another vendor's product is involved.

Then picture a school day with one service down. Can staff carry on, and catch up later without conflicting records?

On cost, count every line over the same period for both options: licences and setup, integration upkeep, training and support, staff administration, and the cost of leaving. A cheaper start can still mean more work later.

And price what staff will actually use. In one American analysis cited by UNESCO, about two-thirds of education software licences went unused.

The same report notes that education technology products change every thirty-six months, on average. So plan your way out on day one.

Ask for a sample export, and check that student identifiers, history and attachments all survive it.

How should your school decide?

So how do you make the call?

Use the comparison questions as your scoring rows. Agree the weights before anyone sees a vendor's score. Every score cites the test behind it. Keep unproven answers visibly open. And give each trade-off an owner.

To recap: neither option wins by default. Start from your real workflows, test every claim, and decide on written evidence.

Easy Edu, a digital learning platform company in Malaysia, has put the full comparison table and every question in one free guide.

Read it at easyedu.com.my. Then email your comparison questions to Easy Edu, without any student records, and ask for written answers.

How do the two options compare, criterion by criterion?

Questions, not verdicts: ask every vendor the same row and leave it open until the evidence arrives.

What to ask, and what counts as evidence
Criterion	Integrated platform: ask	Separate apps: ask	Evidence required
Authoritative record	Is there one data store behind the interface, or several?	Which app is the source for each record, and which hold copies?	A correction traced to every place the record appears
Identity and roles	Does one role change apply everywhere at once?	How are accounts and roles mapped between apps?	A role change and a leaver tested end to end
Integration evidence	Which modules connect behind the screen, and who maintains them?	Is each connection native, standards-based, third-party or custom?	A live transaction plus a deliberate safe failure
Support ownership	Which team owns identity, configuration and escalation?	Who coordinates a problem that crosses products?	A written support path per workflow
Outage recovery	What stops if the platform is unavailable?	What stops if one app or connection fails?	A tested fallback that avoids conflicting records
Full cost	What do setup, training and change cost over the term?	What do integration upkeep and multiple contracts cost?	Costs and staff work over the same period
Exit path	Can everything be exported in one run, with history?	Can each app export, and will the exports reconnect?	A sample export checked for identifiers and attachments

Which school problem is the architecture meant to solve?

Name the workflows that drive the decision, from this list or another approved use:

AttendanceTimetable changesLearning activitiesAssessmentParent or guardian informationReporting

For each one, write down today’s people, data, handoffs, failure points and time cost.

An integrated platform may remove some handoffs; separate applications may keep specialist depth in one area. Neither benefit exists until the proposed products demonstrate it in the school’s own workflow. Keep learning outcomes out of the comparison unless they have been independently established for the actual implementation; an architecture choice is not evidence of a learning result.

If the problem is that the same information is typed into several places, say so plainly and make it the first test. If the problem is that one specialist tool is irreplaceable for a department, say that too. The honest problem statement decides which rows of the comparison table carry the most weight.

Where is each authoritative record created and changed?

For every important record, name the system where it is first created, the system treated as authoritative, the people allowed to correct it and the downstream places that receive a copy. Do this for both options. A single interface does not prove there is one source of record, and several applications do not necessarily mean every record is duplicated.

Created in: The system where the record first appears.
Authoritative in: The system that wins when two copies disagree.
Corrected by: The roles allowed to change it, and who approves.
Copied to: Every downstream place, with the timing of each update.

Test a correction, not only a new record. Easy Edu’s guide to mapping who sees, changes and approves each record helps build this map.

How do identity and role boundaries differ?

Map how a teacher, student, parent or guardian and administrator signs in to each proposed arrangement, and ask four questions of each option:

Accounts: Where is each account created, and by whom?
Roles: Are roles shared across systems or mapped between them, and how does a role change spread?
Recovery: Who can restore a lost sign-in, and with what approval?
Leavers: What happens to access and records when a person leaves?

Count the administrative steps, but also test whether the resulting access matches the school’s role matrix.

For personal data, map which system and which organisation can reach each category, and for what purpose. Malaysia’s Personal Data Protection Department publishes seven personal-data-protection principles and lists six data-subject rights in its public FAQ. These are general context: they do not show that either architecture complies, and they do not assign legal roles. The school should take advice on the actual data flow and contracts. Easy Edu’s guide to evaluating role access sets out the tests.

What evidence should support an integration claim?

Integration claims need the closest checking, whichever option is chosen. Ask for the exact sending product, receiving product, versions, sign-in method, data fields, direction and supported events. Then run it:

TransactionSend one representative record and confirm it arrives complete.
Safe failureBreak the connection on purpose and see what error the school is shown.
CorrectionFix the record at the source and confirm the fix reaches every copy.
OwnershipName who maintains the connection after either product updates.

Record whether each connection is native, standards-based, third-party or custom. If a vendor cites an interoperability standard, ask which version and services the exact configuration uses; the existence of a standard does not show that Easy Edu or any other vendor supports it.

Who owns support, change and outage recovery?

Draw the support path for each workflow. With one platform, the school still needs to know which team owns identity, network, configuration, content and vendor escalation. With separate apps, someone must coordinate a problem that crosses products, and that work may fall to the school. Ask each vendor for four answers in writing:

Support hours: When help is available, and through which channels.
Escalation: The conditions that move a problem up, and to whom.
Maintenance: How much notice the school gets before planned changes or downtime.
Other providers: Who is responsible when a problem involves another vendor’s product.

Then test resilience at the level of a real workflow. If one service or connection is unavailable during a school day, can staff continue safely, record work for later entry and recover without creating conflicting records? Ask who decides that a fallback is needed and who tells teachers and parents.

Do not award points for a general uptime or reliability statement unless its scope, measurement and remedy apply to the exact proposal in front of the school.

How do data, cost and exit compare over the full arrangement?

Request a sample export from each proposed source of record and check whether identifiers, relationships, history and attachments survive. With separate apps, check that the exports can be joined back together. Easy Edu’s data ownership, export and deletion questions list what to ask for.

Count every cost line below over the same period, for both options, and record who does the work, not only the invoice amount. A lower opening price can still carry more operating or exit work.

LicenceSetupIntegrationTrainingSupportAdministrationChangeExit

About two-thirds of education-software licences went unused in one United States analysis cited by UNESCO’s 2023 Global Education Monitoring Report. Price what staff will actually adopt, and ask what happens when one app is replaced or the platform is left.

How should the school make a weighted decision?

Use the seven rows of the comparison table as the scoring criteria, and fix the method before anyone sees a vendor’s score:

Weight first: Agree each criterion’s weight from the problem statement in section 01, before scoring.
Score with a reference: Every score cites the test or document behind it.
Mark confidence: A high score with open evidence stays visibly different from one backed by a completed test.
Record trade-offs: Each accepted compromise gets an owner and a review trigger.

A school may accept more applications to keep a specialist workflow, or a broader platform to remove some handoffs. Either is defensible when it is written down. Revisit the decision if the products, the data or the school’s needs change.

Quick answers

Frequently asked questions about integrated platforms and separate apps

Is one integrated school platform always simpler to manage?

No. It may reduce some interfaces, but the school still needs to examine roles, data stores, dependencies, support boundaries and exit. Simplicity should be shown in the school’s real workflows, not inferred from one login or one interface.

Are separate school apps always harder to secure?

No universal conclusion is justified. Separate apps create more relationships to examine, while one platform can concentrate access and dependency. Compare the actual identity, permissions, data flows, controls, contracts and evidence for each proposal.

Does a standards claim prove two school products will integrate?

No. Ask which version and services of the standard each product supports, whether that combination covers the required workflow, and who maintains it. Test the exact configuration, including failure and reconciliation.

External context

Which sources does this comparison rely on?

These sources give evaluation and legal context only. They do not describe, assess or endorse Easy Edu.

On this page

12 sections

Email Easy Edu

Next move

Ask Easy Edu for written evidence

Send the comparison questions to Easy Edu’s published enquiry email, without student records, and ask for its current product record.

Email the comparison questions Download the comparison worksheet

EVERYTHING ON THIS SITE