Shift Handoff & Knowledge Capture Template

Purpose

This single-page handoff template helps teams preserve not only clinical facts but the local reasoning that matters for safe, continuous care. Use it for complex patients and handoffs between teams where context, time‑sensitive tasks, or device settings matter. Keep it succinct, factual, and actionable.

How to use

1. Complete the top summary line: a 1–2 sentence clinical snapshot and the immediate plan.
2. Fill required fields for any patient with complexity, pending tasks, infusions/devices, or safety risks. Attach or save to the EHR or team knowledge platform.
3. Highlight the most urgent items using the Priority marker and expected due times.
4. Capture the 'why' for important decisions so successors quickly understand intent and tradeoffs.

Template fields (expanded)

• Patient identifiers — name, MRN, bed/unit, age, primary team, primary contact (phone).
• One-line snapshot — short clinial summary + immediate goal (example: "Septic shock on vasopressors; goal: wean norepinephrine by 0800 if MAP >65 for 2 hours").
• Primary problems & plan
  • Problem 1 — current status, specific plan, who owns it
  • Problem 2 — status, plan, owner
• Pending tasks & time-sensitive items
  • Task — due (time/date) — priority (High/Med/Low) — assigned to
  • Specify expected completion criteria (e.g., "obtain lactate by 06:00 and repeat in 6 hours")
• Therapies & devices (with settings)
  • IV drips (name, concentration, rate, target)
  • Ventilator settings and targets
  • Dialysis/CRRT settings
• Critical labs/imaging pending — test, expected time, action on result.
• Key clinical reasoning notes (the "why")
  • Why this plan was chosen (brief): alternatives considered, thresholds for change.
  • Known pitfalls or common misinterpretations.
• Known system / workflow risks
  • Examples: limited infusion pumps, pharmacy delays for urgent meds, pending consult not yet assigned, equipment sharing conflicts.
  • Actions already taken to mitigate and who to contact next.
• Escalation triggers / red flags — explicit thresholds or signs that require immediate notification or higher-level review (e.g., "MAP <60 OR urine <0.3 mL/kg/hr for 2 hours: call critical care fellow").
• Allergies & code status — place prominently.
• Handoff metadata — from (name/role), to (name/role), date/time, mode (bedside/phone/chart), signature or initials.

Suggested defaults & policies

• Mandatory use for all ICU transfers, post-op ICU discharges, and any patient on continuous infusions or high-risk devices.
• Attach the completed form to the EHR note or upload to the team knowledge platform so it's discoverable and auditable.
• Keep the top snapshot to one sentence; details belong in the relevant sections below.

Practical tips

• Prioritize: list time-sensitive tasks first with clear owners and due times.
• Write the 'why' in plain language: what prompted the decision and what should be watched.
• Use checkboxes for completed tasks to reduce repeated questions during rounds.
• Confirm receipt: receiver should repeat back the 1–2 urgent items to ensure clarity for high-risk patients.

Example (compact)

Patient: Jane Doe | MRN 12345 | Bed 6A | Team: Med-ICU
Snapshot: Post-op sepsis on norepi 6 mcg/min; goal: MAP ≥65 and wean as tolerated.
Problems & plan:
 - Sepsis: continue broad-spectrum antibiotics; reassess cultures q12h. Owner: Dr. K
 - Hemodynamics: norepi 6 mcg/min; attempt wean at 08:00 if MAP ≥65 for 2h. Owner: Nurse A
Pending tasks:
 - Repeat lactate at 06:00 (High) — Dr. K
Therapies/devices:
 - Norepi 6 mcg/min; central line in R IJ
Key reasoning:
 - High lactate + vasopressor need suggests persistent hypoperfusion; aiming to wean cautiously once lactate downtrending.
Risks:
 - Pharmacy delay expected for vancomycin IVPB; contact pharmacy ext. 402. 
Escalation: MAP <60 or lactate rising >1 mmol/L in 6h -> notify critical care fellow immediately.
Handoff: From Dr. K to Dr. L | 05:45 | bedside | initials: K/L
  

Measuring effectiveness

Audit a sample of handoffs weekly for completeness (top snapshot, pending tasks, escalation triggers present). Track incidents where handoff omissions contributed to near-misses; use findings to refine the template.

Adaptation & ownership

Units should copy this template and tailor fields, escalation thresholds, and mandatory usage rules to their workflows. Version the template and document ownership (unit lead or clinical educator) so iterative improvements are tracked.

When not to use

For very stable, low-risk patients a single-line status in the EHR may be sufficient. Use this one-page template when complexity, devices, or time‑sensitive tasks are present.

If you want this as a fillable, savable form that auto-populates from the EHR, or that stores submissions for analytics and learning, see Capability Enhancement notes below.