Community outreach, street work, child-care institutions, family restoration, alternative care and aftercare carry different duties. This playbook begins with the operating model, then identifies the information and safeguards each team genuinely needs.
| Boy ~13 | Howrah stn pf 9 | new case |
| Boy 13 yrs | Howrah | 3rd time?? |
Five registers, one child. Nobody can see he's run away three times.
Many organisations combine two or three. Start with the closest match, then borrow only the parts that solve a real programme problem.
You work with children, families, schools and communities to identify risks early.
Teams meet children in public spaces and respond to immediate safety, health or shelter needs.
A residential team manages daily care, education, health, safety and statutory obligations.
You support families so children can remain safely at home or return with follow-up.
You recruit, assess and support foster, kinship or other family-based placements.
Young adults receive housing, education, livelihood and legal support; policy teams track patterns.
Not sure which one you are? Bring one tracker and describe a normal week. The model usually becomes clear quickly.
These come up in almost every first conversation we have with child protection teams.
"The day they turn 18, our records stop."
Aftercare support, jobs and housing get tracked by one social worker on WhatsApp, until she leaves and the contacts go with her.
"He told his story to five people in the first week."
Police, doctor, caseworker and CWC each keep their own account, and the gaps get used against him later.
"The care plan gets opened at inspection time."
Counselling, school and family tracing sit in three staff diaries, so reviews slip for months.
"We close cases. We can't say who's still safe."
Follow-up depends on travel budget, and visits get marked done after a word with the parent at the door.
We haven't published a CCI or helpline case study yet. We've built restricted case management for abuse disclosures with MukkaMaar and HR systems for Aangan Trust across 7 states, and we work with child rights organisations including CRY.
Students, trainers and sessions in one system, with location-stamped trainer attendance, a restricted case module for abuse disclosures and donor reports.
Read the case study →Aangan Trust7 statesone HR system for a child protection teamZoho People for 100+ staff, where each person sees only what their role needs, with leave rules per state. Time spent on attendance fell from six hours a month to two.
Read the case study →Recognise your programme? Tell us where the work gets stuck and we'll suggest a useful first version.
This is one operating model, not a template for every child protection organisation. Use it to see how everyday work, follow-up and management decisions can connect.
Stage 01 · Call to case
The first record decides how fast someone gets there. Log too little and the field team goes in blind. Log too much and you've recorded a disclosure the child hasn't agreed to share.
| ID | Concern | Location | Status |
|---|---|---|---|
| IN-2214 | Child labour | Liluah | No update, 55 min |
| IN-2209 | Possible trafficking | Santragachi | Police informed |
| IN-2201 | Child marriage | Bally | Verify by 10 am |
| CP-0731 | Missing child | Howrah station | Field worker with him |
Stage 02 · Ready for the CWC
The JJ Act requires a rescued child to be produced before the CWC within 24 hours. A thin file means a placement made on guesswork, so every fact collected once should serve everyone who needs it.
| ID | Concern | Next step | Status |
|---|---|---|---|
| CP-0744 | Child labour | CWC production | Hour 16, not produced |
| CP-0738 | Trafficking | Placement review | Needs sign-off |
| CP-0731 | Missing child | SIR draft | Due in 4 days |
| CP-0729 | Missing child | Family tracing | Gaya partner assigned |
Stage 03 · Care that moves
The Individual Care Plan is meant to drive every intervention. In practice it's written at admission and opened again at inspection, while progress sits in three staff diaries.
| ID | Days in care | Plan focus | Status |
|---|---|---|---|
| CP-0692 | 134 | Family tracing | No plan at 120 days |
| CP-0731 | 41 | School, counselling | Review brought forward |
| CP-0714 | 62 | School enrolment | Documents pending |
| CP-0705 | 88 | Home study done | Ready for CWC |
Stage 04 · Home, and safe
Restoration and leaving care at 18 are where most files go quiet. Children found back at work or re-trafficked are usually the ones whose families never got the scheme support promised.
| ID | District | Last visit | Status |
|---|---|---|---|
| CP-0671 | Malda | Missed, 19 days | Escalated |
| CP-0648 | Purulia | Parent at door only | Revisit needed |
| CP-0655 | Gaya | Seen alone, in school | Stable |
| CP-0633 | Sahebganj | Seen alone, month 12 | Closure review |
One illustrative child, A. K., from a CWC order at eight to aftercare at 21.
Illustrative. Initials only, as the JJ Act requires.
Choose modules according to your legal role and duty of care. A prevention programme should not collect the same detail as a shelter or statutory casework team.
Track orders, hearings, reports, responsible people and time limits without replacing legal judgement.
Support admissions, daily care, visits, rosters, supplies, incidents and handovers.
Connect the child’s goals, education, health, relationships and review actions.
Document contact, assessment, services, decisions and post-restoration follow-up.
Manage carer assessment, placement stability and young adults’ chosen transition plans.
Restrict sensitive information, escalate concerns and confirm services were actually received.
Most AI projects stall because the records underneath are messy. So we work in a fixed order.
Every field has to earn its place by helping someone decide something. If nobody uses it, we don't collect it.
A system people avoid is worse than a spreadsheet. We design around shared phones, patchy signal and WhatsApp.
On clean, connected records, AI can read paperwork, draft reports and flag who needs attention. A person always checks.
Where you start depends on where you are. If your records are already in good shape, we can move to AI quickly. If they're in notebooks, we start there, and we don't start from zero.
Offline forms, local languages, links to government IDs and AI features are set up to suit each programme's needs and consent rules, so not every build includes all of them.
We picked the jobs that save child protection teams the most hours. Each starts with a problem we hear often, and each keeps a person in charge of the decision. How we think about AI →
“Our caseworkers spend days every quarter writing CWC progress reports from three staff diaries.”
Your team still decides: the caseworker reviews and signs every report.
“CWC orders arrive as paper, and their directions get lost in a file nobody reopens.”
Your team still decides: the CWC liaison checks each field against the original.
“We find out a document is missing when the CWC asks for it at the hearing.”
Your team still decides: the supervisor confirms the file is ready the day before.
“Children stay longer than they need to because nobody reviews restoration readiness across all our homes.”
Your team still decides: the supervisor reviews each flagged child. No restoration is pushed to hit a number.
“We lose touch with care leavers within a year, and only hear again when they call in crisis.”
Your team still decides: the mentor chooses how to reach out, and nobody loses support because of a flag.
“Families and care leavers miss support they're entitled to because the forms take hours.”
Your team still decides: the caseworker checks every field with the family or young person before submitting.
A child's file follows them for years. These lines don't move, whoever's asking.
A short update once the child is verified, with no case details. It's why they keep calling.
Pulled from what's already entered. No retyping the same facts in three formats.
Care plan goals on the same screen where they log attendance.
Missed deadlines, rising risk and closure requests, in one list.
Anonymised re-entry, school continuation and scheme linkage by district.
A visit where someone spoke to the parent at the door counts the same as one where the child was seen alone. We report how many follow-ups saw the child alone, and keep cases lost to contact apart from safe closures.
It's a harder number to show. It's the one that tells you a child is safe.Most systems launch in three to four months. The timeline moves with the number of programmes and roles, how messy the old data is, and how many tools need connecting.
Tell us where the work gets stuck today. Spreadsheets, notebooks, WhatsApp groups, all of it.
You show us how the programme runs. We'll tell you straight if you need a new system, a better workflow or nothing at all.
We map how your programme works, talk to the people who'll use it, review the tools you use today and hand you a System Blueprint, a clear plan of what we'll build.
Working screens every 2 to 4 weeks, tested by your field team in your own terms. We clean up your old spreadsheets and move them across.
Field training and launch, then 30 to 60 days of close support. After that, the system keeps changing as your programmes do.
We connect to CWC and JJB order registers, JJ Model Rules forms, Mission Vatsalya and TrackChild exports, and your sponsor management system, rather than replacing what already works. Zoho licences sit in your organisation's name, and everything exports whenever you want it.
The questions your finance head and IT lead will ask, answered before the call.
Zoho licences are bought in your organisation's name and hosted in the Zoho data centre region you choose, including India. We work inside your account.
Every record exports to Excel or CSV whenever you want, including the day you stop working with us. You're not locked in to us for support either.
Each person sees only the records their role needs. Section 74 of the JJ Act applies: a child's identity is never shown to sponsors, donors or the public, and counselling notes are visible only to the counsellor and supervisor.
Edits are logged with who made them and when, so an audit or a funder query doesn't start from memory.
Consent is recorded for each purpose, and we agree up front how long data is kept and when it's deleted. ZolaShield, our DPDP platform, shows where you stand.
AI features run on your records under your account's controls. Beneficiary records never go into public AI tools.
Use these focused implementation guides alongside the sector playbook.
We’ll map what your team does now, identify the smallest useful first version and show where follow-up, learning and reporting can share the same information, without forcing your programme into a generic template.
If budget is tight, ask about the Built for Impact Programme, which gives eligible nonprofits free Zoho credits.
The same approach, shaped to each kind of work.
