Easy Edu FAQ: company, product status and platform evaluation

EASY EDU SDN BHD is the company that ES PRODUCATION GROUPS BERHAD describes as its digital learning platforms business. Its stated mission is to develop integrated digital learning solutions and applications that enhance teaching delivery, support student progress and enable transparent parent monitoring. That mission describes direction rather than a finished product: the current product name, release status and confirmed modules have not been published, so this site does not claim that any feature is live. The about Easy Edu page sets out what is confirmed and what is not.

ES PRODUCATION GROUPS BERHAD is Easy Edu’s parent company. “Producation” is the spelling used in the group’s own documents. Within the group, Easy Edu is assigned the knowledge and innovation role and carries the group colour yellow, which is why yellow marks the “period in progress” throughout this site. The group places Easy Edu in the digital learning platforms category. No other commercial relationship, partnership or customer arrangement has been published.

The stated vision is to be a leading digital education platform that supports effective teaching, engaged learning and informed parental involvement. That is an aspiration, not a claim of current market position. The five stated core values are Learner-Centric Design, Digital Innovation, Data Security & Privacy, Collaboration & Connectivity, and Continuous Platform Development. They are values the company says it holds, not audited controls, so a school should still ask for written evidence of how each one is applied to school records.

No. The timetable, attendance, result and activity screens on this site are illustrative design elements, and no evidence has been published that they are live product features. Before relying on any screen, a school should ask for the current product name, its release status, real screenshots, the workflows it supports and a demonstration tied to dated product documentation. Label every screen released, planned, illustrative or out of scope; the school platform evaluation guide shows how to keep concept and product status apart.

It presents the same school day from three viewpoints, the teacher’s, the student’s and the parent’s, as a design concept. The class names, subjects, times, attendance counts and results are placeholders written to show the idea; they are not data from a real school, pupil, parent or teacher. The design explains how Easy Edu thinks about one shared record of the school day. It is not evidence that a product with those views is released or in use.

Start with the school’s own problem, not a vendor’s feature list. Write down the work that causes delay or duplicate entry today, who does it and who is affected, and what observable result would change the decision. Note fixed constraints such as the calendar, devices, connectivity and existing systems. Then test a few ordinary scenarios across teacher, student, guardian and administrator roles. The six-check evaluation guide sets out the full order.

Include teachers, students, parents or guardians, administrators and whoever is responsible for technology, data and the final decision. Then add the exceptions that break simple role lists: substitute teachers, staff with two roles, guardians of several children, transferred students and leavers. For each role, ask who grants access, how it changes and what happens when the person leaves. The guide to evaluating teacher, student, parent and administrator access turns this into a sign-off matrix.

Ask for the product name and release status, the current module list, real screenshots, supported devices, a demonstration of named workflows, an implementation plan, support terms and a change history. Mark each item released, planned, illustrative or out of scope, and keep the date of every document, because scope can change after an evaluation. The list of questions to ask in a school platform demo gives the wording to use in the meeting.

Neither is automatically better. Compare both options against the school’s own workflows: where each record is created and treated as correct, how accounts and roles are managed, how data moves between tools, who supports each part, and how the school would export its records and leave. Any claimed connection between products needs evidence in the exact configuration proposed. The guide to choosing between an integrated school platform or separate apps lays out the comparison.

Ask for the privacy notice, a data-flow diagram, who decides and who processes the data, hosting locations, subcontractors, access controls, audit records, retention periods, the deletion process, the export method and the incident response. Easy Edu has not published these details. Its stated Data Security & Privacy value is a direction, not proof of controls, so every answer should arrive in writing for the exact service. The school data questions guide turns the list into requests.

Ask for a sample export built from invented records, open it in the tools the school actually uses, and check that identifiers, fields, attachments and timestamps still make sense. Ask how long a full export takes, whether it costs anything and who can request it. Then ask what happens to live data, backups and logs after the service ends. The guide to school data ownership, export and deletion covers the written terms to request.

No partnership, endorsement or integration with DELIMa or Google has been published. Google for Education’s privacy and security material is cited on this site only as outside context, for the topics buyers commonly examine, such as administration, privacy settings and data ownership. It does not validate Easy Edu’s product, privacy or integrations. Any claim of a connection would need written evidence and a live demonstration; the guide to comparing an integrated platform with separate apps explains how to check one.

Easy Edu has not confirmed that it offers evaluation sessions, so this site provides an agenda the school runs itself rather than a booking. The agenda covers the decision, the roles, one traced scenario, the data path and a closing evidence register, in about 90 minutes. A school that wants Easy Edu involved can ask by email at easyedu.my@gmail.com. The self-run evaluation session agenda is ready to use.

The published enquiry route is easyedu.my@gmail.com, listed on the contact page. No address, telephone number or response time has been published. Keep a first message short: the school’s decision, the roles involved and the evidence requested. Do not attach student records or any other sensitive information. How an email is handled is set out in the privacy notice, so share only what the request needs; the contact page also lists what to include before writing.

Create one evidence register listing every claim, the document requested, an owner and a due date. Then choose one next step: clarification, a controlled demonstration, a pilot, commercial review or no further action. A first session should sharpen the decision record; it does not prove that a product fits the school. If the school moves to a rollout, the school software onboarding checklist covers scope, data preparation, role testing and handover.