Problem
Progress in a tutoring or learning setting is often recorded in a notebook, and parents learn about it when they ask. Enrolment lists are retyped from a spreadsheet, and a session that happened but was not written down becomes a disagreement rather than a record.
Our role
Design and build: the tracking model, the two views it serves, and the import path.
Approach
Educators record sessions and progress; parents see a dashboard of what has been logged. The two roles are separated deliberately, so the parent view is a presentation of records rather than an editing surface. Parent access uses one-time-code authentication, which avoids issuing and resetting passwords to people who will use the service a few times a month.
CSV import exists because the first real dataset always arrives as a spreadsheet, and retyping it is where a migration loses a term. Session acknowledgements go out by email. Capacitor is used for mobile-oriented packaging, so the same application can be installed rather than only visited.
Outcome
Tracking, the parent dashboard, and the import path are built. The security question — who can see which student's records — is the one that decides whether this can hold real data, and it has not been reviewed yet.
Notes
No student names, progress records, or family details are published. Access controls must be assessed before any demonstration uses real information.