Occupancy and demand
- Places, attendance and expected demand across settings
- Admissions pipeline compared site by site
- Patterns visible without exporting spreadsheets
Groups and multi-site
Group oversight without collapsing every setting into one pile
Nurtalo HQ gives an organisation-wide view across your settings, then lets the right people drill into a site. Scope is enforced by the system, so oversight never quietly becomes unrestricted access to children's records.
What multi-site providers keep asking for
- Comparable settings. The same modules, vocabulary and states in every nursery, so a number from one site means the same thing at another.
- Oversight that is not a back door. Group visibility of occupancy and compliance without granting person-level access to every child record by default.
- New settings that start correctly. A setting opened next quarter inherits the same structure instead of inventing its own.
Scope
One organisation, several settings, one set of rules
HQ starts from the group and narrows deliberately. Occupancy, staffing pressure and compliance coverage are read as aggregates first, and a named person can open a single setting only where their membership allows it. Adding a nursery does not mean rebuilding your vocabulary: the rooms, states and permissions arrive already shaped like the rest of the group.
- Site membership decides what a regional manager can open, not a checkbox on a profile
- Aggregate figures state the sites they cover and the sites they could not read
- A new setting inherits modules, roles and policy versions rather than starting blank
- Every drill-down into person-level detail is written to the audit trail
Across the group
Comparable settings, not identical ones
Consistency is about the record, not the character of a nursery. Each setting keeps its own rooms, routines and garden; what matches across the group is the way things are written down.
Nurtalo HQ
Aggregate first, drill down deliberately
HQ views are organisation-wide by design. Person-level detail appears only where both the metric and your access allow it.
Safety and compliance
- Outstanding compliance checks per setting
- Policy versions and acknowledgement coverage
- Safeguarding kept restricted, never aggregated casually
People and practice
- Workforce records, supervisions and leave across the group
- Consistent modules and vocabulary in every setting
- New settings inherit the same structure from day one
Group workflows
The work a group office actually does
- 1
Compare settings on like-for-like terms
Occupancy, attendance and admissions read the same way in every nursery because they come from the same recorded events, not from locally invented spreadsheets.
- 2
Chase what is outstanding
Compliance checks, policy acknowledgements and supervisions that are overdue are visible per setting, so the conversation is specific rather than a general reminder.
- 3
Open a new setting
Rooms, roles, fee plans, policies and check templates start from the group's structure, so a new nursery is consistent from the first day.
- 4
Move people between settings
Site assignments are explicit records, so a practitioner covering another nursery gains exactly the access that was granted and no more.
- 5
Answer a group-level question
Reports and exports are built from the operational record, so an answer to head office and an answer to a regulator come from the same source.
Governance
Central control that stands up to scrutiny
Membership is the source of truth
- Access derives from organisation and site membership records
- Decided on the server, never from something a user can edit
- Row-level security applies to every read and write
- Cross-tenant access is denied by the database, not by the interface
Change you can evidence
- Sensitive actions written to an immutable audit trail
- Policies versioned, with acknowledgements recorded
- Operational history kept rather than overwritten
- Full export available for the whole organisation
Scope is explicit
- HQ access and setting access are separate grants
- A group metric does not imply a right to the underlying records
- Safeguarding stays with named responders in the setting
- Drill-down is a deliberate step, not a default view
Consistency without rigidity
- Shared templates for checks, policies and fee structures
- Local settings still describe their own rooms and sessions
- One vocabulary across the group's reports
- Differences between settings become visible instead of hidden
Questions
From group operations and compliance leads
- Can head office see every child's record?
- Not by default. Organisation-level access grants aggregate oversight; person-level records require access that both the metric and the membership scope permit. Safeguarding casework remains restricted to named responders.
- How do you stop one setting seeing another's data?
- Separation is enforced in the database with row-level security driven by membership records, not by hiding menu items. Cross-setting reads are refused by the database itself.
- Can we roll out setting by setting?
- Yes, and for most groups that is the sensible sequence. We will talk plainly about what transfers cleanly, what needs re-entering, and where Nurtalo is still being built.
- Is there a separate group application to install?
- No. Nurtalo HQ is a desktop-first workspace inside Nurtalo Web rather than a separate product to deploy.
Planning a rollout across several settings?
We will talk honestly about sequencing, what transfers cleanly, what needs re-entering, and where Nurtalo is still being built.