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, messagesWhat it covers
Hiring in early learning is not generic recruitment. A vacancy has to say whether the role counts toward your qualified ratio and where it sits on the pay parity scale, and nobody starts until their safety check clears. All of that lives with the applicant rather than in somebody's inbox.
Most job software treats a role as a title and a salary band. Yours has to answer questions the Ministry asks: is this person qualified, do they count, can they be left in charge.
Recording that on the vacancy means the answer is already there when you hire, rather than something worked out again on the day they start.
Every open vacancy can appear on a careers page we host on your behalf, written in your words. Nothing to build and nothing to keep in step, because closing a vacancy removes it.
If you already have a website, the same roles embed into it instead. Either way the applications land in the same place.
The list answers the question a manager has in front of them, which is not how many applied but who is waiting on them. Certificate type and right to work sit on the row, so a shortlist does not need six records opened to build.
Turning somebody down records why. Over a year that becomes an answer to a harder question: whether the roles are written the way the people you want read them.
Somebody who reads two strong yeses before writing their own is no longer giving a second opinion. They are endorsing the first one. Until you submit yours you can see how many of the panel have answered and nothing about which way they went.
The panel is emailed for you: when they are added, if the time moves, the day before, and again if their feedback has not come in. Nobody has to remember to send any of it, which is usually why it does not get sent.
The safety check has a referee step of its own and that is the statutory record. It only exists once you have decided to hire, so the calls that informed the decision were happening somewhere else: a notebook, an inbox, somebody's memory of a chat.
Recording the outcome as well as the words means a reference nobody could take shows as its own answer rather than as a blank somebody forgot to fill in.
A children's worker cannot start before they are safety checked, so the check is part of hiring rather than something onboarding catches up on. Until it is complete and approved, the hire button says why it will not proceed.
It can be overridden, because sometimes there is a real reason, but the reason is typed in and kept. The check itself then moves onto the staff record rather than being done twice, which is what keeps the evidence intact from applicant to employee.
Saying yes to somebody creates the four things that have to exist for them: a staff record, a login, their pay parity row, and access to the centres they will work at. They are created together, so there is no half-finished person in the system.
The login is deliberately switched off until somebody turns it on. Most people hired have a notice period to work, and a live account sitting there for six weeks is an account nobody is watching.
Good relievers turn up when you have nothing open. The talent pool keeps them, with the centres and hours that would suit them, so the next vacancy starts with a list rather than an advert.
Matching somebody creates a genuine application with the usual safety-check gate, and records that you approached them. A pool nobody can act on is a pool nobody maintains, so the point of it is that one click.
Volume is the easy number and the least useful one. A channel that sends forty applications and no hires is a channel worth stopping, and you cannot see that without both figures beside each other.
Median days to any answer is the one most organisations have never measured. It is how long a person waits to hear something either way, and it is the part of your process they describe to other people.
The Privacy Act says you must not keep personal information for longer than you need it. Once an application has been settled long enough, Oversite takes the person out of it overnight and leaves the shape of it behind, so the reporting above keeps working without anybody holding a filing cabinet of other people's details.
A file you have to keep can be held, with the reason written down, and the nightly job reports how many it left alone. Deleting on schedule is right up until the file is evidence in a dispute, which is the one case where the right rule gives the wrong answer.
Tell us how many sites you run and what you're using now, and we'll show you the parts that matter most to you. No obligation, and you'll hear back within one working day.
Book a demo