Essays

The form of supervision matters

By Chris English6 min read

TL;DR

Logging is a tally function. It is not what supervisors do. Why the December 2025 framework turned an aesthetic gap into a structural one.

Why supervision was never a logbook problem


Open any Board-Approved Supervisor's drawer in private practice and you'll find a notebook. Or a Word document. Or a spreadsheet nobody else sees. That notebook is where supervision actually runs. The tool — whatever subscription generates the audit trail — is what gets shown when AHPRA asks.

That two-system arrangement is so common that supervisors rarely stop to question it. It's just the cost of doing the work properly. But the gap between what the tool wants and what the work needs is the entire argument of what follows.


What supervisors actually carry

The actual cognitive load of supervision has very little to do with hours.

A supervisor with three provisionals on the books holds, at minimum: each caseload, each therapeutic alliance, each provisional's reactions to the work, the alliance you have with each of them, your own reactions to supervising them, and the practice context around all of it.

The Supervisor Training and Approval Program (STAP), which underpins supervisor training in Australia, names seven aspects of every supervisory relationship:

  1. The client

  2. The intervention

  3. The supervisee–client alliance

  4. The supervisee's reactions

  5. The supervisee–supervisor alliance

  6. The supervisor's own reactions

  7. The surrounding systems

Brisbane supervisor Catherine Hynes has publicly outlined her own working-through of all seven, session by session.

Seven aspects, per session, per provisional. A supervisor with three provisionals running fortnightly sessions makes about seventy-five complete passes through that geometry a year, each one anchored to a different person at a different stage.

That's the load. The hours are an artefact of the work, not the work itself.

When a tool says it's for supervisors, the honest test is which of those seven axes it touches. Most of the answer, on most tools, is none.


Existing tools digitised the wrong layer

Three things happen in supervision, not one.

There's the session itself, where the seven aspects land in the room. There's the carry between sessions — the holding, the pattern recognition, the quiet flag that says this case is starting to feel different. And there's the arc across the relationship: twelve months in which a provisional moves from anxious technician to capable practitioner, ending with you signing a competency attestation that puts your professional name on someone else's standing.

Existing tools digitise one of these three. The smallest one.

The carry between sessions has no infrastructure. You do it in your head, in your notebook, in the margins of clinical notes that aren't yours to keep. The arc across the relationship has no infrastructure either. You stitch it together at sign-off from emails, memory, and whatever your provisional happened to log.

Supervision is a two-way process — preparation, openness, reflection, tracking, on both sides. That's an accurate description of the work, and it's also a description of work that nothing currently on the market helps with. Logging the hour the work happened in is not preparation. It's a receipt for it.

The category itself gives this away. The dominant tool name is logbook.

Logging is a tally function. It is not what supervisors do.

If your tool feels like it's doing the wrong job, that's because it is. It isn't built for the work — it's built around the bit of evidence the regulator used to count.


December 2025 turned an aesthetic gap into a structural one

Until last December, the gap between supervision-as-tools-imagined-it and supervision-as-supervisors-did-it was a matter of taste. The regulator counted hours. The tools counted hours. The form of supervision was your own private business.

Then the framework moved.

The Psychology Board of Australia's competency-based assessment framework, operative from December 2025, doesn't reward hour completion. It assesses development across eight core competencies, formalised in the PACF-76. Your job at the end is no longer to confirm hours are full. It's to make a structured judgement about whether the provisional has developed competency — and to put your professional name on that judgement, with the new Code of Conduct holding you statutorily liable for what they go on to do in practice.

The regulatory frame has moved from output to architecture, from quantity to form.

Hours are now evidence supporting a competency claim. They are not the claim itself.

Tools that count hours are no longer just shallow. They're misaligned with the question being asked of you.

If your evidence base for sign-off is a stack of session entries proving time happened, you're prepared for a 2024 audit. Not a 2026 one.


What it would look like to build for the work

The bet behind Bridgyr is that the form of supervision is the actual work, and the work is what the system around you should be built to hold.

That doesn't mean replacing your thinking with software. The thinking belongs where it has always belonged — in your head, in the room, in the supervision itself. What changes is what gets carried around it.

You sit down for a session and your own observations from the last one are still in front of you, not buried in a notebook in a drawer. The unease you flagged three weeks ago about a particular case is on the page when the same case comes up again, and you notice the pattern in time to raise it — not at sign-off when it's too late.

When you bring a hard conversation to a provisional — about a competency you've watched develop more slowly than others, or about a case you've been holding quiet concern over — you're not asking them to take a hunch on faith. The history is there. You can both look at it.

When the year ends, the competency attestation isn't a leap of faith on a Friday afternoon. It's the natural conclusion of twelve months of work that has been visible to you the whole way through.

The two systems collapse into one. The work you've been doing in private becomes the structure of how you supervise — visible, held, part of the record.

If you're already keeping your own notes between sessions because the tool doesn't carry them, that's the labour a supervisor-built tool should absorb. Anything that doesn't isn't built for you.


The notebook in the drawer

That notebook was never a workaround. It was always the work, written down somewhere safe because the system you were given couldn't hold it.

It's the most honest thing in your supervision practice. The job is to make the rest of your tooling worthy of it.


Sources