## TL;DR
Small teams cover vacations with buddies, not depth charts: each person has one buddy who can handle their queue, a handoff note written before they leave, and a clear list of what waits versus what gets covered. Cap simultaneous vacations at one-third of the team. The handoff note is the whole system: open tickets, VIP watchlist, and where the bodies are buried.

## The query

```text
vacation coverage plan for a small support team
```

## Use this when

- Vacations leave the queue exposed
- Teams under ten people
- Writing coverage policy
- Summer and December crunch

## Not for

- Enterprise coverage models
- PTO approval policy
- Hiring for redundancy
- Contractor coverage

## Steps

### 1. Assign every person one buddy

The buddy can handle the person's queue, knows their specialties at a basic level, and is the first call for their tickets. Buddies are mutual pairs, reviewed quarterly. No buddy, no approved vacation.

Expected output: buddy pairs documented.

### 2. Require a handoff note before departure

Open tickets with status and next step, VIP or sensitive accounts to watch, anything unusual in flight. One page. Written the day before departure, not from the airport.

Expected output: a handoff note per vacation.

### 3. Triage: cover, defer, or escalate

Cover: SLA-bound and VIP tickets. Defer: projects, non-urgent improvements, nice-to-have follow-ups. Escalate: anything the buddy cannot handle goes to the lead. Deciding this before the vacation prevents buddy burnout.

Expected output: the three lists, agreed in advance.

### 4. Cap simultaneous vacations

No more than one-third of the team out at once, and never both halves of a buddy pair. Publish a shared calendar. First-come on popular weeks, with a rotation for fairness on holidays.

Expected output: the cap rule and a shared calendar.

### 5. Protect the buddy

The buddy's own queue gets lightened during coverage, and coverage weeks count in workload planning. An unprotected buddy is just two burned-out people instead of one rested one.

Expected output: workload adjustment for coverage weeks.

## Template: the handoff note

```text
VACATION HANDOFF: [name], out [dates]. Buddy: [name].
Open tickets needing action:
- [ticket]: [status], next step: [step], due: [date]
- [ticket]: [status], next step: [step], due: [date]
Watch list: [VIP / sensitive accounts and why]
In flight: [anything unusual - launches, incidents, migrations]
Defer until I return: [list]
Escalate to [lead] if: [conditions]
Reachable for: [true emergencies only / not at all]
```

## Variant phrasings

### small team PTO coverage

Steps 1, 2, and 4. Buddies, handoff, cap.

### support coverage while on vacation

Full sequence. Step 5 is what teams forget.

### handoff template for vacation

Step 2 plus the template.

## Why it works

Small teams cannot afford redundancy, so coverage must be lightweight and explicit. The buddy pair keeps it to one relationship per person, the handoff note transfers the essential context, and the cap prevents the mathematically impossible weeks. It is a system a five-person team will actually follow.

## Edge cases

- The buddy is also the expert's backup for a specialty: cross-train basics quarterly. Coverage fails on specialties first.
- Emergency vacations: keep a skeleton handoff template for no-notice departures.
- The lead is on vacation: name an acting lead with decision authority, not just a contact.
- Overlapping buddy vacations slipped through: the lead covers or pulls in a contractor. Do not just hope.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_St5xHXXlTl0mqY6XPoEonQ