The shift handover is the single most documentation-intensive task in a nurse's shift. On a standard 12-hour ward shift, nurses report spending 25–40 minutes per handover — often more at the end of a busy shift when attention is depleted and time pressure is high. The quality of that handover directly affects patient safety on the next shift. Claude Cowork for shift handover reports changes both the time cost and the quality, consistently and measurably.

This is a workflow guide, not a concept guide. It covers the exact steps to run the SBAR handover workflow in Claude Cowork, the prompt templates that experienced users have refined through hundreds of shifts, and a format comparison between SBAR and I-PASS. For the broader context of how Cowork applies across nursing practice, start with our complete guide to Claude Cowork for nurses.

Why Shift Handovers Are Broken — And Why It Matters

A 2023 Joint Commission analysis found that communication failures during handover were the leading contributing factor in over 70% of sentinel events — the most serious preventable adverse events in healthcare. The problem is not that nurses do not care about handover quality. It is that the process is systematically broken: nurses are producing a complex clinical summary from fragmented shift notes, often from memory, under time pressure, at the end of their most exhausting shift hours.

The result is handovers that are inconsistent in structure, variable in completeness, and dependent on individual nurse performance on a given day. Claude Cowork removes the human variability from the document production while keeping the clinical judgment where it belongs: with the nurse who reviews and approves the output.

The 5-Step Cowork SBAR Handover Workflow

This is the production workflow. It takes 5–7 minutes for a 6-patient caseload. It produces a structured, complete SBAR document that can be read directly in a bedside handover or filed into your ward's handover system.

1

Prepare your files (2 minutes)

Before uploading, name each file with the patient identifier and bed number: "Patient-A-Bed4-ShiftNotes.pdf". This is not optional — Cowork uses these filenames to correctly attribute each SBAR section. If your shift notes are in a single document, add a header row for each patient. Cowork can parse a single multi-patient document, but individual files produce cleaner output.

2

Upload everything to the Cowork canvas (30 seconds)

Drag all patient files, your observation charts, and any pending task lists into the Cowork canvas. You can upload PDFs, Word documents, plain text files, and images of handwritten notes. Cowork reads all of them. Do not worry about formatting — it handles the extraction.

3

Run the batch SBAR prompt (30 seconds to type, ~2 minutes to generate)

Paste the SBAR prompt (see below) and run it. Cowork processes all uploaded files simultaneously and generates a structured SBAR section for each patient. For 6 patients, generation takes approximately 90–120 seconds.

4

Review and annotate (2–3 minutes)

Read each SBAR section. Add any context that is not in your written notes: the patient's emotional state, a family member's concerns, a conversation you had with the covering doctor. These qualitative observations are yours to add — Cowork cannot capture them from documentation. Mark any section that needs escalation.

5

Export and hand over (30 seconds)

Copy the final document into Epic, Cerner, or your ward handover system. Print or share digitally for the bedside handover. The incoming nurse receives a structured, complete summary — not a verbal ramble from a nurse trying to remember 12 hours of events.

The SBAR Handover Prompt Templates

Three variants depending on your handover format:

Standard SBAR — Batch (6 patients)
I've uploaded shift notes for all patients in my caseload. Please generate a structured SBAR handover for each patient. Structure each section as: SITUATION: Patient name/ID, age, admitting diagnosis, current clinical status in 2 sentences BACKGROUND: Relevant medical history, current medications (key ones), significant events during this admission ASSESSMENT: Changes during this shift, current observations summary, clinical priorities, risk flags RECOMMENDATION: Outstanding actions, pending results with expected timeframe, tasks for incoming nurse, any escalation needs Flag patients requiring immediate attention with ⚠ at the start of their section. Present each patient as a clearly separated section with their identifier and bed number as the heading.
I-PASS Format Handover
Using the uploaded shift notes, generate an I-PASS format handover for each patient: ILLNESS SEVERITY: [Stable / Watcher / Unstable] with one-sentence justification PATIENT SUMMARY: Reason for admission, hospital course summary, active problems ACTION LIST: Pending tasks, ordered investigations, treatments to complete SITUATION AWARENESS: Anticipated changes, contingency plans (if X then do Y), what could go wrong SYNTHESIS BY RECEIVER: [Leave blank — for incoming nurse to complete verbally] For any patient marked Watcher or Unstable, include specific deterioration criteria to monitor.
End-of-Shift Outstanding Tasks Only
From the uploaded shift notes, extract all outstanding tasks, pending actions, and incomplete items for my entire caseload. Present as a checklist organised by patient (use their identifier and bed number as headers). For each item include: what the task is, when it was ordered or identified, who is responsible, and the priority level (urgent / routine / as needed). Flag anything that has been outstanding for more than 4 hours.

Before and After: What the Handover Actually Looks Like

The qualitative difference between a traditional handover report and a Cowork-generated one is significant. Here is what changes:

Dimension Traditional With Cowork
Time to produce 28–40 min 5–7 min
Structural consistency Variable by nurse/shift Identical structure every time
Outstanding tasks captured What nurse remembers All items from documentation
Escalation flagging Implicit, easily missed Explicit ⚠ flags on every report
End-of-shift nurse fatigue impact High — quality degrades None — output quality is consistent

SBAR vs I-PASS: Which Format Should Your Ward Use?

SBAR (Situation-Background-Assessment-Recommendation) is the most widely used nursing handover framework in the UK, Australia, and parts of the US. It is well understood, quick to train, and works for most general ward settings. I-PASS (Illness Severity, Patient Summary, Action List, Situation Awareness, Synthesis by Receiver) was developed specifically for hospital handovers and has a stronger evidence base for reducing medical errors — particularly the "Synthesis by Receiver" component, which forces the incoming nurse to verbally summarise their understanding of each patient.

Cowork supports both. Most ward teams start with SBAR because their nurses already know the format, then move to I-PASS after 4–6 weeks when they want to formalise the incoming nurse engagement step. Both formats can be saved as a Cowork Skill — one click, no re-typing the prompt.

Integration with Epic, Cerner and Other EHR Systems

The most common deployment pattern is what we call the "draft and paste" workflow: Cowork produces the structured handover document, the nurse reviews and annotates it, then pastes the final version into the EHR's nursing handover section. This requires no IT configuration and can start on day one of Cowork access.

For organisations that want deeper integration — where Cowork reads directly from Epic FHIR data exports and writes structured notes back into the EHR — our EHR integration guide covers the technical setup. This typically requires a 4–6 week IT configuration project. For a managed deployment, see our Claude Cowork deployment service.

The 82% time saving is conservative. Nurses who run the batch SBAR workflow consistently report total handover time of 4–8 minutes. The 82% figure is based on a comparison against the median traditional handover time of 32 minutes. On busy shifts where the traditional process takes 45+ minutes, the saving is closer to 90%.

Building a Handover Skill Your Whole Ward Can Use

The SBAR handover workflow becomes dramatically more valuable when it is deployed as a ward-level Cowork Skill, not just an individual prompt. A Skill means any nurse on the ward — including bank staff and new starters — can run the same structured handover process with one click, without needing to write or even understand the prompt. Build it once, the whole ward benefits.

Our recommendation: make the SBAR Skill your first deployment priority. Within 2 weeks of building it, every nurse on the ward will be using it. Within 4 weeks, handover quality will be measurably more consistent. This is the most impactful single investment you can make in nursing documentation efficiency.

For more techniques across the full nursing workflow, read our 8 daily Claude Cowork tricks for nurses. For the documentation reduction case that justifies this investment at CNO level, see our guide to how Claude Cowork reduces documentation burden for nursing teams. For patient education materials, see our guide to generating patient education materials at scale with Cowork.

30 Minutes of Handover. Cut to 5. Starting This Week.

Most nursing wards can deploy the SBAR Cowork workflow without any IT project, API configuration, or infrastructure change. You need an enterprise Cowork licence and 2 hours of onboarding. Book a call to see a live demo on real ward data.