Pre-primary school administration starts with the individual child, not a large examination register. Good digital records should help teachers observe development, maintain safe daily routines and communicate clearly with parents and guardians.
Start with a careful child enrollment record
For each learner, collect the preferred name, admission identifier, PP1 or PP2 class, guardian contacts, authorised collection arrangements and relevant emergency information. Only collect sensitive details that are genuinely required for care and school operations; restrict access appropriately.
Agree on who can create or edit learner profiles and who checks duplicates. If a child changes class or leaves the institution, retain the appropriate history instead of silently overwriting it.
Describe learning through observations, not just marks
Prepare a simple observation framework aligned with the learning activities your institution teaches. Record the date, activity, observed behaviour and teacher comments. Avoid converting observations into unsupported numerical scores merely because the software contains a grade field.
Let teachers distinguish a developmental observation from a parent-facing progress summary. School leaders should review the reporting templates against the curriculum and requirements applicable to their institution.
- Define learning activity and observation categories before importing data.
- Identify who can review or approve progress summaries.
- Use clear, respectful comments that parents can understand.
- Restrict photo, health and safeguarding information to authorised roles.
Record attendance and the daily handover process
Choose a consistent attendance convention for present, absent, late and excused. Maintain an audit trail when a record is corrected. A guardian contact update should be checked before sending notices or releasing a child.
Create a documented escalation process for emergencies, unusual attendance patterns or an unrecognised pickup request. An LMS can support record keeping, but it does not replace the school safeguarding policy.
Prepare an initial data import and staff orientation
Start with one class and a small, reviewed dataset. Confirm class names, teacher permissions, and whether the actual LMS release supports the specific observations and parent communications needed.
Train staff to enter one full day of sample records and export a progress summary before considering a wider rollout. Keep a signed-off backup of the original records during any migration.