on-call-handoff-patterns

wshobson ｜商業與營運｜原文｜ MIT

做好 on-call 輪班交接，傳遞 context 並記錄調查進度

中文翻譯

---
name: on-call-handoff-patterns
description: 精通 on-call 輪班交接，包含 context 傳遞、升級程序與文件記錄。在工程師之間交接 on-call 責任並確保接手的人掌握完整狀況、撰寫涵蓋進行中事件、調查中問題與近期變更的班次摘要、在事件處理到一半時交接讓新工程師能接下 incident commander 角色而不遺失 context、首次讓新工程師加入 on-call 輪值，或稽核並改善各團隊現有交接流程的品質時使用。
---

# On-Call Handoff Patterns

on-call 班次轉換的有效模式，確保跨班次的連續性、context 傳遞與可靠的事件應變。

## When to Use This Skill

- 交接 on-call 責任
- 撰寫班次交接摘要
- 記錄進行中的調查
- 建立 on-call 輪值程序
- 改善交接品質
- 讓新的 on-call 工程師上手

## Core Concepts

### 1. Handoff Components

| Component                  | Purpose                 |
| -------------------------- | ----------------------- |
| **Active Incidents**       | 目前壞掉的東西 |
| **Ongoing Investigations** | 正在除錯的問題   |
| **Recent Changes**         | 部署、設定變更    |
| **Known Issues**           | 已經採用的替代做法    |
| **Upcoming Events**        | 維護、發布   |

### 2. Handoff Timing

```
Recommended: 30 min overlap between shifts

Outgoing:
├── 15 min: Write handoff document
└── 15 min: Sync call with incoming

Incoming:
├── 15 min: Review handoff document
├── 15 min: Sync call with outgoing
└── 5 min: Verify alerting setup
```

## Templates and detailed worked examples

完整的範本庫與詳細的範例放在 `references/details.md`。需要具體範本時，再去讀那個檔案。

## Troubleshooting

**接手的工程師因為交接文件不完整，漏掉了一個關鍵問題。**
把交班檢查清單當作關卡：每個段落至少要有一筆內容（或明確寫「無」），才能標記為交接完成。把不完整的交接列為 blameless postmortem 的行動項目。

**因為時區差異，沒辦法開 30 分鐘的同步通話。**
退而使用非同步的快速交接範本（Template 2）。再補上一段簡短的 Loom 或語音備忘，帶過觀察清單。確保接手的工程師有直接的聯絡方式，萬一有後續問題可以問。

**接手的工程師一接班就碰上處理到一半的事件，立刻不知所措。**
專門使用事件交接範本（Template 3）。交班的工程師在交接後的 15 分鐘內，即使已經下班，也應該留在 Slack 上待命，回答釐清用的問題。

**各團隊的 on-call 交接文件格式不一致。**
全組織採用班次交接範本，並把完成的交接文件存放在共用位置（wiki、Notion、Confluence）。在 PagerDuty 的 on-call 排班條目中連結每一份交接文件。

**接手的工程師在交班的人下線前，無法確認自己的警報有在運作。**
加入一個標準步驟：交班的工程師發送一則測試警報，確認接手的工程師在 PagerDuty 和 Slack 都收到了，才結束重疊的時間窗口。

## Related Skills

- [incident-runbook-templates](../incident-runbook-templates/SKILL.md) — 處理中途交接的事件所用的 runbook
- [postmortem-writing](../postmortem-writing/SKILL.md) — 把班次中已解決的事件整理成結構化的 postmortem

英文原文

---
name: on-call-handoff-patterns
description: Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use this skill when transitioning on-call responsibilities between engineers and ensuring the incoming responder has full situational awareness, when writing a shift summary that captures active incidents, ongoing investigations, and recent changes, when handing off mid-incident so a fresh engineer can take over the incident commander role without losing context, when onboarding a new engineer to the on-call rotation for the first time, or when auditing and improving the quality of existing handoff processes across teams.
---

# On-Call Handoff Patterns

Effective patterns for on-call shift transitions, ensuring continuity, context transfer, and reliable incident response across shifts.

## When to Use This Skill

- Transitioning on-call responsibilities
- Writing shift handoff summaries
- Documenting ongoing investigations
- Establishing on-call rotation procedures
- Improving handoff quality
- Onboarding new on-call engineers

## Core Concepts

### 1. Handoff Components

| Component                  | Purpose                 |
| -------------------------- | ----------------------- |
| **Active Incidents**       | What's currently broken |
| **Ongoing Investigations** | Issues being debugged   |
| **Recent Changes**         | Deployments, configs    |
| **Known Issues**           | Workarounds in place    |
| **Upcoming Events**        | Maintenance, releases   |

### 2. Handoff Timing

```
Recommended: 30 min overlap between shifts

Outgoing:
├── 15 min: Write handoff document
└── 15 min: Sync call with incoming

Incoming:
├── 15 min: Review handoff document
├── 15 min: Sync call with outgoing
└── 5 min: Verify alerting setup
```

## Templates and detailed worked examples

Full template library and detailed worked examples live in `references/details.md`. Read that file when you need the concrete templates.

## Troubleshooting

**Incoming engineer misses a critical issue because the handoff document was incomplete.**
Use the outgoing checklist as a gate: do not mark handoff complete until every section has at least one entry (or an explicit "none"). Make incomplete handoffs a blameless postmortem action item.

**A 30-minute sync call is not possible due to timezone gaps.**
Fall back to the async quick handoff template (Template 2). Supplement with a short Loom or voice memo walking through the watch list. Ensure the incoming engineer has a direct contact method if they have follow-up questions.

**The incoming engineer inherits a mid-incident and is immediately overwhelmed.**
Use the incident handoff template (Template 3) specifically. The outgoing engineer should remain available on Slack for 15 minutes after handoff, even if off-call, to answer clarifying questions.

**On-call handoff documents are inconsistently formatted across teams.**
Adopt the shift handoff template organization-wide and store completed handoffs in a shared location (wiki, Notion, Confluence). Link each handoff from the on-call schedule entry in PagerDuty.

**Incoming engineer cannot verify their alerting is working before the outgoing engineer logs off.**
Add a standard step: outgoing engineer fires a test alert and confirms incoming engineer receives it in PagerDuty and Slack before ending the overlap window.

## Related Skills

- [incident-runbook-templates](../incident-runbook-templates/SKILL.md) — Runbooks for the incidents that are handed over mid-response
- [postmortem-writing](../postmortem-writing/SKILL.md) — Turn resolved incidents from the shift into structured postmortems