Why we exist
Educators should be with the children, not writing about them at 9pm.
That is the whole mission. Everything we build gets measured against whether it gives an educator their evening back without taking their voice away.
Almost every educator we talk to writes documentation on their own time.
Evenings. Sunday afternoons. The gap between finishing a shift and picking up their own children. It is the most common complaint in the sector and it is almost never in anyone's job description. Nobody trained for years in early childhood education because they wanted to spend weekends writing up what happened on Tuesday.
The strange part is that the writing is not really the hard bit. Educators know exactly what they saw and exactly why it mattered. What costs them is the blank page, and the fact that by 9pm the specific details have blurred into something generic. The moment a child changed their mind, or tried a different approach, or said a thing in their own funny phrasing, is the part that makes a story worth keeping. It is also the first thing memory loses.
So the documentation gets written anyway. Later, thinner, and more generic than the day deserved. Families skim it. It goes in a file. And the educator carries a low background guilt about work that was never really theirs to do unpaid in the first place.
A tool should take the blank page away, and give the specifics back.
Not write the child's story for them. Not decide what the learning was. Take a rough note or a voice memo captured in the moment, while the detail is still sharp, and turn it into something complete enough to edit rather than something to start from nothing. The judgement stays with the person who was actually standing there.
What we will not do
Six promises, and they are the constraints we build inside.
These are not aspirations. Each one is enforced in the product itself, and it is why some things you might expect an AI writing tool to do, StoryLoop deliberately refuses to do.
01
The educator has the last word. Always.
StoryLoop writes a first draft. It does not publish, it does not send, and it does not decide what is true about a child. Every story arrives with the checks worth confirming before it is shared, and nothing leaves your account unless you send it. If a draft is wrong, it stays wrong until you fix it, and that is the correct order of authority.
02
A child's words are evidence, not a typo.
When a two year old says something in their own particular way, that phrasing is the most valuable thing in the note. It is the bit whānau read twice and keep. So we do not tidy it. Quoted words stay exactly as the educator wrote them, and if no quote was recorded, the story does not invent one to sound better.
03
Interpretation yes, invention never.
There is a real difference between reading meaning into what you saw and making things up. The first is professional practice. The second is fabrication that someone may later judge a child by. Drafts stay anchored to the observation, and anything the note does not support is raised as an assumption to confirm rather than written in as fact.
04
Every story should read like nobody else's.
A folder of near identical documentation helps no one. Families skim it, assessors see through it, and educators resent writing it. Run the same note twice and you should get two genuinely different pieces of writing, because the child in front of you is not a template.
05
Documentation is professional work about real children.
This is not marketing copy. It goes into a child's record, families read it, and it can be looked at years later. Every draft is checked for diagnosis language, other children's identifying details, sensitive family information, and physical safety moments, and those are raised for your review against your own service's process.
06
Your work stays yours.
Everything you write stays in your account, editable and exportable into whatever system your centre already uses. Cancel any time and it is all still there. We are not interested in holding documentation hostage to keep a subscription, and a product that needs to do that has already failed.
Who builds it
A small team in Aotearoa New Zealand, building for the sector we came from.
StoryLoop is made by Aria Care, a small New Zealand software company. We are not a large international platform with a childcare product somewhere in the portfolio. Early childhood documentation is the thing we work on, and Te Whāriki and the EYLF are the frameworks we build around rather than adapt to afterwards.
Being small is the reason the product changes quickly. When an educator emails to say a particular kind of story comes out wrong, or that something is confusing on a phone, it goes into the next build rather than a roadmap review in six months. Several things in StoryLoop right now exist because one kaiako took the time to tell us they were missing.
It is also why we would rather say plainly what the product does not do. We have no interest in selling anyone the idea that documentation can be fully automated. It cannot be, and anyone claiming otherwise has not sat with a child long enough to know why.
If you use StoryLoop and something about it is wrong, tell us. Every message is read by the people who build it, and it genuinely shapes what gets made next.
Judge it on one real observation.
Paste something you actually wrote this week, however rough it is. That is the only test that matters.
No credit card required.