The admin grows. Time for children does not.
an AI use policy staff and families can read, written before any tool touches enrolment or child data.
Early learning centres, schools and activity providers all report the same imbalance: the compliance, communication and administrative load grows every year while the hours in the day stay fixed. The work that can move is the writing, the chasing and the assembling, never the care.
Early childhood education · Schools · Children's sport and activity providers
What we hear from providers.
The same four, from a two-room centre to a multi-campus school.
Enrolment and waitlists
Enquiries, tours, waitlists and enrolment forms handled by email and phone, with the same questions answered by hand every day.
Family communication
Newsletters, incident notes, reminders and replies written at the end of the day by the people who spent it with children.
Compliance documentation
Quality improvement plans, policies, incident records and audit evidence assembled from scattered files before every assessment.
Rostering and ratios
Rosters rebuilt weekly by hand around ratios, qualifications, leave and casual availability.
First use cases, with the number we scope to.
Each is scoped in the free audit with a target, a named owner and a human review point. The targets are what we set; the audit puts your own number on them.
Enquiry and enrolment admin
Enquiries answered from your own policies and availability, tours booked, waitlist positions confirmed and enrolment documents chased, with a person handling anything about a specific child.
Family communication drafts
Newsletters, reminders and routine replies drafted in your voice for an educator to check and send. Incident communication stays with a person, always.
Compliance packs
Quality improvement plans and assessment evidence assembled from the records you already keep, for the nominated supervisor to review, rather than built from scratch the week before.
The rules that apply.
Children's data and safety set the boundary for any tool. This is what we check each use case against. It is not legal advice; it is the list your regulator and your board will ask about.
- 01Child Safe Standards. The National Principles for Child Safe Organisations and the state standards (for example Victoria's eleven Child Safe Standards) govern how any system that touches children's information or communication is designed and reviewed.
- 02Working with Children Checks. State-based checks for staff and volunteers. An agent that helps with rostering or onboarding must never let an unchecked person near a shift.
- 03National Quality Framework. The Education and Care Services National Law and Regulations, the National Quality Standard and ACECQA's requirements for early childhood services, including ratios, qualifications and record-keeping.
- 04Privacy Act 1988 and state schools' privacy law. Children's personal and health information, parental consent, and where enrolment data may be processed. Government schools sit under their state's privacy legislation.
- 05School registration and wellbeing frameworks. State registration requirements (for example the VRQA in Victoria) and the Australian Student Wellbeing Framework shape what a communication or record must contain.
Guardrails that matter most here
- 03Data governed: minimum child data per task, and none of it to a model you have not approved.
- 05Human in control: anything about a specific child goes through an educator.
- 10Built with people: educators and families shape the tool before it ships, not after.
How a first engagement usually runs.
Week one and two: the free audit. We walk enrolment, family communication and the compliance calendar with the director or principal and the people who run the office, and score the six pillars against your standards.
Weeks three to eight: enquiry and enrolment admin on a free trial, because it produces a countable number (enquiries answered, tours booked, documents received) without touching anything about a specific child. The AI use policy for staff and families goes out in the same weeks.
Then the roadmap, with the next use case chosen by the number the first produced, all of it against the Guardrails Framework.
Questions.
Does any child data go into an AI model?
Only what a task needs, only to models you have approved, and never for anything about a specific child without an educator in the loop. The audit maps that for each use case, and the policy says it in words families can read.
Will educators have to learn new software?
The tools fit the work you already do, in the systems you already use. Training is part of every engagement, and adoption is measured the same way everything else is.
Can this help before an assessment and rating visit?
Yes. Compliance packs assembled from the records you already keep are one of the first use cases we scope for early childhood services, with the nominated supervisor reviewing and signing off.
Where do we start?
With the free audit: a readiness scorecard, your three highest-return use cases with a number on each, and a 90-day roadmap. Three hours of your time.
Is AI appropriate around children’s data?
With the right boundaries, yes. Children’s information stays in your controlled systems, access follows staff permissions, and nothing is shared with public models. Anything touching welfare or safeguarding goes to a human first, every time.
We are a small centre. Is this really for us?
The free audit costs nothing and is sized for businesses from about 10 staff. Small centres often see the fastest wins because one administrator carries everything, and giving them hours back changes the whole week.