Start with the school's existing information landscape
Map learner admissions, class lists, attendance, assessment, progression, staff and parent communication. Identify the official system of record for each information type and avoid creating conflicting parallel records.
Where SA-SAMS or provincial processes are in use, verify the actual integration method, data fields, update frequency, permissions and reconciliation responsibilities. Never assume compatibility from a marketing claim.
Protect learner information
Define role-based access for teachers, school management, administrators, parents and support staff. Limit each role to the information required for its responsibilities.
Agree consent, correction, retention, export and incident procedures. Test access for transferred learners, former staff and guardians whose authority changes.
Measure adoption and educational usefulness
Test the workflow teachers use most often, such as capturing attendance or assessment results. Measure time saved, error rates and completion rather than counting screens or features.
Plan staff onboarding, low-connectivity use, data migration, support and term-cycle reporting before rolling out across multiple schools.
School software should fit South African school processes, protect learner records and reduce administrative burden without creating another disconnected source of truth.