Pupil Protect

How the products fit together

Pupil Protect is six products that share one sign-in and one set of pupil and staff records. A concern logged in Safeguard can reach the right part of the school without anyone typing it twice, and only the people who need it see it.

Shared records at the centre of the six productsPupil and staff records, synced from the school’s MIS, sit in the middle. Safeguard adds concerns and plans. Staff adds allegations, kept apart. Visitors uses a watch list. Connect shares what you choose with other agencies. Health records medicines, first aid and accidents. Insight sees counts only.Shared recordsPupils and contactsStaffSynced from your MISconcerns and plansallegationscounts onlywatch listsharinghealthSafeguardStaffInsightVisitorsConnectHealth
Shared records sit in the middle, and each product uses only the part it needs. The same information is set out in words under What each product shares.

One sign-in, wherever you work

Staff sign in once and choose the school and product they need. People who work in more than one school, or for the trust, switch between them without signing out.

If someone has an account at two schools, they can link them to use one password and one two-step code. Only the person can link their accounts, after proving they own both email addresses. Both schools’ admins are told.

Linking changes how someone signs in, nothing else. Each school still decides what that person can see there, and records never pass between schools.

Choose where to sign in · Daniel, deputy DSL · example
  • Northfield AcademyDeputy DSLProducts: Safeguard, Staff, Visitors and Connect3 alerts4 products
  • Oakfield PrimaryDSL cover, linked accountProducts: Safeguard1 alertOpens Safeguard
  • Northfield Learning TrustTrust safeguarding leadProducts: InsightNothing waiting2 products
Switch school or product any time from the switchers, without signing out.

One set of pupil and staff records

Pupils, contacts, staff and attendance come from your management information system (MIS) and stay in sync. Every product reads the same records, so a pupil who joins mid-year appears in every product at the next sync.

Supported systems: Arbor, Bromcom, SIMS, iSAMS, IRIS Ed:gen, Compass, ScholarPack, Facility CMIS, Double First Engage, WCBS, RM Integris, Juniper Horizons, or a CSV import. How often records sync: [sync frequency].

What comes from the MIS is marked as such, so staff know where to correct it.

A public API, with scopes so you decide exactly what each integration can read or change.

Amelia, Year 10 · exampleFrom MIS, synced 08:12
Registration group10HN, tutor Mr J Patel
CharacteristicsPupil premiumFree school mealsYoung carer
Siblings in schoolBrother, Year 7
ContactsMother, maternal grandmother and aunt. Father: court order, no contact.
Attendance86.4% this year

Connected, but kept apart where it matters

Sharing records doesn’t mean everyone sees everything. These lines hold across all six products.

  • Concerns about adults stay in StaffPupil records never show them, and only the case manager and the DSL see the link to a child.
  • Reception never sees a child’s nameA watch list match tells reception what to do, not who it is about.
  • Insight holds counts, never namesNo record content and no pupil names, at school or trust level.
  • First aiders see health, not concernsConditions, allergies and healthcare plans, but never the chronology.
  • Agencies see only what you shareEvery view and download in Connect is logged for the DSL.
  • Schools stay separateOne sign-in across schools never mixes their records.

See how it would join up in your school.

A 30-minute demo, starting with the products you’re thinking about.