The Clinical Supervision Contract: What to Include and Why It Matters

Introduction

A clinical supervision contract is the written agreement that defines the supervisory relationship: who the parties are, what the work covers, how confidentiality and evaluation are handled, and what happens when something goes wrong. Beyond the regulatory expectation that registered supervisors document the arrangement, a well-drafted contract protects both parties, surfaces assumptions early, and gives the supervisory alliance a stable frame. This guide sets out the ten elements every clinical supervision contract should include, with practical drafting notes and jurisdictional considerations for Australia, the United States and Canada.

Why a written supervision contract is non-negotiable

A written supervision contract serves three functions at once. It satisfies a regulatory requirement. It documents informed consent. And it gives both supervisor and supervisee a shared reference point when the work becomes harder than either of them expected at intake.

Regulators across the three jurisdictions Kindred operates in have moved decisively toward requiring documented supervision arrangements. The Psychology Board of Australia (n.d.) requires board-approved supervisors to document the terms of supervision, particularly for provisional psychologists on internship pathways and for registrars completing area-of-practice endorsement. The American Psychological Association's Guidelines for Clinical Supervision in Health Service Psychology (2025) treat informed consent and written contracting as foundational supervisor competencies. In Ontario, the College of Registered Psychotherapists of Ontario (n.d.) requires registrants in supervised practice to have documented supervision agreements that members can be asked to produce.

The clinical case is stronger than the regulatory one. Falender and Shafranske (2019), whose competency-based supervision framework is widely cited in supervisor training across all three jurisdictions, describe the contract as the supervisor's primary risk-management tool and the supervisee's first experience of being treated as a developing professional rather than a student. An ambiguous contract produces an ambiguous alliance. A specific contract produces a specific one.

The ten elements every clinical supervision contract should contain

The following ten elements appear in nearly every competency-based supervision text and in the regulatory templates published by AHPRA, the APA and most Canadian regulators. The headings are stable; the wording under each will vary with your context, modality and jurisdiction.

1. Parties, credentials and supervisor scope of practice

Full names, registration or license numbers, the supervisor's board approval or endorsement, and the specific areas in which the supervisor is competent to supervise. If the supervisor is not endorsed in a relevant area of practice, say so and define how that limitation is handled.

2. Purpose, scope and learning goals

What is this supervision for? Hours toward registration or licensure, area-of-practice endorsement, ongoing professional supervision, or specific competency development. Name the regulatory framework the hours count toward and the supervisee's specific learning objectives for the period. Goals should be revisited at agreed intervals.

3. Logistics

Frequency, duration, modality (in-person, video, hybrid), location, and the platform used for telehealth supervision if relevant. Specify the minimum acceptable frequency under the relevant regulatory framework and what happens if a session is missed.

4. Fees, payment terms, and cancellation policy

Hourly rate, invoicing cadence, accepted payment methods, late-payment consequences, and cancellation notice required. Free or organizationally funded supervision still warrants a fees clause that says so explicitly, including who funds it and what happens if funding ceases.

5. Confidentiality and its limits

What stays in supervision, what does not, and the specific circumstances under which the supervisor will disclose information to a regulator, training program, employer, or third party. This clause is the one most under-draft contracts and is treated separately in the next section.

6. Documentation and record-keeping

Who keeps session notes, what they contain, where they are stored, how long they are retained, and which party owns them. Distinguish supervision notes from clinical notes about the supervisee's clients. Specify any use of session recordings, including consent and storage.

7. Evaluation and feedback processes

How and when the supervisor provides formative feedback, when formal evaluations occur, what criteria are used, and how the supervisee can give feedback to the supervisor. If the supervisor will sign off on competencies or report to a training program, the evaluation framework should be named.

8. Reporting obligations

To whom the supervisor reports, when, in what format, and what the supervisee will see before it is submitted. This is particularly important where the supervisor reports to a regulator (provisional pathways), a training program (internship sites), or an employer (organizational supervision).

9. Dispute resolution and complaints

What happens if the supervisor and supervisee disagree, how concerns are raised, and the supervisee's right to seek consultation, change supervisors, or complain to the relevant regulator. Naming the regulator's complaint process explicitly is good practice and signals confidence rather than vulnerability.

10. Termination procedures

Notice period, conditions under which either party may terminate, handover arrangements, and what happens to outstanding supervision hours or evaluations. The contract should anticipate planned, unplanned and emergency termination.

This list functions well as a drafting checklist and as a review tool when an existing contract starts feeling thin.

Confidentiality, mandatory reporting, and the limits clause supervisors most often under-draft

Most supervisors include a confidentiality clause. Fewer write it well. The clause needs to do three things: state the default, name the specific exceptions, and describe the supervisor's process when an exception is triggered.

The default is straightforward. Material discussed in supervision is confidential between supervisor and supervisee, with the caveat that the supervisee's clients are entitled to confidentiality from the supervisor as a downstream professional. The exceptions are where contracts get vague.

A specific limits clause should name: mandatory reporting obligations regarding child or vulnerable-adult safety; notifiable conduct obligations to AHPRA, a state licensing board, or a Canadian regulator (for example, AHPRA's mandatory notification thresholds for impairment, intoxication, or significant departure from accepted standards); risk to the supervisee, supervisor, or an identifiable third party; subpoena or other legal compulsion; and reporting required under the supervisor's relationship with a training program or employer. Each of these warrants its own sentence rather than a catch-all reference to "professional and legal obligations".

The process matters as much as the trigger. Most supervisees can tolerate a clearly described disclosure pathway. What they cannot tolerate is finding out after the fact that a conversation they considered confidential was reported elsewhere. The contract should commit the supervisor to telling the supervisee, where safely possible, before a disclosure is made, and to documenting the rationale and content of any disclosure.

Evaluation, documentation, and what the contract says when problems emerge

A supervision contract is at its most useful when supervision becomes difficult. The contract that names evaluation criteria upfront makes a remediation conversation easier later. The contract that defines documentation responsibilities makes a regulatory audit straightforward. The contract that anticipates termination removes a layer of relational uncertainty when the work needs to end.

Three drafting principles help here. Define competencies in observable terms where possible (specific clinical behaviors, documentation standards, attendance and preparation expectations) rather than relying on global descriptors. Specify the frequency and format of evaluations, with at least one formal review per six-month period in most regulatory contexts. And name the steps the supervisor will take if a competency concern emerges, including additional observation, written feedback, a remediation plan and, if necessary, withholding a competency sign-off.

The remediation clause is the one most supervisors avoid drafting because it feels adversarial. In practice it does the opposite. A supervisee who knows in advance what a remediation process looks like is much more likely to engage with one constructively. A supervisee who first encounters the idea of remediation when it is being applied to them is much more likely to experience it as a rupture.

Jurisdictional notes: contract requirements across AU, US and Canada

The principles above hold across the three jurisdictions in which Kindred operates. The specifics differ. The table below summarizes the main jurisdictional contracting expectations supervisors should be aware of.

Two qualifications matter. State and provincial requirements within the US and Canada vary materially; the table reflects representative rather than universal positions, and supervisors should verify current rules with the specific board or college whose registrants they are supervising. And requirements change. The freshness note at the foot of this article applies particularly to this section.

A worked example: contracting at the first session

Maya is a board-approved supervisor in Melbourne taking on a provisional psychologist, Daniel, who is completing his internship. Their first contracting session runs ninety minutes. Maya works through the ten elements in roughly the order above.

On parties and scope, Maya confirms her board approval and her competence in Daniel's primary area of practice (adult mental health in private settings). She names the area she is not endorsed in (pediatric assessment) and they agree that if Daniel takes on pediatric work, secondary supervision will be required.

On purpose and logistics, they confirm the supervision is for Daniel's internship hours, document the required frequency under his Provisional Psychologist Plan of Supervision, and agree on weekly fifty-minute sessions in person, with video as a fallback during school holidays.

On confidentiality, Maya works carefully through the limits. She names AHPRA's mandatory notification thresholds, the reporting she will provide to Daniel's principal supervisor and training program, and her commitment to tell Daniel in advance of any notification where it is safe to do so. Daniel raises a question about disclosures to his employer. They draft a sentence covering that scenario specifically.

On evaluation, they agree to formative feedback at each session, a written six-monthly evaluation against the AHPRA competency framework, and a remediation pathway that begins with a written competency concern and a development plan before any formal report.

On termination, they agree on six weeks' notice in either direction, with provision for shorter notice in safety-critical circumstances and a handover meeting with Daniel's principal supervisor.

Maya documents the conversation, sends Daniel a draft for review, and they both sign at the second session. Total time invested: under three hours across two sessions. Risk reduced for both parties: substantial.

Common contracting mistakes supervisors make

Several patterns recur in supervisor training and in regulatory complaints:

• Using a template without adaptation. Generic templates miss jurisdictional specifics, the supervisor's actual scope, and the supervisee's particular pathway. The template is a starting point, not the contract.

• Treating contracting as paperwork rather than process. The conversation matters more than the document. A signed contract no one read through together is a thin protection.

• Under-drafting the limits of confidentiality. A vague reference to professional and legal obligations is not adequate informed consent for a supervisee about to share sensitive material.

• Avoiding the evaluation and termination clauses because they feel adversarial. Both clauses make the work easier, not harder, when difficulties emerge.

• Never revisiting the contract. Supervision is a developmental relationship. The contract should be reviewed at agreed intervals, certainly when learning goals shift, and renegotiated when the relationship continues into a different phase (for example, from supervised practice to ongoing professional supervision after registration).

For supervisors managing several supervisees across organizations, keeping contracts current and accessible is itself a workflow problem. Some platforms, Kindred Clinical among them, store supervision agreements alongside session notes and hour logs so that the contract remains a living document rather than a one-off artefact.

Conclusion

A clinical supervision contract is not administrative clutter. It is one of the most important documents in the supervisory relationship because it defines the purpose, boundaries, expectations, responsibilities, and limits of the work before problems arise. A well-drafted contract supports informed consent, protects both supervisor and supervisee, and gives the supervision relationship a stable frame when issues such as confidentiality, evaluation, reporting, remediation, or termination become difficult.

The strongest supervision contracts are specific, current, and discussed rather than simply signed. They name the parties, scope, goals, logistics, fees, confidentiality limits, documentation practices, evaluation processes, reporting obligations, dispute pathways, and termination procedures. They also reflect the supervisee’s jurisdiction, profession, registration pathway, and learning needs rather than relying on a generic template.

Contracting well is a high-leverage supervision practice. It reduces ambiguity, strengthens the supervisory alliance, supports regulatory compliance, and makes hard conversations easier because the process has already been agreed. Supervisors who treat the contract as a living document – reviewed, updated, and used when needed – create clearer, safer, and more defensible supervision.

Note: This article is general information current as of June 2026. Licensure, registration and supervision requirements change. Always verify current rules with your relevant regulatory body before making professional decisions.

Key takeaways

• A clinical supervision contract is the written agreement that defines the supervisory relationship, including its purpose, scope, expectations, confidentiality limits, evaluation processes, documentation practices, and termination procedures.

• A written contract is non-negotiable because it supports regulatory compliance, informed consent, risk management, and a clearer supervisory alliance.

• Strong contracts protect both parties. They help supervisees understand what they are agreeing to and help supervisors document expectations before concerns arise.

• A good supervision contract should include ten core elements: parties and credentials, purpose and learning goals, logistics, fees, confidentiality, documentation, evaluation, reporting obligations, dispute resolution, and termination procedures.

• Generic templates are only a starting point. Contracts need to be adapted to the supervisor’s scope, the supervisee’s profession, the relevant jurisdiction, and the specific pathway or purpose of supervision.

• The confidentiality clause is often under-drafted. It should clearly explain what remains confidential, what must be disclosed, to whom disclosure may be made, and the process the supervisor will follow when disclosure is required.

• Limits to confidentiality should include mandatory reporting, notifiable conduct, risk to self or others, legal compulsion, and reporting obligations to training programs, employers, regulators, or boards.

• Evaluation and feedback processes should be defined at the beginning of supervision. This includes formative feedback, formal review points, assessment criteria, competency sign-off, and what happens when concerns emerge.

• Remediation clauses are not adversarial. They make difficult conversations easier by explaining in advance how competency concerns will be identified, documented, reviewed, and escalated if necessary.

• Documentation responsibilities should be explicit. The contract should clarify who keeps supervision notes, what they include, where they are stored, how long they are retained, and how recordings are handled if used.

• Jurisdiction matters. Supervision contract requirements vary across Australia, the United States, and Canada, and supervisors should verify current rules with the relevant board, regulator, college, or professional body.

• The contracting conversation matters as much as the document. A signed contract that has not been discussed offers much weaker protection than a contract both parties have reviewed and understood.

• The first session should usually focus on discussing the contract, surfacing assumptions, and adapting the agreement before it is signed.

• Supervision contracts should be reviewed at agreed intervals, especially at formal evaluation points, when learning goals shift, when scope or registration status changes, or when supervision moves into a new phase.

• Contracting well reduces ambiguity, supports accountability, and gives supervisors and supervisees a shared reference point when supervision becomes complex.

Frequently asked questions

Q. Is a written supervision contract legally required?

A. In Australia, written supervision agreements are required for provisional psychologists, registrars and area-of-practice endorsement supervisees, and strongly recommended across all supervisory relationships. Most US state boards require written contracts for pre-licensure supervision, with the specifics varying by state and discipline. Most Canadian provincial regulators, including CRPO in Ontario, require documented supervision agreements for registrants in supervised practice. Verify current rules with the specific board or college that registers your supervisee.

Q. How long should a clinical supervision contract be?

A. Long enough to cover the ten elements specifically, short enough that both parties read it. Most well-drafted supervision contracts in private practice run three to six pages. Organizational supervision contracts and training-program contracts tend to run longer because they document reporting relationships and program-specific competency frameworks. Length is not the marker of quality; specificity is.

Q. Should the supervision contract be signed at the first session?

A. The first session is usually too early. A more effective sequence is: an initial session to discuss the contract content, draft adjustments, a second session to review and sign, and a copy held by both parties. Rushing the signing flattens the contracting conversation into a paperwork exercise and misses its most useful function, which is to surface assumptions early.

Q. What should a supervision contract say about session recordings?

A. If recordings are used (which is increasingly common for competency assessment and reflective practice), the contract should specify what is recorded, who has access, where the recording is stored, how long it is retained, when it is destroyed, and whose consent has been obtained. Client consent for recordings used in supervision is a separate question and should be addressed in the supervisee's client contracts, not assumed.

Q. How often should a supervision contract be reviewed?

A. At minimum at each formal evaluation point (typically six-monthly), whenever learning goals shift, when the supervisee's scope or registration status changes, and at any transition (for example, from supervised practice to post-registration supervision). The review does not require a new document each time; a dated annexure noting changes is usually sufficient.

Q. What if the supervisor and supervisee disagree about something in the contract?

A. The disagreement is useful information. A supervisee who pushes back on a clause is engaging with the contracting process, which is precisely what the process is for. Where genuine disagreement persists about a non-negotiable clause (for example, the limits of confidentiality), the supervisor should explain the regulatory or ethical basis and document the conversation. Where the disagreement is about a negotiable clause (frequency, fees, modality), it should be resolved in the contract itself.

Q. Putting the contract to work in your supervision practice

A. The clinical supervision contract is one of the few documents in a supervisor's working life that genuinely repays the time spent drafting it well. A good contract is rarely consulted because it has already done its work at the front end of the relationship. A poorly drafted one is consulted often, usually under stress, and usually too late.

Supervisors who contract well tend to share three habits. They treat the document as a conversation rather than a form. They revisit it at agreed intervals rather than at the point of crisis. And they keep their templates current with the regulatory frameworks of the registrants they supervise, not the framework they themselves were trained under.

Kindred Clinical works with board-approved supervisors across Australia, the United States and Canada who are building supervision practices on solid contractual foundations. Whether you are formalizing a new supervision offering or refreshing existing agreements, the time spent contracting well is reliably the highest-leverage investment you can make in your supervision work.

References

• American Psychological Association. (2025). Guidelines for clinical supervision in health service psychology. https://www.apa.org/about/policy/guidelines-supervision

• Bernard, J. M., & Goodyear, R. K. (2019). Fundamentals of clinical supervision (6th ed.). Pearson.

• Canadian Counselling and Psychotherapy Association. (n.d.). Canadian Counselling and Psychotherapy Association. https://www.ccpa-accp.ca/

• College of Registered Psychotherapists of Ontario. (n.d.). College of Registered Psychotherapists of Ontario. https://www.crpo.ca/

• Falender, C. A., & Shafranske, E. P. (2021). Clinical supervision: A competency-based approach (2nd ed.). American Psychological Association.

• Psychology Board of Australia. (n.d.). Supervisor guidelines. https://www.psychologyboard.gov.au/Standards-and-Guidelines/Codes-Guidelines-Policies.aspx#