Some organisations support frontline workers; others improve facilities, nutrition, reproductive health or emergency referral. Start from your operating model and connect the family’s journey only where your team has a real responsibility to act.
| Rekha | LMP ? | reg 11 wk |
| Rekha Bai | 26 Jan | dup? maika |
Five places, one mother. Nobody can see she has no way to the hospital.
Many organisations combine two or three. Start with the closest match, then borrow only the parts that solve a real programme problem.
Community workers register families, counsel them and follow pregnancy and early-childhood milestones.
Your team improves planning, review and capability inside government health systems.
Teams assess and strengthen readiness, respectful care and clinical processes.
Children and caregivers receive screening, counselling, supplementation or treatment support.
Adolescents and adults access information, counselling, services and referral.
Your programme helps recognise danger, coordinate transport and reach higher-level care.
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 maternal & child health teams.
"She registered at 28 weeks. We lost the whole first trimester."
The ASHA's diary and the sub-centre register don't talk to each other, so pregnancies come to light late.
"Every card says 120/80."
Visits get counted, but nobody can see which ones actually measured BP and haemoglobin.
"The slip goes with her. We never learn if it was the right hospital."
Referring and receiving facilities keep separate registers, so nobody can show which referrals were appropriate or complete.
"She delivered at her mother's place. We lost the baby's visits."
Two registrations in two villages, and the day 1 and day 3 newborn visits fall between them.
We haven't published a maternal health case study yet. We've worked with health organisations including FMCH and The Antara Foundation, and these are real systems that follow one person across stages, staff and partners.
Identification, enrolment, attendance and retention in one system, with separate access for field associates, partners and managers.
Read the case study →Tapasya Foundation5,000+families matched to schemesA master list of government schemes and their eligibility rules matches each family to the right ones, and each application is tracked until the benefit arrives. Live in four months.
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 maternal & child health organisation. Use it to see how everyday work, follow-up and management decisions can connect.
Stage 01 · Register early
A pregnancy registered at 28 weeks has already missed the visits that catch anaemia, hypertension and twins. The risk profile made at registration decides how closely she's followed.
| ID | Mother | Weeks at reg | Status |
|---|---|---|---|
| MC-2231 | Sunita Jamre | 26 | Late registration |
| MC-2207 | Rekha Bai | 11 | High risk |
| MC-2224 | Meena Dawar | 14 | Possible duplicate |
| MC-2219 | Kavita Solanki | 9 | ANC 1 booked |
Stage 02 · ANC that counts
A visit where nobody measured BP doesn't protect against eclampsia. Anaemia found at 16 weeks can be treated. At 36 weeks it's a bleeding risk.
| ID | Mother | Latest | Action |
|---|---|---|---|
| MC-2207 | Rekha Bai | Hb 9.6 · BP 136/86 | No transport |
| MC-2198 | Lalita Barela | BP 146/94 | Referred today |
| MC-2231 | Sunita Jamre | Hb 6.8 | IV iron booked |
| MC-2219 | Kavita Solanki | Hb 11.2 · BP 110/70 | On track |
Stage 03 · Birth & referral
Delays in deciding, reaching and getting care still kill. A referral is only done when she's arrived and been seen, and the birth record opens the child's.
| ID | Mother | Route | Status |
|---|---|---|---|
| MC-2198 | Lalita Barela | PHC to DH Barwani | No arrival, 2h 10m |
| MC-2185 | Anita Chouhan | SC Pati to PHC | In transit, 1h 5m |
| MC-2177 | Radha Mujalda | CHC to DH Barwani | Arrived, admitted |
| MC-2169 | Sita Awasya | PHC to CHC | Live birth |
Stage 04 · First 42 days & beyond
Most newborn deaths happen in the first week, often at home after an early discharge. After that, the vaccine card and growth chart become the child's record.
| Child ID | Child | Due | Status |
|---|---|---|---|
| MC-2169-C1 | Baby of Sita | Day 3 visit | Missed yesterday |
| MC-2102-C1 | Aarav | Penta-3 | 21 days overdue |
| MC-2117-C1 | Pari | MR-1 | Due Friday |
| MC-2088-C1 | Diya | Weight check | Growing well |
Follow one illustrative referral from a city health post to a maternity home and back.
Illustrative facility scorecard. Every referral closes at both ends.
Choose the parts that match your role. A facility-improvement team does not need the same personal record as a home-visiting programme, and a messaging programme should collect less.
Keep pregnancy, birth, newborn and child information connected without duplicate registration.
Turn due services, missed visits and danger signs into prioritised daily work.
Track standards, gaps, owners, resources and verified improvement over time.
Coordinate facilities, calls, transport, handover and outcome confirmation.
Follow measurements, counselling, services, supplies, defaulters and recovery.
Support confidential counselling, referrals and responsible messaging programmes.
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 maternal & child health 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 →
“Every card says 120/80, and we can't tell which facilities are actually measuring.”
Your team still decides: the programme manager checks equipment first. A broken BP machine isn't a staff failure.
“Mothers register in the city and again in their native village, and the baby's first visits fall between the two.”
Your team still decides: a data officer reviews every merge before it happens.
“We know referrals are delayed and sometimes sent to the wrong place, but we can't say where it goes wrong.”
Your team still decides: the facility nodal officer checks timestamps are complete before using it.
“Our WhatsApp line gets thousands of messages, and a mother mentioning bleeding can sit in the queue behind feeding questions.”
Your team still decides: the nurse calls her back. The bot never tells a mother she's fine.
“Past vaccines and weights are only on the MCP card in the mother's bag, so our records start half empty.”
Your team still decides: the ANM checks every date against the card.
“Death reviews take days of pulling papers from three facilities, so the review committee meets late or not at all.”
Your team still decides: the review committee reads the source records and owns the findings.
Mothers and newborns can't wait for AI to be right. These lines don't move, whoever's asking.
Every woman she registered, her weeks, next visit and risk, with reminders. The diary list, done for her.
Anaemic and hypertensive mothers, pending referrals and vaccine session lists, in one place.
High-risk mothers due in the next four weeks, with birth plan and transport status.
First-trimester registration, newborn visits and full immunisation by village, linked back to pregnancy risk.
Outcomes linked by Mother and Child ID, with visit quality shown beside visit counts.
ANC4+ is counted everywhere. We also report how many visits actually recorded BP and Hb, because a card that says 120/80 every time means nobody's measuring.
It's a smaller number. It's also where pre-eclampsia gets caught.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 RCH portal exports, WhatsApp and IVRS, your helpline or chatbot, and government facility registers, 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. If she discloses violence, a confidential referral can go to your counselling team without showing on her ANC record.
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.
