Clinical Intern and Student Supervision Log

This template is for supervisors, clinical educators, and trainees who need to document supervision sessions for therapy interns, counseling students, or other clinical placements. It works best when an academic program requires proof of hours, competency review, and signed attestation. If your program uses a separate practicum or internship evaluation form, this log can still serve as the session-level record.

It covers direct supervision, indirect supervision, and any session where competencies, case discussion, or progress are reviewed. The session_type and supervision_mode fields let you distinguish in-person, telehealth, phone, or other approved formats. If a meeting is purely administrative and does not count toward training hours, it should be logged separately or excluded based on program rules.

Complete it at the time of each supervision session or immediately afterward, while details are still accurate. Waiting until the end of the week increases the risk of missing hours, mixing up case notes, or forgetting what competencies were reviewed. For programs with weekly supervision, the log should support each weekly entry rather than a monthly summary.

Keep the summary focused on the training purpose of the discussion, not unnecessary clinical detail. Include enough context to show why the supervision occurred, such as a treatment planning issue, skills practice, documentation review, or ethical concern. Use data minimization and avoid adding extra PII or sensitive details that are not needed for the academic record.

Yes, the attestation and submission section is important when the log is used to verify hours or competency progress. Supervisor and trainee signatures create a clear record that both parties reviewed the entry and agree it is accurate. If your workflow is digital, keep an audit trail of edits, timestamps, and submission status.

The template is designed to support minimum-necessary documentation by capturing only the fields needed for supervision records. For public-facing or shared workflows, use clear consent or data-use acknowledgment language and avoid collecting unnecessary identifiers. If the log includes any health-related case discussion, keep the content limited to what is needed for training and program verification.

Common mistakes include leaving required fields vague, using free-text where a date picker or numeric field would be more accurate, and failing to separate direct from indirect hours. Another frequent issue is writing too much case detail, which creates privacy risk without improving the record. Missing signatures or not recording the next review date can also make the log less useful for program tracking.

Yes, you can adapt the competency list, progress rating scale, and follow-up actions to match your academic program or placement site. It also works well with workflow tools that support conditional logic, so you can show extra fields only when follow-up is required or when a specific supervision mode is selected. If you connect it to a records system, keep the exported fields aligned with your program's hour-tracking and approval process.