01 · What breaks
Design for the failure modes, not only the happy path.
Child protection records hold the most sensitive information a nonprofit will ever store, about people who cannot easily object. These four failures tend to stay invisible until a child is harmed or a file reaches the wrong person.
Broad access to narrative notes
Case notes often describe abuse, family conflict and the names of alleged perpetrators. If every staff member, volunteer or donor-facing role can open them, one careless screenshot can put a child at risk. Restrict narrative notes to the assigned caseworker and supervisor, and log every view and export.
Automatic risk scoring used as judgement
A checklist that adds up vulnerability points can help a new caseworker notice what to ask. Once the total starts deciding which cases get a visit, it becomes a judgement nobody signed. Show the indicators behind any flag, and require a named person to record the response and the reason.
Referrals without confirmed ownership
A referral sent by email or WhatsApp to a counselling partner or a district office is not a referral until someone accepts it. Track each one with a status (sent, acknowledged, accepted, declined, completed), the receiving person and a due date, and escalate silence after an agreed number of days.
Records continuing beyond a justified retention period
Closed cases tend to stay open to every user for years, long after the child has turned eighteen. Agree a retention rule per record type with your legal adviser, move closed cases into a restricted archive, and remove narrative detail that no longer serves a service, a legal duty or the child's own request.
02 · Minimum viable model
Build the record around the case chronology, not a single form.
EdZola's How Nonprofits Operate field guide separates two kinds of journey: cohorts that move together and cases that move alone. Child protection is always the second kind. These six records carry one child's case from first concern to restricted archive, and each has its own access rule.
| Record | Who normally sees it | Where Indian law or schemes touch it (as of October 2026) |
|---|---|---|
| Concern and intake | Intake officer, caseworker, supervisor | Under Section 19 of the POCSO Act, 2012, anyone who knows of or suspects a sexual offence against a child must report it to the Special Juvenile Police Unit or the local police. Store the date of the report and the receiving officer. |
| Assessment and safety plan | Caseworker, supervisor | The Juvenile Justice (Care and Protection of Children) Act, 2015 requires an Individual Care Plan to guide each child's rehabilitation. Keep every version of the plan, dated. |
| Referral to a Child Welfare Committee | Caseworker, supervisor | States set up a Child Welfare Committee in every district under Section 27 of the JJ Act. Log what was submitted, the hearing date and the order received. |
| Missing or found child | Caseworker, supervisor | The former TrackChild and Khoya-Paya portals are now part of the Mission Vatsalya portal of the Ministry of Women and Child Development. Record the reference the district shares instead of copying its record. |
| Emergency escalation | Duty officer on call | Child Helpline 1098 still works and is integrated with the emergency number ERSS-112. Note which line was called, when and by whom. |
India's Digital Personal Data Protection Act, 2023 requires verifiable consent of a parent or lawful guardian before a child's personal data is processed. Most of these duties apply from around May 2027, as of October 2026. In child protection the guardian may be connected to the concern, so settle how consent works for those cases with a legal adviser before go-live. None of this table is legal advice. See our page on DPDP compliance for nonprofits.
03 · Implementation sequence
Move through reviewable gates.
Build the smallest version a caseworker can run end to end on anonymised scenarios, then widen it. Access rules sit at both the first and the last gate, because that is where the harm sits.
Define access and escalation before configuration
Write the role matrix before anyone opens the software: who can create a case, read notes, approve a safety plan, send a referral and close a case. Name the escalation route for an urgent concern after office hours, including when staff call 1098 or 112. Leadership signs this document.
Model the case and review cycle
Set the case statuses your team will use, such as open, under assessment, plan active, under review and closed, and the review interval for each risk level. Every status change is dated and needs a reason from a master list, so a supervisor sees why a case moved, not only that it did.
Separate allegations from findings
Store what was reported, who reported it and what the assessment later concluded as three separate fields. A single incident text box turns an unverified claim into a fact the next caseworker inherits. Mark each finding with the assessor and the date, and never overwrite the original account.
Test partner handoffs
Run five anonymised referrals through each kind of partner you use, such as a counselling service, a shelter or a district child protection unit. Check what the partner can see, how acceptance is recorded and what happens when nobody responds. Fix the handoff before go-live, not after a child falls between two organisations.
Monitor overdue safety actions
Give each supervisor a weekly list of safety actions past their due date, reviews not held and referrals still unacknowledged, grouped by caseworker. The list starts a conversation; it is not a performance score. Nothing on it closes until a person records what happened.
Audit access and closure decisions
Each quarter, a named data owner reviews who opened closed cases, every export, and a sample of closures against the closure checklist. Findings go to leadership in writing. The same review confirms that archived records follow the agreed retention rule.
04 · Evidence
Measure whether the work became clearer.
These four measures tell a programme lead whether the system is keeping children's cases moving safely, not whether staff are typing more. Review them with supervisors each month and read every number next to the cases behind it.
05 · Responsible automation
Let systems prepare. Keep consequence with people.
Systems can support
- Case chronology with dated status changes
- Overdue review and referral reminders
- Role-based access with view and export logs
- Restricted archive after closure
People should decide
- Best-interest determination
- Risk and safeguarding response
- Placement or removal decisions
- Case closure and disclosure
06 · Common questions
Practical questions teams ask.
Answers for child protection leads, supervisors and teams setting up their first case system.
What is a child protection case management system?
It is a secure record of each child's case over time: the concern that opened it, the assessment, the safety plan, referrals to other services, scheduled reviews and the closure decision. Unlike a general beneficiary database, it is built around one child's chronology and strict access, so only the people working on that case can read the sensitive detail.
What fields should a child protection case record include?
Keep only what the case needs: child identifiers, safe and unsafe contacts, the concern and its source, assessment findings, each safety action with an owner and date, referrals with their acceptance status, review dates and the closure reason. Leave out anything no decision uses. Sensitive details such as religion or full family histories belong in the record only when a service or legal duty requires them.
Who should be able to see child protection case notes?
By default, only the assigned caseworker, their supervisor and a named data owner. A partner receiving a referral should see the referral summary, not the full file. Donors and leadership should see counts, never names or narratives. Every view and export of a case note should be logged, and someone should actually read that log on a schedule.
Can software or AI assess the risk to a child?
It can organise what a practitioner needs and remind them what has not been checked, but it should not decide. Risk to a child depends on context a form rarely captures, and a wrong score can delay help or trigger an unnecessary intervention. Treat any flag as a prompt for a trained person, who records the decision and the reasoning.
How should a small NGO start with child protection case management?
Start with one team, one case type and a short status list, and run it on anonymised scenarios before using it for real children. Write the access rules and the escalation route first. Add partner referrals, review schedules and dashboards once caseworkers trust the record. A small system with tight permissions is safer than a large one with loose permissions.