For the Pre-Primary Class Teacher
The Pre-Primary
Teacher Dashboard.
Notebooks closed. Children watched.
Six surfaces written for two-to-six-year-olds — slot timeline, mood-aware attendance, diaper + meals + nap, NEP 2020 observations, consent-first photo studio, and a safety screen the substitute teacher trusts. Built mobile-first; the children never see it.
Scroll the keynote — one act per surface, one decision per act.
Walk into class with the day already composed.
In a pre-primary room the morning is forty small decisions before nine-thirty. Who is missing, who needs the gentle hello, which child is in which slot, whose snack to watch for peanuts. The information lives in the teacher's head — and on a paper attendance sheet that the parents will never see.
Edullent opens to a single screen: today's slots laid out, the four care-actions (attendance · diaper · meals · note) within a thumb's reach, the morning mood already auto-summarised for the parent feed. The teacher stops being a notebook. She becomes the room.
The four care actions an early-years teacher repeats all day — attendance, diaper, meal, note — placed on the home screen instead of two layers down.
Signals it reads
- The class roster for the day
- Attendance and mood as they are marked
- Care events as they happen
- The day’s snack menu
What the engine computes
- One tap per care action, time-stamped on the spot
- A room-wide mood distribution composed in real time
- Each child’s parent feed assembled as the morning runs
- Written once — no re-entry at the end of the day
Decisions it drives
- Which child needs attention right now
- What the principal should know without walking in
- What goes home to each parent today
The day at a glance
Every slot of the pre-primary day — Circle Time, Snack, Art, Nap, Story — laid out on one strip with live status. Done · live · next · planned.
Care, one tap each
Mark attendance, log a diaper, save a meal, write a note — the four care actions live on the home screen, not buried two layers deep.
Mood auto-rolled
Every child checked in with a mood pill. The class-wide snapshot lands in the parent feed at 9 AM without the teacher writing a word.
Saved every morning vs the paper attendance + notebook era
Needed to remember a meal-allergy or sleepy child
Every child marked, and how they walked in — by 8:30 AM.
Pre-primary attendance is not a checkbox. A child who is present but missing-mum needs a different morning than a child who is present and bouncing. K-12 attendance software has no concept of mood; the teacher writes it into the back of a notebook that no one will read again.
Edullent treats mood as first-class data. Each present-tap pairs with a mood pill — happy, quiet, sleepy, missed-mum — and that signal flows into the parent feed, the principal's morning report, and the end-of-week observation roll-up. The teacher's instinct becomes the record.
Attendance and emotional state captured together, so the room can be read as a whole rather than one child at a time.
Signals it reads
- Present, absent or late, per child
- How each child arrived
- Time of arrival
- Yesterday’s pattern for the same child
What the engine computes
- Mood recorded as a first-class field, not a free-text afterthought
- A class-wide distribution composed as marks come in
- One tap to commit, so it happens at the door and not later
- History retained, so a run of quiet mornings becomes visible
Decisions it drives
- Which child to sit with first
- Whether to change the morning plan for the whole room
- What to mention to a parent at pickup
4-mood vocabulary
Happy · quiet · sleepy · missed-mum — the four pills that cover 95% of pre-primary mornings. One tap, no typing.
Live class snapshot
The room-wide mood distribution composes itself in real time — so the principal can sense the day without walking in.
Parent feed by 9 AM
Each child's parent sees their own check-in with the mood — the ‘reached safely’ the WhatsApp group used to attempt, but personal.
Of parents read the mood pill within 15 minutes of the morning post
Cover what 200 words of teacher-notes used to
The toddler-day logged in one screen — diaper, meals, nap.
Pre-primary has three logs no K-12 software thinks about — the diaper register, the meals + allergens log, the nap timer. The school keeps them on paper because every existing ‘school management software’ was built for high-school report cards. The parent of a three-year-old gets none of it.
Edullent ships the three as first-class surfaces. Quick-log buttons for diaper. Four meals with allergen flash and parallel nap timers. A pickup queue with photo + OTP verification. Built for the rhythm of a pre-primary room, not retrofitted from a K-12 grade-book.
Diaper, meals and rest logged as they happen, with allergens checked against the child before the food reaches them.
Signals it reads
- Diaper events by type
- Meal type and portion size
- Nap start, end and total
- Each child’s recorded allergies
What the engine computes
- Five one-tap states for changes, time-stamped and parent-visible
- Four meal types and four portion sizes, logged in the moment
- Allergens auto-matched to the child and flagged before serving
- Rest tracked as an open pulse rather than estimated afterwards
Decisions it drives
- Whether a child needs a change, a top-up or a longer rest
- What to warn the kitchen about before the next snack
- What to tell a parent about the day, with times attached
Diaper register, digital
Wet · soiled · mixed · dry-check · washroom — five buttons, one tap each, time-stamped + parent-visible.
Meals with allergen flash
Four meal types · four portion sizes. Allergens auto-detected from the snack menu — the system warns the teacher before the spoon lands.
Pickup, verified
Photo + OTP + authorized-list match for every child handover. Mismatch auto-pings the principal — never ‘who is this person taking my child’ again.
Replaced — diaper register, snack log, pickup register, all in one app
Per care event · what used to be three columns of a paper sheet
Five domains, four rubrics — every note tagged to the framework.
NEP 2020 and the NCF-FS rewrote how pre-primary growth should be measured — five learning domains, four rubric bands, evidence-based observation. Most schools already write the notes; nobody is tagging them. At inspection time, the file is a stack of paper a teacher composed the night before.
Edullent ships the framework as the data model. Every observation lands on a child + a domain + a rubric band + a visibility tier (teacher · principal · parent). The end-of-term report writes itself from the evidence, not from the teacher's memory of who did what.
Developmental observations recorded against the NEP 2020 domains, so coverage gaps surface during the term instead of at the end of it.
Signals it reads
- Teacher observations as they are written
- The domain each note belongs to
- The rubric level assigned
- Coverage accumulated across the term
What the engine computes
- Physical, Cognitive, Language, Socio-Emotional and Creative — every note lands on one
- A rubric level attached to the note, not prose alone
- Per-child coverage tracked as the term runs
- Gaps surfaced while there is still time to fill them
Decisions it drives
- Which domain a child has no evidence in yet
- What to plan next week to close a coverage gap
- What to show a parent at the review, with evidence behind it
Five-domain coverage
Physical · Cognitive · Language · Socio-Emotional · Creative. Every note is forced to land on a domain — coverage gaps become visible at term-end.
Rubric-band scoring
Beginning · Developing · Achieving · Excelling — applied per topic, not per term. The picture is a heatmap, not a single number.
Tiered visibility
Teacher-only · principal · parent-visible. The note that helps the next teacher need not become a WhatsApp forward — the system decides, the teacher commits once.
NEP 2020 + NCF-FS evidence file generates automatically each term
Median in pilots — vs ~6 in the paper-notebook era
Class photos with every parent's permission — built in.
A class teacher takes twenty photos a day. WhatsApp pushes them to the group. Two parents quietly didn't want their child on social. The school finds out from a phone call on Saturday morning. The trust is gone before the term is.
Edullent ships photos with consent as a first-class concept. Face-detection identifies each child in the frame, the consent matrix dictates publish · face-mask · auto-exclude, and the teacher uploads with one tap knowing zero parents have been crossed. The Saturday call never happens.
Photo sharing governed by per-child consent and enforced by the system at the moment of publishing, rather than by staff memory.
Signals it reads
- Every face detected in an uploaded frame
- The class roster
- Four consent toggles set by each parent
- The intended destination — app, social, group or brochure
What the engine computes
- Faces matched against the roster at upload; unmatched faces held for review
- Consent applied per photo and per destination, never as a blanket setting
- A child without consent auto-masked, or the photo excluded outright
- Nothing publishes against a parent’s setting
Decisions it drives
- Whether this photo can go out, and where
- Which frame to use when one child’s consent is off
- What to re-shoot now rather than argue about later
Face detection at upload
Every face in the frame is identified against the class roster. Photos without a face match get flagged for review — strangers never sneak through.
Consent matrix · per child
Each parent sets four toggles — in-app · social · group share · brochure. The system never publishes against a setting.
Auto-mask · auto-exclude
When one child in a group photo has consent off, the engine face-masks that child or auto-excludes the photo entirely. One tap from teacher, zero risk.
In pilot schools across a full term — vs 3-7 incidents the year before
Per class photo · what manual review used to take an hour to clear
One screen the substitute teacher needs — and the parents trust.
A substitute teacher walks into a pre-primary classroom and inherits twelve children's allergies, medical notes, blood groups, comfort cues and authorized pickup lists — most of it nowhere in writing. Every absence is a liability waiting for the day it goes wrong.
Edullent collapses the safety record into one printable A4 — allergens rolled up class-wide, per-child medical alerts surfaced by severity, authorized pickup register tappable to call. The substitute teacher walks in informed; the regular teacher walks out covered.
Allergies, medical notes and authorised pickup gathered into one screen a stand-in teacher can act on immediately.
Signals it reads
- Allergies and severity, per child
- Medical and dietary notes
- Authorised pickup and emergency contacts
- The day’s menu
What the engine computes
- A class-wide allergen roll-up with counts and severity
- Pinned to the snack and canteen view, where the risk actually sits
- Cross-contamination made visible rather than assumed
- Parent-maintained, so the record stays current
Decisions it drives
- What a substitute must know before the first snack
- Who may collect which child today
- What the kitchen cannot serve in this room
Class-wide allergen roll-up
Every allergen in the class surfaced with count + severity — pinned to the canteen + snack-prep tab. Cross-contamination becomes visible.
Per-child severity tier
Critical · high · medium · low — sorted automatically. The new teacher knows whose EpiPen, whose inhaler, whose comfort blanket before lunch.
Tap to call · auto-trail
Mother · father · doctor · driver — all in one card, all one tap. Every call timestamps itself into the incident log.
Substitute-teacher handover sheet · auto-generated from the live data
For 12 children · what used to be 3 filing cabinets and a WhatsApp scramble
Tomorrow's pre-primary teacher
won't carry a notebook. She'll carry the room.
Edullent ships the slot timeline, the care logs, the NEP-aligned observations, the consent-respecting photo studio and the substitute-ready safety screen — so the pre-primary teacher's hours go back to the children.