For special schools
Your programme already works. The paperwork is what is drowning you.
Saathi is the platform Saathi Special School runs on every day. One deployment per school, built for Indian classrooms — assessment to report in a single loop, with the paper fallback still intact.
The problem
None of this is a technology problem until March
Then it is all of them at once.
The plan lives in six places
A checklist in one register, the IEP in a Word file, session data in a diary, the report typed from memory in March.
Progress is an opinion
Without session-level data, "improving" is a feeling. Parents deserve a number and a trendline.
Reports eat a fortnight
Term reports get assembled by hand, per child, every term — from data that was never structured to begin with.
Parents wait for the meeting
Families hear about their child twice a year, which is exactly when it is too late to change anything.
What you get
One loop, one record, one source of truth
The whole loop, one system
Assess, locate, plan, log, roll up, report, re-assess. Nothing is re-keyed between stages.
Reports assembled from data
Term reports build from the milestones and logs your team already entered, then publish as immutable HTML plus a matching PDF.
A parent portal on day one
Every family gets a login. Consents, home activities, progress and messages, in plain language.
Your clinical settings, not ours
Mastery criteria, intensity bands, term dates and dosage policy are school configuration — seeded with TODO markers your coordinator signs off before go-live.
Roles & permissions
Who can see and change what
Capability and student scope are re-checked on the server for every action. Client-side checks are never trusted.
| Role | Access |
|---|---|
| Admin | Users, school configuration, templates, audit log. No clinical write access. |
| Coordinator | Full clinical span: overrides, IEP sign-off, report approval and publishing. |
| Therapist / special educator | Own stream, own caseload: assessments, goals, objectives, session logs, report drafts. |
| Assistant | Logging only — attendance, trials, incidents. No plan edits. |
| Parent | Own child only: published notes, progress, home activities, consents, messages. |
Go-live
Go-live, for a school that is already running
The product must not launch empty. Migration is a first-class feature, not an afterthought.
Bulk import
CSV import for students and guardians, so day one is not a hundred manual forms.
Historical entry
Past assessments are entered with their real administration date and flagged as transcribed, so the timeline is honest.
Adopt an existing IEP
A wizard turns a paper IEP into an active one mid-cycle, without forcing a child back through the full assess-to-plan pipeline.
Transcription sprint
Assistants transcribe, therapists verify — supported by the same paper-backup and backdated-entry flows used after a power cut.
Pilot one classroom
One class, its therapists and about five families for a term. Logging compliance and parent weekly-active rate are measured before school-wide go-live.
An explicit end to paper
Parallel paper records get a dated end, agreed up front. Running both forever is how digitisation dies.
Reality
Built for the room it runs in
Session logs written offline queue durably on the device and sync when the connection returns.
Printable session sheets, attendance registers and ABC forms keep the day running when a device does not.
Backdated entry is explicit and audited — the record always shows both the session date and the entry date.
The session screen is budgeted at under a minute and the open-to-complete time is measured, not assumed.
Deployment
India-region deployment & DPDP posture
One deployment per school. The schema is deliberately single-tenant — hard isolation is the right posture for children's clinical data.
Hosted in India, on infrastructure you or we operate, with backups verified by an actual restore before go-live.
Consent is a first-class record with a type, a grant time, a revoke time and a document version.
No third-party analytics, advertising or session-replay scripts exist in the product.
Every read and write on a child's record is attributable to a named user in the audit log.
Honesty
What Saathi does not do
An honest list is worth more than a long one. None of the following is built, and we will tell you so before you ask.
- Fees, billing and transport
- Staff HR and payroll
- Native mobile apps (the web app installs to a phone home screen instead)
- Full offline reads and two-way sync — only the session-logging write queue is offline-durable
- WhatsApp and SMS gateways (WhatsApp Business API is the first item on the post-v1 roadmap)
- Multi-school tenancy — multi-school means one deployment per school
- Telugu and Hindi translations (the structure is ready; the translations are not)
- Automated diagnosis of any kind, and any AI output that is not approved by a named human
Request a demo
We would rather show you than send a brochure
Tell us roughly how many children you work with and what is hurting most right now. Someone from Saathi Special School will call you back and walk you through the whole loop with sample data.