Remote education app analytics audit

This audit is for programme leads, e-learning coordinators, and faculty chairs who already run a remote education app — a homework app, a lecture-catch-up library, or a distance-learning portal — and need a plain-language account of what a named cohort actually did with it.

Who it is for

A Malaysian university faculty teaching a hybrid or fully remote diploma or degree. A private college that issued a catch-up app during a semester of split attendance. A tuition group whose homework app is now the only nightly contact with secondary students. If the app does not yet exist, this reading is the wrong request; we do not design or build apps.

The result

You receive a written reading of one app, one cohort, and one academic term (or a defined six-to-twelve week block). The reading names where students entered, where they stalled, which recorded lectures sat unplayed, which quizzes were attempted after the live class rather than before, and how last-open dates sit against the timetable. A ninety-minute working session then walks the programme lead — and, if you wish, two or three colleagues — through the pages.

What is included

• A kick-off conversation to agree the cohort, the term dates, and what the export can honestly show.
• A checklist of fields we can use (lesson opens, video progress, quiz attempts, last-open dates, hashed student identifiers).
• A written draft in ordinary language, with room for two rounds of factual correction from your side.
• One ninety-minute briefing, in Malacca or by video.
• A short final note after the briefing, capturing decisions the faculty actually took in the room.

What is excluded

We do not host the app, change its screens, write tracking code, or keep a standing login for you. We do not read marketing pages about student recruitment. We do not handle named student files; hashed identifiers are enough. If a later term needs a fresh look, that is a separate mid-term check or a new audit.

How the work proceeds

Once the anonymised export and the teaching calendar arrive, we spend the first days mapping fields to the timetable: which module week each lesson belongs to, which live class each recording was meant to support, which quiz sat before or after a tutorial. The middle stretch is the reading itself. The last stretch is the briefing and the final note. Three to five weeks is usual; a messy export or a cohort split across two apps takes longer, and we say so before we quote.

Preparation on your side

Ask whoever administers the app for an export covering the cohort and the term. Strip names. Keep hashed IDs so we can see repeat visits without meeting a student. Send the academic calendar, including public holidays and any week when live classes moved online at short notice. If parents also hold logins — common in tuition-centre homework apps — say so; mixed adult and student opens change how a last-open date should be read.

Constraints

We work in English. Briefings can include Malay glosses for faculty who prefer them; the written reading stays in English. We will not claim a cause we cannot see in the records. A quiet week after Deepavali or Hari Raya is not the same as a quiet week in ordinary teaching time, and the calendar is what lets us tell the two apart.

Fee and next step

Fees are quoted after we see the shape of the export and the size of the cohort. A single faculty app with one term of records typically starts from RM 6,800. Write to us with the app’s name, how many students were enrolled, and the term dates. We reply within two working days from Office 7, 58 Test Avenue, Malacca 00000.