Available now
Student admission
Keep enquiry, guardian and enrolment context connected for the new-intake season.
Explore capability Preschools
Calm daily operations for early years
A calmer preschool day—for families and every team behind it.
Connect admissions, arrival, attendance, authorised care notes, fees, transport and parent updates around one child-and-guardian record.
- 90-day trial
- No card
- Fit review included
- Parent-firstarrival and communication context
- Role-basedaccess to child and health records
- Invoice-ledfee collection with receipts
A calmer family experience
Give families a clear front door while staff keep one reliable record.
Connect guardian context, the daily child view and approved communication without exposing internal operating complexity to families.
- Guardian-linked
- Care permissions
- Approved updates
Family portal
Explore this workflow The day families need, in one place
Attendance, the daily schedule, invoices, learning updates, results and notices are organised around the child and guardian context.
A connected operating loop
Make the sensitive moments clear, calm and accountable.
Early-years teams need less operational noise, not less control. The page focuses on the hand-offs families notice most.
- 01
Arrival
Start with the right child and guardian context
Admissions and daily records keep guardian relationships attached to the child instead of relying on an informal contact list.
Guardian and child context remain linked - 02
Attendance
Mark the day without a heavy workflow
Teams can use the configured attendance flow and parent notification policy while corrections remain reviewable.
Attendance and correction history remain distinct - 03
Care notes
Keep health details behind the right permissions
Allergy and medication notes are available only to authorised roles; they are not exposed as general classroom data.
Sensitive records remain role restricted - 04
Pickup and updates
Use the channels the preschool actually configured
Notices, attachments and approved updates follow configured providers and retain a clear source inside the school record.
Channel readiness and delivery state stay explicit
Capability map
Build the operating system preschools and early-years teams need every day.
Open any capability for the detailed workflow, then shape the final scope around your roles, providers and rollout plan.
Available now
Student attendance
A simple daily record with configured notifications and correction evidence.
Explore capabilityAvailable now
Health records
Restrict allergies and medication notes to authorised staff.
Explore capabilityAvailable now
Fee collection
Term fees, pay links where configured and verified receipts.
Explore capabilityAvailable now
Transport management
Routes, stops and rider assignments where transport is enabled.
Explore capabilityAvailable now
Parent notification
Approved notices and updates through configured channels.
Explore capabilityLooking for the complete inventory? Browse 50+ modules across 9 workspaces.
A clear-fit plan
Set the operating boundaries once—then give every team a confident path.
Best fit
Preschools that want a light daily workflow while keeping guardian, fee and sensitive child context governed.
Review before rollout
Pickup, transport, health-note visibility and notification providers must match the preschool’s actual policy.
Data boundary
Sensitive health and child records remain limited to authorised roles.
Aira AI
Permission-scoped answers in 11 languages
Ask supported questions about records the person is already allowed to see. The source record and permissions remain authoritative.
See the governed AI suiteSwitching
Review mappings before committing supported student data
The student import flow maps CSV/XLSX headers, surfaces row-level validation and supports a dry run before commit.
See how switching worksDesigned for adoption
Move from the first mapped workflow to daily confidence in four stages.
Each stage has a clear owner, a visible outcome and an acceptance point before the next part of the institution comes online.
- 01
Map children and guardians
Confirm guardian relationships, classes, authorised staff and the minimum records needed for opening day.
- 02
Set daily boundaries
Configure attendance, correction, health-note and communication permissions before staff training.
- 03
Connect providers
Verify payment, messaging and transport dependencies that are part of the agreed scope.
- 04
Practice real scenarios
Run arrival, absence, fee receipt and parent-update scenarios before releasing them to families.
Bring your current process
Use the demo to review a real workflow, not a generic slide deck.
Plan with confidence
The questions preschools and early-years teams ask before a confident rollout.
01Can health notes be hidden from most staff?+
Yes. Health information is permission-aware and should be assigned only to authorised roles during configuration.
02Can parents receive automatic absence updates?+
The school can configure an attendance notification policy and an available delivery provider. A configured channel is required; the page does not assume every provider is active.
03Does the preschool need every module on day one?+
No. Start with the smallest useful daily flow, validate it with staff and families, then release the next agreed workflow.
04Can we collect fees online?+
Online collection is available when the school’s payment provider is configured and ready. Invoice, collection and receipt evidence remain separate records.
Start with evidence
Ready to review the fit for your preschool?
Use the trial and a workflow review to confirm scope, providers, data migration and plan availability before a wider rollout.