Does Your Nursery-Management Software Already Cover Safeguarding?

Looking at safeguarding within broader systems such as Famly and Ovivio

Information checked: September 2026

A word before we start

We created On the Button, so this is not an independent review. This article is not intended to suggest that broader nursery-management systems are poor at safeguarding simply because safeguarding is not their only purpose.

Famly and Ovivio are both much broader nursery-management platforms. They bring together large amounts of information about children, families and the running of a setting, and both include safeguarding-related functions.

For some settings, the safeguarding functions already available within a nursery-management system may be entirely sufficient.

The important question is not simply: Does my software include safeguarding?

It is: Is the safeguarding within it robust enough, accessible enough and visible enough for the way we actually work?

The issue is not whether safeguarding is digital

Moving safeguarding information from paper into software does not automatically make it safer.

Digital information can still be difficult to find, overlooked or disconnected from what happens next.

A broad nursery-management system may also hold attendance, parent messages, observations, learning journeys, bookings, staff information, invoices, payments, medication, diaries, photographs and dozens of other everyday records.

That breadth can be extremely useful.

But safeguarding information is different. When something important is recorded, the right person may need to know immediately, access may need to be tightly controlled, actions need to be followed through and the full history may need to make sense months or years later.

So one of the most important questions is:

Could an important safeguarding concern become just another piece of digital information?

What Famly currently provides

Famly is a broad early years management platform rather than a specialist safeguarding system.

Its current public information shows a genuine range of safeguarding and health-and-safety functions. These include:

• safeguarding disclosure notes within a child's profile

• regular, sensitive and safeguarding note types with visibility controls

• accident and incident reporting

• interactive body maps for injuries

• management review or approval flows for accident and incident reports

• parent/carer notification and acknowledgement

• medication records

• attendance and absence information

• digital headcounts

• allergy and health information

• permissions controlling access to information

Famly's safeguarding-disclosure notes can be marked separately from ordinary notes and can be restricted according to permissions. Accident and incident reports sit in the child's safeguarding area and can include body maps, first-aid information, witnesses, external reporting information and parent acknowledgement.

Those are meaningful safeguarding functions, and it would be wrong to dismiss them simply because Famly also manages many other parts of nursery life.

The questions to ask Famly

The public information reviewed makes some safeguarding functions clear, but it does not answer every question we would want answered before deciding that no separate safeguarding system was needed.

Ask Famly to demonstrate:

• what happens after a practitioner records a safeguarding disclosure

• who is alerted and how quickly

• what happens if the usual DSL or manager is absent

• how actions, decisions and outcomes are attached to the original concern

• whether several low-level observations can be brought together into a clear safeguarding chronology

• how child, family and staff wellbeing concerns are handled when they do not yet meet a safeguarding threshold

• how parent complaints that may have safeguarding implications are followed through

• whether there is a genuinely anonymous route for staff whistleblowing

• what an exported safeguarding record looks like when it is shared with Social Care, the LADO or Ofsted

• how safeguarding information is surfaced to senior leaders among all the other information held in the platform

Some of these functions may already be available. The point is to ask to see them working rather than assume that a safeguarding tab automatically provides the full safeguarding journey.

What Ovivio currently provides

Ovivio is also a broad nursery-management system. Its children's profiles bring together attendance, contacts, bookings, learning journey, finance, notes, diary information and safeguarding in one place.

Its current public safeguarding information clearly includes:

• accident and incident reporting

• accidents from home

• injury-location recording

• timestamps and first-aid details

• approval and signature workflows

• medication records

• child health, dietary and allergy information

• attendance and booking information

• safeguarding information within the child's profile

Ovivio's current help information shows that accident and incident reports can move through draft, approval and signature stages, and can be filtered by date, report type, supervisor, room and injury type.

Again, that is useful functionality and may meet the needs of some providers.

The questions to ask Ovivio

What is less clear from the public information is the depth of the safeguarding-concern journey beyond accidents, incidents and associated child records.

Ask Ovivio to demonstrate:

• how a practitioner records a safeguarding concern or disclosure that is not an accident or incident

• who is alerted and by what route

• whether urgent safeguarding information is treated differently from ordinary child-profile information

• how actions, decisions and outcomes are recorded

• how a safeguarding chronology is built over time

• whether wellbeing concerns can be recorded separately from safeguarding

• how parent complaints with safeguarding implications are connected

• whether staff concerns and anonymous whistleblowing are supported

• what permissions apply to practitioners, managers and group leaders

• what an external safeguarding report looks like

The public material reviewed does not establish that these functions are absent. It simply does not explain them clearly enough for us to assume that they are present.

Broad nursery-management software has real advantages

There are good reasons for keeping information together.

A practitioner may already be logged into the system throughout the day. Attendance, health information, parent communication and accidents can sit alongside the child's other records. Staff do not need to learn multiple pieces of software, and information may be easier to enter because the system is already part of everyday practice.

For some settings, that convenience and breadth may outweigh the advantages of a separate specialist safeguarding system.

The question is whether safeguarding remains prominent enough inside that broader environment.

Could safeguarding information get lost among other digital data?

This is the question that you should ask most carefully.

Paper records can be lost in filing cabinets. Digital records can be lost in volume.

Not physically lost, but:

• not seen quickly enough

• stored in the wrong part of a child's record

• visible only to someone who is not currently working

• not connected to an earlier concern

• not followed through to an action or outcome

• buried among routine notifications and everyday operational information

• difficult to turn into a coherent chronology later

A specialist safeguarding system should make important information difficult to overlook.

That does not mean a general nursery-management system cannot do the same. It means you should make the supplier show you exactly how it does it.

Specialist does not automatically mean better

A specialist system should not earn its place simply because the word safeguarding appears in its name.

It still needs to be easy for practitioners to use, secure, properly permissioned, reliable and proportionate.

Equally, a broad nursery-management platform should not be assumed to provide enough safeguarding depth simply because it contains accident forms, safeguarding notes or a safeguarding area.

Both types of system should be tested against the same practical journey.

The test for each supplier

Give every supplier the same real-life example.

A practitioner notices a mark on a child and, during the conversation that follows, the child says something that worries them.

Then ask the provider to show you:

• where the practitioner records it

• how quickly they can do that while still working with children

• who is told that the concern has been submitted

• how that person is alerted

• what happens if that person is absent

• what previous concerns, injuries, absences or wellbeing entries they can see

• where their decision is recorded

• where the action is recorded

• how the outcome is added

• how the concern appears in the chronology later

• what the record looks like if it is shared externally

If the safeguarding function sits inside a large nursery-management platform, add one more question:

How do you make sure this cannot disappear among everything else happening in the system?

When the safeguarding within your nursery-management system may be enough

It may be perfectly reasonable to use the safeguarding functions already within Famly, Ovivio or another broad nursery-management platform if:

• the whole appropriate team can record concerns easily

• the right people are alerted reliably

• permissions protect confidential information

• concerns can be followed through from first record to outcome

• patterns and previous information are easy to see

• the chronology is clear

• reports can be shared externally without rewriting the history

• wellbeing, complaints and staff concerns are handled in a way that meets your needs

• senior leaders can readily see what requires their attention

If it can demonstrate all of that, adding another system may simply create duplication.

When a separate specialist safeguarding system may still be worth considering

A separate specialist system may be worth exploring if:

• safeguarding feels like a small feature inside a much larger system

• practitioners are unsure where to record lower-level concerns

• urgent concerns rely mainly on somebody logging in and finding them

• actions and outcomes are held somewhere different from the original concern

• wellbeing information is difficult to distinguish from safeguarding

• complaints and whistleblowing sit outside the safeguarding picture

• leaders find it difficult to see patterns or chronologies

• group leaders cannot easily see what needs attention across settings

• producing a safeguarding history requires information to be gathered from several areas

Where On the Button fits

On the Button does not try to replace a nursery-management platform such as Famly or Ovivio.

It was built from practice up around the safeguarding journey itself.

The starting point is somebody noticing something. The system is then designed to make sure that information reaches the right people, remains visible, is connected to actions and outcomes and contributes to a wider chronology.

It brings safeguarding together with child, family and staff wellbeing, complaints and anonymous whistleblowing, while keeping access controlled.

That means a provider could use On the Button alongside a nursery-management system rather than replacing it.

Whether that additional specialist layer is worthwhile depends on what the safeguarding functions you already have can actually do.

Final Thoughts

We would not tell a nursery using Famly or Ovivio that it automatically needs separate safeguarding software.

We would tell them to test what they already have properly.

Do not ask: Have we got a safeguarding function?

Ask:

Is it robust enough?

Is it accessible enough?

Is it visible enough?

Will the right person know when something important has been recorded?

Can we follow it through and show exactly what happened next?

And can we be confident that important safeguarding information will not become lost among all our other digital data?

If the answer to all of those questions is yes, your existing system may be enough.

If not, that is the point at which a specialist safeguarding system becomes worth considering.

Accuracy note: Features, packages and terminology can change. Where a function was not clearly described in the public information reviewed, this article does not assume that it is unavailable. Ask the provider to demonstrate anything important before making a buying decision.

Reviews See How it Works Pricing

Sources

This comparison uses the providers’ own descriptions of their purpose and approach: Famly, Ovivio and On the Button. Product details should be checked directly before making a decision.

Safeguarding Software Demo
Safeguarding Software Questions