One record, seven stages, two surfaces

An administrator creates the school year, the grade levels, the sections and the subjects, and sets the weight each subject gives its components.

The school decides the weighting once and every class reads it. A teacher signing in alone gets a personal workspace instead, and can start without a school at all.

A class is a subject, a section and a schedule. Teachers keep their own; an administrator creates the ones the school needs to see across it.

A teacher-managed class stays private even inside a school. Whether an administrator can open a class is decided by that class’s access mode, in the database, on every query.

Attendance is one tap per student against a roster already on the device. Grade items are created under each component and scored as the work comes in.

One attendance row per class, per student, per day, and the class teacher is its only writer. Scores are raw marks out of the item’s total. A standing is derived from them, never typed in.

Recording does not wait for a signal. The device holds the records and the class carries on exactly as it would with full bars.

The on-device database is the source of truth rather than a cache of the server, so nothing in the recording path touches the network. An expired session stops syncing and still never blocks capture.

Everything pending goes up together. A connection lost mid-upload leaves the records intact, and the next attempt finishes the job.

One transaction per push, keyed by identifiers the phone generated, so a retry after a timeout produces the same end state rather than a second copy. Timestamps come from the server’s clock; a phone’s is never trusted.

Administrators open the roster, the attendance and the scores the teacher entered, without anyone re-typing them.

A student’s standing is computed by one shared function and stored nowhere, so the phone and the portal cannot show different numbers for the same student.

Thresholds are set for the school, or overridden for a single class, and a student’s record always shows the values behind an indicator rather than a verdict.

A threshold resolves in order: the class override first, then the school default, then the TAKI default. An administrator sets them in the portal today.

The nightly engine that raises flags against those thresholds, and guardian notifications by SMS and email, are still being built. No indicator on this site is a real flag.