How Nurseries Use AI to Write Daily Reports for Parents

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How Nurseries Use AI to Write Daily Reports for Parents.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How Nurseries Use AI to Write Daily Reports for Parents.

Nurseries use AI to turn a practitioner's quick notes and the routine data already logged (meals, sleep, nappy changes) into a short, warm paragraph for each child. The key person reads and corrects it before it reaches parents. The safest way is the writing assistant built into the nursery app, not pasting children's details into a public chatbot.

A daily report has two halves, and only one needs AI. The routine half is data: what was eaten, when the nap started, how many nappy changes. Nursery software already records that from a few taps. The other half, "what they did today", is where staff spend the time at 5pm, and where a writing assistant helps. Accident, medication and safeguarding records are a different category altogether and should never be AI-written.

Follow me on Instagram@sagnikteaches

Which parts of a daily report AI should touch

Part of the reportWhere it comes fromAI's role
Meals, drinks, bottlesTaps in the app during the dayNone. Data should stay exactly as logged
Sleep and nappy timesTaps or timersNone
Activities and playPractitioner's shorthand note or voice memoDraft or polish into two to four sentences
Mood and settlingPractitioner's notePolish only; keep the practitioner's words for anything negative
Something to try at homePractitioner's ideaDraft a friendly suggestion from the idea
Accidents, incidents, medicationFormal formsNone. These are records, not messages
Concerns about wellbeing or developmentRoom leader or key personNone. A conversation, not a daily note

Drawing that line clearly on day one prevents the most serious failure: a worrying observation softened into cheerful prose because the tool was asked to "make it sound nice".

Connect on LinkedInSagnik Bhattacharya

How the drafting step works, from tap to parent's phone

  1. Routine taps during the day. Food, sleep and nappies are logged as they happen, as most nurseries already do.
  2. Two or three shorthand notes per child. Typed or dictated in seconds, straight after the moment: "sponge painting, used both hands, named red and yellow".
  3. The assistant turns notes into sentences. Inside the app, the practitioner taps an option such as "improve writing" or picks a tone.
  4. The key person checks the draft against what happened. Every name, every activity, every claim about how the child felt.
  5. Send, translated if the family reads another language more comfortably.

Here is what that looks like for one child (illustrative). The practitioner's notes:

Subscribe on YouTube@codingliquids
ate most of pasta, not the broccoli. nap 12.40-1.55.
teary after drop off, settled with bubbles by 9.15.
sponge painting - named red + yellow. built long train w/ blocks,
counted carriages to 5.

A first AI draft:

What a wonderful day [Name] has had! After a few tears at drop-off she soon settled and loved every minute of our bubble play. She enjoyed a delicious pasta lunch and had a lovely long nap. [Name] was so creative with sponge painting, confidently naming all her colours, and built an amazing train, counting all the carriages!

What the key person changed, and why:

  • "Loved every minute" was not observed. Replaced with "was settled by quarter past nine".
  • "Delicious pasta lunch" hid the fact she left her broccoli, which her parents had asked to hear about.
  • "Naming all her colours" overstated two colours. Changed to "named red and yellow".
  • "Counting all the carriages" became "counted the carriages up to five", which is the detail a parent can build on at home.

The corrected version is shorter, calmer and more useful: "[Name] had a few tears after drop-off and was settled by quarter past nine with the bubbles. She ate most of her pasta but left the broccoli. At sponge painting she named red and yellow, and later built a long block train and counted the carriages to five. You could count stairs or buttons with her tonight." The meal and nap times appear separately from the logged data.

Built-in writing assistants versus a public chatbot

Several nursery platforms now include a writing assistant, which is usually the better option:

  • Famly's Sidekick corrects spelling and grammar, changes tone (professional, polite, observant or conversational) and has a "Make it shorter" option. Famly made it free for all its users across packages in October 2025. Famly also offers live translation of daily updates and messages across more than 130 languages.
  • Ovivio (formerly Blossom Educational) has an assistant called Bloom for observations and daily diary entries. The practitioner writes first, then accepts or rejects Bloom's suggestions; nothing changes without their say-so.

Built-in tools have three advantages. The child's details stay inside a system already covered by your data processing agreement with the software company. Staff don't need personal AI accounts. And the assistant polishes what the practitioner wrote rather than inventing from a prompt. It still makes sense to read your provider's data processing terms to see where the AI processing happens.

If your software has no assistant and you use a general tool instead, use a business plan that doesn't train on your content, remove surnames and anything identifying, and never upload photos of children to it. The detail on what is and isn't allowed is in whether it is safe to use AI with children's data in a nursery. If you are choosing new software anyway, what to compare in nursery software with AI covers the questions to ask.

What it looks like across a 48-place nursery

Take a hypothetical nursery with four rooms, 12 practitioners and about 40 children in on a typical day. Before AI, each key person writes their children's "today" paragraphs in the last hour, while also doing handovers. Say that takes four minutes a child: 160 minutes of staff time a day, squeezed into the busiest part of the afternoon.

With shorthand notes taken through the day and an assistant turning them into sentences, the end-of-day work becomes checking and correcting. Two minutes a child is realistic once staff are used to it, so about 80 minutes a day, or more than six hours a week across the nursery, is moved away from the pick-up rush. The figures are illustrative; time your own rooms for a week before and after. Cost is often nothing extra if the assistant is part of your existing package.

What changes in practice is less about minutes than about attention: practitioners who aren't writing at the door can actually talk to parents at pick-up, which is what parents remember.

Where AI-written daily reports go wrong

  • The wrong child. A practitioner writes one note for a group ("Child A and Child B built a train, Child A counted to ten") and the assistant gives Child B the counting. Rule: one note per child, never a group note pasted into several reports.
  • Invented feelings. "Loved", "adored" and "had the best time" appear because the model fills gaps with enthusiasm. Parents who know their child can tell.
  • Every report sounds the same. Parents compare notes at pick-up and siblings' reports sit side by side on the same phone. If five children in the room "had a wonderful day exploring", the reports stop being read.
  • Softened concerns. A child who refused lunch and was upset all afternoon becomes "had a quieter day". Negative observations stay in the practitioner's words, or go into a conversation.
  • Assumptions about families. Drafts default to "Mummy and Daddy". Use the carer names the family gave you, stored on the child's profile.
  • Translation of idioms. "Full of beans" does not survive translation. Plain sentences translate better.

A harder case shows where the line sits. Suppose a toddler bit another child at lunchtime. The incident goes on the incident form, written by the practitioner who saw it, and the parents of both children hear about it in person. The daily report should not describe it, and the assistant should never be asked to phrase it. If anything, the daily note says only: "There's something from lunchtime we'd like to talk to you about at pick-up." It names no other child, and nothing about it has been through a writing tool.

One more mistake to watch for comes from the tools themselves. Writing assistants often have a "make it longer" or "expand" option. Used on a thin note ("played outside, sandpit"), it will produce three sentences about building sandcastles and sharing spades that nobody saw. Staff under time pressure accept it because it looks finished. The rule for the room: never expand a note you haven't added detail to yourself. If a report looks thin, the fix is a better note tomorrow, not a longer paragraph today.

Reports for children with additional needs

For a child with additional needs, daily reports carry more weight. Parents may be tracking specific targets agreed with the nursery and other professionals, and generic warmth can feel like the nursery hasn't noticed what matters. Suppose a child has a speech and language target of using two-word phrases. The key person's note: "said 'more juice' and 'bye mummy' today, pointed for everything else." An AI polish that turns this into "[Name] was chatty and communicated wonderfully today" erases the very detail the parents want. The version that serves them keeps the exact words: "[Name] said 'more juice' at snack and 'bye Mummy' at drop-off. He pointed to ask for everything else." For these children it is often wiser to switch off AI polishing for the development section altogether and use it only for routine and activities.

Translated reports: check the first few by hand

Live translation, such as Famly's, means parents can read updates in the language they're most comfortable with. Before relying on it, ask a staff member or a willing parent who reads the language to compare a week of translated reports with the originals. Two things to look for: nursery terms that don't translate well ("free flow", "key person", "circle time" can come out as odd literal phrases), and tone, since a friendly note can read as oddly formal or overly casual in translation. If a term keeps coming out wrong, replace it in the original with plain words ("the children chose where to play" rather than "free flow"), which also helps parents who read English as a second language.

Weekly and end-of-term summaries built from daily notes

Once daily notes are consistent, they become raw material for longer pieces. A key person preparing a short end-of-week summary might ask the assistant, inside the nursery software or a business account with names removed (illustrative):

Here are five daily notes for one child (Child A). Write a 5-sentence
weekly summary for parents: one sentence each on play, language,
physical development, social, and one thing to try at home. Use only
what is in the notes. If a heading has nothing in the notes, say
"Nothing new to report this week" for that heading.

A typical draft is useful but will usually need one fix: it merges two days into a single achievement ("climbed to the top of the frame on her own") when Tuesday's note said "with help" and Thursday's said "nearly on her own". The key person corrects it to show the progress across the week, which is exactly the story parents enjoy reading. The "nothing new to report" line matters too; without it, the model fills empty headings with invented progress. Longer learning records are covered in using AI for childcare observations.

Rolling it out room by room over three weeks

Switching every room on at once is how the wrong-child mistake reaches forty families on the same afternoon. A gentler plan:

  1. Week 1, one room. Pick a room leader who likes the idea. Staff practise shorthand notes for every child and use the assistant for the "today" section only. The room leader reads every report before it goes, and keeps a tally of what they had to correct.
  2. Week 2, review the tally. If most corrections are invented enthusiasm, tighten the style card. If they are factual (wrong activity, wrong child), the notes are too thin or too grouped; fix the note-taking habit, not the tool.
  3. Week 3, the other rooms. The first room's leader shows each team a real before-and-after, with details removed. Staff believe a colleague's example more than a training slide.

After that, a monthly spot check is enough: the manager reads ten sent reports from different rooms and asks whether each sounds like the child and like the key person. If reports start to blur together, the fix is usually more specific notes, not a different tool.

A house style card for AI-polished reports

Print this for each room and use it as the instruction if your tool takes one:

Daily report style - [Nursery name]
- 2 to 4 sentences for the "today" section. Plain words.
- Only what was seen. No "loved", "adored", "best day ever"
  unless the practitioner wrote it.
- Keep numbers and specifics: "counted to five", "named red and
  yellow", not "counted" or "named colours".
- Include one small thing to try at home when there is one.
- Anything negative stays in the practitioner's own words.
- Use the carer names on the child's profile.
- Never mention other children by name.
- Accidents, incidents, medication, concerns: not in the daily
  report. Use the proper form and speak to the parent.
- Key person reads every report before it is sent.

How to tell whether it's working

Three measures, taken for two weeks before you start and again after the first month, tell you more than staff impressions:

  1. Minutes per report written at home time. Ask each room to time five reports on a Tuesday and a Thursday. If the number hasn't fallen, staff are probably rewriting the drafts from scratch, which usually means the notes are too thin.
  2. Corrections per 20 reports, tallied by the room leader. A falling count shows notes and style card are working; a stubborn count of factual corrections (wrong activity, wrong child) is a warning to slow down.
  3. What parents say. A three-question message at the end of the month: "Do the daily reports tell you what your child actually did? Is there anything you'd like more or less of? Do they sound like your child's key person?" The last question is the one that catches reports drifting into sameness.

If parents say the reports have become more generic, believe them over the time savings. The point of the report is the relationship with the family; minutes saved at the door only matter if that stays intact.

Telling parents how reports are written

Parents are generally fine with a writing assistant tidying up a practitioner's notes; what upsets them is discovering it by accident. Tell them once, in your parent handbook or a message at the start of term, and mention it in your privacy notice. Wording you can adapt:

How we write your child's daily report
Your child's key person notes what they see through the day. At home
time, our nursery app's writing tool helps turn those notes into a
short update, and your key person checks every word before it is sent.
Meals, sleep and nappy changes come straight from what staff record.
Accidents or anything we're concerned about are never written by the
tool; we'll always speak to you in person.

The same approach works for termly progress summaries, which follow similar rules to how tutoring centres write parent progress reports. For the front door of the nursery, see AI chatbots for nursery enquiries and visit bookings, and for the checking routine itself, setting up human review without slowing down.

Further reads

Sources: Famly, Sidekick writing assistant announcement (October 2025) and live translation page; Ovivio (formerly Blossom Educational), Bloom AI observations page.

Want daily reports that take half the time?

On a 1:1 call we'll look at how your rooms write reports now, what your nursery software can already do, and the rules that keep children's details safe.

Book a 1:1 call with me