Most senior clinicians who supervise have very little context on the software their supervisees use. They know what they themselves use, maybe what their hospital ran ten years ago, occasionally a name they’ve heard. The supervisee says “I’m using X” and the conversation moves on.
This is a gap worth filling. A supervisee’s tool choices affect:
- Whether you can review their notes meaningfully
- Whether their records hold up if challenged
- The habits they build for a thirty-year career
- The data they can or can’t show you when reviewing cases
A short guide for the supervisor’s perspective.
What to ask
A handful of questions at the start of supervision (or now, if you’re already supervising):
1. What practice-management tool are you using?
If “Excel” or “Google Docs” — flag concern. These tools fail ethics tests on encryption and access control. A supervisee who’s serious about their practice needs a proper tool by year two at the latest.
2. Where is the data stored?
Most supervisees won’t know. The right answer is “in a vendor data centre, encrypted at rest.” If they can’t tell you, ask them to find out. This is basic.
3. Can I see a recent note?
With client identifiers redacted. Look for:
- Is the note structured (date, presenting, session, plan)?
- Is it appropriate length (not too short to be useful, not so long it suggests over-documentation)?
- Are observations clearly distinguished from interpretations?
- Are third-party identifiers handled with care?
The supervisee’s note-writing tells you a lot about their clinical thinking.
4. How are you handling client consent for supervision?
The supervisee’s clients should have consented to having their case discussed in supervision. This is part of the supervisee’s intake informed consent. If they haven’t built that into intake, it’s a gap.
5. Can you export everything if you needed to?
A test of how well they understand their own data sovereignty. If they don’t know, they should run an export and check. Build the habit.
What you can expect to find
Three common patterns:
Pattern A: organised and over-engineered. Supervisee uses three tools that don’t quite integrate, spends too much time on documentation, has elaborate but possibly excessive systems. Reasonable; help them streamline.
Pattern B: minimum-viable. Practice-management tool used at the basics, notes brief, intake form basic but adequate, no fancy integrations. Often the healthiest pattern.
Pattern C: undisciplined. Mixed Excel and notebook, no formal intake, notes scribbled and lost, no real export capability. This is a supervision priority. Help them build the foundation.
What you should encourage
A short list of habits to build:
Note-writing immediately after session. Not “later.” Five to eight minutes between sessions. The note is best when it’s fresh.
Quarterly export. Run a full export every three months. Check that it includes everything. Store it somewhere safe. This builds data-sovereignty habits.
Audit log awareness. Show them where the audit log is in their tool (if there is one). Even if they never look at it, knowing it exists shapes how they treat the system.
Consent paragraph review. Every six months, re-read the informed-consent paragraph you give clients. Update it as your practice evolves. Most supervisees never look at theirs after year one.
Backup awareness. What’s the vendor’s backup policy? What happens if the vendor’s system fails? Do they have any local copy? Most won’t have thought about this.
A specific question on AI tools
A growing 2026 issue. Some supervisees are starting to use AI transcription and AI note-generation tools. Worth a specific conversation:
- What AI tool are they using?
- Where does the audio/text go?
- Has client consent been obtained?
- Is there a data-processing agreement?
- Are they reading the AI output critically or accepting it?
Most supervisees who’ve started using these tools haven’t thought through the confidentiality implications. The supervisor’s role is to slow them down and ensure they have.
What MindMaster supports
In the interest of disclosure (we make it):
- Multi-practitioner workspaces (so a supervisor can be a user)
- Audit log present (full UI surfacing on roadmap)
- Export available (CSV + JSON)
- Per-practitioner accounts with 2FA
- Encryption at rest and in transit
What we don’t yet have: a separate “supervisor view” with read-only access to a supervisee’s notes. That’s roadmap. For now, supervisors who want to see notes review them in shared sessions.
A specific note on legal-portfolio supervision
If you supervise someone working toward formal credentialing (RCI registration, a degree programme’s clinical hours, a specific training programme’s certified supervised hours), the documentation requirements are stricter:
- Hours of supervision documented
- Cases discussed (with identifiers redacted)
- Specific learning outcomes
- The supervisee’s signature on the log
Your supervisee should have a supervision log. The format depends on what the registering body requires. Set this up in the first month, not retroactively.
What conversations to have
A short list of conversations worth having explicitly:
Year 1: foundational. Tool choice, basic note discipline, consent framework, supervision logs.
Year 2: efficiency. Are they over-documenting? Under-documenting? Where is their time actually going?
Year 3: independence. Are they building a practice that can sustain without you? What’s their export discipline? What’s their emergency-supervisor backup?
Year 5+: scale. If their practice is growing, the operational questions change. Hiring, group work, possibly associates. The supervision conversation expands.
A specific note on what NOT to do
Supervisors sometimes overreach into supervisee tool decisions. Examples:
- Mandating a specific tool they themselves use
- Pushing supervisees toward your preferred vendor
- Requiring documentation formats that aren’t industry standard
- Inserting yourself into the supervisee’s vendor relationships
The supervisor’s role is to surface the questions and ensure the supervisee has thought them through. The choices are theirs.
A close
Supervision in 2026 increasingly includes a layer of practice- infrastructure conversation that wasn’t part of clinical supervision in earlier eras. The supervisor who engages with it helps the supervisee build practice habits that compound over a career.
For the operational side of your own and your supervisees’ practices, our tool at mindmaster.modoware.com is one option. The supervisor’s role is to ensure the tool chosen — whichever it is — supports the kind of practice that holds up over decades.