Oversite watches the dates so nobody has to

Most compliance failures are not decisions. They are dates that passed while everyone was busy. Oversite runs twenty-six scheduled jobs every day looking for exactly those, and tells the right person before the date matters rather than after.

26 scheduled checks daily
In-app and email
Wording and settings are yours

The reminders that arrive before the deadline

Warrants, certificates, vetting, insurance, drills, policy reviews: every one of them has a date attached, and every one is checked nightly. What is coming up reaches the person responsible for it while there is still time to act.

The same schedule generates invoices, creates the day's attendance sessions, closes records left open, and chases overdue accounts. Work that would otherwise be somebody remembering to do it on the right morning.

Staff certificates and safety checks approaching expiry
Contractor insurance and health-and-safety documents lapsing
Evacuation drills, healthcare plan reviews, policy reviews due
Pay parity attestations and progressions falling due

The Email templates list in dark mode, showing every automated message the system sends with its name, the module it belongs to and whether it is active.

The Tasks list in dark mode, showing follow-ups raised across the organisation with their status, due date and whether they are private or visible to the site.

Every automated email, in your words

Every automated email is a template you can open and rewrite, subject and body, with merge fields for the child, the site, the date. If a reminder sounds wrong coming from your organisation, change it rather than apologising for it.

All seventy-seven of them, including the ones nobody thinks about until they land badly, such as an overdue invoice reminder or a notice that a child was signed out automatically.

Subject and body, edited in place
Merge fields listed per template, so nothing is guesswork
Reply-to set to an address families recognise
Preview before it goes anywhere

The Invoice issued email template open for editing, with a subject line built from the invoice number and site name merge fields, a body using those same fields, and a panel listing nine available placeholders such as Payer Name, Invoice Total and Invoice Due Date, each clickable to copy.

What runs, and when

Twenty-six jobs on a schedule. Nothing to switch on, nothing to configure, and nothing that depends on somebody remembering.

Expiry watching, daily

Staff practising certificates approaching expiry
Safety checks due for renewal
Driver licences expiring
Vehicle WOF, registration and servicing
Contractor public liability insurance
Contractor health & safety plans
Contractor staff vetting
Household associate vetting

Compliance deadlines, daily

Evacuation drills falling due
Healthcare plan reviews
Child protection policy reviews
Governance reviews
Coordinator visits overdue
Staff compliance gaps
Pay parity attestations
Pay parity progressions due

Work that would otherwise be manual

Attendance sessions created at 00:01
Open records auto-closed at 23:59
Roster lock grace period applied
Invoices generated weekly
Educator payments generated weekly
Overdue invoice reminders sent
Tasks reminded before they are due
Public holidays seeded each year

Each of these finds the records that qualify, works out who is responsible for them, and notifies those people in the app and by email, using wording you control. The ones that generate something (invoices, attendance sessions, educator payments) produce a draft you review rather than acting on your behalf unsupervised.

And your vocabulary too

Absence reasons, incident causes, job statuses, decline reasons, vetting statuses, trades, areas, drill types: all of these are lists you maintain rather than values compiled into the product. If your organisation calls something by a different name, change it.

Behaviour follows flags on those records rather than their names, so renaming an option is safe. Nothing anywhere asks whether a status is called Won; it asks whether the record is flagged as one.

Around 90 configurable lists across 19 areas
Your own statuses, reasons, categories and types
Colours and defaults set per option
Renaming an option never changes what it does

A configuration screen in dark mode showing the Children config group with its lookup tables listed, among them absence reasons, ethnicities, immunisation statuses, iwi and languages, beside an editable table of absence reasons with colours and a default flag.

Told once, in the right place

Notifications arrive in the app and by email, and each one links to the record it concerns rather than describing it. Fewer emails that say "something needs your attention" and more that take you to the thing.

People choose what they are notified about, so a centre manager and an administrator don't receive identical inboxes.

In-app notifications alongside email
Each notification links to the record it is about
Per-person control over what they are sent
Nothing sent twice for the same event

The Site notifications screen, where a person chooses which centres they want to hear about rather than receiving everything from everywhere.

See it with your own setup

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