Audit process
How an audit actually runs
Six named stages, from the first call to the note that leaves the room. No stage is a software installation.
01
Kick-off
A conversation with the programme lead. We name the app, the cohort, the term dates, and whether parent logins exist. If the app is still being built, we stop here; there is nothing to read.
02
Hashed export
You send lesson opens, video progress, quiz attempts, and last-open dates with hashed identifiers. Files with names are returned unread. We send back a one-page field map so both sides know what arrived.
03
Calendar mapping
Each lesson and recording is placed on the teaching week, including Malaysian public holidays and any week live classes moved. A quiet cluster on a festival week is labelled as such before anyone calls it neglect.
04
Written reading
The draft in English. It says what the records show and what they cannot show. You may correct facts twice — a wrong module name, a missing holiday — not the conclusions you merely dislike.
05
Briefing
Ninety minutes in Malacca, on your campus by arrangement, or by video. The pages are shared. Arguments in the room are expected. We do not grade lecturers.
06
Final note
A short record of decisions actually spoken: a quiz moved, a duplicate lecture retired, a request for a later mid-term check. Then we close the file.
The span from a clean export to the briefing is usually three to five weeks. A late vendor strip of names, a renamed module tree, or a cohort split across two apps lengthens that span, and the quote will say so.
If you only need a slice of this sequence — one module, or a sitting without a new reading — look at the shorter formats rather than forcing the full audit. When you are ready to open a term’s records, write with the cohort details.
Ready to open a term’s records?
Send the app name and the teaching calendar. We will say what we need from the export and whether an audit, a shorter engagement reading, or a briefing is the honest next step.
Request an audit conversation