Most clinical supervision in India happens over a chai conversation, a phone call, or an hour-long Zoom. The tools, where they exist, are basic — Google Docs for case formulations, WhatsApp for between- session questions, occasionally a structured form a supervisor has built themselves.
This is fine for two practitioners who know each other well. It starts to fall apart at scale. If you supervise more than three or four people, or if your supervisees rotate, the lack of structure becomes the limiting factor on supervision quality.
This post is what works, what doesn’t, and what would be worth paying for if it existed.
What supervision actually requires
A working supervision relationship needs to track:
- Cases discussed (anonymised), with key clinical questions
- Decisions made and rationale
- Action items for the supervisee
- Themes across sessions (the supervisee’s growth edges)
- Documentation that, if needed, demonstrates supervision happened
That last point matters. Some training programmes and registration processes require evidence of supervised hours. The supervision log becomes part of a portfolio.
Most ad-hoc supervision misses the documentation point. Conversations happen; nothing is written. A year later, neither party can reconstruct what was discussed.
What people use today
The actual tool landscape:
Google Docs. Most common. Each supervisee gets a document; entries are dated; case discussions are summarised. Cheap, simple, requires discipline.
Notion / Coda. Used by more tech-comfortable supervisors. Database of cases, linked to supervisees, tagged by theme. More powerful but also more setup.
A notebook. Still common. Works for one supervisor with two or three supervisees. Doesn’t scale and isn’t searchable.
Dedicated supervision software. Exists but mostly American (e.g., Theranest, some CPD platforms). Limited Indian adoption.
Practice-management tools with supervision modules. A small category. Most don’t have it; some have partial support.
A workable Google Docs structure
If you supervise and want a free workflow that holds up, here’s the structure:
Per supervisee, one document:
# Supervision log: [Supervisee name]
## Aug 12, 2026 — supervision session
Case: Client A (anonymised initial only)
Clinical question: Suspected dissociation pattern
Notes:
- Reviewed presentation with supervisee
- Suggested CTQ administration next session
- Discussed when to refer for psychiatric evaluation
Actions for supervisee:
- Read [reference]
- Bring full intake to next session
Growth edge: Supervisee's discomfort with silence in session
That’s it. Twenty entries per supervisee per year. Searchable. Backup- able. Exportable if you ever need a portfolio.
The discipline is in the doing. The tool is incidental.
What the cross-cutting view should show
If you supervise five people, you want a view that aggregates across:
- Themes that show up in multiple supervisees (everyone is struggling with crisis sessions this quarter — maybe run a workshop)
- Specific cases that span supervisees (rare but instructive)
- Your own pattern as supervisor (are you over-directing? under- pushing?)
Most ad-hoc setups don’t surface this view. A Notion database can. Practice-management tools mostly can’t.
What ethics requires
Supervision touches client data. Two specific obligations:
Client consent for supervisor review. Your supervisee’s clients should have consented to having their case discussed in supervision. This is part of the supervisee’s informed-consent process at intake, not a separate ask.
No client identifiers in the supervision log. Initials only. No full names, no employer, no specific neighbourhood. The log is a working document; it shouldn’t carry identifying data.
Secure storage. A Google Doc with supervision content is sensitive data. Two-factor on the Google account. Don’t share documents widely. If your supervision platform is in a foreign country, think about the DPDP implications.
The role of recording
The temptation to record supervision sessions for review is real, especially when supervisees want to listen back. The risks are the same as recording therapy sessions:
- Audio storage and deletion discipline
- Third-party transcription services and confidentiality
- Future re-interpretation
A pragmatic compromise: brief, written summaries after each supervision, prepared by the supervisee and reviewed by the supervisor. Captures the value of review without the storage problem.
What MindMaster does and doesn’t
Disclosure (we make it): MindMaster currently supports multi- practitioner workspaces but doesn’t have a dedicated supervision module. Practitioners in the same workspace can see each other’s work if access is granted. A specific “supervisor view” — read access to a supervisee’s notes with no edit ability and a separate supervision-log feature — is on our roadmap for 2026.
For now, most supervisors who use MindMaster do supervision documentation in Google Docs alongside the practice tool. Not elegant, but it works.
The market opportunity
If you build software for therapy practices, supervision is one of the cleanest unmet needs in the category. The features:
- Each supervisee has their own caseload visible to the supervisor
- Supervisor can leave comments on specific notes without editing
- A supervision-log feature with templated structures
- Aggregated theme view across supervisees
- Audit trail of who saw what when
No tool I’m aware of does this fully in 2026. The first one that does will pick up the supervision-heavy practices fast.
A close
For most supervisors with a small caseload, the right answer in 2026 is still: a clean Google Docs structure, a calendar that holds the sessions, and the discipline to write things down. The tools haven’t caught up to the practice yet.
If you want our practice-management tool for the actual client work your supervisees do, that’s at mindmaster.modoware.com. The supervision layer above it is still your job — and probably will be for another year or two.