FIELD GUIDE / EVIDENCE FIRST

Integrated School Platform or Separate Apps?

Neither architecture is automatically better. Compare an integrated platform and separate applications against the school's real workflows, source-of-record decisions, identity and access, data movement, support ownership, resilience, verified integrations, full cost and exit path. Weight the criteria before scoring and keep unresolved evidence visible.

Reviewed draft · 14 September 2026

KEY TAKEAWAYS

What should the reader carry into the decision?

  1. Start with school workflows and authoritative records rather than the number of applications.
  2. An integrated interface can still hide several data stores, owners and support paths.
  3. Separate applications can fit specialist needs but increase handoffs that the school must test and own.
  4. A standards claim matters only when the exact products, versions and services support the required configuration.
  5. Score evidence, operational responsibility and exit cost; do not declare a universal winner.

Method and scope. Prepared from the cited public sources and the verified client facts available for this article.

Evidence and editorial review: Acclaira AEO team · 14 September 2026

Download the reusable worksheet →Send a prepared evidence request →
Decision exhibit for Integrated School Platform or Separate Apps?
A structured evidence map for the decision described on this page.
01

Which school problem is the architecture meant to solve?

Name the workflows that drive the decision: attendance, timetable changes, learning activities, assessment, parent or guardian information, reporting or another approved use. For each workflow, identify the people, data, handoffs, failure points and time cost today. An integrated platform may reduce some handoffs; separate applications may preserve specialist depth. Neither benefit exists until the proposed products demonstrate it.

UNESCO's report warns that education-technology evidence depends on context and that a specific application does not automatically produce a particular learning result. Use the school's workflow evidence to define the comparison, and keep educational outcomes outside the claim unless they are independently established for the actual implementation.

02

Where is each authoritative record created and changed?

For every important record, name the system in which 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.

Test a correction as well as a new record. Note the direction of transfer, timing, identifiers, conflict rule and person responsible when two systems disagree. The comparison should reveal who reconciles the record and how the school detects a failed or delayed update.

03

How do identity and role boundaries differ?

Map how a teacher, student, parent or guardian and administrator signs in to each proposed arrangement. Ask where accounts are created, whether roles are shared or mapped between systems, how a role change propagates, who can recover an account and what happens when a person leaves. Count administrative steps, but also test whether the resulting access matches the school's matrix.

For personal data, map which system and organisation can access each category and for what purpose. Malaysia's regulator publishes seven personal-data principles and six data-subject rights as general context. Those sources do not prove either architecture is compliant or assign legal roles; the school should obtain advice for the actual data flow and contracts.

04

What evidence should support an integration claim?

Ask for the exact sending product, receiving product, versions, authentication method, data fields, direction and supported events. Run a representative transaction, then test a safe failure and correction. Record whether the integration is native, standards-based, supplied by another party or custom, and identify who maintains it after either product changes.

1EdTech says its LTI standard is “a technical standard (not a product) used to connect learning tools with an institution's learning environment.” A claim of LTI support should identify the version and services used in the proposed configuration. The existence of the standard does not establish that Easy Edu or any vendor in this comparison supports it.

05

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, define who coordinates a problem that crosses products. Ask for support hours, escalation conditions, maintenance notices and responsibilities when another provider is involved.

Test resilience at the workflow level. If one service or connection is unavailable, can the school continue safely, record work for later entry or recover without creating conflicting records? Do not award points for a general uptime or reliability statement unless its scope, measurement and remedy apply to the exact proposal.

06

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

Compare data categories, access, transfer, retention, export and deletion across every product and connection. Request a sample export from each proposed source of record and check whether identifiers, relationships, history and attachments survive. Google's administrator export documentation is one example of a provider documenting a product-specific export path; it cannot stand in for another vendor's answer.

Count licence, setup, integration, training, support, administration, change and exit costs over the same period. Record who bears the work, not only the invoice amount. Ask what happens when one app is replaced, the integrated platform is left, or a connecting service ends. An option with a lower initial price may still carry more operating or exit work, but the school should calculate that from the actual proposal.

07

How should the school make a weighted decision?

Agree the criteria and weights before scoring. Useful rows include workflow fit, source-of-record clarity, role access, data movement, integration evidence, resilience, support ownership, full cost and exit. Give each score an evidence reference and confidence level. A high score with unresolved evidence should remain visibly different from a high score supported by a completed test.

Record trade-offs instead of forcing every criterion toward one winner. The school may accept more applications to retain a specialist workflow, or accept a broader platform to reduce some handoffs. Name the operational owner and review trigger for each accepted compromise, then revisit the decision if the products, data or school needs change.

QUICK ANSWERS

Frequently asked questions

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 demonstrated in the school's real workflows, not inferred from one login or 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 proposed arrangement.

Does LTI support prove two school products will integrate?

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

See every guide in the insights index →

EXTERNAL CONTEXT

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