Purpose of the Clinical Supervisor (CS)

The CS supports and supervises the foundation doctor during their placement. Key responsibilities include:

• Day‑to‑day supervision and workplace observation
• Integrating the doctor into the team
• Ensuring appropriate opportunities, feedback, and portfolio engagement
• Supporting attendance at team meetings
• Providing clear feedback on performance and development needs

Supervisors should meet with trainees regularly—at the start and end of the placement, with optional mid‑placement reviews (recommended for trainees needing extra support).

MEETING FRAMEWORK

1. Induction Meeting (within first 2 weeks)

Getting to know the trainee

• Their experience (F1/F2 background)
• Any health, personal or domestic issues impacting training
• Any concerns or expectations for the placement

Training Needs

• Introduce senior staff and how to contact them
• Discuss goals for the placement and strengths/weaknesses
• Curriculum areas that can be evidenced in this post
• Opportunities for assessments
• Placement‑related PDP items
• For F2s: regional teaching bookings, study leave, tasters
• Audit opportunities
• Importance of contemporaneous portfolio logging

Consider contacting the Educational Supervisor, especially for out‑of‑Trust posts (GP, psychiatry, public health).

Practical requirements

• Ensure you have Horus access
  
• Identify potential Placement Supervision Group (PSG) members (senior doctors, nurses, AHPs)
• Review the trainee’s PDP
• Log the meeting (Induction Meeting with CS form)

Horus instructions

• Sign In - Horus ePortfolio
• Admin menu → Foundation Doctors → trainee name
• Trainee homepage → orange box → PDP
• Forms (start new) → “Induction meeting with CS”

2. End‑of‑Placement Review

Before the meeting:

• Set up the PSG (each trainee must have at least one per year; good practice to run one each placement). Guidance found here - Microsoft Word - How to Gain PSG Feedback Jan 2019.docx
• Review any concerns logged on Horus
• Contact the ES if further clarification is needed

During the meeting:

• Review development during the placement
• Check any absences are recorded
• Discuss reflections and PDP updates
• Ensure curriculum evidence has been linked*
• Log the meeting
• Escalate concerns to the Educational Supervisor if required

Horus instructions

• Trainee homepage → orange box → Concerns
• → Contents (to review placement activity)
• → Placement Supervision Group → Manage Feedback
• → PDP/Reflections
• → Curriculum
• Forms (start new) → “CS end of placement report”

The curriculum requires evidence for all capabilities; items can map to max 3 capabilities; do not exceed 5 items per capability.

3. May/June – Final Placement Report

CSRs for the final placement must be completed by the end of May, as portfolios are submitted in early June.

If you feel unable to complete the report (e.g., little opportunity to observe the trainee or early concerns), advise the trainee that you cannot complete it at this time.
Explain this may lead to an Outcome 5, and the trainee must inform their TPD.

Appendix – Study Leave (Key Summary)

Policy - Study Leave - Foundation

F2 Study Leave (30 days total)

Pre‑allocated:

• 5 days teaching (min 4 regional days + 6 hrs foundation teaching)
• 1 day simulation
• 5 days tasters (may also be taken in F1)
• 5 days GP learning sets
• 2 days ALS

Trainees not in GP: 17 days remaining
Trainees in GP: 12 days remaining

Teaching Hours

• ALL teaching logged in Horus personal learning log
• Includes regional, local, departmental teaching, and eLearning
• Hard‑to‑verify teaching requires an additional achievement form

ARCP Requirements

• Minimum 60 hours teaching (min 30 hours core)
• F2s must attend 4 regional teaching days (24 hrs)
• Max 6 eLearning modules (6 hrs)