9 Supported clinical autonomy

Decision authority and clinical advice

Clinical autonomy includes responsibility for making and implementing decisions without routine supervisory approval. Its extent should be described through the actual work. Consultants, Specialists, Associate Specialists and Specialty Doctors all need access to expertise beyond their own. Advice may come from an appropriately experienced colleague of any grade or profession; responsibility follows the agreed clinical arrangement rather than a presumed hierarchy.

This chapter distinguishes three arrangements: documenting established autonomous practice, supporting development in a new activity, and providing supervision where a capability is not yet established. They require different responses. An experienced practitioner should not be placed on a developmental ladder merely to make existing responsibility easier to document. Chapter 4 sets out the common principles.

Start with the activity and its boundaries

Autonomy becomes meaningful when it is attached to an activity. A doctor does not become universally autonomous on a particular date. Their capability and support arrangements relate to the work, setting and patient group.

Begin by describing the activity using T02. Identify the decisions the doctor will lead, what falls outside the intended scope and how advice or escalation is accessed. Then consider what evidence is available and what observation or review would help. This sequence is more useful than deciding first that contact with a consultant should reduce.

Appropriate help-seeking is part of senior judgement. A doctor who recognises an unfamiliar problem and obtains advice may be demonstrating sound practice. A doctor who avoids discussion to appear independent may be making the evidence less reassuring. The question is the quality and timing of the decision, not simply whether advice was sought.

The support agreement proposed here is an educational and operational aid. It is not a universal supervision scale or a substitute for local clinical governance. It should fit the service and be agreed by the people responsible for making it work.

Different kinds of support

Clinical support concerns care and the decisions arising during the activity. Educational support concerns learning and progress. Mentoring concerns professional reflection and direction. One person may contribute to more than one, but the functions should not be confused.

A mentor who meets you occasionally may be excellent for career reflection but unavailable during clinical work. A consultant providing clinical advice may not be the person who controls the job plan. A line manager may authorise the opportunity without being the observer best placed to comment on clinical reasoning.

T06 therefore asks who is available, for what purpose and through which route. It also asks who provides backup and what happens during absence. These details matter because vague reassurance can fail at the point of need.

Do not assume that “consultant support available” means the same thing to everyone. Is the consultant on site, reachable remotely or providing a planned review later? Which situations require immediate discussion? What is the alternative if the usual person cannot respond? The agreement should answer the relevant questions without creating a rigid rule for every possible clinical event.

Observation that informs judgement

Observation can take several forms appropriate to the activity. A colleague may observe a consultation, review reasoning in a case discussion, examine how a plan was communicated or consider a pattern of decisions over time. The evidence should identify what was actually observed.

Avoid the impression that a single observation proves the whole scope. Equally, do not require an arbitrary number of repeated observations without a reason. The review should consider the range and limitations of the available material and identify any important uncertainty.

The observer's role is to provide specific, informed feedback. “Very good doctor” may be encouraging but tells little about the activity. “Explained the competing problems, identified the uncertainty and used the agreed advice route before finalising the plan” provides a basis for understanding the judgement.

Feedback should include what remains outside the observer's knowledge. This does not weaken an honest account. It prevents a limited observation from becoming an unsupported global endorsement.

An illustrative support agreement

The following example sets out the elements of a support arrangement for a new outpatient clinic responsibility. It requires local detail and agreement before use.

The doctor will undertake the defined follow-up consultations within the clinic's agreed patient scope. The supporting clinician will be available through a specified advice route, with a named backup. The agreement will identify uncertainties requiring discussion and the escalation pathway for urgent deterioration or needs beyond the clinic's capability.

Selected work will be reviewed through observation and case discussion. The review will consider reasoning, communication, recognition of limits and follow-through. The initial review date is a local agreement. If the intended support is unavailable, the activity will be reconsidered through the service's clinical arrangements rather than continue on an assumption that the doctor should simply cope.

Make informal support explicit

In ordinary clinical relationships, experienced colleagues often describe support informally. They may know each other well and recognise when to intervene. That relationship can be valuable, but a development plan benefits from making its essential features explicit.

Ask what the supporting colleague is observing, how concerns will be raised and when they would step in. Ask what the doctor should discuss proactively and what can be reviewed afterwards. Record the arrangements that matter for the activity, especially where another colleague may need to provide cover.

This is not an attempt to document every human interaction. It is a way to ensure that trust does not depend entirely on unspoken assumptions. A clear agreement can support a good relationship by reducing uncertainty about expectations.

An operational agreement should make the support reliable across the service, including during absence or competing demands. Its purpose is to clarify responsibilities and access to advice. The appropriate level of observation and review depends on the activity, the evidence and the working environment.

Review the decisions rather than the appearance of independence

A review should consider what the doctor did when the work was straightforward and when it was uncertain. Did they identify important information? Explain the alternatives? Recognise a limit? Communicate the plan? Follow through on advice? These are examples of useful review questions, not a prescribed assessment instrument.

Patient outcomes can be relevant but require interpretation. A favourable outcome does not automatically establish good reasoning, and an adverse outcome does not by itself show poor judgement. Consider the information available at the time and the quality of the decision process.

Also review the service arrangement. Was advice accessible? Were responsibilities understood by the team? Did the support plan fit the activity? If the arrangement failed, do not attribute every difficulty to the doctor.

Record what can now be said with confidence and what remains uncertain. A conclusion such as “established within this scope, with continued discussion for the specified situations” is more useful than a broad label that conceals the boundaries.

More support can be appropriate progress

If review identifies a category of complexity that has not been encountered sufficiently, add focused discussion or observation in that area. Established work can continue under the existing arrangement while the specific uncertainty is addressed.

This is not a reversal of professional worth. It is a more accurate plan. The purpose of review is to change the arrangement when the evidence calls for it. A process that only allows support to decrease encourages people to conceal uncertainty.

The same principle applies to experienced autonomous doctors entering a new setting. Induction, advice and review can be appropriate without erasing established capability. A service should be able to distinguish familiarisation with local arrangements from a judgement about the doctor's entire clinical experience.

A discussion trigger should distinguish advice from mandatory approval. For example, a clinician may seek another opinion while retaining responsibility for the decision, or may be learning an activity in which a supervisor must approve the plan before implementation. T06 asks the team to record which applies. Emergency escalation and local safety protocols remain applicable to everyone.

Review should answer a real question. A changed service, unfamiliar procedure or concern may justify closer assessment. Routine peer review and governance can support established autonomous work without repeatedly reopening whether the doctor is allowed to practise because of their grade.

Established autonomy and recognition

If you already lead the activity, do not create an artificial developmental ladder merely because it seems easier to document. Describe the current scope and support, identify the evidence of practice and seek informed corroboration. The issue may be recognition rather than permission to begin.

Review still has value. It can clarify boundaries, update documents and identify changes in the service. But it should have an honest purpose. An experienced doctor should not be asked to repeat unnecessary steps solely to fit a generic programme.

Where actual responsibility exceeds the recorded role, connect the discussion to job planning and the applicable progression route. Do not let an autonomy discussion become an indefinite substitute for a formal consideration of recognition.

A review conversation about support

In a hypothetical review, the supporting clinician asks which decisions the doctor made within the agreed scope, which needed discussion and what uncertainty prompted the request for advice.

The doctor demonstrates sound reasoning in familiar work but needs more experience with one less familiar presentation before the support arrangement changes. The manager also identifies a cancelled review and unclear backup cover during leave: these become service actions, not evidence of a clinical deficiency.

The record states what continues, what needs further observation, who owns the backup arrangement and when the decision will be reviewed. Progress does not always mean reducing support; it means matching support to evidence and the work.

Keep mentoring separate from immediate clinical advice

As practice becomes established, the educational relationship may move towards occasional reflection and mentoring. That does not remove the need for a dependable clinical advice route. A mentor who is off duty or works elsewhere cannot be assumed to provide immediate help during the activity.

Describe both arrangements where they differ. The clinical support record identifies the available service response. The mentoring agreement identifies the purpose and frequency of professional discussion. This distinction is particularly useful when a service relies on remote advice or when the usual supporting clinician changes role.

For a doctor whose autonomy is already established, begin with the existing arrangements. Ask whether colleagues share the same understanding of scope and escalation. If the answer is yes, document it. If it is not, resolve the discrepancy before treating a confident personal account as evidence that the whole service arrangement is sound.

What the service needs to arrange

Provide dependable advice and escalation arrangements, appropriate observation and feasible review. Make sure support does not disappear during leave or ordinary pressure. If the proposed activity cannot be supported safely, reconsider the arrangement before it begins.

Clinical safety concerns require the established service response. They should not wait for a career review meeting. The development plan can record learning afterwards, but it must not replace clinical governance or incident processes.