What records should I prepare before holiday client handoffs?
Prepare four records before the break: every open job's current state written on its handover, every pending client decision chased with a response date, the coverage note naming who holds each account while the team is away, and the access list confirming which agents keep running and which are paused, with owners for both.
Holiday handovers fail in the gap between "we told the client" and "the client can find it." In late December the telling evaporates: the person who sent the email is offline, the client's covering contact never saw it, and an open job's state exists only in a thread nobody can search from a phone. Records close the gap because they are findable by the people who were not in the conversation.
The state-on-record rule does the heavy lifting: each open handover gets its current position written where the client already looks, what is done, what waits, whose move it is, and the date it resumes. Pending decisions get chased before the break with the link and a date, not because December chases succeed often, but because the chase itself, recorded, converts January's "we never heard" into a dated fact.
The internal half mirrors it: coverage named per account (a person, not a team), agents inventoried (what keeps running over the break, what is paused, who owns an incident if one fires), and the return date's first task pre-written: the scan of everything the records accumulated while the team was away. Teams that prepare this way come back to a queue; teams that do not come back to an archaeology dig with deadlines.
Checklist: the pre-holiday record pass
1. Open jobs: state written on each handover (done, waiting, whose move, resume date). 2. Pending decisions: chased with link and response date; chases recorded on the jobs. 3. Coverage: one named holder per account, with their contact route, filed with the index. 4. Agent inventory: running versus paused over the break, incident owner named for the running set. 5. Client note: one message per account pointing at the records, not summarising them. 6. Return task: the first-day scan of accumulated records, calendared now.
Worked example
The open job a client may land on mid-break: https://zambo.dev/handover/bd7e5325-33fd-4c5e-b029-76b781fa2f51 , five steps visible, its acceptance state readable by the client without anyone being online to explain it. The checklist's first item is what makes every open job read that clearly, with the holiday position stated on it.
Frequently asked questions
Our clients also shut down. Is this overkill?
Their shutdown is exactly why the records matter: their covering staff and their January selves are the readers. The pass takes an afternoon per account list, and its value concentrates in the two weeks when nobody who knows anything is reachable.
Should agents keep working over the break?
Some should (monitoring, scheduled jobs), most should pause, and the decision belongs in the inventory with an owner either way. The dangerous configuration is not running or paused; it is unknown, which the inventory exists to eliminate.
What is the single most-skipped item?
Item 2, chasing pending decisions with dates. Teams write the client note (item 5) and skip the chases, then spend January re-litigating what was agreed. The chase is two lines and a link; its absence costs weeks.
By Brennan Zambo, founder of Zambo.
Last verified: 2026-10-17.
Try a handover
A handover gives your client one proof link with verifiable receipts to review, then Accept or Flag.
try it: say 'use zambo to hand this over to <client>' in your ai