Questions, answered with the evidence available

EASY EDU SDN BHD is part of ES PRODUCATION GROUPS BERHAD and is described by the group as a digital learning platform company. The current site uses a timetable concept to show teacher, student and parent perspectives. Product name, release status and confirmed modules have not yet been supplied, so capability claims are deliberately withheld.

Ask the company for its current product name, release status, legal registration details and the person responsible for the answers. Keep the group description and company aspiration separate from operational product evidence, because they establish direction without proving deployed software. Read the verified company boundary →

No evidence has been supplied that the timetable, attendance, result, activity or related screens are live product features. They are illustrative design elements. A school should ask for the current product name, release status, real screenshots, supported workflows and a demonstration tied to written product documentation.

Label every visual as released, planned, illustrative or out of scope. Request a real demonstration and dated product documentation for anything described as released. Keep the screen and supporting evidence together so the evaluation record cannot silently promote a concept into a current feature. Separate concept from product status →

Start with the school problem, the people affected and the decision evidence. Map the current process before comparing features. Then test a small number of ordinary scenarios across teacher, student, parent or guardian and administrator roles. This keeps the evaluation focused on real work instead of allowing a demonstration menu to define the need.

Write the school problem in one sentence, identify affected roles and agree what evidence would change the decision. A vendor checklist can then support the discussion without replacing the school’s own requirements. Record constraints such as calendar, devices, connectivity and existing systems. Open the evaluation guide →

Include teachers, students, parents or guardians, administrators and the people responsible for technology, data and the final decision. Also consider substitute teachers, staff with several roles, guardians of several children, transferred students and leavers. These exceptions often expose permission, identity and support requirements that a simple role list misses.

Give each role a concrete scenario and include exceptions. Ask who grants access, how it changes and what happens when someone leaves. A teacher, learner, guardian and administrator label is only useful when the permitted actions and information are made explicit. Map roles and permissions →

Request the product name and release status, current module list, real screenshots, supported environments, workflow demonstrations, implementation plan, support terms and change history. Mark each item as released, planned, illustrative or out of scope. Keep the evidence date because software scope and operating arrangements can change after an evaluation.

Date every document and tie it to the exact service demonstrated. Capture product scope, workflows, implementation, support, privacy and exit evidence separately. If an item needs future development or configuration, record that status rather than merging it into the released product description. Build the evidence checklist →

Ask for the privacy notice, data-flow diagram, controller and processor roles, hosting locations, subcontractors, access controls, audit records, retention periods, deletion process, export method and incident response. Easy Edu has not supplied these details for this package. Its stated privacy value should therefore be treated as direction rather than proof of controls.

Use a data-flow diagram to connect each answer. The record should identify information types, transfers, storage, access and deletion, along with the responsible party. Ask for written policies and operating evidence; the appearance of an interface does not establish any of these controls. Open the data questions →

Request a sample export using non-sensitive demonstration data. Check the format, fields, identifiers, attachments and timestamps, and ask about timing and cost for a full export. Confirm what happens to live data, backups and logs after exit. A written export right is more useful when the school has tested whether the output is usable.

Check a sample export with non-sensitive test data before depending on it. Verify whether identifiers, attachments, timestamps and relationships remain usable. Record the process for a full export and the treatment of active data, backups and logs after the service ends. Test export and deletion →

No partnership or endorsement has been supplied. DELIMa and Google for Education appear only as external context about digital education users and evaluation topics. Their official documentation does not validate Easy Edu’s product, privacy or integrations. Any future partnership or interoperability claim needs specific written evidence before publication.

Treat the external platforms only as examples of topics a buyer may examine. Any claim about partnership, endorsement, data exchange or compatible login needs separate written evidence from the organisations involved and a current demonstration of the exact connection. Review external-platform evidence →

Easy Edu has not confirmed that it offers an evaluation session, so this site provides a self-run agenda rather than a booking promise. The company publishes easyedu.my@gmail.com as an enquiry route, but no response time, address, telephone or session availability is confirmed. Ask whether a suitable discussion is available before sending detailed material.

Prepare a concise request that states the decision problem, roles involved and evidence requested. Ask Easy Edu whether it currently provides a suitable discussion, who would attend and what materials it can supply. Avoid attaching student records or other sensitive information. Use the self-run agenda →

Create an evidence register with every claim, document requested, owner and due date. Decide whether the next step is clarification, a controlled demonstration, a pilot, commercial review or no further action. A first session should improve the decision record. It should not be treated as proof that a product fits the school.

Choose the next step from the evidence: request clarification, schedule a controlled demonstration, define a pilot, begin commercial review or stop. Give missing items owners and dates. The evaluation is complete when the decision record is clear, even if the result is to wait. Choose the next step →