Picture a nursery assessment day. A three-year-old is sat at a desk, handed a paper, and asked to circle the red apple. She has never held a pencil properly, she does not know what "circle" means, and she is frightened because a stranger is watching. She cries. The school records "cannot identify colours". The same afternoon, in free play, she sorts all the red blocks into one pile and all the blue blocks into another, singing a colour song as she goes. The test measured nothing — except her fear. The play showed the truth. This is why assessing nursery students without tests is not a soft option. It is the only honest option.
This guide shows nursery teachers how to assess young children properly: through anecdotal notes, developmental checklists, and photo portfolios — three simple tools that together give a far truer picture of a child than any test ever could.
Why Tests Fail Nursery Children
Tests assume four things that are not true of nursery children: that the child can sit still and focus on demand, that the child understands test instructions, that the child performs the same under pressure as in play, and that a single moment represents the child's ability. None of these hold at age three or four. Young children's performance varies wildly by time of day, mood, hunger, sleep, and whether the assessor is familiar. A child who "fails" a morning test may pass the same task after lunch. A test score at this age measures the testing situation far more than it measures the child.
Worse, tests teach the wrong lesson. A nursery child who experiences school as a place where they are tested and judged learns that school is a place of fear — the opposite of what nursery should teach. Parents, too, are misled: a test result with a number on it feels scientific, so parents trust it, even when it contradicts everything they see at home. Observation-based assessment avoids all of this. It watches the child in real situations, over weeks, and records what the child actually does — which is the only evidence that deserves the name.
Anecdotal Notes: The Teacher's Notebook
An anecdotal note is a short, factual record of something a child did or said, with the date: "12 March — Ayesha built a tower of nine blocks and counted them aloud, 1 to 9, without help." That is it. No judgement, no grade, no interpretation — just what happened. A teacher who writes two or three such notes per child per week will have, by the end of a term, a rich, dated record of that child's growth: the first time they shared without being asked, the first full sentence, the first time they wrote their name.
The discipline is in the writing. Notes must be factual ("Bilal cried when his mother left and calmed after five minutes with a story") not interpretive ("Bilal is a difficult child"). They must be dated, because dates show progress. And they must cover strengths, not just problems — a notebook full of complaints is a record of the teacher's frustration, not the child's development. Practical setup: a small notebook per child, or one class notebook with a page per child, kept at the teacher's side. Notes can be written during free play, at snack time, or in the last five minutes of the day. Teachers who say they have no time should start with just one note per child per week — the habit matters more than the volume.
Developmental Checklists: Quick, Honest, Useful
A developmental checklist turns observation into a shared framework. It lists the milestones for each area — language, motor skills, social development, self-care, early maths and literacy — and the teacher ticks each one as "emerging", "developing", or "confident", based on observation over time. Example items: "Speaks in sentences of four or more words", "Holds a crayon with a tripod grip", "Takes turns in a game", "Counts objects up to 10", "Uses the washroom independently". The checklist is filled in twice a term, never in one sitting, and never on the basis of a single observation.
Two rules keep checklists honest. First, the evidence rule: a tick needs an observation behind it — ideally an anecdotal note. A checklist filled in from memory at the end of term is guesswork. Second, the "not yet" rule: an unticked item means "not yet observed", not "failed". Children develop unevenly, and a blank on the checklist is a prompt to look more closely and support more deliberately, not a verdict. Schools can build their checklist from the standard early-years milestones: language, motor skills, social development, self-care, and early maths and literacy.
The Observation Rule
Photo Portfolios: Evidence Parents Can See
A photo portfolio is a folder — physical or digital — holding a child's work and moments across the term: a photo of the first block tower, a drawing from September beside a drawing from December, a picture of the child watering the class plant, a snapshot of their first beaded necklace. Each item carries a date and a one-line caption: "First time threading beads independently — 8 October". The portfolio does something no checklist can: it lets parents see growth. A parent who sees the September scribble next to the December picture of a house with a family will understand their child's progress in a way no report ever conveys.
Practicalities: one photo per child per week is plenty. Keep a class camera or a dedicated school phone, and take photos during normal activities — never stage them. Respect privacy: get written parent consent at admission for classroom photos, store portfolios securely, and never post identifiable photos of children on public social media. For schools with a parent communication system, sharing a monthly portfolio photo directly with each parent is a powerful way to build trust. At the end of the year, the portfolio goes home — a keepsake for the family and a record the school can be proud of.
Reporting to Parents: Progress, Not Marks
A nursery report should read like a story of growth, not a scorecard. Structure it in three parts: what your child can do now (with two or three specific examples from observation notes), what they are working on (one or two next steps, framed positively — "Ayesha is learning to hold her crayon with three fingers"), and how you can help at home (one or two concrete suggestions, like "let her pour her own water at mealtimes" or "read one story together each night"). No marks, no percentages, no class position, no comparison with other children. A parent who reads that their child "counts to 9, shares with friends, and is learning to use scissors" knows far more than a parent who reads "72%".
Deliver the report in a short parent meeting, not as a paper sent home in a bag. Ten minutes is enough: show the portfolio, walk through the checklist, share the anecdotal notes, and listen to the parent's observations from home. Parents know things the school does not — a child who is quiet at school may be talkative at home — and the meeting is where the two pictures combine. If a teacher has a genuine concern, this is where it should be raised: gently, with specific observations, and with a plan for support, never as a label. For schools formalising their reporting, our guide to digital report cards covers how to record developmental progress, and our parent-teacher meeting guide covers running the conversation well.
AI Help: Muse AI
Muse AI is Meta's personal AI assistant, available in the Muse app. It can help you turn rough observation notes into polished parent-report paragraphs — keeping your exact facts and dates, but phrasing them warmly and clearly for families.
Join Muse with invite code LTGSWD — in the Muse app, go to Settings > Redeem token and enter the code.
Disclosure: LTGSWD is the author's Muse invite code.