Why Oversite
What we cover Case study Security & data Procurement Moving across Support Roadmap Book a demoChildren & families
Enrolments & attendance Enquiry to roll call, one record The guardian portal Journal, invoices and consents Learning & records Te Whāriki entries, media library Daily care Sleep, nappies, absences, excursions Health & medical Plans, medication, allergies Home-based services Schedule 1A, educators, coordinatorsCompliance & safety
Ratios & funding Schedule 2, RS7, ECE Census Hazards & incidents Registers, drills, HSWA evidence Governance & quality ERO cycles, consultation, checklists Reports 72 built in, across thirteen areas Automation & setup 26 daily checks, your wordingRunning the organisation
Staff & rosters Records, pay parity, costed rosters Hiring & recruitment Vacancies, careers page, safety checks Billing & payments Invoices, bonds, late fees Property & assets Sites, equipment, fleet Contractors & works Jobs, projects, vetting Portals & kiosks Sign-in tablets for every door Seeing your day Dashboard, tasks, messagesAbout
Oversite is built in New Zealand for New Zealand early learning, by Kiwis, for Kiwis. The people who write the code and the people who answer the phone are the same dedicated team, and they are here.
Early learning here runs on rules that are specific to this country: Schedule 2 and Schedule 1A ratios, RS7 returns three times a year, the ECE Census, pay parity attestations, seven-year record retention.
Oversite starts from those rules. Ratios are checked against the schedule your service is licensed under. Funding returns are assembled from attendance you have already recorded. Census readiness is a report you can run in August rather than a scramble in October. That is the whole design, and it is why the product fits without a spreadsheet beside it.
Oversite has been developed alongside established New Zealand early learning organisations: multi-site groups with real rolls, real rosters and real funding returns riding on it. Not a prototype validated with interviews, but a system built against the daily work of people running services.
That is why the roll call shows booked time against actual: it is the gap that costs funding. Why the hazard register tracks review dates: that is what lapses. Why the roster totals cost while you build it: finding out afterwards is too late. Every one of those came from somebody who needed it on a Tuesday.
Feature requests go on a shared wishlist every customer can see and vote on. Ideas are visible to every customer the moment they are posted, votes are weighted across organisations so a smaller service isn't outranked by a louder one, and the status of each is visible.
You can see what is coming, and you can influence it. That is a practical advantage of buying from a team you can reach.
The administrative side and the educator side are the same organisation, so they are the same system, together with the health, safety, property and contractor work that is just as much a part of running early learning.
Every module is included at every size. There is no tier that unlocks compliance, and no add-on pricing for the parts you are legally required to do.
You deal directly with the people who build it. No account manager relaying your question to a development team in another timezone, and no support tier to upgrade into before somebody takes your call seriously.
The near-term work is depth rather than breadth: making the compliance and funding paths as close to automatic as the rules allow, and continuing to close the gaps customers raise on the wishlist.
If there is something your organisation needs that Oversite does not do yet, that is worth a conversation rather than a workaround.
Book a demo and ask whatever you need to. You'll hear back within one working day.
Book a demo