Skip to content

Self-run agenda · School team

How to run a school platform evaluation session

To run a school platform evaluation session, gather a small school team for about 90 minutes and work through five periods: agree the decision, map each role and its exceptions, trace one ordinary scenario from entry to notice, check the data path, and close with an evidence register naming every open claim, owner and due date. The school runs it itself; it is not a confirmed Easy Edu service.

Published 14 September 2026 · Reviewed 18 September 2026

On this page8 sections

Key takeaways

What should the team carry out of the room?

  1. Write the decision and its fixed constraints before anyone opens a vendor feature list.
  2. Trace one ordinary scenario across teacher, student, guardian and administrator roles, including one exception.
  3. Leave with one evidence register that gives every open claim an owner and a due date.

Scope. The agenda is a vendor-neutral preparation tool. It does not show that Easy Edu delivers the session or any feature illustrated on this site.

Download the session worksheet Email Easy Edu an evidence request
Before

Who should prepare for the session, and what should they bring?

Invite four to six people who cover classroom work, administration, leadership and family communication. Each brings one ordinary task, one exception and one recurring frustration. The chair prepares a blank evidence register, a list of the systems in use today and invented test data, so no real student record enters the room. Invite a product representative only after the school has written the questions it needs answered.

  1. 01Decision sponsor. Owns the question and the deadline.
  2. 02Teacher representative. Brings a real classroom task and its workaround.
  3. 03Administrator. Knows accounts, records and current systems.
  4. 04Parent or student view. Tests what the family actually receives.
Session roles: a decision sponsor, a teacher representative, an administrator and a parent or student perspective.
00:00

What decision must the school define first?

Spend the first fifteen minutes on one written sentence: what is being considered, for whom, and by when. Put the constraints that cannot move beside it, such as the academic calendar, the devices students already use, connectivity and existing systems. Agree what evidence would change the decision. That shared test stops a demonstration from drifting into possibilities nobody asked for.

A purchase is not an outcome; the decision sentence is what the session tests.

Decision
Whether to shortlist a platform for attendance and parent notices
For whom
Form 4 teachers, students and their guardians
By when
Before the next term’s timetable is fixed
Fixed limits
Current devices, school calendar, existing records system
00:15

Which school roles and exceptions should be mapped?

Spend twenty minutes writing what each role should see, what it may change and one exception to test. Google Classroom’s official page, for example, addresses education leaders, educators and IT administrators separately and says parents and guardians can view assigned classwork through a link or weekly guardian email summaries, a reminder that one platform can treat each group differently; it says nothing about Easy Edu. The role information-flow map extends this table into a full matrix.

RoleShould seeMay changeException to test
TeacherOwn classes’ attendance and resultsMarks for own periodsSubstitute covering a class
StudentOwn timetable and tasksOwn submissionsTransfer mid-term
GuardianOwn child onlyContact detailsGuardian of several children
AdministratorSchool-wide recordsAccess rights, correctionsLeaver whose access ends
The school’s own expectations for each role, written before any vendor shows its own design.
00:35

Which ordinary school scenario should the team trace?

Give the longest period to one scenario, such as an attendance correction. Follow the record from first entry to the last person who reads it, and ask at each step where the correct value lives and who can change it. Use invented details. One scenario that crosses several roles reveals more than a tour of every screen.

  1. 01Origin. A teacher marks a student absent in period one.
  2. 02Authority. Which system holds the value everyone else must trust?
  3. 03Correction. The student arrives late; who fixes the mark, and is the first entry kept?
  4. 04Notice. What the guardian receives, and whether it is updated.
  5. 05History. Who can later see what changed, by whom and when.
An attendance correction traced from the first mark to the guardian’s notice and the record’s history.
01:00

Which data-path questions belong in the session?

Use twenty minutes to follow the traced record from collection to deletion and list the document that should answer each step. Easy Edu has not published this operating record, so every answer stays open until a vendor supplies it in writing. The school data questions guide turns each step into a request, and the Malaysian Personal Data Protection Department’s seven principles give general legal context.

Do not assume the law answers these questions: UNESCO’s 2023 report found only 16% of countries explicitly guarantee data privacy in education by law.

  • Collection: which fields are captured, and for what purpose
  • Storage: where the record is hosted, and by which parties
  • Access: who can open it, and whether access is logged
  • Retention and deletion: how long it stays, and how removal is proved
01:20

What must the closing evidence register contain?

Use the last ten minutes to fill one register: the claim, the evidence requested, its status, an owner and a due date. Keep concept screens apart from demonstrated features. Then choose one next step: clarification, a controlled demonstration, a pilot definition, commercial review or a pause. Circulate the register the same day and note any disagreement beside its row.

ClaimEvidence requestedStatusOwnerDue
Corrections keep the first entryDemonstration with test dataOpenAdministratorBefore shortlist
Guardians see one child onlyConfigured guardian accountOpenTeacher representativeBefore shortlist
Full export on exitSample export and written termsRequestedSponsorBefore contract
A sample register from the attendance scenario: every open claim has an owner and a date.

Prepare the status and workflow questions with the school platform evaluation guide →

Quick answers

What do teams ask before running the session?

Is this an Easy Edu consulting or workshop service?

No. Easy Edu has not confirmed that it offers evaluation sessions. This page is an agenda a school team runs itself. Use it to prepare questions, then send them to Easy Edu’s published enquiry email if the school chooses to continue.

Who should attend the first session?

A decision sponsor, a teacher, an administrator and a parent, guardian or student perspective. Add the person responsible for technology or data when those questions are in scope. Each attendee brings one ordinary task, one exception and one frustration.

What should the session produce?

One evidence register listing each claim, the document or demonstration requested, its status, an owner and a due date, plus a single chosen next step: clarification, a controlled demonstration, a pilot definition, commercial review or a pause.

Sources

Which sources informed this agenda?

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 take the register into due diligence?

The full evaluation guide covers implementation work, privacy evidence and the exit test in more depth.

EVERYTHING ON THIS SITE

Every EASY EDU guide and page