Skip to main content
Nurtalo

Platform

Every nursery workflow, working from one record

Nurtalo is a single system rather than a bundle of separate tools. Attendance feeds ratio awareness, admissions feeds the register, care feeds family updates, and everything sensitive is recorded once with a clear owner and time.

Try free for 30 daysHow data is protected

What one record actually means

  • Entered once. A care event, an observation or an accident is recorded where it happens and flows to families, reports and evidence without being retyped.
  • One permission model. Every module answers to the same membership, role and site scope, so access does not drift between areas.
  • One audit trail. Sensitive changes are written as history you can produce later, rather than overwritten in place.

Inside and outside

Software that follows the setting, not the other way round

A nursery day moves between the room, the garden, the sleep room and the office. Recording is designed for short interruptions on a phone or tablet, and for the office work that comes afterwards.

A nursery garden with a wooden mud kitchen, waterproof coats on hooks and raised herb planters after rain.
Outdoor provision at a fictional setting we use for our own testing.

One record

Entered once, and still answerable months later

Every module in Nurtalo writes to the same record with the same permission model and the same audit trail. An accident recorded in the room is the accident a family acknowledges, the accident in your monthly analysis and the accident an inspector is shown, without being retyped or reconciled by hand.

  • One membership, role and site scope across every area
  • Sensitive changes written as history rather than overwritten
  • Exports and reports built from the operational record itself
  • No module that keeps its own private copy of a child

Daily operations

Attendance, ratios and the shape of the session

Registers and room presence

  • Sign children in and out with the responsible adult recorded
  • Move children between rooms as a recorded event, not a mental note
  • Live headcount per room derived from entered events only
  • Visitor and emergency roll-call surfaces for the whole setting

Ratio awareness

  • Room-level staffing and headcount compared as the session runs
  • Incomplete pictures stated as incomplete rather than shown as fine
  • Time-specific eligibility handled as a reviewed, evidence-backed decision
  • No silent assumption that an absent record means everything is in order

Bookings and absence

  • Booking patterns, one-off exceptions and change requests
  • Absence notices submitted by families and acknowledged by staff
  • Expected arrivals reflect what families have already told you
  • Session requests carried through from admissions

Operational work

  • Tasks, handovers and daily operational logs
  • Menus and meal planning with published versions
  • Site-level checks kept as history rather than notice-board paper
  • Outstanding work surfaced before general activity

Care, health and safety

Safety records that hold up when someone asks

These capabilities are base entitlements. They are never gated behind a plan, and they never depend on a paid add-on being active.

Daily care

  • Structured meals, sleeps and personal care events
  • Corrections recorded as corrections, with the original preserved
  • Care plans and their current status per child
  • Daily summaries assembled from what was actually recorded

Health and medication

  • Allergy and health alerts attached to the child record
  • Medication authorisations with explicit family consent
  • Administrations recorded against authorisation, dose, time and witness
  • Accidents and incidents with follow-up and family acknowledgement

Safeguarding

  • Cases restricted to named responders rather than the whole team
  • Chronology entries and actions kept in order
  • Access itself recorded, so who saw what is answerable
  • Never aggregated casually into group-level dashboards

Emergency readiness

  • Roll-call started from the live register
  • Every child marked present, accounted for or outstanding
  • Emergency contacts and permissions reachable without a search
  • The whole event kept as a record afterwards

Learning and families

Sharing the day deliberately

Learning journeys

  • Observations with media, linked to one or several children
  • Next steps and weekly planning kept with the observation
  • Assessments with items and outcomes rather than a single score
  • Framework links so evidence maps to your chosen curriculum

Family communication

  • Message threads with an explicit participant list
  • Newsfeed posts and announcements with a named audience
  • Polls and RSVPs for events and closures
  • Read receipts, so 'sent' and 'seen' are different facts

Permissions and consent

  • Consent wording versioned, with the decision recorded against a version
  • Photo, outing, sun cream and similar permissions per child
  • Withdrawal handled as a first-class action, not a support request
  • Guardian grants and pickup credentials managed explicitly

Documents and forms

  • Documents published to specific families with acknowledgements
  • Digital forms with structured fields and submissions
  • Assignments visible to the family alongside the nursery's messages
  • Everything traceable back to who sent it and when

Running the business

Admissions, workforce, finance and compliance

Admissions

  • Enquiries, visits, offers and onboarding tasks in one pipeline
  • Status changes recorded as events with an author
  • Session requests captured before the child starts
  • A child arriving next month already has the information you need

Workforce

  • Staff profiles, site assignments and availability
  • Shifts, leave requests and time events
  • Supervisions with shared outcomes and private notes kept separate
  • Qualification records with evidence and reviewed statutory decisions

Finance

  • Billing accounts, payers and the children they cover
  • Fee plans, assignments and funding entitlements
  • Invoices, lines, payments and allocations
  • Online payment and mandate handling exists as a reviewed boundary and is not yet switched on

Compliance

  • Check templates, runs, items and results
  • Policy versions with acknowledgement coverage
  • A compliance register with owners and review dates
  • Evidence kept with authors and timestamps, not reconstructed later

How it behaves

Product rules that apply across every module

These are not features of one screen; they are commitments the whole system keeps.

Safety capabilities are never a paid extra

  • Attendance, headcount and ratio awareness
  • Accidents, incidents, medication and safeguarding
  • Emergency information, permissions and consents
  • Immutable audit history and a full data export

Access is decided on the server

  • Every record belongs to an organisation and a setting
  • Membership records are the source of truth, not a browser claim
  • Row-level security applies to reads and writes alike
  • Cross-setting access is refused by the database, not hidden by the interface

State is stated plainly

  • Draft, queued offline, submitted, approved, shared and signed are different
  • Nothing reads as done while it is only saved on the device
  • Unknown is never rendered as a reassuring green
  • Receipts say what happened, who did it, when, and who can see it

Accessible for the people actually using it

  • WCAG 2.2 AA treated as the working minimum, checked as we build
  • Full keyboard operation with a clearly visible focus indicator
  • Minimum 44 x 44 pixel targets on every product action
  • Status never communicated by colour alone
  • Readable at 200% text size, and respects reduced-motion preferences

Honest about the network

  • Loading, empty, error, permission-denied and offline states everywhere
  • Your typed input survives a recoverable error
  • Authenticated pages are never served from a stale cache
  • Offline shows an offline page, not yesterday's records dressed as today's

Questions

About the platform

Which modules are available today?
The areas described on this page exist in Nurtalo Web. Some capabilities are deliberately delivered as reviewed boundaries that are switched off until they are complete: online payments, e-mail and push delivery, document virus scanning and data-export brokering are the current examples. Where that is the case we say so rather than implying they are live.
Can we turn safety capabilities off to reduce cost?
No. Attendance, headcount, ratios, accidents and incidents, medication, safeguarding, emergency information, permissions and consent, immutable audit and full data export are base entitlements in every configuration.
Does Nurtalo work on a tablet in the room?
Yes. Nurtalo Web is responsive and can be installed to a device home screen. A dedicated managed kiosk application for sign-in is planned and is not yet released.
Can we export everything?
A full organisation-wide export is a base capability. The export broker is implemented as a reviewed boundary and is enabled deliberately rather than left permanently open.

Want to see a specific module?

Start with the part of your day that is hardest right now and explore it in your own nursery workspace for 30 days. No card details are needed to begin.

Try free for 30 daysSee pricing