Why it matters

Most schools can tell you a concern was raised. Far fewer can show what happened next.

Concerns live in notebooks, inboxes and corridor conversations. Care is the response backbone: the place a concern is logged, routed to a named person, acted on, and evidenced, so pastoral practice is defensible rather than personality-dependent.

3

record systems in one place: safeguarding concerns, behaviour observations and the SIAS support workflow.

1

named holder on every concern, with open, overdue and closed states visible to leadership.

100%

of decisions carry an audit trail: who saw it, who acted, when, and what was decided.

About the system

A live case system,
not a survey.

Staff log concerns as they arise. Each record is filed against a controlled category, routed to a named holder, and tracked through to a decision, with the safeguarding log kept structurally separate from behaviour.

  • Safeguarding concern log and behaviour observation log, never merged
  • SIAS support module following the department's own structure and tiers
  • Per-category access control, so staff see only what their role permits
  • Audit trail on every view, action and decision

Example of the LearnerLens Care log and case queue dashboard

C

Care · Case queue

Whole school · 24 open · 3 overdue

Home circumstances

SG-0412 · Gr 9 · N. Dlamini

Open

Peer conflict

SG-0409 · Gr 8 · R. Petersen

Overdue

Classroom conduct

BH-1187 · Gr 11 · T. Mokoena

Open

SIAS · moderate support

SI-0073 · Gr 10 · SBST

Open

Attendance concern

SG-0398 · Gr 12 · A. Fourie

Closed

Safeguarding

14 open

Behaviour

7 open

SIAS

3 open

How it works

A clear, structured process

From the moment a concern is raised to the moment it is closed, in one traceable line.

  1. 1

    Concern logged

    A staff member files a safeguarding concern, a behaviour observation or a SIAS referral against a controlled category.

  2. 2

    Routed to a holder

    The record lands in a named person's queue, with open, overdue and closed states visible to leadership.

  3. 3

    Acted on

    The holder records what was done, refers it onward where it needs different hands, and closes it with a decision.

  4. 4

    Evidenced

    Every view, action and decision is stamped, giving a complete audit trail on any single case.

  5. 5

    Reported in aggregate

    Category and grade trends are read across a term for the SMT, SGB and parent body, without exposing case detail.

Why it's different

Built to show what the school did about it.

Safeguarding and behaviour never merge

A pastoral concern is not a discipline record. Keeping the two logs structurally separate is what protects the trust of the learners a school is trying to help.

Routing, not filing

Every concern is assigned to a named person with a queue, and a referral workflow moves it onward when it needs different hands. The educator who logged it can see that it reached someone.

SIAS is built in, not bolted on

The support module follows the Policy on SIAS: support domains and areas, low, moderate and high levels of support, and school-based support team tiers with a named coordinator. No parallel paper process.

Access is decided by category

A staff member sees only the categories their role permits. Aggregate reporting reaches leadership and the SGB without exposing case detail.

What schools gain

What changes when the response is recorded.

A live queue view: what is open, what is overdue, and who holds it
Category and grade trends across a term, not only at year end
A complete audit trail on any single case, on request
SIAS records held under the same access control as the rest of Care
Aggregate reporting for the SGB and parent body without case detail
A consent and retention model built to POPIA requirements by design

Signature feature

Care includes the SIAS workflow, in the department's own structure.

The support module follows the Policy on Screening, Identification, Assessment and Support: the SIAS support domains and support areas, low, moderate and high levels of support, and the school-based support team tiers, with a named SIAS coordinator. Schools do not have to keep a parallel paper process alongside the platform.

SIAS records sit under the same access control and the same audit trail as the rest of Care, and are reportable in aggregate without exposing case detail.

Paired curriculum

A paired staff practice programme, so the people who log concerns know what good looks like before, during and after a referral.

  • Short staff modules on what to log, what to escalate, and what to leave to a professional
  • Category guidance written to the same taxonomy staff use in the log
  • SIAS induction for the school-based support team and the named coordinator
  • Record-keeping and POPIA practice, including what may be shared and with whom
Begin the conversation

Understand your learners more deeply.

Tell us about your school and we'll be in touch to set up your account and walk you through LearnerLens.