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.
Leo, 20
Ōtautahi Christchurch, Aotearoa
Hi, I'm Leo. I built the first version of this when I was 19.
I am not an early childhood teacher. I want to be upfront about that, because it would be easy to pretend otherwise and educators can smell it a mile off.
I started StoryLoop because I kept seeing kaiako still writing learning stories after the children had gone home. The job they trained for is with the tamariki. The job that actually eats their evening is writing about the tamariki afterwards, unpaid, long after the details have gone fuzzy. Nobody in the sector seems surprised by that anymore, and that is exactly what made it worth doing something about.
So I built something, put it in front of educators, and asked them to tell me what was wrong with it. They did, at length. Early drafts were too flowery, invented things nobody had seen, and tidied children's words into proper sentences, which turned out to be the worst thing it could possibly do. Most of what StoryLoop is now exists because an educator told me a version of it was not good enough.
I still build every part of it myself, from Christchurch. That means it moves slower than a company with a team behind it. It also means that when you email StoryLoop, I am the one who reads it, and if you tell me a story came out wrong I can usually do something about it that week.
I am 20, building this for a sector I did not grow up in. What keeps it honest is that the people using it tell me, straight, when I get it wrong.
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.
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.
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.
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.
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.
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.
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.
One person in Ōtautahi builds this, and that is on purpose.
StoryLoop is part of Aria Care, a New Zealand business, but there is no team standing behind that name. It is me. I write the code, I answer the support email, and I decide what gets built next. Early childhood documentation is the only thing I work on, and Te Whāriki and the EYLF are what StoryLoop is built around rather than adapted to afterwards.
The honest trade-off: one person ships big features slower than a company with thirty engineers, and if it is the middle of the night in New Zealand your email waits until morning. What you get back is that the person who built the thing is the person who reads your message.
- Business
- Aria Care, a New Zealand business (StoryLoop is its early childhood product)
- Based in
- Ōtautahi Christchurch, Aotearoa New Zealand
- Built for
- Te Whāriki in New Zealand and EYLF V2.0 in Australia
- Your work
- Editable and exportable at any time, on every plan, including after you cancel
- Contact
- ariacareapp@gmail.com
Judge it on one real observation.
Paste something you actually wrote this week, however rough it is. That is the only test that matters.
Three stories a month free, no card needed.