Supervision level is the field that trainees leave blank because it feels bureaucratic until the day a critical incident review asks specifically who was responsible for the case and in what capacity. Local supervision, Distant supervision, Consultant, NCCG — these are not formalities. They are the governance record for your training portfolio, and in any clinical audit they are the first field the reviewer looks at when something went wrong.
An anaesthesia logbook that captures procedures and case times without capturing supervision status is a training record with a structural gap that becomes visible at the worst possible moment.
The Complexity That One Case Can Contain
A single list entry — Date, Start, End — might represent a straightforward elective general with one anaesthetic and one procedure. Or it might represent a vascular case with two anaesthetic techniques, a central line, an arterial line, and an epidural placed under distant supervision while the consultant was in a second theatre. Version 2 of this logbook captures both scenarios.
The three-procedure architecture — Procedure 1, 2, and 3, each with their own Operator Status and Technique fields — handles the multi-procedure reality without requiring workarounds. Operator Status for each procedure (Primary, Assistant, Observed) is logged independently because you might be primary on the epidural and assistant on the arterial line in the same case. That distinction matters for your numbers at ARCP, and it matters for understanding your own competency progression. A logbook that collapses all procedures into a single entry hides that nuance.
The Technique field per procedure is where the clinical specificity lives. A central line is not just a central line — it is US-guided right IJV, or landmark technique left subclavian, or femoral access in a coagulopathic patient where the standard approach was not available. The technique field is the one you will mine when you are writing up your CESR portfolio and need to demonstrate evidence of practice in non-standard clinical contexts.
ASA Status, Speciality, and Priority as Training Analytics
These three classification fields are the variables that let you see the shape of your training experience over time.
An ST3 with 200 logged cases that are all ASA 1 and 2 elective general surgery cases has not built the same risk exposure as one whose log shows a distribution across ASA 3 and 4, emergency priority cases, and multiple specialties including obstetrics, cardiothoracic, and neuro. The individual case record is clinical documentation. The aggregate pattern is a training adequacy assessment.
The Priority field — Elective, Urgent, Emergency, Immediate — is especially important because the decision-making environment changes categorically across that spectrum. An immediate case logged at 02:30 AM with ASA 4 and an incident flag carries a completely different profile than a morning elective ASA 2 appendicectomy, even if both lasted 90 minutes and used the same anaesthetic technique.
The Incident Field and Its Correct Use
The Incidents choice field plus the Incident Details free-text field is the safety documentation layer.
The tendency among trainees is to leave the Incidents field blank because logging an incident feels like creating a record of failure. This is backwards. A logbook that shows zero incidents over 18 months of varied casework is less credible than one that shows a handful of documented events with clear Incident Details explaining what happened, what the response was, and what was learned.
Critical Incident Technique reporting is an expected component of anaesthesia training portfolios. The logbook is the natural capture point. A difficult airway managed correctly with detailed incident documentation is a demonstration of competence, not evidence of a problem. The trainer reviewing your log at the end of year 2 who sees an AAGA incident with clear documentation and appropriate escalation noted in the details field understands that you are someone who documents honestly — which is the quality they are specifically looking for.
Cases per day logged on a given date, total across Start and End time, cross-referenced against Supervisor and Supervision Level: this is the portfolio that gets presented at ARCP. Build it every case.