Shift handoff playbook

Transferring operational responsibility cleanly: the handoff document template, doctor run, copilot brief, and the checklist that a backup operator works through.

Updated

Status: Draft | Last Updated: 2026-05-03 | Version: 1.0

Executive Summary

This scenario demonstrates knowledge transfer between operators during shift changes or transitions. Proper handoffs ensure operational continuity, prevent information loss, and maintain team morale.

Scenario Context: An operator (Rocky) is handing off operational responsibility to a backup operator for a 2-week vacation. The handoff must cover all aspects: workspace state, active issues, routines, and upcoming work.

Handoff Outcome: Complete knowledge transfer in 90 minutes, backup operator fully operational, no incidents during Rocky’s absence.

Learning Objectives:

  • Creating comprehensive handoff documentation
  • Running pre-handoff validation checks
  • Conducting live handoff session
  • Monitoring during absence
  • Post-handoff reintegration

Table of Contents

  1. Pre-Handoff Preparation
  2. Handoff Documentation
  3. Live Handoff Session 4 During Absence
  4. Reintegration
  5. Key Takeaways
  6. Related Documentation

Pre-Handoff Preparation

Validation Checklist

Operator (Rocky) runs pre-handoff validation:

Ctrl+K → "Run Doctor and create handoff validation report"

Doctor Report:

┌─────────────────────────────────────────────────────────────────────┐
│ Handoff Validation Report — Pre-Departure Check                         │
├─────────────────────────────────────────────────────────────────────┤
│                                                                     │
│ ✅ System Health              PASS                                │
│    All workspaces operational                                   │
│                                                                     │
│ ✅ Backup Operator Ready        PASS                                │
│    Backup operator (Backup_Op) has access configured            │
│                                                                     │
│ ✅ Routines Stable              PASS                                │
│    5 active routines, no failures in past 7 days                │
│                                                                     │
│ ✅ Budgets On Track              PASS                                │
│    All workspaces within budget                                │
│                                                                     │
│ ✅ No Critical Issues            PASS                                │
│    Copilot shows 0 critical insights                            │
│                                                                     │
│ ⚠️  Action Items Pending          WARNING                             │
│    3 tickets in progress require attention during absence:          │
│    • #87 (Client C urgent fix) — assign to Backup_Op               │
│    • #88 (Routine optimization) — pause until return              │
│    • #89 (Documentation update) — optional, can defer            │
│                                                                     │
│─────────────────────────────────────────────────────────────────────│
│                                                                     │
│ STATUS: Cleared for handoff with 3 action items                      │
│                                                                     │
│ [View Full Report]           [Schedule Handoff]    [Cancel]        │
└─────────────────────────────────────────────────────────────────────┘

Assigning Action Items

Rocky assigns action items to Backup_Op:

Ctrl+K → "Assign ticket #87 urgent fix to Backup_Op"

Result: Backup_Op now owns the urgent fix and will handle it during Rocky’s absence.

Handoff Documentation

Comprehensive Handoff Document

Rocky creates handoff document in shared vault:

Navigate to: Files → Create Document

Handoff Document Contents:

# Operational Handoff — Rocky to Backup_Op
**Dates:** May 3 - May 17, 2026 (2 weeks)
**Prepared by:** Rocky
**Prepared for:** Backup_Op

---

## 1. Workspace Overview

### Active Workspaces

| Workspace | Purpose | Monthly Budget | Key Contacts | Current Status |
|-----------|---------|--------------|--------------|---------------|
| Strategia-X | Internal product | $300 | Rocky (owner) | Healthy |
| Client A | Ecommerce analytics | $100 | Rocky (owner) | Healthy |
| Client B | Fintech pipeline | $80 | Rocky (owner) | Healthy |

### Employee Count

| Workspace | Total | Active | Idle | Notes |
|-----------|-------|--------|------|-------|
| Strategia-X | 12 | 10 | 2 | Normal turnover |
| Client A | 5 | 5 | 0 | Full utilization |
| Client B | 3 | 3 | 0 | Full utilization |

### Routines Summary

| Routine | Schedule | Last Execution | Status | Notes |
|---------|----------|----------------|--------|-------|
| Daily code review | MWF 9am | Today 9:05am | ✅ Active | Normal |
| Nightly data sync | Daily 2am | Today 2:03am | ✅ Active | Normal |
| Weekly summary | Mon 9am | Last Monday | ✅ Active | Normal |
| Security scan | Daily 3am | Today 3:02am | ✅ Active | Normal |
| Cost anomaly scan | Every 6h | 2 hours ago | ✅ Active | Normal |

---

## 2. Active Issues

### Critical (Requires Immediate Attention)

**Ticket #87: Client C Urgent Fix**
- **Workspace:** Client C
- **Assigned to:** Backup_Op (you)
- **Priority:** Critical
- **Description:** Data pipeline failing, client impacting
- **Status:** In progress
- **Next Action:** Diagnose and resolve within 4 hours
- **Fallback:** Contact Rocky if escalation needed

### Important (Monitor Daily)

**Ticket #88: Routine Optimization**
- **Workspace:** Strategia-X
- **Assigned to:** Elena (Tech Lead)
- **Priority:** High
- **Description:** Optimize daily code review routine
- **Status:** In progress, paused for handoff
- **Action:** Do NOT complete until Rocky returns (awaiting decision)

### Optional (Can Defer)

**Ticket #89: Documentation Update**
- **Workspace:** Strategia-X
- **Assigned to:** Alex (Product Manager)
- **Priority:** Low
- **Description:** Update user guide with new features
- **Status:** Open
- **Action:** Can defer until Rocky returns

---

## 3. Budget Status

### Current Spend (Month-to-Date)

| Workspace | Budget | Spent | Remaining | Projection |
|-----------|--------|-------|----------|-----------|
| Strategia-X | $300 | $187 | $113 | On track ✅ |
| Client A | $100 | $82 | $18 | On track ✅ |
| Client B | $80 | $65 | $15 | On track ✅ |
| **TOTAL** | **$480** | **$334** | **$146** | **On track** |

### Budget Approvals

**Approval Authority:** Backup_Op has approval authority for:
- Budget overrides up to $50
- Routine changes (non-breaking)
- Employee hiring/firing (consult Rocky first)

**Requires Rocky Approval:**
- Budget overrides over $50
- Routine breaking changes
- Employee termination

---

## 4. Copilot Insights Review

### Recent Insights (Last 7 Days)

Critical Insights: 0 Warning Insights: 1 Info Insights: 3

Warning Details:

  • ⚠️ WORKFLOW, Routine optimization ticket paused for 2 weeks Impact: Minor (routine continues running with old settings) Action: Monitor for stall

Info Details:

  • ℹ️ COST, Monthly spend trending down 5% (good!)
  • ℹ️ INFO, Client B expressed satisfaction with deliverables
  • ℹ️ INFO, New employee (Sarah) onboarding smoothly

**Action:** No immediate actions required. Continue monitoring.

---

## 5. Contacts and Escalation

### Primary Contact (Rocky)

- **Availability:** Limited (email checked daily at 9am and 5pm)
- **Response Time:** < 24 hours for urgent matters
- **Emergency Contact:** [Phone number for true emergencies]

### Secondary Contacts (By Workspace)

**Strategia-X:**
- Elena (Tech Lead): Technical issues, architecture
- James (DevOps): Infrastructure, deployments

**Client A:**
- Priya (Frontend Lead): Client deliverables
- Mike (Backend Lead): Data pipelines

**Client B:**
- Alex (Product Manager): Client relationship
- Sarah (QA): Testing issues

### External Support

**Provider Issues:**
- Anthropic Support: [Contact for API issues]
- OpenAI Support: [Contact for API issues]
- Ollama Support: [Self-hosted, no external support]

---

## 6. Known Issues and Workarounds

### Issue: Safari Chart Rendering

**Status:** Known, deferred to iteration
**Impact:** Medium (Safari users see chart artifacts)
**Workaround:** Use Chrome/Firefox for dashboard
**Ticket:** #91 (deferred to post-vacation)

### Issue: GitHub Webhook Delay

**Status:** Monitoring
**Impact:** Low (5-min delay vs. real-time)
**Workaround:** Manual polling compensates
**Ticket:** #92 (under investigation)

---

## 7. Decision Log

### Decisions Requiring Backup_Op Judgment

**Scenario:** Client C requests urgent data pipeline fix requiring overtime work.

**Decision Framework:**
1. Is client safety at risk? → Approve immediately
2. Does budget allow? → If yes, approve; if no, consult Rocky
3. Does it require breaking change? → Consult Rocky first

**Scenario:** Routine optimization stalled

**Decision:** Do NOT complete until Rocky returns. Routine continues with old settings.

---

## 8. Quick Reference Commands

### Common Tasks

Check system health

Ctrl+K → “Run Doctor”

View all active issues

Ctrl+K → “Show me all critical and warning insights”

Check budget status

Ctrl+K → “What’s our current spend vs budget across all workspaces?”

Monitor stuck loops

Ctrl+K → “Show agentic loops running > 30 minutes”

View routine status

Ctrl+K → “Are all routines running normally?”


### Emergency Procedures

**If multiple systems failing:**
1. Run Doctor immediately
2. Check Copilot for critical insights
3. Review recent ticket threads for patterns
4. Escalate to Rocky if unresolved

**If budget exhausted:**
1. Check which workspace exceeded budget
2. Review routine spend for anomalies
3. Approve budget override (if < $50) or consult Rocky
4. Consider pausing non-critical routines

**If employee complaint:**
1. Review ticket thread for context
2. Check employee status (Mission Control)
3. Escalate to workspace lead or Rocky

---

## 9. Return Plan

### Reintegration Checklist

**When Rocky Returns:**

- [ ] Review handoff document with Backup_Op
- [ ] Review Copilot insights from absence period
- [ ] Review Audit log for key events
- [ ] Reassign ticket #88 (Routine optimization)
- [ ] Address ticket #89 (Documentation) or defer further
- [ ] Debrief with Backup_Op on learnings
- [ ] Update handoff document with any new procedures

### Timeline

- **May 3, 5pm:** Handoff session
- **May 3 - May 17:** Backup_Op operational
- **May 17, 9am:** Rocky returns, Backup_Op hands back
- **May 17, 10am:** Reintegration complete

---

## Signature

**Prepared by:** Rocky (Operator)
**Reviewed by:** Backup_Op (Backup Operator)
**Date:** May 3, 2026

**Backup_Op Acknowledgement:**
I have reviewed this handoff document, understand my responsibilities, and confirm I can perform operational duties during Rocky's absence.

**Signature:** _________________ (Backup_Op)
**Date:** May 3, 2026

Live Handoff Session

Session Structure

Scheduled: May 3, 5pm (90 minutes) Attendees: Rocky, Backup_Op Location: Conference room / Video call

Agenda:

  1. System Walkthrough (30 min)

    • Workspace overview
    • Employee status
    • Routine status
    • Active issues

  2. Demonstration (20 min)

    • Rocky demonstrates key workflows
    • Backup_Op performs guided practice

  3. Q&A (20 min)

    • Backup_Op asks clarifying questions
    • Rocky provides context and answers

  4. Validation (20 min)

    • Backup_Op performs independent tasks
    • Rocky validates, provides feedback

During Session

Rocky demonstrates:

"I'll walk you through a typical operator workflow:

1. MORNING CHECK (5 min)
   Ctrl+K → "Run Doctor"
   Review report, note any issues
   Check Copilot for insights

2. ACTIVE ISSUES (10 min)
   Navigate to Tickets tab
   Filter by In Progress
   Review #87 (your urgent fix)
   Note #88 (paused - don't complete)
   Note #89 (optional - defer if busy)

3. BUDGET CHECK (5 min)
   Ctrl+K → "Show budget status for all workspaces"
   Review spend vs budget
   Note projections

4. ROUTINE CHECK (5 min)
   Autonomy → Routines
   Verify all 5 routines show "Active"
   Note last execution times

5. EMERGENCY CONTACT (5 min)
   Show emergency contact info
   Explain escalation procedures

Now you try...

Backup_Op performs guided practice:

[Backup_Op runs Doctor]
✅ Success — All systems healthy

[Backup_Op checks Copilot]
ℹ️  1 warning noted (routine optimization paused)
✅ No critical issues

[Backup_Op checks Tickets]
3 tickets in progress, 2 assigned to Backup_Op
✅ Confirms ownership of #87
✅ Notes #88 paused status
✅ Notes #89 can be deferred

[Backup_Op checks Budgets]
All workspaces on track
✅ No action needed

[Backup_Op asks:]
"I noticed ticket #88 is paused. What if a routine optimization becomes 
urgent while you're away? Should I consult you or wait?"

Rocky responds:

Good question. For routine optimization:

If it's critical (security issue, data loss risk), consult me.
If it's can wait, wait for my return.

The pause is intentional to prevent changes during my absence — we 
don't want to introduce instability when you're still learning.

You're doing great. Any other questions?

Session Wrap-Up

Rocky provides final guidance:

You're ready. A few final reminders:

1. TRUST YOUR TRAINING: You've demonstrated competence. Trust your 
   judgment.

2. DOCUMENT EVERYTHING: Update tickets as you work. The audit trail 
   helps me understand what happened.

3. WHEN IN DOUBT: Err on caution. I'd rather you ask than make a 
   mistake you're unsure about.

4. ENJOY THE ROLE: This is great learning. You'll be a full operator soon.

I'll check email daily at 9am and 5pm. For true emergencies, call my 
cell.

See you in 2 weeks!

During Absence

Rocky’s Monitoring (Lightweight)

Daily Routine:

  • 9am: Check email for urgent requests
  • 5pm: Check email for urgent requests
  • As needed: Review Copilot insights (email summary sent daily)

Availability:

  • Email response: < 24 hours
  • Emergency call: < 2 hours
  • Video call: Within 48 hours if requested

Backup_Op’s Daily Checklist

Each morning (9am):

1. Run Doctor: Ctrl+K → "Run Doctor"
2. Check Copilot for critical insights
3. Review #87 status (urgent fix)
4. Monitor budgets (ensure no overspend)
5. Respond to Rocky's email (if any)

Each evening (5pm):

1. Review Copilot insights from day
2. Update #87 status if changed
3. Note any issues for tomorrow
4. Send Rocky end-of-day summary

Issue Escalation Example

Scenario: Client C data pipeline issue escalates

Backup_Op attempts resolution but hits complexity:

Backup_Op in ticket #87:

I've diagnosed the pipeline issue — it's a race condition in data 
ingestion. I can attempt a fix but it requires modifying core pipeline 
logic, which feels risky without your guidance.

Rocky — guidance needed. This is beyond my comfort level for changes 
without approval.

Expected impact if not fixed: Client C data delayed by 4-8 hours.

Rocky (responds in 3 hours):

Good catch on the complexity. Don't modify core pipeline logic.

Instead:
1. Implement temporary workaround: Manual data export/import
2. Document technical issue for proper fix after I return
3. Notify Client C of delay (4-8 hours acceptable per SLA)

Your judgment was correct to escalate. This is why we don't make 
breaking changes without consultation.

Proceed with workaround. Great job!

Reintegration

Post-Handoff Debrief

When Rocky returns (May 17, 9am):

Agenda:

  1. Review period (15 min)

    • Discuss what went well, what surprised Backup_Op
    • Review any issues and resolutions

  2. System review (15 min)

    • Review handoff document vs. reality
    • Update with any new procedures discovered

  3. Feedback (15 min)

    • Rocky provides feedback on Backup_Op’s performance
    • Backup_Op provides feedback on handoff quality

  4. Transition back (15 min)

    • Rocky resumes full operator duties
    • Backup_Op returns to backup status
    • Active tickets reassigned if needed

  5. Documentation update (30 min)

    • Update handoff document with learnings
    • Archive handoff document
    • Schedule next handoff (if applicable)

Lessons Learned Documentation

Rocky updates handoff document for next time:

## Lessons Learned — May 2026 Handoff

What Went Well:
- ✅ Pre-handoff validation caught all critical items
- ✅ Backup_Op quickly operational with guided practice
- ✅ Escalation threshold appropriate — Backup_Op escalated correctly

What Could Improve:
- ⚠️ Add more context to #88 pause (why it's paused, what changed)
- ⚠️ Include more screenshots in handoff doc for visual reference
- ⚠️ Schedule mid-absence check-in (backup operator felt isolated)

Action Items for Next Handoff:
- [ ] Add mid-absence check-in call (Day 7)
- [ ] Create video walkthroughs for key procedures
- [ ] Expand emergency contact procedures (backup operator needed guidance)

Key Takeaways

1. Preparation Prevents Chaos

The pre-handoff validation (Doctor + Copilot review) ensured system health before handoff. Rocky addressed 3 action items upfront, preventing Backup_Op from inheriting problems.

2. Documentation Enables Autonomy

The comprehensive handoff document served as Backup_Op’s reference during the 2-week period. When issues arose, the document provided context and decision frameworks.

3. Escalation Thresholds Prevent Mistakes

Backup_Op’s appropriate escalation on the pipeline issue prevented a risky fix. Rocky’s guidance prioritized safety over speed, which protected client data.

4. Debrief Captures Learning

The post-handoff debrief captured lessons learned, ensuring each handoff improves on the last. This prevents repeated mistakes and builds institutional knowledge.

5. Trust Requires Training and Validation

Guided practice during the live handoff session gave Rocky confidence in Backup_Op. Trust was earned through competence, not assumed.

Scenario: Shift Handoff Playbook, Draft v1.0