Early intervention, rehabilitation, inclusive education, assistive technology, community-based inclusion and employment programmes work around different teams and outcomes. The common thread is a person-led plan connected to the environments that enable or block participation.
| Sneha J. | 22 | mother answered |
| Sneha Jadhav | 21 | dup? |
Five places, one person. Nobody can see her chair doesn't fit the door.
Many organisations combine two or three. Start with the closest match, then borrow only the parts that solve a real programme problem.
Young children and caregivers receive developmental assessment, therapy and home support.
Therapists and specialists coordinate goals across disciplines and settings.
Learners receive classroom accommodations, individual education plans and family support.
Teams assess, fit, deliver and maintain devices with training and follow-up.
Community workers connect health, education, livelihoods, social life and entitlements.
Candidates and employers prepare, match and sustain accessible work.
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 disability & inclusion teams.
"We count wheelchairs handed over. Nobody goes back."
A chair that doesn't fit the doorway ends up in a corner, and the report still counts it as delivered.
"The UDID applications live in my phone gallery."
Photos of forms and portal screenshots, no dates. Nobody can say who's been waiting six months.
"The plan says 'improve gait'. She said 'get to the market alone'."
Goals get written in therapy language, and the person stops seeing why they should come.
"Every programme sends a different Excel to the funder."
Early intervention counts children, livelihoods counts candidates, the workshop counts devices. At year end someone spends weeks making plan versus actual add up.
We run skilling and placement systems for persons with disability with TRRAIN. Early intervention, therapy and device workshops would be new builds on the same foundations, and we'll say so in the walkthrough.
Pankh (persons with disability) and TRRAIN Her (women) run in one system, from regional teams down to each trainee, with centre and placement approvals and automatic certificates. Live in four months.
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 disability inclusion organisation. Use it to see how everyday work, follow-up and management decisions can connect.
Stage 01 · Find who's missed
Official figures put disability at about 2% in India. The Washington Group questions usually find several times that, mostly people with psychosocial, intellectual and less visible disabilities, and children kept at home.
| ID | Person | Domain | Status |
|---|---|---|---|
| PD-0409 | Rahul Gaikwad | Anxiety / depression | Referral overdue |
| PD-0422 | Farida Sayyed | Hearing | Proxy answered |
| PD-0417 | Sneha Jadhav | Walking | Assessment booked |
| PD-0431 | Ganesh More | Seeing | Referred |
Stage 02 · Assess & plan
Without a certificate and UDID card, pensions, scholarships, ADIP devices and reservations stay out of reach. The plan that follows has to be built with the person, around goals they chose.
| ID | Person | UDID | Next step |
|---|---|---|---|
| PD-0409 | Rahul Gaikwad | Applied 5 May | 98 days pending |
| PD-0422 | Farida Sayyed | Applied 2 Jul | Camp date due |
| PD-0417 | Sneha Jadhav | Issued | Pension applied |
| PD-0431 | Ganesh More | Issued | Scholarship received |
Stage 03 · Therapy & devices
Therapy works when it's regular and tied to daily life. Devices get abandoned within months when nobody checks fit, training or terrain.
| ID | Person | Device | Status |
|---|---|---|---|
| PD-0417 | Sneha Jadhav | Wheelchair | Refit today |
| PD-0422 | Farida Sayyed | Hearing aid | Battery issue |
| PD-0438 | Meena Waghmare | Walker | Terrain check |
| PD-0431 | Ganesh More | Low-vision aid | In use |
Stage 04 · Stay included
Placement numbers are easy. Retention is where barriers show: an inaccessible toilet, a teacher who won't adapt, an accommodation agreed at placement and forgotten by month three.
| Employer / school | Placed | Accommodation | Status |
|---|---|---|---|
| Shree Garments | 6 | Ramp promised | 2 exits, review |
| ZP School, Mundhwa | 9 | Accessible toilet | Pending 34 days |
| Sahyadri Tailoring Unit | 4 | Extra break time | Met |
| Hadapsar Print House | 3 | Screen reader | Met |
Choose modules across the life stage and setting you support. A device programme, a school-inclusion team and an employer network should not share one generic outcome screen.
Use ICF-informed domains and the person’s priorities, without turning them into a label.
Coordinate goals, sessions, home plans, reviews, with each discipline seeing what it needs.
Connect classroom goals, accommodations, support and participation.
Manage assessment, prescription, fitting, issue, training, repair and replacement.
Track caregiver priorities, referrals, peer groups, local resources and barriers.
Follow accommodations, employer actions, benefit access, placement and retention.
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 disability & inclusion 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 →
“People qualify for pensions, scholarships and ADIP devices, and we find out a year later that nobody applied.”
Your team still decides: The coordinator confirms eligibility before telling the person.
“We know UDID is slow, but we can't show the district which board is holding it up.”
Your team still decides: The coordinator adds context before anything is shared outside.
“Therapists spend evenings writing plans families don't read.”
Your team still decides: The person and family review and edit it before it's final.
“Home exercise sheets are photocopies nobody follows.”
Your team still decides: The therapist approves every programme before it goes home.
“Caregivers tell us a device is broken on WhatsApp, and the message gets lost.”
Your team still decides: The coordinator reviews every device-related message weekly.
“Every CSR funder wants plan versus actual in their own format, for their own slice of our programmes.”
Your team still decides: The programme lead checks the numbers and adds the stories before it's sent.
Nothing about us without us. These lines don't move, whoever's asking.
Their plan, progress and next session in their format, and a direct line when something's wrong.
Everyone she screened, whether they've been assessed, and which entitlements came through.
Caseload, goal progress, missed sessions and plans due for review, on one screen.
Check-ins due, accommodations still pending and placements at risk.
Placement and 12-month retention with accommodation data, split by disability type and gender.
A camp that hands out 200 wheelchairs reports 200. We report how many are still in use at three months, and why the rest aren't.
Funders notice when you track what happens after handover.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 UDID and Swavlamban exports, WhatsApp and IVRS, partner NGOs' own sheets and your device workshop records, 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. UDID details, disability type and therapy notes are treated as sensitive personal data, with consent recorded per purpose.
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.
