Case management software for child protection NGOs: the record set, the gates and the consent rules
Child protection case management software has to do three things a general case tool often doesn’t: keep allegations and findings apart, lock narrative notes to the few people who need them, and stop at the points where a trained person, not the system, decides what happens to a child. This deep dive walks one case through those requirements. For the wider buying picture, vendor comparison and pricing, start with our case management software for nonprofits guide.
Why child protection is different
The Inter-Agency Guidelines for Case Management and Child Protection (CPWG, 2014) set out the same six stages every case service uses: intake, assessment, case plan, implementation, follow-up and closure. What changes is the weight on confidentiality. The guidelines are explicit that sensitive information is shared “on a need-to-know basis” with as few people as possible, and that the limits of confidentiality are explained to the child and family during consent or assent.
That one principle drives most of the software design. A system that lets every staff member search every child, or that sends a full case history to a partner when only a referral was needed, breaks it, however good its forms are.
One case, stage by stage
Picture a referral from a school teacher about a 12-year-old who has stopped attending and shows signs of neglect at home. Here is what the system should hold at each step.
| Stage | Record the system creates | Who can see it | Human gate |
|---|---|---|---|
| Intake | Referral record: source, date, urgency triage, duplicate check against existing children | Intake officer, assigned caseworker, supervisor | Supervisor confirms urgency level |
| Assessment | Versioned assessment; concerns recorded as allegations, separate from findings | Caseworker, supervisor | Caseworker records findings; system never converts an allegation into a finding |
| Case plan | Safety plan with named owner per action and due dates; child's own wishes recorded | Caseworker, supervisor; child and family see a plain-language version | Best-interest review by a qualified person |
| Implementation | Partner referral (e.g. to a health or education service) with status: sent, accepted, service received | Partner sees only the referral it received | Caseworker confirms service received |
| Follow-up | Scheduled reviews, overdue safety action alerts on the supervisor's dashboard | Caseworker, supervisor | Supervisor reviews any overdue safety action |
| Closure | Closure reason, approver, move to restricted archive with retention rule | Supervisor, named records lead | Closure approved by supervisor, never automatic |
Three design choices in that table matter more than any feature list.
Allegation and finding are different records. If both live in one free-text note, a later reader can’t tell what was reported from what was established. That matters for the child, for the family and for any legal process.
Partner access is referral-shaped. A health partner needs the child’s name, the reason for referral and a contact route. It doesn’t need the home assessment. Build the partner role so it opens on the referral record and nothing else.
The system never decides. Across all our sector work we hold one rule: software can flag risk quickly, but it should never automate a best-interest determination, a placement or removal decision, or a closure. A risk score that people start treating as a verdict is a safeguarding failure, not a feature. Our child protection case management systems guide lists the minimum record set and review gates in more detail.
Consent and assent for children
Record both the parent or guardian’s consent and, where appropriate, the child’s assent, with the language used, the version of the consent text and the date. Explain the limits of confidentiality at the same moment, as the 2014 guidelines require, and record that you did.
In India this moves from good practice to legal duty. Under the DPDP Rules, 2025, processing a child’s personal data needs verifiable parental consent, and the main obligations apply from around 13 May 2027 (summary). Paper consent registers can’t follow a child through a case file, so the consent fields belong in the child’s record. Our guide to verifiable parental consent under DPDP for NGOs covers how to do this in practice, including cases where the guardian is not a parent.
When Primero is the right answer
If you work in an inter-agency humanitarian setting, look at Primero before anything else. It is open source (AGPL-3.0), owned by UNICEF and listed as a digital public good, with self-reported use by more than 200 organisations in over 60 countries (DPGA). Its CPIMS+ module was built for exactly this kind of coordinated child protection case work, and other agencies in your coordination group probably already use it. Licensing is free; hosting, configuration and support are not.
Outside humanitarian coordination, for example a state-level child-rights nonprofit in India running case work alongside education and livelihood programmes, Primero can feel rigid. That is where a configured build tends to fit better, because the child’s case record has to sit inside a wider registry. If that’s your situation, our beneficiary management system guide explains how the two layers fit together, and our deep dive on role-based access and confidentiality in case management gives you the permission matrix to start from.
A short checklist before you shortlist
- Allegations and findings are separate record types.
- Narrative notes are restricted to the assigned caseworker and supervisor, and every view is logged.
- Partner roles open on the referral record only.
- Best-interest review, placement and closure each have a named human approver.
- Guardian consent and child assent are fields in the child’s record, with version and date.
- Closed cases move to a restricted archive with a stated retention period.
If a tool can’t do all six, it isn’t ready for child protection work, whatever its demo looks like.
Find your gaps first
Before you compare products, check where your organisation actually stands. EdZola’s free nonprofit technology assessment takes about ten minutes and scores you across six areas, including data and records and security and data protection, then tells you the two to fix first. Your answers stay in your browser.